Francesco Bartoli
Francesco Bartoli
@GeoSander +1 to make the default format configurable. For example, in a couple of production instances, which are not internet-facing, having the `HTML` format doesn't make any sense at all
> Implement the [STAC](https://stacspec.org/) API specification to support search/discovery of geospatial assets. Notes for implementation based on initial discussions with @matthewhanson : > > * add front end routes (`/stac/search`)...
> > Are you considering external libraries for marshalling? Or we need to implement our own? > > Good point. I'm guessing a STAC backend could provided via one of...
@tomkralidis Should `stac/search` endpoint be optional in the configuration? I would say yes...
@pvgenuchten I would consider its own endpoint as suggested in the bullet above from @tomkralidis (cc @matthewhanson)
Configuration could be something like: ```yaml catalogs: sat-api: provider: name: STAC data: https://sat-api-dev.developmentseed.org/stac ```
Thanks @matthewhanson, so in the meantime, we could adopt `/items` but for users that might be a bit confusing to understand if it is not part yet of the OAF...
> @francbartoli is the thought that STAC catalog providers would be their own provider architecture (i.e. separate from dataproviders), or that STAC would be a quality of existing data providers?...
Well actually the first does make sense to me
@tomkralidis it had fixed duplicates on query with bbox in query parameter