You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PostgreSQL with the PostGIS extension allows spatial data to be stored in a way that allows spatially explicit querying. It would be nice to support this in two ways:
Allow importing of strictly spatial files (rasters, shapefiles, etc.). These kinds of files could only be imported into PostgreSQL.
Allow importing tabular data that has a spatially explicit component (e.g., site locations with latitudes and longitudes) as a spatially enabled table.
The later should be optional and both approaches would need to be constrained to PostgreSQL and any other formats (HDF5?) that support spatially explicit data.
The text was updated successfully, but these errors were encountered:
PostgreSQL with the PostGIS extension allows spatial data to be stored in a way that allows spatially explicit querying. It would be nice to support this in two ways:
The later should be optional and both approaches would need to be constrained to PostgreSQL and any other formats (HDF5?) that support spatially explicit data.
The text was updated successfully, but these errors were encountered: