Adaptions in style (needed to make good use of) for overview2 branch
So - I've played around a bit - just rendering Europe for right now - actually I would suggest the following (needs some adaptations in the lines/poi file though): levels = 0:24, 1:22, 2:20, 3:18 overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12.... This should give quite sensible map detail for European countries, or Europe as a continent - without getting near to crash the overview map, because it 's getting too big. I'm unsure whether we should add a completly empty 9:11 or 9:10 so that when zooming out superfar, the map get's blank instead of a pixel mashup... We definitely do need resolutions 14 and 12 in the overview map. They help tremendously when opening big maps in orientation - without the dreaded setting of details to max setting. As the speed of drawing is now very fast compared to before, resolution 14 and 12 with data do make lot of sense! Level 8 should only contain capitals and country borders. Here are some adpation proposals for *points file* - add this before any other POI - due to continue other pois will still be included: (place=capitol | place=capital) & population > 999999 & name=* {set cityxx=yes} [0x0100 resolution 12 continue with_actions ] place=city & population > 799999 & cityxx!=yes & name=* {set cityxx=yes} [0x0200 resolution 14 continue with_actions ] place=city & population > 399999 & cityxx!=yes & name=* {set cityxx=yes} [0x0300 resolution 15 continue with_actions ] place=city & population > 299999 & cityxx!=yes & name=* {set cityxx=yes} [0x0400 resolution 16 continue with_actions ] place=city & population > 199999 & cityxx!=yes & name=* {set cityxx=yes} [0x0500 resolution 16 continue with_actions ] place=city & population > 99999 & cityxx!=yes & name=* {set cityxx=yes} [0x0600 resolution 17 continue with_actions ] place=city & population > 49999 & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 17 continue with_actions ] place=city & population > 9999 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 18 continue with_actions ] place=city & population > 0 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 18 continue with_actions ] place=city & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 18 continue with_actions ] place=town & population > 69999 & cityxx!=yes & name=* {set cityxx=yes} [0x0600 resolution 17 continue with_actions ] place=town & population > 19999 & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 18 continue with_actions ] place=town & population > 9999 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 19 continue with_actions ] place=town & population > 4999 & cityxx!=yes & name=* {set cityxx=yes} [0x0900 resolution 19 continue with_actions ] place=town & population > 999 & cityxx!=yes & name=* {set cityxx=yes} [0x0a00 resolution 19 continue with_actions ] place=town & population > 0 & cityxx!=yes & name=* {set cityxx=yes} [0x0b00 resolution 20 continue with_actions ] place=town & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 19 continue with_actions ] *Relations file:* route=road & network=e-road { apply { add ref='${ref'; add int_ref='${int_ref'}; set network=e-road } *Lines file* # (the main routing part needs to be adapted to only start with level 21) - this here can then start the lines file: highway=motorway & network=e-road [0x01 resolution 14-14 continue] highway=motorway [0x01 resolution 15-20 continue] highway=trunk & network=e-road [0x02 resolution 15-17 continue] highway=trunk [0x02 resolution 18-20 continue] highway=primary & network=e-road [0x03 resolution 16-18 continue] highway=primary [0x03 resolution 19-20 continue] highway=secondary & network=e-road [0x04 resolution 17-18 continue] highway=secondary [0x04 resolution 19-20 continue] # Maybe add main rivers - but how to know what are the biggest rivers worldwide? There doesn't exist a relation/network thingy so far AFAIK. # country borders are already at 12. Dunno if they maybe should stop at 14 already. *Polygons file:* # I would propose to only show sea/land up to resolution 17 by default. Maybe forest/wood and other very important big objects also in 17?
Oh and maybe make: reduce-point-density=3 the default. Without reduce-point-density the overview map would get much bigger. I also use reduce-point-density-polygon=6 With the rules as above, the germany overview map, is 318KB and really helps in orientation, as well as being just about right amount of detail at "normal detail setting" in Mapsource/Basecamp. Well there could maybe be some forest/lakes/rivers still added - but I assume that will only work for country maps - for continent maps this would overflow the overview map. On 7 May 2013 13:44, Felix Hartmann <extremecarver@gmail.com> wrote:
So - I've played around a bit - just rendering Europe for right now - actually I would suggest the following (needs some adaptations in the lines/poi file though): levels = 0:24, 1:22, 2:20, 3:18
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12.... This should give quite sensible map detail for European countries, or Europe as a continent - without getting near to crash the overview map, because it 's getting too big. I'm unsure whether we should add a completly empty 9:11 or 9:10 so that when zooming out superfar, the map get's blank instead of a pixel mashup...
We definitely do need resolutions 14 and 12 in the overview map. They help tremendously when opening big maps in orientation - without the dreaded setting of details to max setting. As the speed of drawing is now very fast compared to before, resolution 14 and 12 with data do make lot of sense!
Level 8 should only contain capitals and country borders.
Here are some adpation proposals for *points file* - add this before any other POI - due to continue other pois will still be included:
(place=capitol | place=capital) & population > 999999 & name=* {set cityxx=yes} [0x0100 resolution 12 continue with_actions ] place=city & population > 799999 & cityxx!=yes & name=* {set cityxx=yes} [0x0200 resolution 14 continue with_actions ] place=city & population > 399999 & cityxx!=yes & name=* {set cityxx=yes} [0x0300 resolution 15 continue with_actions ] place=city & population > 299999 & cityxx!=yes & name=* {set cityxx=yes} [0x0400 resolution 16 continue with_actions ] place=city & population > 199999 & cityxx!=yes & name=* {set cityxx=yes} [0x0500 resolution 16 continue with_actions ] place=city & population > 99999 & cityxx!=yes & name=* {set cityxx=yes} [0x0600 resolution 17 continue with_actions ] place=city & population > 49999 & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 17 continue with_actions ] place=city & population > 9999 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 18 continue with_actions ]
place=city & population > 0 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 18 continue with_actions ] place=city & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 18 continue with_actions ]
place=town & population > 69999 & cityxx!=yes & name=* {set cityxx=yes} [0x0600 resolution 17 continue with_actions ] place=town & population > 19999 & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 18 continue with_actions ] place=town & population > 9999 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 19 continue with_actions ] place=town & population > 4999 & cityxx!=yes & name=* {set cityxx=yes} [0x0900 resolution 19 continue with_actions ] place=town & population > 999 & cityxx!=yes & name=* {set cityxx=yes} [0x0a00 resolution 19 continue with_actions ] place=town & population > 0 & cityxx!=yes & name=* {set cityxx=yes} [0x0b00 resolution 20 continue with_actions ] place=town & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 19 continue with_actions ]
*Relations file:* route=road & network=e-road { apply { add ref='${ref'; add int_ref='${int_ref'}; set network=e-road }
*Lines file* # (the main routing part needs to be adapted to only start with level 21) - this here can then start the lines file: highway=motorway & network=e-road [0x01 resolution 14-14 continue] highway=motorway [0x01 resolution 15-20 continue] highway=trunk & network=e-road [0x02 resolution 15-17 continue] highway=trunk [0x02 resolution 18-20 continue]
highway=primary & network=e-road [0x03 resolution 16-18 continue] highway=primary [0x03 resolution 19-20 continue]
highway=secondary & network=e-road [0x04 resolution 17-18 continue] highway=secondary [0x04 resolution 19-20 continue] # Maybe add main rivers - but how to know what are the biggest rivers worldwide? There doesn't exist a relation/network thingy so far AFAIK. # country borders are already at 12. Dunno if they maybe should stop at 14 already.
*Polygons file:* # I would propose to only show sea/land up to resolution 17 by default. Maybe forest/wood and other very important big objects also in 17?
Hi, does this also needs a resolution=12 in splitter or are these different things? Henning Am 07.05.2013 19:44, schrieb Felix Hartmann:
levels = 0:24, 1:22, 2:20, 3:18
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12....
Hi Henning, no, the values are not related to each other. Gerd Henning Scholland wrote
Hi, does this also needs a resolution=12 in splitter or are these different things?
Henning
Am 07.05.2013 19:44, schrieb Felix Hartmann:
levels = 0:24, 1:22, 2:20, 3:18
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12....
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Adaptions-in-style-needed-to-make-good-use-of... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, overview-map looks nearly great. I've got only some problems with ugly-looking sea. See attached pictures out of qLandkarte. Options I've used: https://github.com/aighes/RadReiseKarte/blob/master/resources/style_rrk_ov/o... But it is very, very great to have this overview-map. Fantastic speedup! Henning Am 07.05.2013 22:20, schrieb GerdP:
Hi Henning, no, the values are not related to each other.
Gerd
Henning Scholland wrote
Hi, does this also needs a resolution=12 in splitter or are these different things?
Henning
Am 07.05.2013 19:44, schrieb Felix Hartmann:
levels = 0:24, 1:22, 2:20, 3:18
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12....
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Adaptions-in-style-needed-to-make-good-use-of... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I would say, play with theese two values: reduce-point-density-polygon=8 min-size-polygon=8 I use 6/12 and for Germany at least, it also still looks good at 12. (or better at 300km normal map detail everything but the country border disappears..). I'm still waiting for Europe to finish compiling... On 07.05.2013 16:39, Henning Scholland wrote:
Hi Gerd, overview-map looks nearly great. I've got only some problems with ugly-looking sea. See attached pictures out of qLandkarte.
Options I've used: https://github.com/aighes/RadReiseKarte/blob/master/resources/style_rrk_ov/o...
But it is very, very great to have this overview-map. Fantastic speedup!
Henning
Am 07.05.2013 22:20, schrieb GerdP:
Hi Henning, no, the values are not related to each other.
Gerd
Henning Scholland wrote
Hi, does this also needs a resolution=12 in splitter or are these different things?
Henning
Am 07.05.2013 19:44, schrieb Felix Hartmann:
levels = 0:24, 1:22, 2:20, 3:18
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12....
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Adaptions-in-style-needed-to-make-good-use-of... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Oh forgot one important line: (place=capitol | place=capital) & name=* {set cityxx=yes} [0x0200 resolution 14 continue with_actions ] just add it after the first place=capitol line... else some capital cities don't appear... On 7 May 2013 13:44, Felix Hartmann <extremecarver@gmail.com> wrote:
So - I've played around a bit - just rendering Europe for right now - actually I would suggest the following (needs some adaptations in the lines/poi file though): levels = 0:24, 1:22, 2:20, 3:18
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12.... This should give quite sensible map detail for European countries, or Europe as a continent - without getting near to crash the overview map, because it 's getting too big. I'm unsure whether we should add a completly empty 9:11 or 9:10 so that when zooming out superfar, the map get's blank instead of a pixel mashup...
We definitely do need resolutions 14 and 12 in the overview map. They help tremendously when opening big maps in orientation - without the dreaded setting of details to max setting. As the speed of drawing is now very fast compared to before, resolution 14 and 12 with data do make lot of sense!
Level 8 should only contain capitals and country borders.
Here are some adpation proposals for *points file* - add this before any other POI - due to continue other pois will still be included:
(place=capitol | place=capital) & population > 999999 & name=* {set cityxx=yes} [0x0100 resolution 12 continue with_actions ] place=city & population > 799999 & cityxx!=yes & name=* {set cityxx=yes} [0x0200 resolution 14 continue with_actions ] place=city & population > 399999 & cityxx!=yes & name=* {set cityxx=yes} [0x0300 resolution 15 continue with_actions ] place=city & population > 299999 & cityxx!=yes & name=* {set cityxx=yes} [0x0400 resolution 16 continue with_actions ] place=city & population > 199999 & cityxx!=yes & name=* {set cityxx=yes} [0x0500 resolution 16 continue with_actions ] place=city & population > 99999 & cityxx!=yes & name=* {set cityxx=yes} [0x0600 resolution 17 continue with_actions ] place=city & population > 49999 & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 17 continue with_actions ] place=city & population > 9999 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 18 continue with_actions ]
place=city & population > 0 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 18 continue with_actions ] place=city & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 18 continue with_actions ]
place=town & population > 69999 & cityxx!=yes & name=* {set cityxx=yes} [0x0600 resolution 17 continue with_actions ] place=town & population > 19999 & cityxx!=yes & name=* {set cityxx=yes} [0x0700 resolution 18 continue with_actions ] place=town & population > 9999 & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 19 continue with_actions ] place=town & population > 4999 & cityxx!=yes & name=* {set cityxx=yes} [0x0900 resolution 19 continue with_actions ] place=town & population > 999 & cityxx!=yes & name=* {set cityxx=yes} [0x0a00 resolution 19 continue with_actions ] place=town & population > 0 & cityxx!=yes & name=* {set cityxx=yes} [0x0b00 resolution 20 continue with_actions ] place=town & cityxx!=yes & name=* {set cityxx=yes} [0x0800 resolution 19 continue with_actions ]
*Relations file:* route=road & network=e-road { apply { add ref='${ref'; add int_ref='${int_ref'}; set network=e-road }
*Lines file* # (the main routing part needs to be adapted to only start with level 21) - this here can then start the lines file: highway=motorway & network=e-road [0x01 resolution 14-14 continue] highway=motorway [0x01 resolution 15-20 continue] highway=trunk & network=e-road [0x02 resolution 15-17 continue] highway=trunk [0x02 resolution 18-20 continue]
highway=primary & network=e-road [0x03 resolution 16-18 continue] highway=primary [0x03 resolution 19-20 continue]
highway=secondary & network=e-road [0x04 resolution 17-18 continue] highway=secondary [0x04 resolution 19-20 continue] # Maybe add main rivers - but how to know what are the biggest rivers worldwide? There doesn't exist a relation/network thingy so far AFAIK. # country borders are already at 12. Dunno if they maybe should stop at 14 already.
*Polygons file:* # I would propose to only show sea/land up to resolution 17 by default. Maybe forest/wood and other very important big objects also in 17?
Maybe place=country would also be a nice thing for 12 and 14. Henning
as a POI? I think rather not. The boundary should suffice. At least for 12. Then depending if you create a continent or a single country map, add major capitals, or the capital. I must say I don't understand resolution 11 so far - with options having defined resolution 12 as lowest resolution. Why are country borders still visible - but capitals and ocean disappears. This is nothing really important - for orientation it suffices. It would just make it look a little bit nicer. Maybe it's mapsource/basecamp limitation? City Navigator stops at resolution 13... (and adds 12,11,10 empty - so if you zoom out to 12, the map is just an empty square). I think I will add empty resolution 11 too - it's nicer than the country boundaries (but then less practical) - so tough decision... BTW - with the style example I posted, Europe overview map is ~5MB. I think that's a good size.... On 07.05.2013 17:27, Henning Scholland wrote:
Maybe place=country would also be a nice thing for 12 and 14.
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I'm trying it actual as an extended-poi. My thought was, that it makes it easier on multi-country-maps for people without knowing much about geography. Henning Am 07.05.2013 23:34, schrieb Felix Hartmann:
as a POI?
I think rather not. The boundary should suffice. At least for 12. Then depending if you create a continent or a single country map, add major capitals, or the capital.
I found out that Mapsource won't render pois in the overview map if they have different types on each zoom level. Points: place=city & capital=yes [0x0b00 resolution 12-15 continue] place=city [0x0400 resolution 16] Options file: levels = 0:24, 1:23, 2:22, 3:20, 4:18 overview-levels = 0:17, 1:15 Only the 0x0400 poi is rendered, but in the lowest levels (<16) from the overview map no capital 0x0b00 is shown, altough you can still see it in the ovm_ file. If I change the type into either 0x0400 or 0x0b00 , it is rendered. Don't know if this is a Mapsource bug or something that can be impproved in mkgmap?
I have updated my Benelux map with the latest overview changes: http://www.openfietsmap.nl/downloads/bnl_full Overall the results are pretty good, thanks Gerd for the great work implementing it! There is one issue, I dont see any poi names anymore from zoom resolution 15 and below in Mapsource. In Basecamp and on the overview map (viewed in gpsmapedit) they are rendered (capital cities and country names). Can you have a look at this Gerd?
I found out that Mapsource won't render pois in the overview map if they have different types on each zoom level.
Points:
place=city & capital=yes [0x0b00 resolution 12-15 continue] place=city [0x0400 resolution 16]
Options file:
levels = 0:24, 1:23, 2:22, 3:20, 4:18 overview-levels = 0:17, 1:15
Only the 0x0400 poi is rendered, but in the lowest levels (<16) from the overview map no capital 0x0b00 is shown, altough you can still see it in the ovm_ file. If I change the type into either 0x0400 or 0x0b00 , it is rendered. Don't know if this is a Mapsource bug or something that can be impproved in mkgmap?
Extra information: points place=country & population>250000 [0x1500 resolution 12-17 continue] place=country & population>250000 [0x1400 resolution 18-19] place=country [0x1500 resolution 18-19] place=city & mkgmap:area2poi!=true & (capital=2 | capital=yes) [0x0600 resolution 12-17 continue] place=city & mkgmap:area2poi!=true & (capital=2 | capital=yes) [0x0400 resolution 18] options levels = 0:24, 1:23, 2:22, 3:20, 4:18 overview-levels = 0:17, 1:15
There is one issue, I dont see any poi names anymore from zoom resolution 15 and below in Mapsource. In Basecamp and on the overview map (viewed in gpsmapedit) they are rendered (capital cities and country names).
Can you have a look at this Gerd?
Hi Minko, Minko-2 wrote
There is one issue, I dont see any poi names anymore from zoom resolution 15 and below in Mapsource. In Basecamp and on the overview map (viewed in gpsmapedit) they are rendered (capital cities and country names).
Can you have a look at this Gerd?
I have no idea where to look at. If only MapSource shows this problem I'd say it is a bug or limit in MapSource ? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Adaptions-in-style-needed-to-make-good-use-of... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Maybe a limit, I have to test different poi types to see if they render. Or maybe there shouldnt be an overlap between the regular map and the overview map? levels = 0:24, 1:23, 2:22, 3:20, 4:18 overview-levels = 0:16, 1:14 instead of 0:17 1:15?
I have no idea where to look at. If only MapSource shows this problem I'd say it is a bug or limit in MapSource ?
Gerd
Yes, might be an explanation. BTW: It was intended that you continue counting the levels so it should be overview-levels = 5:xx,6:xx,.. It shouldn't matter if you don't assign levels in your rules. Gerd Minko-2 wrote
Maybe a limit, I have to test different poi types to see if they render. Or maybe there shouldnt be an overlap between the regular map and the overview map? levels = 0:24, 1:23, 2:22, 3:20, 4:18 overview-levels = 0:16, 1:14 instead of 0:17 1:15?
I have no idea where to look at. If only MapSource shows this problem I'd say it is a bug or limit in MapSource ?
Gerd
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Adaptions-in-style-needed-to-make-good-use-of... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, I'm trying to build an overview map of already compiled img's (didn't keep the ovl files or in case I want to use older img's from previous mkgmap versions) but this dont seem to work anymore: -c mkgmap.args *.img I have moved the option overview-levels: 5:17,6:15 in the mkgmap.args file instead of in the option file but this doesnt work either. Is this not implemented anymore / yet or did I forget something?
Hi Minko, right, if mkgmap doesn't find an ovm_ file it adds an empty area for that tile. Gerd Minko-2 wrote
Hi Gerd, I'm trying to build an overview map of already compiled img's (didn't keep the ovl files or in case I want to use older img's from previous mkgmap versions) but this dont seem to work anymore: -c mkgmap.args *.img
I have moved the option overview-levels: 5:17,6:15 in the mkgmap.args file instead of in the option file but this doesnt work either. Is this not implemented anymore / yet or did I forget something?
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Adaptions-in-style-needed-to-make-good-use-of... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Yes, that was the reason why I kept it like that ;-) Gerd
Date: Fri, 10 May 2013 16:12:09 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Adaptions in style (needed to make good use of) for overview2 branch
right, if mkgmap doesn't find an ovm_ file it adds an empty area for that tile.
Gerd
Ah ok, in that case the default should be --remove-ovm-work-files=false as it is now.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
that's a bug (or should we call it feature?) in Mapsource/Basecamp. I think only 0x0100 to 0x0900 render in the overview map. Not sure about extended POIs. On 09.05.2013 05:57, Minko wrote:
I found out that Mapsource won't render pois in the overview map if they have different types on each zoom level.
Points:
place=city & capital=yes [0x0b00 resolution 12-15 continue] place=city [0x0400 resolution 16]
Options file:
levels = 0:24, 1:23, 2:22, 3:20, 4:18 overview-levels = 0:17, 1:15
Only the 0x0400 poi is rendered, but in the lowest levels (<16) from the overview map no capital 0x0b00 is shown, altough you can still see it in the ovm_ file. If I change the type into either 0x0400 or 0x0b00 , it is rendered. Don't know if this is a Mapsource bug or something that can be impproved in mkgmap? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Felix wrote:
that's a bug (or should we call it feature?) in Mapsource/Basecamp. I think only 0x0100 to 0x0900 render in the overview map. Not sure about extended POIs.
I narrowed it down to a place poi of 0x0100 that Mapsource didnt like: (place=sea | place=ocean) & mkgmap:area2poi!=true & name=* [0x0100 resolution 16] As soon as I skipped this tile with the sea name, the poi names of capital cities and countries are rendered ok. With this tile in it, pois disappear from 15 and lower (strange, because the sea names are only until 16). This bug only shows up in Mapsource, in Basecamp it is rendered fine. I have to test further if I can use other poi types instead of 0x0100...
On 09.05.2013 05:57, Minko wrote:
I found out that Mapsource won't render pois in the overview map if they have different types on each zoom level.
Points:
place=city & capital=yes [0x0b00 resolution 12-15 continue] place=city [0x0400 resolution 16]
Options file:
levels = 0:24, 1:23, 2:22, 3:20, 4:18 overview-levels = 0:17, 1:15
Only the 0x0400 poi is rendered, but in the lowest levels (<16) from the overview map no capital 0x0b00 is shown, altough you can still see it in the ovm_ file. If I change the type into either 0x0400 or 0x0b00 , it is rendered. Don't know if this is a Mapsource bug or something that can be impproved in mkgmap? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I have used now another type for the sea names without problems. So it seems it is not recommended to use point type 0x0100 in the overview map, it will make all pois disappear from the whole map at resolution 15 and below in Mapsource.
which types do you use now? I didn't use 0x0100, but 0x0400 and higher, and same problem happened (well the POIs didn't disappear, but the labels did)... On 16.05.2013 12:40, Minko wrote:
I have used now another type for the sea names without problems. So it seems it is not recommended to use point type 0x0100 in the overview map, it will make all pois disappear from the whole map at resolution 15 and below in Mapsource.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
thanks. However note, it's not only about 0x0100 I used 0x1000 and 0x1100 and both would have label problems. Maybe the non usable list is 0x0100, 0x1000 and 0x1100. (in some way this makes sense). So 0x1200 should work again? 0x0900 and 0x0800 are both fine... On 16.05.2013 16:53, Minko wrote:
which types do you use now? I use place=country 0x1500 Major cities/capitals 0x0600 place=sea/ocean 0x1e04
I've also problems with 0x9000 in qLandkarte. At least there is no name displayed (I'm using a transparent icon). Has someone discoverd which ranges of point-IDs work? Henning Am 16.05.2013 23:29, schrieb Felix Hartmann:
thanks.
However note, it's not only about 0x0100
I used 0x1000 and 0x1100 and both would have label problems. Maybe the non usable list is 0x0100, 0x1000 and 0x1100. (in some way this makes sense). So 0x1200 should work again?
0x0900 and 0x0800 are both fine... On 16.05.2013 16:53, Minko wrote:
which types do you use now? I use place=country 0x1500 Major cities/capitals 0x0600 place=sea/ocean 0x1e04
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Ok, you are right. place=country is not the best idea. There are also captitals with is_capital=country and place=city, this should be integrated in the capital-list. Henning Am 07.05.2013 23:34, schrieb Felix Hartmann:
as a POI?
I think rather not. The boundary should suffice. At least for 12. Then depending if you create a continent or a single country map, add major capitals, or the capital.
I must say I don't understand resolution 11 so far - with options having defined resolution 12 as lowest resolution. Why are country borders still visible - but capitals and ocean disappears. This is nothing really important - for orientation it suffices. It would just make it look a little bit nicer.
Maybe it's mapsource/basecamp limitation? City Navigator stops at resolution 13... (and adds 12,11,10 empty - so if you zoom out to 12, the map is just an empty square). I think I will add empty resolution 11 too - it's nicer than the country boundaries (but then less practical) - so tough decision...
BTW - with the style example I posted, Europe overview map is ~5MB. I think that's a good size.... On 07.05.2013 17:27, Henning Scholland wrote:
Maybe place=country would also be a nice thing for 12 and 14.
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
place=capital isn't a tag that is very common. It should be changed into place=city & (capital=yes | capital=2) The tag place=capitol I cant find at all on osm. http://taginfo.openstreetmap.org/tags/capital=yes (339 nodes) http://taginfo.openstreetmap.org/tags/capital=2 (4 nodes) http://taginfo.openstreetmap.org/tags/place=capital (2 nodes) http://taginfo.openstreetmap.org/tags/place=capitol Felix wrote:
just add it after the first place=capitol line... else some capital cities don't appear...
(...)
Here are some adpation proposals for points file - add this before any other POI - due to continue other pois will still be included:
(place=capitol | place=capital) & population > 999999 & name=* {set cityxx=yes} [0x0100 resolution 12 continue with_actions ]
Hi, capital=yes is also used for regional capitals, eg. capital of a county or lower administrative areas. Note: there are only 193 countries accepted by UN and additional 13 ones not accepted. So I would recommend to use is_capital=country in combination with place=city. My experience tells me, that it's best to have only resolution 24 routeable, if you are using --merge-lines. Otherwise BaseCamp puts a routing-destination somewhere on the road, if you are in a higher zoomlevel. If you move this routing-destination afterwards back to the intended point, it works well. If you only have resolution 24 routable it works perfect without "jumping". Henning Am 20.05.2013 10:48, schrieb Minko:
place=capital isn't a tag that is very common. It should be changed into place=city & (capital=yes | capital=2) The tag place=capitol I cant find at all on osm.
http://taginfo.openstreetmap.org/tags/capital=yes (339 nodes) http://taginfo.openstreetmap.org/tags/capital=2 (4 nodes) http://taginfo.openstreetmap.org/tags/place=capital (2 nodes) http://taginfo.openstreetmap.org/tags/place=capitol
Felix wrote:
just add it after the first place=capitol line... else some capital cities don't appear...
(...)
Here are some adpation proposals for points file - add this before any other POI - due to continue other pois will still be included:
(place=capitol | place=capital) & population > 999999 & name=* {set cityxx=yes} [0x0100 resolution 12 continue with_actions ]
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Mon, May 20, 2013 at 11:07:53AM +0200, Henning Scholland wrote:
Hi, capital=yes is also used for regional capitals, eg. capital of a county or lower administrative areas. Note: there are only 193 countries accepted by UN and additional 13 ones not accepted. So I would recommend to use is_capital=country in combination with place=city.
If the capital is the capital of multiple different admin_level, then the tag would be ambiguous or should accept multiple values. I would rather propose something like is_capital:country=[name of country] is_capital:state=[name of state] or even better, use admin_level numbers instead of "country" and "state" in the tag. Best regards, Marko
Typical, the place-node of a capital should be a admin_center-member of the administrative-relation. And you can let mkgmap set a tag to the node. But I haven't checked the admin_level=2-boundaries if they all have a admin_center. Henning Am 20.05.2013 11:59, schrieb Marko Mäkelä:
On Mon, May 20, 2013 at 11:07:53AM +0200, Henning Scholland wrote:
Hi, capital=yes is also used for regional capitals, eg. capital of a county or lower administrative areas. Note: there are only 193 countries accepted by UN and additional 13 ones not accepted. So I would recommend to use is_capital=country in combination with place=city.
If the capital is the capital of multiple different admin_level, then the tag would be ambiguous or should accept multiple values. I would rather propose something like
is_capital:country=[name of country] is_capital:state=[name of state]
or even better, use admin_level numbers instead of "country" and "state" in the tag.
Best regards,
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Would be something like this in relations-file: type=boundary & admin_level=2 { apply role=admin_centre { set rrk:capital:country=yes } } Henning Am 20.05.2013 12:09, schrieb Henning Scholland:
Typical, the place-node of a capital should be a admin_center-member of the administrative-relation. And you can let mkgmap set a tag to the node. But I haven't checked the admin_level=2-boundaries if they all have a admin_center.
Henning
Am 20.05.2013 11:59, schrieb Marko Mäkelä:
On Mon, May 20, 2013 at 11:07:53AM +0200, Henning Scholland wrote:
Hi, capital=yes is also used for regional capitals, eg. capital of a county or lower administrative areas. Note: there are only 193 countries accepted by UN and additional 13 ones not accepted. So I would recommend to use is_capital=country in combination with place=city.
If the capital is the capital of multiple different admin_level, then the tag would be ambiguous or should accept multiple values. I would rather propose something like
is_capital:country=[name of country] is_capital:state=[name of state]
or even better, use admin_level numbers instead of "country" and "state" in the tag.
Best regards,
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
If you combine capital=yes it with place=city and a certain population number (>500.000?) you can filter all less important capitals (for instance those of smaller countries/ mini nations, states and provinces or even lower districts) for the lower zoomlevels. You can also look if those capitals of lower admin. districts are part of a relation lower < admin_level=2 to filter them out. So this way I think you can avoid that capital cities / towns that are either too small or not a capital of a nation are rendered too early.
Hi, capital=yes is also used for regional capitals, eg. capital of a county or lower administrative areas. Note: there are only 193 countries accepted by UN and additional 13 ones not accepted. So I would recommend to use is_capital=country in combination with place=city.
so far "place=capital | place=capitol" worked very well that's why I put/proposed it in the default style. Have you checked that there are actual capital cities, not capitol or capital? For the mail here I just named one... On 20.05.2013 06:30, Minko wrote:
If you combine capital=yes it with place=city and a certain population number (>500.000?) you can filter all less important capitals (for instance those of smaller countries/ mini nations, states and provinces or even lower districts) for the lower zoomlevels. You can also look if those capitals of lower admin. districts are part of a relation lower < admin_level=2 to filter them out. So this way I think you can avoid that capital cities / towns that are either too small or not a capital of a nation are rendered too early.
Hi, capital=yes is also used for regional capitals, eg. capital of a county or lower administrative areas. Note: there are only 193 countries accepted by UN and additional 13 ones not accepted. So I would recommend to use is_capital=country in combination with place=city.
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 20.05.2013 16:03, schrieb Felix Hartmann:
so far "place=capital | place=capitol" worked very well that's why I put/proposed it in the default style. Have you checked that there are actual capital cities, not capitol or capital? For the mail here I just named one... Which data are you using? Taginfo finds (data from today in the morning) only 2 place=capital | place=capitol
Henning
place=capital can surely never be right. The place is not a capital INSTEAD of being a village/town/city etc. The "capital" bit is the status of the place within an administrative entity and the place. The place can have a different capital status in different admin areas at the same time. Being the capital of admin_level=2 does not imply it is also the capital of the lower-level areas. E.g. (symbolic) capital of the Netherlands is Amsterdam which is in the province of North Holland; the provincial capital is Haarlem, not Amsterdam. The only way to represent this properly is in by linking the admin area to the place which is its capital, i.e. the admin_level=2 relation links/points to Amsterdam and the admin_level=4 relation links/points to Haarlem. Colin On 2013-05-20 16:03, Felix Hartmann wrote:
so far "place=capital | place=capitol" worked very well that's why I
put/proposed it in the default style. Have you checked that there are
actual capital cities, not capitol or capital?
For the mail here I just named one... On 20.05.2013 06:30, Minko wrote:
If you combine capital=yes it with place=city and a certain population number (>500.000?) you can filter all less important capitals (for instance those of smaller countries/ mini nations, states and provinces or even lower districts) for the lower zoomlevels. You can also look if those capitals of lower admin. districts are part of a relation lower < admin_level=2 to filter them out. So this way I think you can avoid that capital cities / towns that are either too small or not a capital of a nation are rendered too early.
Hi, capital=yes is also used for regional capitals, eg. capital of a county or lower administrative areas. Note: there are only 193 countries accepted by UN and additional 13 ones not accepted. So I would recommend to use is_capital=country in combination with place=city.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [1]
_______________________________________________
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev [1] Links: ------ [1] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (7)
-
Colin Smale -
Felix Hartmann -
Gerd Petermann -
GerdP
-
Henning Scholland -
Marko Mäkelä -
Minko