Question about warning
I'm getting the warning below, but there's no actual way overlapping way 36823507. I know way 4611... is created by mp processing but, why is it overlapping real way?, why doesn't it happen with other multipolygons? 2010/05/02 08:49:24 ADVERTENCIA (RouteNode): 63240001.osm.gz: Similar arcs ((Plaza de Hernán Cortés, http://www.openstreetmap.org/browse/way/4611686018427389076) and (Plaza de Hernán Cortés, http://www.openstreetmap.org/browse/way/36823507)) from http://www.openstreetmap.org/?mlat=39.62629&mlon=-5.41607&zoom=17
0> In article <4BDDC250.9080801@jemila.jazztel.es>, 0> Carlos Dávila <URL:mailto:cdavilam@jemila.jazztel.es> ("Carlos") wrote: Carlos> I'm getting the warning below, but there's no actual way Carlos> overlapping way 36823507. I know way 4611... is created by Carlos> mp processing but, why is it overlapping real way?, why Carlos> doesn't it happen with other multipolygons? I've found that I got roundabout errors when people created multipolygons with junction=roundabout - that tag was transferred to the synthetic ways of the multipolygon, which then overlapped with the real roundabout. I generally fixed that by deleting the multipolygon - a roundabout is a joined line, not an area. Looking at the data, this is not what's happening. Rather, I suspect the opposite: when building the synthetic polygon, all the tags are being gathered from the 'outer' ways and added to the area. Anyone who understands multipolygons better than me care to elaborate?
On Mon, May 03, 2010 at 12:25:06PM +0100, Toby Speight wrote:
I've found that I got roundabout errors when people created multipolygons with junction=roundabout - that tag was transferred to the synthetic ways of the multipolygon, which then overlapped with the real roundabout. I generally fixed that by deleting the multipolygon - a roundabout is a joined line, not an area.
What if there is forest inside a large maxspeed=100 roundabout and a lake inside the forest? :-) In my opinion, the right solution would be never to share a line for highways and areas. The shared lines are a nuisance when you add footways, cycleways, bus stops and the like. On a somewhat related note, I noticed that some have started tagging overlapping lines for landuse multipolygons: one tagless line for the role=inner and another line (with tags) for the inner area. That is kind logical, but overlapping lines can be confusing when editing the map. Marko
On Mon, May 03, 2010 at 12:25:06PM +0100, Toby Speight wrote:
I've found that I got roundabout errors when people created multipolygons with junction=roundabout - that tag was transferred to the synthetic ways of the multipolygon, which then overlapped with the real roundabout. I generally fixed that by deleting the multipolygon - a roundabout is a joined line, not an area.
What if there is forest inside a large maxspeed=100 roundabout and a lake inside the forest? :-) In my opinion, the right solution would be never to share a line for highways and areas. The shared lines are a nuisance when you add footways, cycleways, bus stops and the like.
On a somewhat related note, I noticed that some have started tagging overlapping lines for landuse multipolygons: one tagless line for the role=inner and another line (with tags) for the inner area. That is kind logical, but overlapping lines can be confusing when editing the map.
Marko
Here's the algorithm of mkgmap how to handle the tags in multipolygons. Basic rule: All polygons are duplicated by the mp algorithm. 1. Check if the mp is tagged with one of [boundary, natural, landuse, land_area, building, waterway]. 1.1 Yes 1.1.1 Copy the mp tags to the new artificial polygons. 1.1.2 Remove all tags from the original ways identical to the mp tags. 1.2 No (mp has no useful tags - tags must be retrieved from the members) 1.2.1 Build the true intersection of all outer way/polygon tags. 1.2.2 Tag all new artifical polygons with this intersection 1.2.3 Remove all tags from the original ways identical to the true intersection Some explanations: 1.1 means that the tags are taken from the multipolygon if this is at least tagged with one polygon tag. This list is non complete! This might be fixed in future. 1.1.2 is necessary because lots of multipolygons are tagged twice - first the multipolygon and second all ways. If the identical (which means tag AND value must match) are not removed here the map will contain each polygon twice. 1.2.1 True intersection means: only the tag/value combinations that are used on all ways are copied to the resulting artificial polygons. 1.2.3 Similar to 1.1.2 these tag/value combinations must be removed from the original ways/polygons. From my point of view sharing lines between multipolygons and lines should work if the tags for the mp are set in the multipolygon. WanMil
participants (4)
-
Carlos Dávila -
Marko Mäkelä -
Toby Speight -
WanMil