4 ms·
Heh, their data model is 99% of the reason why I don't use OSM. It's scattered all over the place with so many tables! It's such a nice project, but damn is it
by chaps 4y ago
Heh, their data model is 99% of the reason why I don't use OSM. It's scattered all over the place with so many tables! It's such a nice project, but damn is it impossible to work with programmatically, let alone poke around it to discover what's all in there.
- matkoniecz 4y ago> so many tables ? There are various complaints about OSM data model but this is a new one to me. In OSM basically everything is mixed together and there is no real separation into layers. What you mean by "many tables"?
- peace4all 4y agoHe probably means what the osm2pgsql import tool creates.
- matkoniecz 4y agoOK, then it is about default osm2pgsql data model that in part is independent from OSM data model. "many tables" is definitely osm2pgsql design decision
- npteljes 4y agoWould the Overpass API (have) fit your use case?