- mkgmap-dev - The mkgmap lists

Interesting partial success when inter-tile routing
by Mark Burton 17 Feb '09

17 Feb '09

I have managed to route across a tile boundary but the route that was taken was not optimal, it took a much longer route than necessary. Further investigation showed that the "obvious" road to take did not join across the boundary of the tiles but the road that was used must have joined across the boundary. I was routing from west to east and I could route right up to the boundary OK but if I wanted to be on the eastern side of the boundary, the routing was done via other roads and so it reached the destination coming from the east. So, is it just a matter of making the coordinates match better? If so, how do we do that? Rounding? Anyone have any ideas? Cheers, Mark

1 1

--level for mp? (mkgmap-r865)
by Xia Zhang 17 Feb '09

17 Feb '09

Hi, Just want to check if --level work for mp file? I used option --levels='0:24,1:22,2:20,3:18' or --levels=0:24,1:22,2:20,3:18 without successful. Thanks Allan

2 1

[PATCH] Print error message if no reading bounding box
by Johann Gail 17 Feb '09

17 Feb '09

Ok, I finally found the reason for my bounding box / clipping problems. It has somethign to do with the regional settings. See the excerpt from a splitter generated osm file: <?xml version='1.0' encoding='UTF-8'?> <osm version='0.5' generator='splitter'> <bounds minlat='47,241211' minlon='8,964844' maxlat='49,042969' maxlon='11,425781'/> <node id='127289' lat='48.2177779' lon='11.3281777'> <tag k='highway' v='mini_roundabout'/> </node> <node id='127290' lat='48.2164303' lon='11.3245295'/> <node id='127291' lat='48.2161293' lon='11.323863'/> <node id='127292' lat='48.2154694' lon='11.3228149'/> Watch the decimal separator! In the bounding it is a comma, in the rest it os a dot. This is the reason for the bounding box not working. To detect this error print a error message in mkgmap: Index: src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java =================================================================== --- src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java (Revision 901) +++ src/uk/me/parabola/mkgmap/reader/osm/xml/Osm5XmlHandler.java (Arbeitskopie) @@ -324,6 +324,7 @@ Double.parseDouble(xmlattr.getValue("maxlon"))); } catch (NumberFormatException e) { // just ignore it + e.printStackTrace(); } } @@ -335,6 +336,7 @@ log.debug("Map bbox: " + bbox); } catch (NumberFormatException e) { // just ignore it + e.printStackTrace(); } } To resolve this error you have to modify splitter SubArea.java. I don't think this is the optimal solution, but it should work. (Not tested yet) I don't know if it is possible to set the NumberFormat global for the application. Index: src/uk/me/parabola/splitter/SubArea.java =================================================================== --- src/uk/me/parabola/splitter/SubArea.java (Revision 21) +++ src/uk/me/parabola/splitter/SubArea.java (Arbeitskopie) @@ -25,6 +25,7 @@ import java.util.Formatter; import java.util.Iterator; import java.util.List; +import java.util.Locale; import java.util.Map; import java.util.zip.GZIPOutputStream; @@ -105,7 +106,7 @@ writer.append("<?xml version='1.0' encoding='UTF-8'?>\n"); writer.append("<osm version='0.5' generator='splitter'>\n"); - Formatter fmt = new Formatter(writer); + Formatter fmt = new Formatter(writer, Locale.US); fmt.format("<bounds minlat='%f' minlon='%f' maxlat='%f' maxlon='%f'/>\n", Utils.toDegrees(bounds.getMinLat()), Utils.toDegrees(bounds.getMinLong()),

1 0

Commit: r904: Add options to set overview description and product version.
by svn commit 17 Feb '09

17 Feb '09

Version 904 was commited by steve on 2009-02-17 21:48:52 +0000 (Tue, 17 Feb 2009) Add options to set overview description and product version. - David Also added the beginning of a functional test for the TDB file.

1 0

Small contribution
by David 17 Feb '09

17 Feb '09

Hello, As I am new here, I introduce myself. I am the author of a Garmin map made with the well known cgpsmapper. I discovered OpenStreetMap few months earlier and I started to work with mkgmap. My goal is to produce my map with mkgmap. I am not yet ready because of these "problems" : - mkgmap cannot compile one of my big polygons even if I slice it with mapedit. - mkgmap produces bigger files than cgpsmapper. - derspite data come from OSM, routing does not work with my maps in Mapsource (it is not a real problem, I cannot also do that with free cgpsmapper). - mkgmap produces a different draw of the map when compiled with net and route options : roads name appear and cities name are not displayed in Mapsource. For mkgmap routing revision 856 and later : PolishMapDataSource.java (line 405): I found a minor bug in polish format reader : the max resolution is wrong when X != 0 in 'DataX' Here is the code that works for me work : private void setResolution(MapElement elem, String name) { if (endLevel > 0){ elem.setMinResolution(extractResolution(endLevel)); //EMERALDISLAND elem.setMaxResolution(extractResolution(name)); } else { int res = extractResolution(name); elem.setMinResolution(res); elem.setMaxResolution(res); } } I also noticed with an old Mapsource version (6.11.x) that strings defined with map.addInfo() and map.addCopyright() in MapBuilder.java appear in a different order (menu help/about/product info). It might be a bug from Mapsource... When you select a map in Mapsource, the column zone is fielded with "overview map". I activated the option --overview-name and also --product-info. Changes are done in these 2 files : TdbBuilder.java and TdbFile.java TdbBuilder.java : public class TdbBuilder implements Combiner { private static final Logger log = Logger.getLogger(TdbBuilder.class); private OverviewMap overviewSource; private TdbFile tdb; private int parent = 63240000; private String overviewMapname; //EMERALDISLAND private String overviewName; private int tdbVersion; /** * Initialise by saving all the information we require from the command line * args. * * @param args The command line arguments as they are at the end of the list. * In otherwords if the same argument appears more than once, then it will * have the value that was set last. */ public void init(CommandArgs args) { overviewMapname = args.get("overview-mapname", "63240000"); try { parent = Integer.parseInt(overviewMapname); } catch (NumberFormatException e) { log.debug("overview map name not an integer", overviewMapname); } //EMERALDISLAND overviewName = args.get("overview-name", "Overview map"); int familyId = args.get("family-id", 0); int productId = args.get("product-id", 1); String seriesName = args.get("series-name", "OSM map"); String familyName = args.get("family-name", "OSM map"); //EMERALDISLAND short productVersion = (short)args.get("product-version", 100); if (args.exists("tdb-v4")) { tdbVersion = TdbFile.TDB_V407; } else { tdbVersion = TdbFile.TDB_V3; } tdb = new TdbFile(tdbVersion); //EMERALDISLAND tdb.setProductInfo(familyId, productId, productVersion, seriesName, familyName, overviewName); } In private void addToTdb(FileInfo finfo) : // add a space between mapdesc and first ( String desc = mapdesc + ' (' + mapname + ')'; TdbFile.java : Add this private class data : private String overviewName; public void setProductInfo(int familyId, int productId, short productVersion, String seriesName, String familyName, String _overviewName) { headerBlock = new HeaderBlock(tdbVersion); headerBlock.setFamilyId((short) familyId); headerBlock.setProductId((short) productId); headerBlock.setProductVersion(productVersion); headerBlock.setSeriesName(seriesName); headerBlock.setFamilyName(familyName); //EMERALDISLAND overviewName = _overviewName; } Finally, I noticed that Version.VERSION returns 'svn' in mapBuilder.java As I was looking for why my contour lines and summits with altitude in meters in my file (polish format .mp) are displayed in meters divided by 3.2808399 (a feet to meters conversion) - is there a setting to solve this ? - I found the function distance() where the earth is supposed to be a sphere which is a pretty good approximation. After a fast search, I found this interesting link for distance computation : WGS84 distance : http://www.movable-type.co.uk/scripts/latlong-vincenty.html spherical distance : http://www.movable-type.co.uk/scripts/latlong.html In the case I want to contribute to the code (to correct bugs or activate functions for example), how can I do this ? Thank you for your great work. PS : there is also somewhere a string "OMS map" instead of "OSM map", I don't remember which file.

3 2

Commit: r903: Deal with EndLevel correctly when not Data0.
by svn commit 17 Feb '09

17 Feb '09

Version 903 was commited by steve on 2009-02-17 20:44:15 +0000 (Tue, 17 Feb 2009) Deal with EndLevel correctly when not Data0. - David

1 0

Commit: r902: Change 'this is a bug in mkgmap' to the
by svn commit 17 Feb '09

17 Feb '09

Version 902 was commited by steve on 2009-02-17 19:36:23 +0000 (Tue, 17 Feb 2009) Change 'this is a bug in mkgmap' to the message that says that you need to split the input file.

1 0

Thoughts on OSM routing
by Toby Speight 17 Feb '09

17 Feb '09

I've had a play with routing over the weekend - it's generally great, though I'm looking forward to routing across map boundaries! I've occasionally seen the roundabout-exit counting problem - though more commonly, data-source problems with entries/exits not marked one-way when they should be. Other than that (and the discussion suggests that's now fixed), it seems to be working really well - thanks, team!

6 14

OSM routing merged to trunk
by Steve Ratcliffe 17 Feb '09

17 Feb '09

Hi, The routing support for .osm files is now merged to the trunk. Many thanks to Mark for his work on this and of course to Robert for the underlying routing implementation and his continued help. ..Steve

3 2

Clipping not working correctly?
by Johann Gail 17 Feb '09

17 Feb '09

I'm using splitter to split up a region in 4 tiles. The result has bounding boxes which dont overlap. But if I transfer the resulting img to my etrex, then there the bounding boxes overlap by approx. 0.08 degrees, which is the plus and minus direction of the default overlapping from the splitter. See attached screenshot. So I assume that the clipping of mkgmap doesn't work correctly. I can try with the trunk or with the nod branch, there is no difference. Has anyone else seen the same problem, or am I doing something wrong? My target would be to get the inter-tile routing patch working, which isn't the case at the moment.

2 2