- mkgmap-dev - The mkgmap lists

BUG with last josm version
by guilhem barbaza 09 Nov '09

09 Nov '09

Hi, I have a problem with routing on garmin nuvi 255 since I have changed my version of JOSM (2255) : The map rendering is cool and all is in the good place, but when i choose to navigate to a city, garmin route me to an other.... so then i zoom in and go to the destination point it is the good cities name who appears but not at the good place !!!! If you have a solution.... Thanks a lot

2 1

Commit: r1320: Branch for combining several maps into a gmapsupp.
by svn commit 09 Nov '09

09 Nov '09

Version 1320 was commited by steve on 2009-10-26 19:46:01 +0000 (Mon, 26 Oct 2009) BRANCH: mapset Branch for combining several maps into a gmapsupp. That is maps with different family-id (and/or product-id).

3 2

Commit: r1362: The attached patch is an attempt to improve the reliability and flexibility for displaying highway shields. It does the following:
by svn commit 08 Nov '09

08 Nov '09

Version 1362 was commited by steve on 2009-11-08 23:13:22 +0000 (Sun, 08 Nov 2009) The attached patch is an attempt to improve the reliability and flexibility for displaying highway shields. It does the following: 1. Removes the alpha balancing coding. (This coding checked that values for signs were primarily numeric, and therefore prevented refs such as "QEW" from being displayed as highway shields.) 2. Removes ALL spaces from refs, so that the complete ref will be displayed in the shield. (Previously only the first space was removed, which caused refs like "B 1 2" to be displayed as "B1" in the shield.) 3. Checks, after spaces have been removed, if the ref is too long to be displayed in a shield. If the ref is too long, the shield code will not be added; the road label will displayed normally. The maximum length of the ref is determined in the following manner: 3.1. The default of 8 characters is used. This is the previous behaviour. 3.2. If a colon character (":") followed by a number is appended to the highway symbol in the style file, that number will override the maximum length. Example: "highway-symbol:box:6" sets the maximum to 6 characters. 3.3. If an additional colon character followed by a number is appended to the highway symbol, this second number will be used as the maximum length for alpha only refs. Example: "highway-symbol:box:6:4" sets the maximum to 6 for numeric and alphanumeric refs, but 4 for alpha only refs. I use the following in my style file: '${ref|highway-symbol:box:6:4}' This sets the maximum length of alphanumeric shields to be 6 (e.g., M1234a, or 123456), and alpha only shields to be 4 (e.g., ABCD). Such a setting works well for me in the areas I am interested in. It prevents labels such as "S?\195?\188dring" from being displayed as shields, but catches most other refs which can reasonably be displayed in shields. - Clinton Gladstone (+ required changes to tests for the new behaviour and unrelated test fix for recent routing changes)

1 0

[PATCH] Improve display of highway shields
by Clinton Gladstone 08 Nov '09

08 Nov '09

The attached patch is an attempt to improve the reliability and flexibility for displaying highway shields. It does the following: 1. Removes the alpha balancing coding. (This coding checked that values for signs were primarily numeric, and therefore prevented refs such as "QEW" from being displayed as highway shields.) 2. Removes ALL spaces from refs, so that the complete ref will be displayed in the shield. (Previously only the first space was removed, which caused refs like "B 1 2" to be displayed as "B1" in the shield.) 3. Checks, after spaces have been removed, if the ref is too long to be displayed in a shield. If the ref is too long, the shield code will not be added; the road label will displayed normally. The maximum length of the ref is determined in the following manner: 3.1. The default of 8 characters is used. This is the previous behaviour. 3.2. If a colon character (":") followed by a number is appended to the highway symbol in the style file, that number will override the maximum length. Example: "highway-symbol:box:6" sets the maximum to 6 characters. 3.3. If an additional colon character followed by a number is appended to the highway symbol, this second number will be used as the maximum length for alpha only refs. Example: "highway-symbol:box:6:4" sets the maximum to 6 for numeric and alphanumeric refs, but 4 for alpha only refs. I use the following in my style file: '${ref|highway-symbol:box:6:4}' This sets the maximum length of alphanumeric shields to be 6 (e.g., M1234a, or 123456), and alpha only shields to be 4 (e.g., ABCD). Such a setting works well for me in the areas I am interested in. It prevents labels such as "Südring" from being displayed as shields, but catches most other refs which can reasonably be displayed in shields. The approach of this patch allows creative mappers to have a certain amount of control over shield display, but still preserves the default behaviour of the

