- mkgmap-dev - The mkgmap lists

Commit: r2906: Merge the mergeroads branch.
by svn commit 01 Jan '14

01 Jan '14

Version mkgmap-r2906 was committed by wanmil on Sun, 22 Dec 2013 Merge the mergeroads branch. * Roads are merged which reduces the number of road entries by 7-25% using the default style. This results in slightly better routing calculation times and slightly smaller img file sizes. * The four labels to pois/lines/roads/polygons are no longer assigned automatically. They must be assigned using the 'name' and 'addlabel' function. This also means that ref tags are no longer used as labels automatically. * Access restrictions of roads are now defined by setting special mkgmap:** access tags (e.g. mkgmap:car, mkgmap:foot, mkgmap:bicycle etc.). * mkgmap:carpool does no longer automatically set all access restrictions. In the trunk mkgmap:carpool=yes/1/true lead to set all access restrictions to "no" except emergency, bus and carpool. * The road speed is no longer automatically calculated using the maxspeed tag. New style functions maxspeedkmh() and maxspeedmph() allow style developers to perform the same by setting the mkgmap:road-speed-class tag. * Styles can now have a <finalize> block. This block is executed for each element if an element style definition matches. The finalize block must contain actions only.

5 10

[Patch v2] link-pois-to-ways and restrictions
by Gerd Petermann 31 Dec '13

31 Dec '13

Hi all, this is version 2 of the patch, based on r2922. Compiled binary is here: http://files.mkgmap.org.uk/download/164/mkgmap.jar Changes compared to v1: - remove sysout messages and an error message that was meant for debugging only - correction: The way was not split when the poi was the 2nd point and the distance was > 25 meters to the 1st point. Changes to trunk: See http://gis.19327.n5.nabble.com/patch-v1-link-pois-to-ways-and-restrictions-… Reg. this post from Chris66: http://gis.19327.n5.nabble.com/patch-v1-link-pois-to-ways-and-restrictions-… I don't see such regression. If no alternative route is available, MapSource and Basecamp both ignore route restrictions. In fact, both MapSource and BaseCamp seem to ignore normal access restrictions (saved with the road) when you select "Shorter distance", both don't ignore them in route restrictions, so this really improves routing. Gerd

1 0

link-pois-to-ways POI tags
by WanMil 31 Dec '13

31 Dec '13

Hi, at the moment all POIs tagged with "highway", "barrier" and/or "access" are used for the --link-pois-to-ways option. I think the "access" tag should be removed because it does not define a POI. Sometime ago I had a way containing a node tagged with access=private and amenity=parking. With --link-pois-to-ways enabled the road was blocked. I propose to use POIs tagged with "highway" and/or "barrier" only. Ok? WanMil

2 4

Commit: r2922: Remove some unused parts from the HighwayHooks and improve its logging
by svn commit 31 Dec '13

31 Dec '13

Version mkgmap-r2922 was committed by wanmil on Tue, 31 Dec 2013 Remove some unused parts from the HighwayHooks and improve its logging

1 0

Commit: r2921: Add/fix some documentation parts that were commited to the mergeroads branch instead of trunk by mistake
by svn commit 31 Dec '13

31 Dec '13

Version mkgmap-r2921 was committed by wanmil on Tue, 31 Dec 2013 Add/fix some documentation parts that were commited to the mergeroads branch instead of trunk by mistake

1 0

style manual
by Ataro A 31 Dec '13

31 Dec '13

In the Table 4.3. List of all substitution filters , the row with name height and argument m=>ft have a mistake in the example. Actually is written as ${ele|m=>ft}, and must became ${ele|height:m=>ft}. Amedeo

2 1

FW: SEVERE (MapSplitter) Errors - "Area too small to split at..."
by Gerd Petermann 31 Dec '13

31 Dec '13

From: gpetermann_muenchen(a)hotmail.com To: geep999(a)yahoo.co.uk Subject: RE: [mkgmap-dev] SEVERE (MapSplitter) Errors - "Area too small to split at..." Date: Tue, 31 Dec 2013 09:09:23 +0100 Hi Peter, thanks for analysing this. The img format has many restrictions, so mkgmap has to make sure that it doesn't produce invalid files. The data in the img file is distributed to so called sub divisions, and mkgmap splits these sub divisions into smaller peaces as long as one doesn't fullfill all restrictions. Some of the restrictions are simple: no more than 255 points, no more than 255 lines, others are complex, e.g. the number of bytes for one sub divison in RGN file must not exceed 0xfff8, and that value is estimated in the split process. It stops splitting when the sub division gets very small (but not the smallest possible), and when that happens, the message "Area too small to split at ..." is printed, but processing continues. Only when you also see the "Can't set city point index for ... (too many indexed points in division)" message, something really was too much. This message is printed when you have 255 or more indexed points in one sub division. All further points are not indexed, so the map should still be ok. So, in short: You can forget the hint regarding max-nodes for splitter, it doesn't solve your problem. If you compile mkgmap from source, you may try to change this line in MapSplitter.java: public static final int MIN_DIMENSION = 10; // just a reasonable value If you change it to e.g. MIN_DIMENSION = 1; mkgmap will produce smaller sub divisions. The value must be > 0, and I see no problem to change that value for all users if it helps you. Gerd Date: Mon, 30 Dec 2013 22:33:01 +0000 From: geep999(a)yahoo.co.uk To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] SEVERE (MapSplitter) Errors - "Area too small to split at..." Hi Gerd,Tried lowering max-nodes value from 150000 to 6500 which reduced but didn't stop the errors. I think that the cause is that within the 1685341 codes in the Ordnance Survey CodePoint data sometimes many different Postcodes are at the same coordinates. On analyzing can see a max of 1327 postcodes at the same co-ordinates in London, and others with hundreds of postcodes at the same coordinates in e.g. Cardiff. These postcodes in London belong to PO Boxes and in Cardiff to massive UK Government office complexes like the Benefits Agency departments. And I found several hundred Postcodes without meaningful coordinates in the list too, which were "parked" in the middle of the Atlantic (being OSGB36 0,0). But if I'd read the spec. I'd have filtered them out beforehand as they are clearly marked. Have you any idea what might be a reasonable number of points to share the same coordinates without breaking mkgmap? As coincident postcodes are usually (but not always!) within sensible alphanumeric series like NW26 9HB, NW26 9HC etc I plan to analyse duplicate code coordinates and just remove the last 1 or 2 characters from the Postcode to minimize or eliminate those with duplicate coordinates. Cheers,Peter _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

