We have some prototype projects - webbased apps mainly which integrate shapefiles etc. into ohdm. I think we should deconstruct this process even more to allow integration into other (batch) processes. First, we need an extension to this converter tool that allows importing geometries from files and some metainformation into an OHDM database.
Would it be a good idea to separate OHDM DB which is filled with OSM data from imported data. I do think so. Geometries can be combined in the rendering, or whatever databases... It would at least offer more flexibility. We would even have a way from shapefile to GeoSPARQL.
We have some prototype projects - webbased apps mainly which integrate shapefiles etc. into ohdm. I think we should deconstruct this process even more to allow integration into other (batch) processes. First, we need an extension to this converter tool that allows importing geometries from files and some metainformation into an OHDM database.
Would it be a good idea to separate OHDM DB which is filled with OSM data from imported data. I do think so. Geometries can be combined in the rendering, or whatever databases... It would at least offer more flexibility. We would even have a way from shapefile to GeoSPARQL.