COG storage/translation and/or STAC API as a service

developmentseed / eoAPI

[Active Development] Earth Observation API (Metadata, Raster and Vector services)

https://eoapi.dev

MIT License

196 stars 21 forks source link

COG storage/translation and/or STAC API as a service #5

Open vincentsarago opened 3 years ago

vincentsarago commented 3 years ago

description: a user could upload a COG (or a file to convert to COG) or a STAC Item pointing to some data (available over https)

zacharyDez commented 1 year ago

Would be interesting to tie into discussion about #65 . It's not the same, but it happens at related times for end-users.

emileten commented 1 year ago

a user could upload a STAC item pointing to some data

How different is this from https://github.com/developmentseed/eoAPI/issues/65 @zacharyDez ?

To me the only difference is the COG translation part.

zacharyDez commented 1 year ago

@emileten #65 is specifically about STAC metadata. This ticket is more about adding some minimal data pipeline options for end-users. We talked about tackling metadata ingestion separately from creative cloud native formats that can be referenced (data pipelines).

Let me know if we should clarify that distinction or other ideas.