May 2013 - mkgmap-dev - The mkgmap lists

ways are deleted when not routable
by Minko 14 May '13

14 May '13

I have found another issue. Mkgmap (latest versions) is deleting parts of roads that are not routable at zoomlevels below 24. See screenshot at http://mijndev.openstreetmap.nl/~ligfietser/test/N301.jpg This is one of the parts that are removed at resolution 22 and below: http://www.openstreetmap.org/browse/way/6971876 I have tested it with two line types: highway=trunk [0x02 resolution 18] road is removed highway=trunk [0x02 road_class=4 road_speed=5 resolution 18] road is rendered It doesn't matter if I use a non routable line type for 0x02, or convert it into motorway. Any ideas what makes this road disappear? BTW I need to make motorways, trunk roads and all other non cyclable roads not routable, because access=no / bicycle=no is not working anymore in the latest devices and Basecamp. But I do want to see them rendered at the map and sometimes I see those holes. I have uploaded the map tile here: http://mijndev.openstreetmap.nl/~ligfietser/test/10010069.o5m

6 25

overlaid lines and reversed oneways
by Gerd Petermann 14 May '13

14 May '13

Hi, see also http://gis.19327.n5.nabble.com/merge-lines-and-routing-tp5758913p5759595.ht… I wonder how this feature (overlaid line shows oneway direction) works with ways that are tagged oneway=-1 or oneway=reverse like this? http://www.openstreetmap.org/browse/way/6971216 or with the recent example from Minko http://www.openstreetmap.org/browse/way/6971876 The current implementation in r2606 works like this: 1) If the tag is found after style evaluation, the points of a road are reversed, but the points of the overlaying line(s) are not. 2) The merge-lines function connects lines without checking the direction. I want to correct the merge-lines method so that it doesn't connect oneway lines with opposite directions, so I have to make sure that all copies of a way have the same order of points. Will this change cause arrows showing into the wrong directions in existing styles? Gerd

1 0

Commit: r2606: set preserved flag for the point that connects two lines in the merge-lines method. This prevents some non-routable lines from disappearing at lower resolutions.
by svn commit 13 May '13

13 May '13

Version 2606 was committed by gerd on Mon, 13 May 2013 set preserved flag for the point that connects two lines in the merge-lines method. This prevents some non-routable lines from disappearing at lower resolutions.

1 0

Commit: r2599: overlayed_lines_v2.patch:
by svn commit 11 May '13

11 May '13

Version 2599 was committed by gerd on Sat, 11 May 2013 overlayed_lines_v2.patch: - make sure that lines overlaying roads have the same points after short-arc-removal. - make sure that lines overlaying roads are removed when the "mkgmap:set_unconnected_type" feature changed the road to a line or removed the road - adapted unit tests

1 0

Free map data of major Rivers, Mountains, Lakes - not from OSM - suitable for overviewmap/worldmap creation
by Felix Hartmann 10 May '13

10 May '13

I know such things exist - but not really where. OSM data is too detailed and impossible to extract that data without getting unimportant data. My plan would be to create a 20-50MB big worldmap - non routable - that people could use on their GPS device instead of the Garmin worldmap / preinstalled routable Worldmaps. Together with the overview maps for Desktop use, that would be perfect addition (create a worldwide map resolution 12-17). We could use OSM for that, but then one would need to limit to big cities (population works well for filtering), capitals, sea/land, motorways. Other OSM data is not really that suitable. It would be cool to have some more data like major mountains, major rivers, maybe major railways, (something else?).? Filtering the important ones from OSM won't really work (also rivers should be lines, not polygons to keep data amount small). Any ideas on that?

2 4

overview2 branch -- sea not rendered at resolution 12
by Felix Hartmann 10 May '13

10 May '13

Well, I first thought it would be a Mapsource/Basecamp bug, but actually mkgmap overview2 is not rendering the sea tiles down to resolution 12. The lowest resolution working is resolution 14... -- at 13 some sea is rendered, at 12 no sea at all is rendered. I think unlike in my earlier reply to Henning - that this is some internal bug (maybe related to that before 13 was the resolution of the overview map) Else I really think that the branch can be merged. It is really working well now... - and I played around a lot with it. Only other thing is maybe to have an option to delete / not delete the ovm*.img files after creation. Resolution 12 is great for continent maps like Europe (not fully needed - 14 could do), or Asia (13 is a must, 12 would be much better). Great stuff!

5 17

Commit: r2580: - correct check-styles: overlays are not used for points and polygons
by svn commit 10 May '13

10 May '13

Version 2580 was committed by gerd on Sat, 27 Apr 2013 - correct check-styles: overlays are not used for points and polygons - separate code for check-styles and list-styles option, check only a single style if --style was used.

4 4

Support place polygons in preprocessed bounds
by WanMil 10 May '13

10 May '13

Hi, I want to support place boundaries in the preprocessed bounds which was requested sometime ago. After having a look at the source code I guess that we can support 4 types of place categories. @Gerd: The BoundaryQuadTree.mkgmapTagsArray can have up to 16 entries because the index is stored as short. Correct? Which place tags are required most? place=city place=town place=village place=hamlet ...??? Please let me know about you most favourite place tags. Have fun! WanMil

2 1

Commit: r2596: Drop legacy format for preprocessed bounds
by svn commit 10 May '13

10 May '13

Version 2596 was committed by wanmil on Fri, 10 May 2013 Drop legacy format for preprocessed bounds This format is no longer created by the boundary preprocessor since April 2012. So we don't need to support it any more.

1 0

Commit: r2595: update doc reg. check-styles
by svn commit 10 May '13

10 May '13

Version 2595 was committed by gerd on Fri, 10 May 2013 update doc reg. check-styles

1 0