PostgreSQL has a module named hstore that implement the use of key/value pairs (it's something like the OpenStreetMap model, but in a single table).
What are the Pros and Cons of hstore regarding GIS compatibilities, data adding and retrieving?
[GIS] What are the Pros and Cons of hstore data type in postgis
databaseopen-source-gispostgispostgresql
Related Question
- [GIS] Mixing geometry types in one PostGIS table
- PostGIS vs Files – Choosing Between Database and Files for Solo Developer
- PostGIS – Converting Geometry_Dump Data Type to Geometry Type
- [GIS] PostGIS spacial data type to represent geo-located polygons
- [GIS] GeoServer create layer from PostGIS (data type point)
- [GIS] Most optimal way to create a (spatial) database for big amounts of data
Best Answer
Pros:
It's a high performance and flexible key/value that can be indexed and queried.
I have a complex schemaless web GIS that uses an HStore column for storing the features properties.
Cons:
Most WMS/WFS tools like Mapserver, Geoserver and similars can't understand and work with HStore columns, so you end up creating hard coded SQL Views (In Geoserver at least). You can still use it for working WMS/WFS but since you have to hardcode the keys you lose the schemaless capabilities.