In Defense of OpenStreetMap's Data Model

Re:In Defense of OpenStreetMap's Data Model by chaps on Monday June 06, 2022 @09:27AM (#31640162)

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.

[ Parent | on HN ]

Re:In Defense of OpenStreetMap's Data Model by matkoniecz on Monday June 06, 2022 @09:35AM (#31640247)

> 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"?

[ Parent | on HN ]

Re:In Defense of OpenStreetMap's Data Model by peace4all on Monday June 06, 2022 @12:37PM (#31642661)

He probably means what the osm2pgsql import tool creates.

[ Parent | on HN ]

Re:In Defense of OpenStreetMap's Data Model by matkoniecz on Monday June 06, 2022 @12:45PM (#31642755)

OK, then it is about default osm2pgsql data model that in part is independent from OSM data model.

"many tables" is definitely osm2pgsql design decision

[ Parent | on HN ]

Re:In Defense of OpenStreetMap's Data Model by npteljes on Tuesday June 07, 2022 @04:23AM (#31651288)

Would the Overpass API (have) fit your use case?

[ Parent | on HN ]