August 2009 - mkgmap-dev - The mkgmap lists

Re: [mkgmap-dev] Memory limits for mkgmap and splitter
by drahtesel42＠web.de 06 Aug '09

06 Aug '09

> Any feedback, questions or suggestions are welcome. > > Chris Hi Chris, thanks a lot for new splitter beta release. I tried your version with a small region (Bayern in Germany). Max nodes 800.000, 12 tiles: old splitter: 310 MB RAM new splitter: 240 MB RAM old splitter: 370 sec new splitter: 470 sec old splitter: problem with 31 relations in more than 4 tiles new splitter: no problem old splitter: problem with 2 ways in more than 4 tiles new splitter: problem with 2 ways in more than 4 tiles So this is basically good news: memory requirement decreased, and the problem with large relations disappeared. The performance is not as good as the old splitter version, but this is not a problem for me. Is it possible to improve your code so that large ways can be in more than 4 tiles? Cheers, Rudi ________________________________________________________________ Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/02/

3 5

[PATCH v1] - styling for the power user
by Mark Burton 05 Aug '09

05 Aug '09

Are you a heavy duty styler? If so, read on: I notice that quite a lot of postings on the list are from people who are having problems with complex style files. This little patch won't (directly) solve those problems but it does provide a useful capability that could be part of a solution for those people who have complex styling requirements and are willing to do some coding. What the patch does is allow elements (nodes, ways) to specify their garmin type (and a few other things) explicitly using these tags: mkgmap:gtype the element's type (integer constant) mkgmap:kind one of "node", "polyline", "polygon" (only polygon is used at this time to differentiate polygons from lines). mkgmap:minres the element's minimum resolution (needed to make element visible) mkgmap:maxres the element's maximum resolution (not required) mkgmap:roadclass the element's road class (needed for roads) mkgmap:roadspeed the element's road speed (needed for roads) If the mkgmap:gtype tag is present, the element will not be passed through the normal style file process at all. So how do these tags get added to the OSM data? Well, you could just add them with an editor but that would get boring pretty quickly so what I would expect to see is some kind of external filter program that reads the OSM file and outputs a new OSM file with the appropriate tags added. That filter program could be written in any language that has some XML processing support. Current issues to be sorted out are handling of the highway shields (not currently implemented) and also this feature is not compatible with the cycleway faking code. All feedback welcome. Cheers, Mark

2 1

phone number bug?
by Clifford Nolan 05 Aug '09

05 Aug '09

Berni, I played around with that POI (Hickeys in Santry) and some other POIs. From what I have observed, the Nuvi 860T seems to be expecting a different set of fields than currently used. If I remove the city tag from a POI, then the phone number dials correctly. I had a look at the built in Garmin maps and for POIs there, whenever the city is given, it is immediately following by the county, e.g., Santry, County Dublin. So maybe that's the problem. Would there be any way to fix this for myself do you think? -- Thanks, Cliff.

1 0

Commit: r1120: adds some options to the help file
by svn commit 05 Aug '09

05 Aug '09

Version 1120 was commited by steve on 2009-08-04 22:18:05 +0100 (Tue, 04 Aug 2009) adds some options to the help file improves wording in the help file adds TODO items in the help file when I think something should be there but don't know the answer a bit of general cleanup in the help file removes option description from README, pointing people to the help file and README.examples - Greg Troxel

4 3

Commit: r1122: Remove --enable-assertions
by svn commit 05 Aug '09

05 Aug '09

Version 1122 was commited by steve on 2009-08-05 10:56:14 +0100 (Wed, 05 Aug 2009) Remove --enable-assertions pointed out by Mark.

1 0

Commit: r1121: Missing '&' in example.
by svn commit 05 Aug '09

05 Aug '09

Version 1121 was commited by steve on 2009-08-05 09:32:49 +0100 (Wed, 05 Aug 2009) Missing '&' in example. - Willem Sonke

1 0

Re: [mkgmap-dev] Problem with styles
by sonke016＠planet.nl 05 Aug '09

05 Aug '09

I now have put the style folder in the mkgmap base map, and --style=fiets doesn't seem to work. Do I have to put the style in a zip-file? Willem1 > sonke016 at planet.nl schrieb: > > I have a problem when I'm trying to use a style. If I create a style, > > for example "fiets", put it in the folder > > "mkgmap\resources\styles\fiets", and I use the command > > > > java -jar mkgmap.jar map.osm --tdbfile --style-file=styles\fiets > > then mkgmap just uses the default style. I tried almost everything: > > using --style, using quotation marks, using > > --style-file=resources\styles\fiets etc. > > I think, the path of the style must be relative to your working > directory. So when you are running in the mkgmap directory, the > parameter --style-file=resources\styles\fiets should work. > > Or you can put the fiets folder as a subfolder under your working > directory, then the parameter would be --style=fiets. > > Gruss > Torsten

6 5

codepage for greece
by dom Team OiD 04 Aug '09

04 Aug '09

Hi, I'm successfully creating full europe mapsets, but I have problems with the code pages. Whih code page can be used that fits all character for europe languages? Is there any? How do you solve this problem? eg for greece I always get "??????" in city names. Thanks, Marco

2 1

phone number bug?
by Nolan Clifford 04 Aug '09

04 Aug '09

Hi Berni, Thanks for taking time to have a look. Below are some screen shots that hopefully will illustrate what I am experiencing (hope they can be posted to the list). The first is what I see when I search for the poi to which you referred to in Santry. The Nuvi 860T was connected via bluetooth to a phone at the time and as you can see, the formatting looks off and does not have blue phone symbol to dial. The second picture shows that it likes the local area code just fine and is letting me dial it (as seen by the phone logo). The third picture is perhaps the most interesting because it shows that it can deal with the +353 prefix alright but the difference here is that there was not any other address info for the poi. So the problem seems to be that on this gps unit, as soon as addr: tags and a phone tag are simultaneously present, then the option to dial is not available and the formatting is messed up :( Is there any way I could hack the code to make it work for my unit do you think? I don't know java, but I have been looking at the code for formatting address records anyway trying to see if I can guess what's going on but to no avail. Anyway, if you have any ideas on what is going on here, I would really appreciate it. Thanks, Cliff. pictures follow directly below ....

2 1

phone number bug?
by Nolan Clifford 04 Aug '09

04 Aug '09

In case you can't view the screenshots in last message, I have posted them publicly at files.me.com/clifford.nolan/ktix62 files.me.com/clifford.nolan/tuoqq2 files.me.com/clifford.nolan/6d6cfh Rgds, Cliff

1 0