Hi Fred I have to check that.
I addmittedly enabled hstore as well as osm_timestamp, osm_changeset, osm_version and osm_uid in the osm2pgsql style file. But I never expected to get constituent nodes added to planet_osm_point as Nick asked in the initial thread. I also observed that planet_osm_polygon alternatively leaves out osm_timestamp and osm_changeset when querying for osm_id;osm_timestamp;osm_changeset;osm_version;osm_uid: E.g. 69915513;"";5332183;1;110450 85344383;"2015-07-21T19:23:41Z";;3;3068030 173060743;"";16080891;4;122489 ... Very strange! :Stefan 2015-09-28 13:25 GMT+02:00 Frederik Ramm <[email protected]>: > Hi, > > On 09/27/2015 05:24 PM, Stefan Keller wrote: >> And: I can't imagine who needs these "way supporting" coordinates >> there (since there's osm_nodes). > > Nodes which have none of the tags defined in your osm2pgsql.style will > not end up in planet_osm_point (if they do, it's a bug, or a careless > use of the hstore facility). > > Bye > Frederik > > -- > Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" > > _______________________________________________ > dev mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/dev _______________________________________________ dev mailing list [email protected] https://lists.openstreetmap.org/listinfo/dev
