Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

[water] group of lakes (within a relation) mislabeled, all with the same name #3143

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

Reporter: fredb
[Submitted to the original trac issue database at 6.17pm, Monday, 26th July 2010]

When looking in OSM for lakes of 7 laux (group of lakes in French Alps), I see all the lakes labeled with the same name ("Lac de la Motte") :
http://www.openstreetmap.org/?lat=45.2415&lon=6.0863&zoom=14&layers=B000FTF
Whereas when looking at the OSM data in JOSM, each lake is correctly labeled with its different name.

@openstreetmap-trac
Copy link
Author

Author: Ldp
[Added to the original trac issue at 7.42pm, Monday, 26th July 2010]

This is most likely caused because each multipolygon member has their own name, and the relation itself also has a name. Somewhere during the import of the data, one of the members' names is selected and applied to them all.

@openstreetmap-trac
Copy link
Author

Author: sly
[Added to the original trac issue at 4.12pm, Monday, 11th October 2010]

In case this might be usefull to track the problem, the osm2pgsql version I downloaded from the 6 April 2010 did not have this issue.

Every lake was inserted in the polygon table with it's own name, and then the multipolygon of the relation was also inserted.

The new osm2pgsql I'm using now (downloaded the 17 july 2010) does only insert one polygon with osm_id of the relation.

The name appears to be the one of the last member lake having a name in the relation.

In case someone wants to test :
331364 = id of the relation

@openstreetmap-trac
Copy link
Author

Author: math1985
[Added to the original trac issue at 2.45pm, Tuesday, 20th May 2014]

Seems to be solved now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant