Hi! To improve usability of map i use custom style for mkgmap. In this patch 2 objects what always use in any my custom styles. Maybe residental area and narrow_gauge railway needed not only for me and add it to default style? wbr Maks Vasilev
Hi Maks, I added the railway=narrow_gauge and landuse=residential, but I did not understand the following:
@@ -124,7 +125,7 @@ boundary=administrative & admin_level<3 [0x1e resolution 16] boundary=administrative & admin_level<5 [0x1d resolution 18] boundary=administrative & admin_level<7 [0x1c resolution 20] -boundary=administrative & admin_level<9 [0x1c resolution 21] -boundary=administrative [0x1c resolution 22] +boundary=administrative & admin_level<9 & landuse!=residential [0x1c resolution 21] +boundary=administrative & landuse!=residential [0x1c resolution 22] boundary=national [0x1e resolution 17] boundary=political [0x1c resolution 17]
What are these needed for? I haven't tested it, but I got the impression that since the style branch was merged to trunk, mkgmap can translate the same line into both a polygon and a line. Or do you need "continue" for that? Marko
В сообщении от Среда 05 мая 2010 22:05:33 автор Marko Mäkelä написал: Hi Marko, Sorry, i have a typing error in "landuse=residential". Code 0x02 not shown in garmin. Need change 0x02 to 0x10.
Hi Maks,
I added the railway=narrow_gauge and landuse=residential , but I did not
understand the following:
@@ -124,7 +125,7 @@
boundary=administrative & admin_level<3 [0x1e resolution 16] boundary=administrative & admin_level<5 [0x1d resolution 18] boundary=administrative & admin_level<7 [0x1c resolution 20]
-boundary=administrative & admin_level<9 [0x1c resolution 21] -boundary=administrative [0x1c resolution 22] +boundary=administrative & admin_level<9 & landuse!=residential [0x1c resolution 21] +boundary=administrative & landuse!=residential [0x1c resolution 22]
boundary=national [0x1e resolution 17] boundary=political [0x1c resolution 17]
What are these needed for? I haven't tested it, but I got the impression that since the style branch was merged to trunk, mkgmap can translate the same line into both a polygon and a line. Or do you need "continue" for that?
I found in OSM more object that have boundary=administrative & admin_level<9 ( see http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative ) and landuse=residential tag. It's a village, hamlet, suburbs.
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Wed, May 05, 2010 at 10:32:48PM +0400, Maks Vasilev wrote:
What are these needed for? I haven't tested it, but I got the impression that since the style branch was merged to trunk, mkgmap can translate the same line into both a polygon and a line. Or do you need "continue" for that?
I found in OSM more object that have boundary=administrative & admin_level<9 ( see http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative ) and landuse=residential tag. It's a village, hamlet, suburbs.
That's what I thought, but why can't you generate both a boundary line and a landuse polygon for these areas? In the past it used to be that only one of the "polygons" and "lines" files would match, but I think someone mentioned that the restriction was lifted in the style branch. I will test the landuse=residential tomorrow and correct it if needed. For what it is worth, resources/garmin_feature_list.csv documents 0x02 as "City2" and it does not document 0x10 at all. Some time ago, I did test 0x04 on my Edge 705, and it was displayed different from the default yellow. Marko
В сообщении от Среда 05 мая 2010 23:37:47 автор Marko Mäkelä написал: 0x00, 0x01 (large city area), 0x02 (small city area), 0x03 (village area) - not shown in Garmin 60 and Oregon :( 0x0f, 0x10, 0x11, 0x12, 0x13, 0x21, 0x22, 0x23, 0x24, 0x25, 0x26, 0x27 - plain area (you use 0x13 for building).
I will test the landuse=residential tomorrow and correct it if needed. For what it is worth, resources/garmin_feature_list.csv documents 0x02 as "City2" and it does not document 0x10 at all. Some time ago, I did test 0x04 on my Edge 705, and it was displayed different from the default yellow.
0x04 - Military Base, bad idea for regular residental area. What default (yellow) code you use? I don't see this by default. Maks
On Thu, May 06, 2010 at 12:24:55AM +0400, Maks Vasilev wrote:
I will test the landuse=residential tomorrow and correct it if needed. For what it is worth, resources/garmin_feature_list.csv documents 0x02 as "City2" and it does not document 0x10 at all. Some time ago, I did test 0x04 on my Edge 705, and it was displayed different from the default yellow.
0x04 - Military Base, bad idea for regular residental area.
Yes, bad idea for residential, but hopefully not too bad for amenity=prison.
What default (yellow) code you use? I don't see this by default.
I mean the default background, which is yellow in day mode and black in night mode on my Edge 705, and I suppose on most Garmin devices. You are right, the 0x02 is not visible on the Edge 705 either (at least not without a TYP file). Marko
On Thu, May 06, 2010 at 09:14:09AM +0300, Marko Mäkelä wrote:
You are right, the 0x02 is not visible on the Edge 705 either (at least not without a TYP file).
The 0x10 is tricky too, because the Edge 705 shows it in the same colour (light yellow or gray) as buildings (0x13). I omitted the landuse=residential from resolution 24 (the only resolution where buildings are displayed). I tested it by selecting the smallest map detail, so that resolution 24 would be displayed on the closest zoom levels only. At resolution 24, I only saw the buildings, and at higher resolutions, I would see the landuse. I hope that this is OK for you too. Marko
В сообщении от Четверг 06 мая 2010 11:52:06 автор Marko Mäkelä написал:
On Thu, May 06, 2010 at 09:14:09AM +0300, Marko Mäkelä wrote:
You are right, the 0x02 is not visible on the Edge 705 either (at least not without a TYP file).
The 0x10 is tricky too, because the Edge 705 shows it in the same colour (light yellow or gray) as buildings (0x13). I omitted the landuse=residential from resolution 24 (the only resolution where buildings are displayed). I tested it by selecting the smallest map detail, so that resolution 24 would be displayed on the closest zoom levels only. At resolution 24, I only saw the buildings, and at higher resolutions, I would see the landuse. I hope that this is OK for you too.
Marko
Good! Now landuse visible without TYP files but changeable with custom TYPs. Maks
Maks, On Wed, May 05, 2010 at 10:37:47PM +0300, Marko Mäkelä wrote:
On Wed, May 05, 2010 at 10:32:48PM +0400, Maks Vasilev wrote:
What are these needed for? I haven't tested it, but I got the impression that since the style branch was merged to trunk, mkgmap can translate the same line into both a polygon and a line. Or do you need "continue" for that?
I found in OSM more object that have boundary=administrative & admin_level<9 ( see http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative ) and landuse=residential tag. It's a village, hamlet, suburbs.
That's what I thought, but why can't you generate both a boundary line and a landuse polygon for these areas? In the past it used to be that only one of the "polygons" and "lines" files would match, but I think someone mentioned that the restriction was lifted in the style branch.
Can you please check this too? Marko
participants (2)
-
Maks Vasilev -
Marko Mäkelä