- mkgmap-dev - The mkgmap lists

elevation/depth point in *.osm & *.mp
by David 25 Feb '09

25 Feb '09

As I was trying to compile an old map with mkgmap, I discovered that elevation spots (0x6300) were wrong. They should be converted in the same manner as contour lines. Now the question is : which tags define depth and elevation spots in OSM format (an elevation spot is not always a named peak) ? Here is the patch for both depth and elevation spots : Index: PolishMapDataSource.java =================================================================== --- PolishMapDataSource.java (revision 929) +++ PolishMapDataSource.java (working copy) @@ -261,6 +261,12 @@ Coord co = makeCoord(value); setResolution(point, name); point.setLocation(co); + /* if it is depth spot (0x6200) or elevation spot (0x6300), then fix units if required */ + if ((point.getType() == 0x6200) || + (point.getType() == 0x6300)){ + fixPointElevation(); + } + } } @@ -282,7 +288,7 @@ if ((polyline.getType() == 0x20) || (polyline.getType() == 0x21) || (polyline.getType() == 0x22)) { - fixElevation(); + fixPolylineElevation(); } setResolution(polyline, name); @@ -318,7 +324,7 @@ * The elevation needs to be in feet. So if it is given in meters then * convert it. */ - private void fixElevation() { + private void fixPolylineElevation() { if (elevUnits == 'm') { String h = polyline.getName(); try { @@ -333,6 +339,21 @@ } } + private void fixPointElevation() { + if (elevUnits == 'm') { + String h = point.getName(); + try { + // Convert to feet. + int n = Integer.parseInt(h); + n *= METERS_TO_FEET; + point.setName(String.valueOf(n)); + + } catch (NumberFormatException e) { + // ok it wasn't a number, leave it alone + } + } + } + /** * Called for each command in a POLYGON section. There will be a Data * line consisting of a number of co-ordinates that must be separated out

1 0

YATTLE (Yet another tile-too-large exception)
by Wolfgang v. Hansen 25 Feb '09

25 Feb '09

I got this one while trying to compile a slightly too large tile with r929. Should be caught and replaced by an appropriate message. Exception in thread "main" java.lang.IllegalArgumentException at java.nio.ByteBuffer.allocate(ByteBuffer.java:311) at uk.me.parabola.imgfmt.sys.Directory.sync(Directory.java:170) at uk.me.parabola.imgfmt.sys.ImgFS.sync(ImgFS.java:218) at uk.me.parabola.imgfmt.sys.ImgFS.close(ImgFS.java:228) at uk.me.parabola.imgfmt.app.map.Map.close(Map.java:252) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:92) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:53) at uk.me.parabola.mkgmap.main.Main.processFilename(Main.java:150) at uk.me.parabola.mkgmap.CommandArgs$Filename.processArg(CommandArgs.jav a:329) at uk.me.parabola.mkgmap.CommandArgs.readArgs(CommandArgs.java:119) at uk.me.parabola.mkgmap.main.Main.main(Main.java:91) -Wolfgang

1 0

Limits for a .img
by Wolfgang v. Hansen 25 Feb '09

25 Feb '09

Talking about memory requirements, what determines the amount of information that can be contained in a single tile? From some experiments with tile sizes I found that for routable maps the number of ways is a better estimate that the number of nodes. But I guess it will actually be a combination of both; does anyone has a formula for that? -Wolfgang

1 0

Out of heap space: Too many tags?
by Wolfgang v. Hansen 25 Feb '09

25 Feb '09

I just tried to compile a relatively small tile and got an out of memory error from Java! Normally when the tiles get too large, there are error messages from mkgmap. So I investigated a little bit and found out that the tile in question contained a huge number of <tag>s. The number of tags is ten times the number of nodes in the file. Is it possible that all these tags filled up my memory? Here's a list of the most frequently occuring tags: k='kms:parish_name' k='kms:parish_no' k='kms:city_name' k='kms:county_name' k='kms:county_no' k='kms:house_no' k='kms:last_updated' k='kms:municipality_name' k='kms:municipality_no' k='kms:street_name' k='kms:street_no' k='kms:zip_name' k='kms:zip_no' k='addr:housenumber' k='addr:street' k='addr:city' k='addr:postcode' k='source' And here's the Exception: Exception in thread "main" java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Arrays.java:3209) at java.lang.String.<init>(String.java:216) at com.sun.org.apache.xerces.internal.xni.XMLString.toString(XMLString.j ava:185) at com.sun.org.apache.xerces.internal.util.XMLAttributesImpl.getValue(XM LAttributesImpl.java:557) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$Attribut esProxy.getValue(AbstractSAXParser.java:2323) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5XmlHandler.startInNode(Osm5X mlHandler.java:178) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5XmlHandler.startElement(Osm5 XmlHandler.java:136) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startEle ment(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser. emptyElement(AbstractXMLDocumentParser.java:179) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp l.scanStartElement(XMLDocumentFragmentScannerImpl.java:1339) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp l$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2747) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(X MLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp l.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X ML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X ML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser. java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Ab stractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.p arse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5MapDataSource.load(Osm5MapDa taSource.java:78) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:134) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:51) at uk.me.parabola.mkgmap.main.Main.processFilename(Main.java:150) at uk.me.parabola.mkgmap.CommandArgs$Filename.processArg(CommandArgs.jav a:329) at uk.me.parabola.mkgmap.CommandArgs.readArgs(CommandArgs.java:119) at uk.me.parabola.mkgmap.main.Main.main(Main.java:91) -Wolfgang

2 2

Re: [PATCH] Bernhard's POI address autofilling code
by Florian Lohoff 24 Feb '09

24 Feb '09

Hi, i tried the last patch concerning --pois-addresses and YEAH it works ... I dont like the "Fix my Address" - When nobody bothered to put any "addr:" tags in it - dont try to be clever ... Not even by auto-guessing the region/city (Which i dont like) - It would be nice to be able to switch off the guessing completely... Ah - and another one - i get an entry for a Junk Food shop which has no addr: tags - It becomes "33330, 33332, 33334, 33335 Guetersloh" which is a list of postcodes in this city ... (And a correctly escaped ü) And without any knowledge about "Umlaute" on the Garmin - "ü" becomes an "u" in a Street name ... It seems "'" becomes a "?" ... Flo -- Florian Lohoff flo(a)rfc822.org +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin

1 0

Some notes on mkgmap Nod version 923
by Jani Patanen 24 Feb '09

24 Feb '09

Comment on --help=options -----------------quote ---------- --code-page=''number'' Use the given code page for the . This is --------- end quote ----------- Something is missing here... ^ ^ -----------------quote ---------- --list-styles List the avaialble styles. -----------------end quote ---------- ^^^ Typo Current version doesn't provide icons for bus stops, just dots. There are dots for every road crossing. Haven't checked if they are there because of highway=crossing or just because two ways cross. Can those dots be disabled? They fill up the display on when looking at wider area. http://www.openstreetmap.org/?lat=60.232652&lon=24.958491&zoom=18&layers=B0… has nice round roundabout. Doesn't look round when looked on my etrex hcx. Map created with revision 913 and following route (green -> red): http://www.yournavigation.org/index.php?flat=60.264601&flon=24.875072&tlat=… Only instruction was to turn left (vanha kaarelan tie). I took the left from the off-ramp. The instruction to turn right to Vaskivuorentie was missing.

3 5

[PATCH] turn restrictions - alpha code for testing (v2)
by Mark Burton 24 Feb '09

24 Feb '09

Hi, The attached v2 patch now notices if the restriction type has not been specified and so it prints a more useful message than before. Don't bother to use this if you already have the first patch unless you want to. Cheers, Mark

2 2

[PATCH] turn restrictions - alpha code for testing
by Mark Burton 24 Feb '09

24 Feb '09

Folks, The attached patch implements the OSM turn restriction relation as described in http://wiki.openstreetmap.org/wiki/Relation:restriction Here's an example that shows multiple relations being used at a junction http://www.openstreetmap.org/?lat=50.26386&lon=10.96498&zoom=17 JOSM shows little restriction signs but I think a lot of renderers won't show anything. Only "well formed" turn restrictions are handled - i.e. the 'from' and 'to' ways must terminate at the 'via' node. Badly formed turn restrictions will yield a (hopefully) useful error message that includes the OSM id so that you can go find the relation using JOSM, etc and fix it. Multiple 'via' members or the 'via' member being a way rather than a node are not handled. Those variants are not forbidden by the above description but not encouraged either and I don't, at this time, think there's good reason to handle them - if you believe otherwise and can present a compelling case for their inclusion, I will add support for them. The "except", "day_on/off", "hour_on/off" tags are ignored. I don't know how to express those constraints in garmin-speak. The --ignore-turn-restrictions option can be used to disable the feature. Please test and report success/failure, etc. Cheers, Mark

5 15

What's d for? (possibly related to clipping issue?)
by Mark Burton 24 Feb '09

24 Feb '09

Why does the line clipper add a tiddly amount (d) in these expressions? double d = 0.00001; if (t[0] > 0) ends[0] = new Coord((int) (y0 + t[0] * dy + d), (int) (x0 + t[0] * dx + d)); if (t[1] < 1) ends[1] = new Coord((int)(y0 + t[1] * dy + d), (int) (x0 + t[1] * dx + d)); On a similar note, why have the non-zero DELTA here? public static int toMapUnit(double l) { double DELTA = 0.000001; // TODO check if we really mean this if (l > 0) return (int) ((l + DELTA) * (1 << 24)/360); else return (int) ((l - DELTA) * (1 << 24)/360); }

3 7

[PATCH] maps tag landuse=farmyard to 0x4e
by Peter & Suzie 23 Feb '09

23 Feb '09

Find attached a patch which maps tag landuse=farmyard to 0x4e (Orchard/Plantation)

2 3