[mkgmap-dev] [PATCH v2] Performance improvement by removing unused elements before the style processing
From WanMil wmgcnfg at web.de on Thu Jan 5 19:15:49 GMT 2012
> On 04/01/12 20:14, WanMil wrote: >> Steve, >> >> can you do me a favour? >> I have uploaded both versions to http://files.mkgmap.org.uk/detail/46 >> (only files that differ and not the gmapsupp.img). >> >> Can you run the display tool and check if you can quickly find the >> difference? I would have to completely install the display tool and have >> to get warm with it... I think you are much quicker? ;-) > > At first sight there is no difference in the number of elements of any > kind. > > The difference is in the poi_properties section, where the patched > version is larger than the unpatched by 6 bytes. > > So I would be looking at tags. I may be able to pin it down a bit > further tomorrow. > > ..Steve Hi Steve, that already helped! I printed out the tags of all POIs and the POI: [mkgmap:city=Saarbrücken,mkgmap:postcode=66117,building=yes,mkgmap:admin_level2=DEU,shop=supermarket,mkgmap:admin_level4=Saarland,mkgmap:admin_level6=Regionalverband Saarbrücken,mkgmap:postal_code=66117,mkgmap:admin_level8=Saarbrücken,mkgmap:area2poi=true,mkgmap:region=Regionalverband Saarbrücken,mkgmap:country=DEU] with internal Garmin coords lat:2293768 long:324722 is included in the patched but not in the unpatched version. The bounding box is: minlat: 2293760 minlong: 323584 maxlat: 2297856 maxlong: 327680 I am a bit helpless why the POI appears with the patched but not with the unpatched release... WanMil
- Previous message: [mkgmap-dev] [PATCH v2] Performance improvement by removing unused elements before the style processing
- Next message: [mkgmap-dev] [PATCH v2] Performance improvement by removing unused elements before the style processing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list