On Sun, Feb 15, 2009 at 11:23 AM, Mark Burton <markb@ordern.com> wrote:
Here's a version that removes any nodes introduced by the clipper if they are too close to an existing node on the same way.
I'm not sure if this is the right approach so comments are welcome.
I tried this patch out (with the latest trunk), however my initial tests did not work. Please let me know what information you would like for a diagnosis. Here is the procedure I used: 1. Downloaded germany.osm from geofabrik.de and used the splitter from SVN with the following options: java -Xmx1024m -jar ..\splitter-svn.jar --max-nodes=800000 germany.osm 2. Called the patched mkgmap as such: java -Xmx1536M -jar ..\mkgmap-svn\mkgmap.jar --route --tdbfile --tdb-v4 --product-id=1 --family-id=523 --series-name=osm-de-rt-20090216 --country-name=Germany --country-abbr=DE --latin1 --code-page=1252 --road-name-pois --style-file=..\styles\blarg-route 63*.osm.gz (I forgot the roundabout-frig option) mkgmap then gave a lot of messages similar to the following: Way K 7006's last point at 52.91016/12.02696 is a boundary node Way K 7005's last point at 52.91016/11.92830 is a boundary node Way K 7005's first point at 52.91016/11.88691 is a boundary node Way K 7005's last point at 52.91016/11.88111 is a boundary node This was tested on a Windows Vista machine (sorry, that's what I had available). Am I perhaps missing an option or similar? I believe that splitter.jar correctly creates boundary boxes, so that should not be a factor. To test the inter-tile routing I used Mapsource (this has generally been a reliable indicator of routing success), and first created a simple route on an Autobahn within a tile. This worked correctly. I then added to the route another point on the same Autobahn, not far away, but across a tile boundary. Mapsource took longer to calculate the route, but then added a straight line between the last two points, instead of routing along the Autobahn. I hope this helps you in some way. Cheers.