Review and edit services.md

[zacdezgeo]

What I changed

Takes a crack at #148. @vincentsarago can you provide some feedback on if it matches your expectations? I'm not sure if you wanted to remove the custom mentions for each service below. They still seem relevant. I'm also unsure on how much detail we want to provide; the API documentation of each service seems to be the best-detailed view, while services.md is meant as an overview.

Edit mentions of custom functionality and detail services to match README.md.

How I tested it

• Run mkdocs serve
• Visit the live site and read through content

[vincentsarago]

I'm not sure if you wanted to remove the custom mentions for each service below. They still seem relevant. I'm also unsure on how much detail we want to provide; the API documentation of each service seems to be the best-detailed view, while services.md is meant as an overview.

Yeah I think we should remove any mention to the the custom runtime and focus on the goal of each service (mention that they are build on stac-fastapi/titiler-pgstac ... ) and what user can expect from the service

Ideally we would have 4 components:

• Database (Postgres with PgSTAC) to host the STAC Catalog and Public vector datasets
• Metadata Service (stac-fastapi)
• Raster (titiler-pgstac)
• Features/Vector (tipg)