- mkgmap-dev - The mkgmap lists

[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

change in style parser from r-1067 to r-1087?
by Torsten Leistikow 19 Jul '09

19 Jul '09

Moin, with mkgmap version r-1067 all my style files were ok. Now version r-1087 reports some errors. For example a ';' is not accepted any more in a tag value. What has happened? Gruss Torsten

2 4

Re: [mkgmap-dev] problems at map intersections?
by Valentijn Sessink 18 Jul '09

18 Jul '09

Hi all, I tried to line up Splitter with the map boundaries; instead of having (hexadecimal showing) 63240008: 251000,25800 254800,38800, I had to use 63240008: XXXXXX,XXXXX 254c00,XXXXX). Now the tool tips would not show up in the +-250 meters around the boundary. Then I used: 63240008: 251000,25800 254c80,38800 63240010: 254b80,25800 262800,40000 ... now the tool tips show *and* the map does not disappear anymore around the boundary. But - as Mark predicted - now inter tile routing does not work anymore. Just another idea: could be possible to line up the boundary nodes, then add some surroundings to have an extra overlap, right? Like so (ascii art alert) (maps below should be joined horizontally, not vertically) map 1----------+------> 1 1 1 1 1 B 1 1 1 1 B 1 ---------------+------> <--+----map 2--- 2 2 B 2 22 B 2 <--+----------- (It you can't, for any reason, please feel free to ignore my mail - as we say here: a fool can ask more questions than 100 wise man could answer) Best regards, Valentijn -- Durgerdamstraat 29, 1507 JL Zaandam; telefoon 075-7074579

1 0

listing all available POI in the point style
by maning sambale 18 Jul '09

18 Jul '09

Hi, I tried to list all mapped POIs around my area and matched them to what code Garmin provides. Please have a look if I missed/misclassified some. There are some POIs that I can't find the proper garmin codes. Any advice? -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

1 0

More on Routing
by Paul 17 Jul '09

17 Jul '09

I've had a chance to play a little with routing today and noticed a couple of things. An example would explain this best so here goes. If routing from north of Manchester to somewhere along the M62 westbound then the route is as expected (M66 onto M62 at J18, M60). Bury to Roe Green is an example of this. Bury to Gorse Covert however starts on the M66, turns off at J3, goes through Whitefield and back on to the M60/62 at J17, travels past Roe Green and arrives at destination. Bury to CHester however starts along the M66, goes straight through junction 18 to the next junction where you go all the way round the roundabout, come back on yourself to junction 18 and then turn left onto the M60 where the route is then as expected.This odd behaviour then continues if routing to places further afield that require the same initial route. http://www.openstreetmap.org/?lat=53.5497&lon=-2.261&zoom=14&layers=B000FTF shows the junctions involved but I can't see how it can be data errors as some routes go M66, M62 westbound without problem and all 3 destinations mentioned above are on the same tile Additionally I will occasionally get the odd routes previously described when routing long distances but usually get the optimal route (this is from the exact same starting point. I realise there's a lot that's not yet fully understood in the img file so I just thought I'd report these observations in the hope that they can somehow add to the overall picture Cheers Paul P.S. The routes described are as given by my Edge 605 and not simulated through software

3 4

Commit: r1088: Separate out the map number and the map name for the TDB file.
by svn commit 17 Jul '09

17 Jul '09

Version 1088 was commited by steve on 2009-07-17 14:28:22 +0100 (Fri, 17 Jul 2009) Separate out the map number and the map name for the TDB file. You can specify a separate name and number for the overview map. - Anton Todorov

1 0

show oneway streets (and other mapping information)
by Valentijn Sessink 17 Jul '09

17 Jul '09

Hello list, I just found a fine way of using the Garmin/OSM features: riding around by bike with my garmin turned on, looking for differences between map and Real World. Now I wondered, if it is possible to get the Garmin to show more information than just roads and road names. Specifically, one-way information seems not visible. On the wish list: access information and maybe even speed information. Is there a way to get the map to show these? (Please note, that this is just for map making purposes, i.e. I realise that you would not want this information on a regular Garmin map). Best regards, Valentijn p.s. I'm using my Garmin with OSM map now for a couple of days and I'm impressed, routing information is really good. (There are some problems when routing by bike; if anyone comes up with a good scheme to check if it's the Garmin or the map that goes berzerk, I'll be glad to test it out; for now, I'll just assume the Garmin is bicycle-unfriendly, just as it is with the manufacturer-supplied map).

6 8

[patch] clean up point in polygon code
by Ben Konrath 16 Jul '09

16 Jul '09

Hi I've made a few changes and fixes to the point in polygon code. Here are the changes included in the attached patch: * Add copyright statements * Correctly assign lat and long to x and y values in MapShape.contains(List<Coord>, Coord, boolean) - This doesn't change the results since the values were used consistently but it's still nice to have it correct. * Clarify comments in MapShape.contains(List<Coord>, Coord, boolean) * Fix comment in MapMaker.makeAreaPOIs(CommandArgs, LoadableMapDataSource) * Add unit test for unclosed shape to ensure all code is exercised. Thanks, Ben

1 0

Long Distance Routing
by Paul 16 Jul '09

16 Jul '09

I don't know when this happened as I haven't tried long distance routing for a while but I noticed today that this is vastly improved. I (amongst others) have commented previously about the sometimes strange routes chosen when trying to route long distances and Mark suggested at the time that we may simply be asking too much of the devices. These routes would work but would be far from optimal i.e from Manchester to Cornwall would go through the middle of Manchester, on to the M6, off the M6 , through Birmingham, on to the M5, off the M5 through Bristol, onto the M5 again and then finally on to the destination. Today, however, when trying a similar route the given route was M60, M6, M5 with no deviations which to me is exactly the way I would travel. Additionally my 605 can now calculate routes to places further away than it previously could. As this is such an improvement and I missed it at the time I thought I'd drop a quick line to say thanks to whoever found the magic key. Cheers Paul

4 3