[mkgmap-dev] RoadMergerFrom Gerd Petermann gpetermann_muenchen at hotmail.com on Mon Jan 6 09:46:58 GMT 2014
Hi WanMil, two points: 1) line 517 is obsolete: mergePoints.add(end); It just blows up the size of the list and processing time. 2) You were right regarding closed ways and different results. The merge may create p-shaped loops. See way 80605369. If the northern node 381305537 is merged first: 2014/01/06 10:20:40 Fein (RoadMerger): e:\gerd\sp_out\63240030.o5m: Merge 33134762 and 80605369 with angle 23.159455845890676 and later: 2014/01/06 10:20:40 Fein (RoadMerger): e:\gerd\sp_out\63240030.o5m: Merge 33134762 and 80605327 with angle 44.86962367701949 This produced a p-shaped road (including a loop). If the node 374244500 is processed first, no merge happens because this would produce a closed loop, so the node is added to mergeCompletedPoints. The p-shaped road is split later in StyledConverter, so this is not an error, but obviously it makes no sense to merge first and split again later. Maybe you see a simple solution for this? Gerd -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140106/8f8e6007/attachment.html>
- Previous message: [mkgmap-dev] Commit: r2946: Write the node count for a road in the NET1 section.
- Next message: [mkgmap-dev] RoadMerger
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list