December 2008 - mkgmap-dev - The mkgmap lists

Commit: r811: First steps in writing restrictions.
by svn commit 12 Dec '08

12 Dec '08

Version 811 was commited by robert on 2008-12-12 16:44:57 +0000 (Fri, 12 Dec 2008) First steps in writing restrictions.

1 0

my map testing
by Alexander Atanasov 12 Dec '08

12 Dec '08

Hi, All! I've tried to parse the problem map from the wiki http://www.osmaustralia.org/garminroute/VIC_route.img.zip w/ libgarmin's gartest. And here are the results: garmin_subdiv.c:370:1|Error have 1 points but datalen is 1, bpx=2, bpy=2 si.sign_info_bits=4 garmin_subdiv.c:371:1|dp=05 extra_bit=1 bs_info=00 garmin_subdiv.c:376:1|05 This comes quite often - looks like the extra_bit is not accounted correctly. 4+2+2 = 8 but with extra bit it's 9. There are some garmin_subdiv.c:200:15|Point 1 have zero deltas eb=1 which means that deltas from the bitstream are 0 only the extrabit is set. garmin_net.c:469:1|SF:63242702 SD:2022 l=0 ot=3 idx=83 gt=0x06(0) lng=150.880587 lat=-34.388967 d:0 sc:0 eb:1 dt:6 garmin_net.c:478:1|1 150.880587/-34.388967 (6b4af9/ffe78bae) garmin_net.c:486:1|1 150.880930/-34.387057 (6b4b09/ffe78c07) e=0 garmin_net.c:486:1|2 150.880952/-34.386992 (6b4b0a/ffe78c0a) e=0 garmin_net.c:486:1|3 150.881402/-34.385684 (6b4b1f/ffe78c47) e=1 garmin_net.c:486:1|4 150.881531/-34.384761 (6b4b25/ffe78c72) e=0 garmin_net.c:486:1|5 150.882239/-34.381135 (6b4b46/ffe78d1b) e=1 garmin_net.c:486:1|6 150.882518/-34.380705 (6b4b53/ffe78d2f) e=1 garmin_net.c:502:1|segments:0 i:83 sd:2022 garmin_net.c:508:1|NOD info at 616790 garmin_net.c:517:1|NOD1 at 3120649 bmlen=5 fb=1 garmin_net.c:522:1|NET: BITMAP: 1f Here the bmlen should be 4. I'll look for more later. -- have fun, alex

2 9

Commit: r810: Set last extra bit if the last point is an internal node.
by svn commit 12 Dec '08

12 Dec '08

Version 810 was commited by robert on 2008-12-12 15:37:00 +0000 (Fri, 12 Dec 2008) Set last extra bit if the last point is an internal node.

1 0

Commit: r809: Only write extra bit at level 0 (patch from Alex Atansov).
by svn commit 12 Dec '08

12 Dec '08

Version 809 was commited by robert on 2008-12-11 21:01:47 +0000 (Thu, 11 Dec 2008) Only write extra bit at level 0 (patch from Alex Atansov).

2 1

Commit: r808: Allow for empty boundary flag in Nod lines.
by svn commit 11 Dec '08

11 Dec '08

Version 808 was commited by robert on 2008-12-11 10:07:19 +0000 (Thu, 11 Dec 2008) Allow for empty boundary flag in Nod lines.

1 0

routing between tiles
by Robert Vollmert 11 Dec '08

11 Dec '08

Hi, I've done a small test with two tiles and a couple of boundary nodes (NOD 3). This by manual editing of .mp-files, so there may well have been errors on that side. Results: * Only one of the two tiles displays. * Routing across tile boundaries works to some extent. It routes through the undisplayed tile, so the NET/NOD stuff is probably ok. It seems like maybe a boundary node had better not be a junction: Routing seems to work better across those boundary nodes that were inserted into the middle of a road, and some routes that were suboptimal could be explained by not taking a junction boundary node. Anyway, it looks like NOD 3 is all that's needed for routing from tile to tile -- no extra index in the gmapsupp.img or anything required. Regarding the display problem: I cut the map up from a very small neighbourhood map which has some problems itself. In particular, it doesn't show street name popups. Larger maps seem to behave better, so my hope is that the display problem would go away on larger tiles. Steve, do you intend for mkgmap to handle the cutting up eventually? Otherwise, my suggestion would be to leave this to external programs and have these put a tag (say mkgmap:boundary=yes) on the boundary nodes. Cheers Robert

1 0

Size Limits
by Andrew Ayre 11 Dec '08

11 Dec '08

I have an OSM file which is 836Mb in size. When I try to convert it to an IMG file I get: "There is not enough room in a single garmin map for all the input data The .osm file should be split into smaller pieces first." I understand how to solve this problem (osmosis, osmcut, etc.) but I'm wondering what the size limit is and whether it is imposed by the IMG file format or mkgmap. Does anyone know? thanks, Andy -- Andy PGP Key ID: 0xDC1B5864

3 5

Commit: r806: Off by one error is determining if a point is a node or not.
by svn commit 10 Dec '08

10 Dec '08

Version 806 was commited by steve on 2008-12-10 19:39:21 +0000 (Wed, 10 Dec 2008) Off by one error is determining if a point is a node or not. Set internal nodes determination temporarily set to n>2.

3 4

Commit: r807: Re-work my patch to fit in with Roberts intention on how it should work.
by svn commit 10 Dec '08

10 Dec '08

Version 807 was commited by steve on 2008-12-10 21:36:12 +0000 (Wed, 10 Dec 2008) Re-work my patch to fit in with Roberts intention on how it should work.

1 0

Commit: r805: Back out nonsense from Coord.java.
by svn commit 10 Dec '08

10 Dec '08

Version 805 was commited by steve on 2008-12-10 18:40:19 +0000 (Wed, 10 Dec 2008) Back out nonsense from Coord.java. Fixed non-compiling test.

1 0