Replies: 2 comments 2 replies
-
Between osm2pgsql 1.2.2 and 1.3.0 the behaviour changed. Until 1.2.2 (when used with your options) the So this is definitely a regression, but I am not sure whether it makes sense to change this now. Is this an actual problem in your case? It should be possible to just change the SQL query accessing this field. |
Beta Was this translation helpful? Give feedback.
-
The change is that we require a |
Beta Was this translation helpful? Give feedback.
-
I'm trying to add a feature to Tilezen's vector-datasource, which uses an osm2pgsql style file that was created quite a while ago. In there, we have
way_area
defined here without any flags specified. Back then, using that style file would add away_area
column to the output postgres tables. Nowadays, it seems to put those in thetags
hstore column. The osm2pgsql docs seem to say that theway_area
special tag will create a column (not get added to the hstore)Matching our vector-datasource docs from back in 2016, I ran:
... but this time I'm running it with a more-modern version of osm2pgsql from homebrew:
What should I change here to move that way_area entry to a column?
Beta Was this translation helpful? Give feedback.
All reactions