- mkgmap-dev - The mkgmap lists

unknown road and cycleway routing
by gbbickerton 15 Feb '13

15 Feb '13

It appears that unknown roads are not routable (many minor roads in my area are tagged as unknown roads) and that cycleways may not be routable for bicycle by default. I am going to try highway=unknown {set highway=minor} highway=cycleway {set bicycle=allowed} will this work? Barry -- View this message in context: http://gis.19327.n5.nabble.com/unknown-road-and-cycleway-routing-tp5749336.… Sent from the Mkgmap Development mailing list archive at Nabble.com.

5 13

--bounds not accepting ~ (tilde)
by Rich 15 Feb '13

15 Feb '13

looks like --bounds option does not properly parse path, starting with ~ that took me some time to figure out why it doesn't find the bounds :) -- Rich

4 8

Distribution of free maps made with mkgmap
by gbbickerton 14 Feb '13

14 Feb '13

I was wondering what Garmin's attitude towards the distribution free maps made with mkgmap was, are there any legal issues to do with reverse engineering their maps or distributing non licensed maps etc. -- View this message in context: http://gis.19327.n5.nabble.com/Distribution-of-free-maps-made-with-mkgmap-t… Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 1

Housenumbers
by WanMil 13 Feb '13

13 Feb '13

Hi Steve, it was very nice to meet you in Essen! The meeting gave me the ideas to modify the mp cut algorithm so that it does not have the small long cuts which produced the white lines in the sea. Anyhow lots of things to do there... Right now I tried to start implementing a protoype for the housenumber support with OSM data. It's very simple but it might become more intelligent... There is one thing which has to be solved. The Numbers class has two fields nodeNumber and rnodNumber. I think the nodeNumber is not required but the rnodNumber is. Can you give me a hint how I can get the rnodNumber for a given node in the MapRoad? If possible it should be accessible from the StyledConverter. I fear it's not? WanMil

1 0

Bug-Report: java.lang.UnsupportedOperationException
by Bernhard Hiller 13 Feb '13

13 Feb '13

After upating from version 2337 to 2484, I receive following error: java.lang.UnsupportedOperationException at uk.me.parabola.mkgmap.osmstyle.eval.AbstractOp.value(AbstractOp.java:110) at uk.me.parabola.mkgmap.osmstyle.eval.EqualsOp.eval(EqualsOp.java:44) at uk.me.parabola.mkgmap.osmstyle.eval.OrOp.eval(OrOp.java:33) at uk.me.parabola.mkgmap.osmstyle.eval.AndOp.eval(AndOp.java:34) at uk.me.parabola.mkgmap.osmstyle.ActionRule.resolveType(ActionRule.java:59) at uk.me.parabola.mkgmap.osmstyle.RuleSet.resolveType(RuleSet.java:68) at uk.me.parabola.mkgmap.osmstyle.StyledConverter.convertWay(StyledConverter.java:216) at uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:237) at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:75) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:144) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:201) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:198) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exiting - if you want to carry on regardless, use the --keep-going option Then mkgmap stops. Does it mean that current mkgmap does not like a statement in my style file? If so, how can I find out which one? No, I did not change anything in that stylefile during the upgrade. mkgmap 2337 still exists on my machine, and I can switch back to that version with ease, and that works without the error.

3 2

splitter r288
by GerdP 13 Feb '13

13 Feb '13

Hi, today I've committed r288 in the problem-list branch. Changes compared to r283 in trunk: - Corrected: Some type=multipolygon relations were not treated as such in the keep-complete processing (this means that splitter did not calculate the bbox of the relation to calculate the writers to find totally enclosed tiles). - Changed: type=multipolygon relations with a boundary tag are now treated like type=boundary tags - Added: Filter for the boundary tag and new parameter --boundary-tags. Purpose: Allow to filter boundary relations in the problem-list-generator. It tells splitter an include list of tag values for the boundary tag. It is used to filter type=boundary or type=multipolygon relations. If these relations do also have a boundary tag, the parameter is used as follows: --boundary-tags=use-exclude-list (the default) means that the relation is added to the problem list if the boundary tag is not one of "administrative", "postal_code", "political" --boundary-tags= (empty list) means that the relation not is added to the problem list if it has a boundary tag --boundary-tags=a,b,c means that the relation is added to the problem list if it has a boundary tag with any of the given values. I hope this description is clear enough? Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r288-tp5749227.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 2

Address info from building polygon to poi in this poly.
by Maks Vasilev 12 Feb '13

12 Feb '13

Typical situation: the building with the address and within the marked poi with the name and others but no address. How to assign the address information such points without an address inside the building with the address?

1 0

What current status of address search?
by Maks Vasilev 12 Feb '13

12 Feb '13

I use mkgmap for everyday convert map for garmin. Now i see address search work only for streets, but housenumbers not usable for search. I convert building with addr:street and addr:housenumber to poi 0x6402 and search not work, but in POI list (around of curren place) i have poi of shop with address information.

2 4

route_name(s) on different lines
by e.rossini73＠alice.it 12 Feb '13

12 Feb '13

This is my file relations: # Route type=route & (route=hiking | route=bicycle) { apply { set route='${route}'; set route_ref='$(route_ref), ${ref}' | '${ref}'; set route_name='$(route_name), ${name}' | '${name}' } } that makes a string like this: route_ref 3,4 route_name Path name 3, Path name 4 I ask you: is it possible display every route name on a different line? I mean like this: Path name 3 Path name 4 Thanks. --enrico

2 1

boundary relations in splitter
by GerdP 12 Feb '13

12 Feb '13

Hi all, the keep-complete processing in current splitter (r283) ignores all type=boundary rels, means, they are not added to the problem list. This is done to avoid adding thousends of ways to each tile because of administrative boundaries covering huge areas. (Boundary rels are treated like type=multipolygon rels, so splitter will calculate the bounding box of the rel and add the members to all tiles intersecting this bbox. The discussion in this thread http://gis.19327.n5.nabble.com/Commit-r2478-Use-outer-polygon-tags-if-the-m… shows a need for more detailed filters. I see some options to handle this: 1) a) we can add type=boundary relations if they have a boundary=xyz tag and xyz is in a hard coded include list b) we can add type=boundary relations if they DON'T have a boundary=xyz tag and xyz is in a hard coded exclude list I looked at taginfo and found quite a lot of candidates for both lists: http://taginfo.openstreetmap.org/keys/boundary?filter=relations#values 2) we can pass the include / exclude lists as parameters (eg. --incl-boundary-filter=national-park,national-forest or --excl-boundary-filter=administrative,postal_code 3) we can add (parts of) the style system to splitter to allow the same filters My opinion: option 1) is too simple, option 3) is too complex (for me) On the other hand, we may also filter type=multipolygon rels , for example taginfo shows that type=multipolygon is often used with boundary=administrative. Comments? Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/boundary-relations-in-splitter-tp5749069.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 4