[mkgmap-dev] problems at map intersections?From Valentijn Sessink valentyn at blub.net on Sat Jul 18 13:21:56 BST 2009
Steve Ratcliffe schreef: > 0010: 52.470703,3.339844 53.701172,5.668945 > 0008: 52.163086,3.339844 52.470703,5.009766 > So top matches bottom, but not the same as the bounds. > This could explain mapsource, but as it is not used > on the device can't explain the problem in the GPS. In fact, I think it's two related, but different, problems: 1) the overview map is out of sync with the actual bounds. Please see my e-mail about a splitting area that will have these synchronised (*); it's a sort of rounding issue, as far as I understand. 2) the fact that, around a map split, some things do not work as they work on the rest of the map. An overlapping map helps here - and you wizards will probably know if it's possible to have a map overlap and still have the routing nodes in place. [...] > So the conclusion is that the definition areas in the overview map > are wrong. This would explain problems in mapsource, but not on the > device. Yes, that's what I think, too. [...] Best regards, Valentijn (*) Use splitter with: 63240008: 2428928,153600 to 2444288,231424 63240010: 2444288,153600 to 2500608,262144 Please note that 2444288 is the only number I changed, the other corners aren't lined up, but since we only use 2 maps here, 2444288 is the only number that is at a map intersection. -- Durgerdamstraat 29, 1507 JL Zaandam; telefoon 075-7074579
- Previous message: [mkgmap-dev] problems at map intersections?
- Next message: [mkgmap-dev] problems at map intersections?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list