1 0

Re: [mkgmap-dev] SEVERE (MapSplitter) Errors - "Area too small to split at..."
by Peter Gardner 30 Dec '13

30 Dec '13

Hi Gerd, Tried lowering max-nodes value from 150000 to 6500 which reduced but didn't stop the errors. I think that the cause is that within the 1685341 codes in the Ordnance Survey CodePoint data sometimes many different Postcodes are at the same coordinates. On analyzing can see a max of 1327 postcodes at the same co-ordinates in London, and others with hundreds of postcodes at the same coordinates in e.g. Cardiff. These postcodes in London belong to PO Boxes and in Cardiff to massive UK Government office complexes like the Benefits Agency departments. And I found several hundred Postcodes without meaningful coordinates in the list too, which were "parked" in the middle of the Atlantic (being OSGB36 0,0). But if I'd read the spec. I'd have filtered them out beforehand as they are clearly marked. Have you any idea what might be a reasonable number of points to share the same coordinates without breaking mkgmap? As coincident postcodes are usually (but not always!) within sensible alphanumeric series like NW26 9HB, NW26 9HC etc I plan to analyse duplicate code coordinates and just remove the last 1 or 2 characters from the Postcode to minimize or eliminate those with duplicate coordinates. Cheers, Peter

1 0

mkgmap:road-speed-class vs. road_speed?
by Thorsten Kukuk 29 Dec '13

29 Dec '13

Hi, I have a question about mkgmap:road-speed-class and the road_speed/road_class elemets. The documentation only writes that "mkgmap:road-speed-class" overrides "road_speed". But if I use "road_speed", what does this mean for "mkgmap:road-speed-class"? Example: highway=motorway [0x01 road_class=4 road_speed=7 level 3] maxspeed=* & mkgmap:road-speed-class!=* & maxspeedkmh() > 60 { set mkgmap:road-speed-class = 4 } Will the second rule overwrite the first one? If yes, how can I check if road_speed was already set or not? If not, will the second rule have ever any affect? This construct is used in the default mkgmap style, setting road_class/road_speed in the action block, and later according to maxspeed in inc/roadspeed. Thanks, Thorsten -- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

2 1

FW: SEVERE (MapSplitter) Errors - "Area too small to split at..."
by Gerd Petermann 29 Dec '13

29 Dec '13

Sorry, something went wrong... From: gpetermann_muenchen(a)hotmail.com To: geep999(a)yahoo.co.uk Subject: RE: [mkgmap-dev] SEVERE (MapSplitter) Errors - "Area too small to split at..." Date: Sun, 29 Dec 2013 10:44:55 +0100 Hi Peter, maybe you can try to use a smaller max-nodes value or the precomp-sea parameter for splitter. If that doesn't help, please provide the splitter.log for further analysis. Gerd Date: Sun, 29 Dec 2013 09:12:57 +0000 From: geep999(a)yahoo.co.uk To: mkgmap-dev(a)lists.mkgmap.org.uk Subject: [mkgmap-dev] SEVERE (MapSplitter) Errors - "Area too small to split at..." Hi, I'm getting lots of errors like this with both mkgmap-r2889 and mkgmap-r2651: SEVERE (MapSplitter): /media/space5/my.osm.stuff.overflow/step4and5/63240021.osm.pbf: Area too small to split at http://www.openstreetmap.org/?mlat=51.53796&mlon=-0.10158&zoom=17 (reduce the density of points, length of lines, etc.) Can't set city point index for N1P 2NS (too many indexed points in division) Can't set city point index for N1P 2NR (too many indexed points in division) However it does run to completion and a gmapsupp.img of a sensible size is created. The file works on my Garmin eTrex Vista HCx and I can see and navigate to the postcodes. But some points, e.g. N1P 2NS, are missing, although others nearby, e.g.N1P 2NN, exist. This has happened since I have been adding postcodes into a map of Great Britain, using some ideas from this recipe: http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Postcode_Search_On_Gar… Anyway - I don't quite know what to do now. How do I set about reducing the density of points and length of lines? Is there something I should do prior to running mkgmap e.g. some splitter options I should change? Currently I'm just doing: time splitter \ /media/space5/my.osm.stuff.overflow/step3/great-britain-latest.osm.with.rightsofway.and.postcodes.pbf \ > splitter.log time java -Xmx3072M -jar /home/dad/osm.stuff/mkgmap-r2889/mkgmap.jar \ --gmapsupp \ --style-file=/home/dad/osm.stuff/mkgmap-r2651/examples/styles/mydefault/ \ --family-id=4538 \ --max-jobs=2 \ -c /media/space5/my.osm.stuff.overflow/step4and5/template.args \ /home/dad/osm.stuff/own.garmin.images/mydefault.v3.txt Cheers, Peter _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

2 2