-
Notifications
You must be signed in to change notification settings - Fork 3
Raster processing roadmap
Sandro Santilli edited this page Feb 4, 2016
·
2 revisions
See initial discussion on https://github.com/systemapic/wu/issues/336
- Import rasters
- raster2pgsql can do this
- Import rasters to a set (with one raster per row)
- raster2pgsql can do this (-t )
- Do clipping of rasters (clip away ocean, for example, to reduce size), aka a
clipfunction - Import clipping mask polygons which will be used to clip areas for calculations on rasters
- "Import" where ?
- Query data from raster by tile (based on Google Tile Coordinate)
- Can be done by unioning the intersection between each intersecting tile and the given google tile polygon
- Query data from raster by tile (based on Google Tile Coordinate) with simplification
- Create vector tiles from raster data
- node-mapnik should be able to do this
- Create vector tiles from a set of rasters (each raster as one layer, will become a timeseries)
- node-mapnik can do this (the multi-layer part)
- Query
avg, min, maxon rasters - Query
avg, min, maxon rasters with an arbitrary clipping mask- ST_SummaryStats(ST_Clip(...))
Clustering
Datasets
OSM Layers
Tile Server overview
API
- Portal
- PostGIS
- Linux Dependencies
- Mapnik
- Postgres-XL (obsolete)
- Tilestache (obsolete)