-
Notifications
You must be signed in to change notification settings - Fork 4
Rendering data base
Thomas Schwotzer edited this page Aug 2, 2016
·
12 revisions
Each data rendering process should avoid complex operations on a data base especially when it comes to huge data. OHDM stores a huge amount of data in well-formed data base, see OHDM-Datenmodell. That data model has no redundancy but is hardly basis of a rendering process.
For that reason, we have a rendering data base which is filled from OHDM data. That's not a very new idea, though. It's simply state of the art.
The idea is very simple. We follow OSM in some way and create a table for each imported (and supported) major frature, see OSM-Import-Rules