search

easierdata / web3-geo-dashboard

1 stars 0 forks source link

Decide most efficient database/file format to store Landsat scene geometries #3

Closed jsolly closed 1 year ago

jsolly commented 1 year ago

Context

The map will have ~500 landsat scenes for the US. Where should these 500 rectangles come from?

What information should be included with the scenes (stored locally on the server) that will not be queried via an API?

Should it just be a flat file that gets ingested or does a database make sense?

jsolly commented 1 year ago

@marquisvictor

Getting the Landsat scenes into the Dashboard could be a useful next step. I suggest using the scene outlines from landsat_scenes_shp shown in this notebook.

We need to figure out how to get that shapefile into the map. Should it be GeoJSON, flat file, geoparquet, database, other?

jsolly commented 1 year ago

The approach that seems to make the most sense if we are going to use Mapbox GL is a Mapbox tileset.

A tileset is a collection of raster or vector data broken up into a uniform grid of square tiles at 22 preset zoom levels.

https://mapbox.com/help/define-tileset

jsolly commented 1 year ago

I think we still might need a database to help with the API fetching, but it looks like we can get most of what we need into the tileset, so I am going to close this one.