Thanks for the tips.
I haven’t noticed the problem with the hamlets, but in MS labels for them have always been bigger than villages. I think that’s a Garmin ‘feature’.
I have now eliminated the power lines, but the labels remain… It would be nice if Lambertus could just filter them out, as they serve no purpose.
Regards,
Peter.
I’ll add power=line to the pre-filter stage.
Thanks, you are a star!
Beddhist, I’ve mailed your suggestion about the labels of place names to the mkgmap developers.
The changes to the places have been committed in mkgmap. About hamlets vs villages, I think its another mkgmap issue.
If I look on http://ati.land.cz/gps/typdecomp/editor.cgi it shows that garmin type 0x1100 (used for hamlets) is shown as City name(Point, big) whereas type 0x0b (villages) is City name (Point, small). I’ll report this too.
Many thanks for taking care of this ligfietser!
Thanks very much for that.
Probably not: hamlets being bigger than villages also happens using GPSMapEdit and cgpsmaper.
I don’t know what this editor is supposed to show me, but I suspect that the mkgmap people are using the codes that they do use precisely to avoid the above issue. But I am guessing.
The real problem is that place names are not visible when you zoom out, making orientation on the map almost impossible.
Regards,
Peter.
i have done this
(place=hamlet | place=suburb | place=village ){set place=town} in mkgmapstyle points.
now all places are shown up at town level zoom 3 km
because the font is bigger like town
the problem was, to search between all streetnames, what village is that!!!
because the font was smaller then the streetnames
i like to see place names and not the street names on first sight too.
The editor shows that hamlets get a bigger font, same size like towns. Villages gets a smaller font. See a screenshot in Basecamp below.
Area is http://www.openstreetmap.org/?lat=52.2186&lon=5.4076&zoom=13&layers=M
Map is Lambertus’ world map without typ file. In Mapsource 6.16.3 it shows the same, although in MS the streetnames are too prominent.
The problem with garmin is that you aint see what you get when you look at the map on the GPS, it can be a totally different story 
Hamlets are in bold fonts, like Doornsteeg, Achterhoek, De Veenhuizen and Palestina. Holk is a village, Nijkerk a town.
This is a real bummer indeed. I feel there is a constant tension between the rendering in the different pieces of software and hardware which makes it difficult to get a good generic map. Shame, really. Many thanks for looking into this stuff Ligfietser, it is really no my kind of thing.
You can imagine I sometimes feel the urge to throw my Garmin into a ravine and quit with this stuff 
If only Garmin would be less frightened of, tja, what, and document their system a little. It would make Garmin more attractive to a lot of people, but those short term profit company people never understand the full picture.
It seems that this is a display problem in Garmin’s applications. It displayed correctly in Basecamp beta, which just auto-upgraded to 3.2.1.0. In this all places now display with the same font.
In MapSource the display is still with villages smaller and faint, but MS seems to have been abandoned by Garmin. That’s a shame, as track editing still seems easier there with keyboard shortcuts. I don’t expect Garmin to add features for that…
It seems strange that Garmin choose to display names of hamlets the same size as mega-cities.
Interesting: maps compiled by me with mkgmap v 1795 display cities up to a zoom of 50 km, villages up to 10 km. Dots for hamlets also appear at 10 km zoom, but names only appear at 3 km in MS and not at all in BC.
In mkgmap v1795 places were rendered earlier compared to the later versions: http://www.mkgmap.org.uk/svn/wsvn/mkgmap/resources/styles/default/points?rev=1775&peg=1968
So … it’s going backwards? Shelters are back to being rendered as camp grounds, too.
I have no idea, please share your thoughts at the mkgmap mailing list!
http://www.mail-archive.com/search?l=mkgmap-dev%40lists.mkgmap.org.uk&q=shelter
Looks like this has already been taken care of in the mailing list.
A new update is running using the stable Mkgmap r1867 and with power=line added to the pre-filtering.
However, it occurs to me that the boundary levels 8, 9 and 10 are also filtered out but are probably needed for the address search when the mkgmap-locator branch is merged with trunk…?