2 1

Commit: r1361: Make it easier to identify assertions that fail.
by svn commit 08 Nov '09

08 Nov '09

Version 1361 was commited by markb on 2009-11-08 11:53:37 +0000 (Sun, 08 Nov 2009) Make it easier to identify assertions that fail.

1 0

Commit: r1360: Don't do flare checks on ways that have mkgmap:flare-check=no/false/0.
by svn commit 08 Nov '09

08 Nov '09

Version 1360 was commited by markb on 2009-11-08 11:53:34 +0000 (Sun, 08 Nov 2009) Don't do flare checks on ways that have mkgmap:flare-check=no/false/0. Also, mkgmap:no-dir-check=yes should now be mkgmap:dir-check=no.

1 0

Commit: r1359: Add isNotBoolTag() method that returns true if tag is defined as false/no/0.
by svn commit 08 Nov '09

08 Nov '09

Version 1359 was commited by markb on 2009-11-08 11:53:30 +0000 (Sun, 08 Nov 2009) Add isNotBoolTag() method that returns true if tag is defined as false/no/0.

1 0

Commit: r1358: Cope with arc segments that are too long and their bbox is too large.
by svn commit 08 Nov '09

08 Nov '09

Version 1358 was commited by markb on 2009-11-08 00:10:07 +0000 (Sun, 08 Nov 2009) Cope with arc segments that are too long and their bbox is too large.

1 0

Tile with very few nodes fail to compile
by Andre Hinrichs 07 Nov '09

07 Nov '09

Hi List! Since yesterday a tile of europe fails to compile and mkgmap crashes with an exception. I would have to reduce max-nodes to 32000 to get this area compiled. Problem is that I do not want to compile complete europe with that low value of max-nodes. Here is the areas.list file which contains this tile already reduced to a size where it nearly crashes: > # List of areas > # Generated Sat Nov 07 09:08:24 CET 2009 > # > 77777777: 2516992,641024 to 2582528,690176 > # : 54.008789,13.754883 to 55.415039,14.809570 And mkgmap crashes with the following exception: > java.lang.AssertionError > at uk.me.parabola.mkgmap.osmstyle.StyledConverter.addRoadWithoutLoops(StyledConverter.java:1078) > at uk.me.parabola.mkgmap.osmstyle.StyledConverter.addRoadAfterSplittingLoops(StyledConverter.java:951) > at uk.me.parabola.mkgmap.osmstyle.StyledConverter.addRoad(StyledConverter.java:879) > at uk.me.parabola.mkgmap.osmstyle.StyledConverter.convertWay(StyledConverter.java:273) > at uk.me.parabola.mkgmap.reader.osm.xml.Osm5XmlHandler.endDocument(Osm5XmlHandler.java:558) > at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endDocument(AbstractSAXParser.java:737) > at com.sun.org.apache.xerces.internal.xinclude.XIncludeHandler.endDocument(XIncludeHandler.java:1119) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:515) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.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(AbstractSAXParser.java:1205) > at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(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(Osm5MapDataSource.java:80) > at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:148) > at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) > at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:190) > at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:188) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) Number of nodes in the created tile is 50935. mkgmap version is 1355. Why are so small tiles crashing? Regards Andre

2 3

Commit: r1357: Use toBrowseURL().
by svn commit 07 Nov '09

07 Nov '09

Version 1357 was commited by markb on 2009-11-07 14:11:21 +0000 (Sat, 07 Nov 2009) Use toBrowseURL().

1 0