
Since some time ago I'd noticed that villages are not findable neither on MapSource nor on my devices (nuvi 300 and Legend HCx) whereas they could be found before, but did not track it down till now. The change was introduced in rev 1987 to get a bigger size of labels for villages than for hamlets, which seem reasonable (see thread [1] for more information). Could you check if the same negative side effect is affecting you? Could we use a different code (searchable) for villages, keeping the current label size? [1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q2/011841.html

El 02/01/12 20:47, Carlos Dávila escribió:
Since some time ago I'd noticed that villages are not findable neither on MapSource nor on my devices (nuvi 300 and Legend HCx) whereas they could be found before, but did not track it down till now. The change was introduced in rev 1987 to get a bigger size of labels for villages than for hamlets, which seem reasonable (see thread [1] for more information). Could you check if the same negative side effect is affecting you? Could we use a different code (searchable) for villages, keeping the current label size?
0x0e00 seems to work. Could you give it a try?
[1] http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q2/011841.html

You are right David, 0x1100 is used for villages and seem not findable. 0x0900 is also findable and I think more logical than 0x0e (smaller than hamlets that use 0x0b)

On Tue, Jan 03, 2012 at 02:06:54PM +0100, Carlos Dávila wrote:
El 03/01/12 10:51, Minko escribió:
You are right David, 0x1100 is used for villages and seem not findable. 0x0900 is also findable and I think more logical than 0x0e (smaller than hamlets that use 0x0b) 0x0900 works as expected. +1 for committing it.
Thanks for the suggestion. r2160 does this in resources/styles/default/points: -place=village [0x1100 resolution 22] +place=village [0x0900 resolution 22] Should the polygon rules be revisited? We only map place=village, place=island, and place=islet there. Or would there already be place=* nodes for most places, placed near the logical center of the area? Marko

Thanks for committing Marko, place=* nodes are commonly used, about polygon place=* I can only speak for the situation in the Netherlands that it is not recommended to render them (a lot of faulty AND-import data like place=city tags on villages or boundary=town on hamlets have been removed or retagged recently). Marko wrote: Should the polygon rules be revisited? We only map place=village, place=island, and place=islet there. Or would there already be place=* nodes for most places, placed near the logical center of the area?
participants (3)
-
Carlos Dávila
-
Marko Mäkelä
-
Minko