[mkgmap-dev] a few points

2011-02-07 Thread Jozef Riha
hello, i've been playing with mkgmap and etrex legend a little bit and these are my findings: examples/styles/default/point: tourism=information {name '${name} - ${description} (${operator})'.. [0x2f0c resolution 20] - this is most likely not right as 2f0c is

[mkgmap-dev] 0x10 for residential in default style

2011-02-07 Thread Jeroen Muris
Hello all, At the moment, I’m merging my own custom style with the default, and I’m wondering about the use of code 0x10 for landuse=residential in the polygons file. Is 0x10 a standard Garmin code for residential areas? If not, isn’t 0x01/0x02/0x03 a better choice (0x03 is already in use for

Re: [mkgmap-dev] a few points

2011-02-07 Thread Marko Mäkelä
On Mon, Feb 07, 2011 at 07:22:11PM +0100, Jozef Riha wrote: examples/styles/default/point: tourism=information {name '${name} - ${description} (${operator})'.. [0x2f0c resolution 20] - this is most likely not right as 2f0c is auto-services|rest-area-tourist-info|Restroom (and also renders as

Re: [mkgmap-dev] 0x10 for residential in default style

2011-02-07 Thread Marko Mäkelä
On Mon, Feb 07, 2011 at 09:45:03PM +0100, Jeroen Muris wrote: At the moment, I'm merging my own custom style with the default, and I'm wondering about the use of code 0x10 for landuse=residential in the polygons file. Is 0x10 a standard Garmin code for residential areas? It is not. I just made

Re: [mkgmap-dev] 0x10 for residential in default style

2011-02-07 Thread Jeroen Muris
Thank you for the quick response. For now I'll keep using my own 0x01 for landuse=residential. If the polygons styling needs work I'm willing to help. Just let me know what I can do. Switching from landuse=residential to building=* may be a nice solution (I did not know it is possible), but

Re: [mkgmap-dev] 0x10 for residential in default style

2011-02-07 Thread Marko Mäkelä
On Mon, Feb 07, 2011 at 10:29:12PM +0100, Jeroen Muris wrote: If the polygons styling needs work I'm willing to help. Just let me know what I can do. Basically, suggest some changes, preferrably by sending patches. Switching from landuse=residential to building=* may be a nice solution (I did

[mkgmap-dev] splitter and long way-segments

2011-02-07 Thread Henning Scholland
Hi everyone I've a problem with ways with long segments (e.g. boarders or ferry-lines) and splitter. These ways gets broken, because the nodes are to far away from splitoffset. I've made a screenshot [1] for explanation. Increasing the splitter-offset wont be a good idea, because tiles will

Re: [mkgmap-dev] splitter and long way-segments

2011-02-07 Thread Minko
Henning, Did you try a higher overlap setting? Maybe --overlap=6000 ? --overlap Nodes/ways/rels that fall outside an area will still be included if they are within this many map units. Default is 2000 ___ mkgmap-dev mailing list

[mkgmap-dev] patch for polygons file

2011-02-07 Thread Jeroen Muris
Marko, I'll have a look at the polygons style file. For know I'll send the results of merging the default style with my own (polygons-1829-JM.patch, attached). I hope the comments make clear what I did. It's not much yet. J-. -Oorspronkelijk bericht- From: MarkoMäkelä Sent: