[mkgmap-dev] [Patch] Overflow in splitter node counters
From Thorsten Kukuk kukuk at suse.de on Tue Apr 3 11:58:49 BST 2012
Hi Gerd, On Mon, Apr 02, Gerd Petermann wrote: > > > I did not find a good explanation for the small difference in the numbers: > > > osmconvert reported 2518069911 nodes, which is > > > ~ 2.518.069.911 -(2^31 - 1) = 370.586.264 > > > - 2^31 + 370.586.264 =* -1.776.897.384* > > > but splitter r200 reported * -1.776.905.107* nodes > > > The formatting routine is not the reason. Any ideas? > > > > The SRTM data has some duplicate nodes (duplicate as of same > > lat/lon, but different ID). Does one of the tools ignore them? > > At least mkgmap warns about them. > > Else no, I have no idea. > > What is the value that the patched splitter reports for the coords occupancy? > Here is what I see for a small file: > ... > *********************************************************** > Final statistics > *********************************************************** > Needed dictionary entries: 25 of 65535 > coords occupancy > MAP occupancy: 7.544.535 > ... With the patched version: Needed dictionary entries: 414 of 65535 coords occupancy MAP occupancy: 1.014.076.753 Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
- Previous message: [mkgmap-dev] [Patch] Overflow in splitter node counters
- Next message: [mkgmap-dev] [Patch] Overflow in splitter node counters
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list