Interestingly enough if I just keep the highways then the routing issues are gone. Are there any other objects besides the highway=* ones that would generate routable data and be the cause of the issue?
On Thu, Jun 2, 2011 at 9:10 AM, Steve Ratcliffe <[email protected]>wrote: > > [This post was too big, I've reduced the size of the image and forwarded > this back to the list, ..Steve] > > > -------- Original Message -------- > Subject: Routing issue > Date: Wed, 1 Jun 2011 22:49:31 -0400 > From: Nakor Osm <[email protected]> > To: Development list for mkgmap <[email protected]> > > > > Hello, > > I have a tile from splitter that have coordinates > > 10000007: 2174976,-3282944 to 2240512,-3196928 > # : 46.669922,-70.444336 to 48.076172,-68.598633 > > I compiled it with the following options: > > java -ea -Dlog.config=logging.properties -jar mkgmap.jar --route > --description="OSM test map minimal" --mapname=99999999 10000007.osm.gz > java -ea -Dlog.config=logging.properties -ja mkgmap.jar --family-id=9999 > --series-name="OSM Test Maps minimal" --family-name="OSM Test Maps > minimal" --overview-mapname=Test_minimal --tdbfile --nsis 99999999.img > > Once loaded in Mapsource routing "jumps" (see attached screenshot) when > trying between N47 35.554 W69 44.684 and N47 31.697 W69 49.760 > > Is this a bug in mkgmap? > > Thanks, > > N. > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
