July 2009 - mkgmap-dev - The mkgmap lists

Commit: r1091: Added support for limiting access when a way routes through a POI.
by svn commit 20 Jul '09

20 Jul '09

Version 1091 was commited by markb on 2009-07-20 22:22:04 +0100 (Mon, 20 Jul 2009) Added support for limiting access when a way routes through a POI.

1 0

Commit: r1090: Add link-pois-to-ways option.
by svn commit 20 Jul '09

20 Jul '09

Version 1090 was commited by markb on 2009-07-20 22:22:00 +0100 (Mon, 20 Jul 2009) Add link-pois-to-ways option. When this options is enabled, if a node has tags it will be represented by a CoordPOI rather than the normal Coord. Also, ways will be flagged as having POIs by adding a mkgmap:way-has-pois tag.

1 0

Commit: r1089: New class to represent a Coord that is a tagged OSM node.
by svn commit 20 Jul '09

20 Jul '09

Version 1089 was commited by markb on 2009-07-20 22:21:56 +0100 (Mon, 20 Jul 2009) New class to represent a Coord that is a tagged OSM node. This allows us to pass the Node object on for use when processing the Way.

1 0

[PATCH v4] - beware of the bollards!
by Mark Burton 20 Jul '09

20 Jul '09

v4 forgot to make the POI a routing node - it is now - this stops routing across the POI when the start and end points are within the restricted area. ------------- v3 now adds extra points either side of the POI to reduce length of way that has restricted access. Currently points are 25m away from the POI. It would be nice if they were really close (like 5m) but if you try that, the map looks crap due to the limited coordinate resolution. So, 25m is a compromise between visual appearance and minimising the extent of the restricted zone. ------------ v2 - quick update based on instantaneous feedback from ML! Now works for any POI that sets "access=no" (could use the more general test of any of the access tags being set but let's see how this works for now). Default access rights now set in style file. Any suggestions for a better code for cycle_barrier? ------------ Fed up of being routed in your car down city streets only to find the way is blocked by a bollard? Well, if so, this is the patch for you. If a way has a bollard on a point, the segments of the way that connect to the bollard have access restrictions placed on them. By default, a bollard implies: access=no, foot=yes, bicycle=yes. Testing using mapsource shows that it generally works as expected although if the destination cannot be reached by any other route, it routes straight through the bollard rather than failing! If the destination can be reached by some other route, even if the route is really long, it will avoid the bollard. I have chosen Garmin code 0x660f (pillar) for the bollard. On my etrex it appears as a small dot in the way. As usual, all feedback is welcome. Cheers, Mark

4 9

problems at map intersections?
by Valentijn Sessink 20 Jul '09

20 Jul '09

Hello list, When trying to use a built map, I'm getting a bit odd results around the edges of tiles - at least, I think it's the edges. It's not exactly on the boundaries, but about 2.5 kilometers below the grey lines that show up in Mapsource (I assume these are the tiles). But strangely, the Splitter arealist has other numbers than Mapsource tells me. You can see tiny interconnections where the roads meet on the tiles; on the highest zoom levels, parts of the map start to dissapear. For example: wget 'http://download.geofabrik.de/osm/europe/netherlands.osm.bz2' bzcat netherlands.osm.bz2 > netherlands.osm Then use Splitter: java -Xmx1700m -jar ./splitter.jar --max-nodes=500000 --overlap=8000 netherlands.osm It produced the following list of areas (you may want to test with this list instead of the automated --max-nodes) 63240001: 2363392,153600 to 2412544,239616 63240002: 2412544,153600 to 2428928,212992 63240003: 2412544,212992 to 2428928,239616 63240004: 2363392,239616 to 2402304,268288 63240005: 2363392,268288 to 2402304,337920 63240006: 2402304,239616 to 2428928,266240 63240007: 2402304,266240 to 2428928,337920 63240008: 2428928,153600 to 2443264,231424 63240009: 2428928,231424 to 2443264,262144 63240010: 2443264,153600 to 2500608,262144 63240011: 2428928,262144 to 2459648,296960 63240012: 2428928,296960 to 2459648,337920 63240013: 2459648,262144 to 2500608,294912 63240014: 2459648,294912 to 2500608,337920 (Splitter says, for example, that it splits 2428928,153600 to 2443264,231424, which would be 52.119141,3.295898 to 52.426758,4.965820, but Mapsource shows a grey line around 52.07145) Anyway: when you load the resulting map into Mapsource and go to 52.07149/5.02083 (or 52.07149/anywhere ), you'll notice small interconnection traces on the more important roads (N230 and A2 in this example), but from zoom level 50 meters and higher, parts of the map will disappear. And if you experiment a bit, you'll notice that the map will vanish at even lower zoom levels. For example - see attached lower part of Mapsource. java -enableassertions -Xmx1700m -jar mkgmap-r1087/mkgmap.jar --country-name=Nederland --country-abbr=NL --latin1 --remove-short-arcs --lower-case --preserve-element-order --location-autofill-1 --tdbfile -c template.args (I removed the routing information that I usually include, just to make sure it's not a routing issue) (And as you can see, I learned from my mistakes and used -enableassertions for map making). The 52.07149 is an example, the same thing happens around 52.25606 (another 2.5 kilometers below a tile). You can see the problem best at locations that are busy with roads and stuff; also, having a main road (a thick one) nearby helps. I was wondering if it has anything to do with areas that are cut of at the edge, but that's pure guessing. My Gærmïn Nüvï also has problems with these sites, refusing to route and/or not showing the map at the lowest zoom levels. If I can do anything to test, please say so. Best regards, Valentijn

8 25

[PATCH v3] - fix clipping when node falls on tile boundary
by Mark Burton 20 Jul '09

20 Jul '09

OK, so it's proving to be a little harder to fix than I thought but I have high hopes for this version. BTW - Valentijn, this version could help routing through "the tunnel". Please see if it changes anything.

3 5

Re: [mkgmap-dev] FW: --TDB option for ways only map doesn't show up in 6324000.img
by Steve Ratcliffe 20 Jul '09

20 Jul '09

> My problem is that if laurels8.mp contains a full set of contours, > hydrography and land cover my 6324000.img file shows a corresponding > 07250732 quadrangle, but if laurels8.mp consists only of ways, there is > no quadrangle for 07250732. Therefore, while I can see the ways in > MapSource, I can’t use MapSource to select the ways only maps to combine > with my other maps. I think that this is expected for transparent maps. As far as I understand it you cannot select anything that does not have a polygon behind it so your land use polygons, so I'm guessing your land use polygons are allowing you to select the ways in the first example. Transparent maps don't have a background polygon so you can't select anything from them normally. So I think that is just how it works and there is nothing we can do about that. If anyone knows any different though, please shout up! ..Steve

1 0

The mailing list
by Steve Ratcliffe 19 Jul '09

19 Jul '09

Hi Just a note that the mailing list and website are being moved onto a new server. There may be a problem or inconsistency if things are slow to update. ..Steve

1 0

[PATCH v2] - fix clipping when node falls on tile boundary
by Mark Burton 19 Jul '09

19 Jul '09

Hi Maning, Here's another attempt at a fix. Please try. Cheers, Mark

1 0

cannot route when end node is at the tile edge
by maning sambale 19 Jul '09

19 Jul '09

The road intersection "Daang Hari" is exactly at the edge of my tile (made with splitter) routing does not work. But when I created another mapset without the splitter, routing works. http://www.openstreetmap.org/?lat=14.413996&lon=121.01714&zoom=18&layers=B0… -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

4 10