Formulate a joint strategy for eoAPI and Stacture

[j08lue]

eoAPI and Stacture are meant to be complementary in providing data access services.

What is our strategy for how they will continue to relate to each other and used together in the future?

Related tickets

• Requirements Analysis and Architectural Design - EOX #2202 #77

Acceptance criteria

• Discussed future needs and implementation pathways
• Conducted technical deep dive and experiments to establish viability

[j08lue]

Preliminary diagram of services, not complete, just as basis for discussions

[j08lue]

Just a little update to the same kind of services diagram

We will complement this with architecture diagrams

[jankovicgd]

Hey, adding my thoughts so far on how titiler requests could be mapped to OGCAPI-maps requests. Coverages is a bit of a mystery and I will let it stay such for the time being, also seeing the standard is in its draft phase and project requirements around it are iffy. We are still researching and my initial thoughts led me to the following options:

1. less likely option currently since the titiler feature is not there but writing it out as that was a first thought
   -query the stac api based on wms parameters
   -construct a dynamic mosaic json using queried information (if multiple items) and storing it temporarily with a presigned url
   -if single item
   /stac/bbox/{minx},{miny},{maxx},{maxy}/{width}x{height}.{format}
   -if multiple items hitting a similar endpoint to this one but for mosaic json as it is the closest to how maps works
   (/stac or /cog)/bbox/{minx},{miny},{maxx},{maxy}/{width}x{height}.{format}
   -forwards result

2. after learning about more features in eoeapi eg. /raster/searches also seems interesting
   -wms query comes in (probably pygeoapi leveraging already existing ogc api logic, would have to see how to reuse internal api for extension)
   -the search is registered based on query params
   -the search is hit with /searches/{search_id}/bbox/{minx},{miny},{maxx},{maxy}/{width}x{height}.{format}
   -the data is returned
   Here it seems that if the endpoint is hit often with a wide array of bboxes, It may create a lot of searches that will be realistically hit once.

[j08lue]

We can consider this spike to be complete - we discussed software roadmaps and identified ways forward, creating a good basis for concrete technical prototyping, like currently going on in

• Design software architecture for OGC API Maps #123