October 2009 - mkgmap-dev - The mkgmap lists

Commit: r1303: Print OSM id and name of oneway roads that go nowhere.
by svn commit 22 Oct '09

22 Oct '09

Version 1303 was commited by markb on 2009-10-22 01:12:01 +0100 (Thu, 22 Oct 2009) Print OSM id and name of oneway roads that go nowhere.

1 0

Commit: r1302: Don't print null name.
by svn commit 22 Oct '09

22 Oct '09

Version 1302 was commited by markb on 2009-10-22 01:11:58 +0100 (Thu, 22 Oct 2009) Don't print null name.

1 0

Commit: r1301: Added --report-dead-ends option to warn about roads that go nowhere.
by svn commit 22 Oct '09

22 Oct '09

Version 1301 was commited by markb on 2009-10-22 01:00:34 +0100 (Thu, 22 Oct 2009) Added --report-dead-ends option to warn about roads that go nowhere. Can generate two different warning messages: "Oneway street goes nowhere" and "Confluence of oneway streets". The first is output for oneway roads that don't join another routable way this occurs quite a lot (i.e. roads into car parks, etc.) so a lot of those warnings can be ignored. The second is output when multiple oneway streets meet with nowhere else to go. This is very likely to be an error in the map data (i.e. motorway segment in the wrong direction) and worthy of investigation.

1 0

Commit: r1300: Make code conform with comment in roundabout direction checking.
by svn commit 21 Oct '09

21 Oct '09

Version 1300 was commited by markb on 2009-10-21 22:23:17 +0100 (Wed, 21 Oct 2009) Make code conform with comment in roundabout direction checking. Should have checked all segments with 3 or more points but it was actually checking those that had 4 or more points.

1 0

Warning when generating the index
by Nakor 21 Oct '09

21 Oct '09

Hello, I just though I would post this if it is useful for improving the index. Generating the index for maps of several US states I got the following warning message: WARNING: string pointer size is not 3, index will probably not work try with fewer maps until this is resolved. Despite this, the map and index work fine in MapSource, I was able to transfer them to my eTrex Vista and did not find any issue using them in the GPS so far. Thanks, N.

3 2

Turn restriction warnings too verbose and terse at the same time
by Marko Mäkelä 21 Oct '09

21 Oct '09

In the warning output of finland.osm, I see 219 warnings about turn restriction relations. Apparently, there not that many errors in the map data, because I see duplicates, like this: 2009/10/20 15:39:32 WARNING (RestrictionRelation): Turn restriction 167929 has multiple 'to' members - first 'to' member is 18628061 2009/10/20 15:39:32 WARNING (RestrictionRelation): Turn restriction 167929 has multiple 'to' members - first 'to' member is 18628061 ... 2009/10/20 15:39:32 WARNING (RestrictionRelation): Turn restriction 167929 'to' way (18628061) doesn't start or end at 'via' node (62,59660/23,66127) ... 2009/10/20 15:40:11 WARNING (RestrictionRelation): Turn restriction 167929 has multiple 'to' members - first 'to' member is 18628061 2009/10/20 15:40:11 WARNING (RestrictionRelation): Turn restriction 167929 has multiple 'to' members - first 'to' member is 18628061 ... 2009/10/20 15:40:11 WARNING (RestrictionRelation): Turn restriction 167929 'to' way (18628061) doesn't start or end at 'via' node (62,59660/23,66127) Could I get the two sets of warnings because I am running with --max-jobs=2? Would it be possible to suppress the duplicate warnings, or at least display a download URL for each violation, e.g., for the 'via' node? All in all, there do not seem to be too many errors in roundabouts and turn restrictions in Finland. I should be able to fix them myself, eventually. I did not enable the checks on flare roads yet. In many roundabouts, the flare roads are bidirectional "radial spokes" instead of triangle-shaped oneway streets. Are these converted by mkgmap automatically? If not, could they be? Best regards, Marko

2 3

Commit: r1299: Add OSM URL to turn restriction diagnostics + rework some of the messages.
by svn commit 20 Oct '09

20 Oct '09

Version 1299 was commited by markb on 2009-10-21 00:14:15 +0100 (Wed, 21 Oct 2009) Add OSM URL to turn restriction diagnostics + rework some of the messages.

1 0

Commit: r1298: Start to clean up road names, initially by
by svn commit 20 Oct '09

20 Oct '09

Version 1298 was commited by steve on 2009-10-20 23:40:58 +0100 (Tue, 20 Oct 2009) Start to clean up road names, initially by just removing any shield symbol it has when creating the global index.

1 0

Commit: r1297: Remove warning when 4 bytes are required for the string
by svn commit 20 Oct '09

20 Oct '09

Version 1297 was commited by steve on 2009-10-20 23:39:54 +0100 (Tue, 20 Oct 2009) Remove warning when 4 bytes are required for the string pointers as it does appear to work.

1 0

what OSM keys are used for creating search index?
by Anton Todorov 20 Oct '09

20 Oct '09

Hi, I am playing with the new searching feature and can not find what information to populate in OSM so the search to be most proper. in Find->Find Places->City tab there are three searching fields: City, State, Country. Here is my test case: I have point for a village with tags: <node id='273815878' lat='42.20031' lon='24.79548' user='LandShark' timestamp='2009-03-03T02:45:49Z' version='2'> <tag k='is_in' v='България'/> <tag k='name' v='Войводиново'/> <tag k='name:en' v='Voivodinovo'/> <tag k='place' v='village'/> <tag k='source' v='bgtopomaps'/> </node> The mapsource find it as: Voivodinovo, Voivodinovo, Plovdiv, Bulgaria Bgr The closest large city is Plovdiv which is the administrative centre of Plovdiv region with tags: <node id='31058184' lat='42.1419116' lon='24.7498026' user='balrog-kun' timestamp='2009-07-23T01:20:24Z' uid='20587' version='10' changeset='1910333'> <tag k='int_name' v='Plovdiv'/> <tag k='is_in' v='Plovdiv, Bulgaria, EU'/> <tag k='is_in:continent' v='Europe'/> <tag k='name' v='Пловдив'/> <tag k='name:ar' v='بلوفديف'/> <tag k='name:bg' v='Пловдив'/> <tag k='name:de' v='Plowdiw'/> <tag k='name:en' v='Plovdiv'/> <tag k='name:la' v='Philippopolis'/> <tag k='name:pl' v='Płowdiw'/> <tag k='name:ru' v='Пловдив'/> <tag k='place' v='city'/> <tag k='population' v='379000'/> <tag k='wikipedia' v='Plovdiv'/> </node> Reading the source of mkgmap I think that the 'Locator' finds Plovdiv as close city to get missing info for the find function I tried the voivodinovo point as: <node id='273815878' lat='42.20031' lon='24.79548' user='LandShark' timestamp='2009-03-03T02:45:49Z' version='2'> <tag k='is_in:country' v='България'/> <tag k='is_in:county' v='Пловдив област'/> <tag k='name' v='Войводиново'/> <tag k='name:en' v='Voivodinovo'/> <tag k='place' v='village'/> <tag k='source' v='bgtopomaps'/> </node> but in find city there is no change: Voivodinovo, Voivodinovo, Plovdiv, Bulharia Bgr. I would like to achive something at least like "Voivodinovo, Voivodinovo, Plovdiv region, Bulgaria Bgr" but do not know what data to fill in OSM file. It is clear that some data is missing but I can not figure out what it is? In short - what is the relation between the tags that define where a node belongs to? Best Regards, Anton Todorov Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0