SRID support
nmandery opened this issue · comments
Currently all consumers and producers are assumed to use the same SRID for the geometries - this is certainly not always the case. To fully support SRS there are a few tasks which need to be done:
Extend the data representation used for streaming
There should be a srid
key to specify the spatial reference system of a feature. Eventually a fallback to a proj4 string would make sense.
Support SRID in serialization tools
Tools like vertorlayer_producer
should support reading the SRID of shapefiles etc...
Support SRID in consumers
postgis_consumer
In postgis_consumer
the functionality would be needed to analyze the database schema of the target table and to determinate the SRID of the geometry column. Incoming features could then be transformed to the SRID of the table.
This has already been implemented in https://github.com/nmandery/batyr/blob/7427680ecda3f22df33741126c3012c0efd0853c/src/server/worker.cpp#L323 and could be ported to python.