Telecom tower (man_made=mast) is not rendered on the generic new because in the Netherlands they are all over the place, thousands of pois are cluttering the map. About OSM generic, missing features you can request on the mkgmap-dev mailing list: http://www.mkgmap.org.uk/dev/maillist
Thanks. I posted as per your suggestion. Type is file bit new for me. It will take some time for me to understand discussion over there. Is there any way I can include bus halts and pedestrian crossings with the gamin maps?
highway=bus_stop
If you look in the points file you see that bus_stops are rendered:
highway=bus_stop [0x2f17 resolution 24]
Go to the corresponding typ file, https://github.com/ligfietser/mkgmap-style-sheets/blob/master/typ/osm%20generic%20new/2000.txt
and lookup poi type 0x2f17
[_point]
Type=0x02f
SubType=0x17
String1=0x04,bus stop
String2=0x03,bushalte
With the typ editor you can make another icon
highway=crossing is not rendered so you can’t add it, you have to compile your own mkgmap style.
I mapped for kuwait, but when i am downloading the map from http://garmin.openstreetmap.nl/ i am getting older map. When new version will be uploaded on http://garmin.openstreetmap.nl/
The update process is broken at the moment (growing pains). I have no eta on a new map update.
Do you need some help or place when would you say what wrong?
An update is running now and seems to do well, so I expect new maps to appear at the end of this weekend.
Do you have map styles focusing on the quality of roads? There are hardly any OSM based maps that use this, especially at lower zoom levels. I just wrote a diary post about the subject, and someone suggested GPS maps might be a solution. I don’t have a Garmin myself, so really I have no idea what’s available.
There are currently no maps with styles focussing on OSM road quality on my site. Perhaps one of the other offroad oriented map providers cover that better, e.g. http://openmtbmap.org/ ?
I’m offering to consider adding a specific maptype if someone is willing to maintain the style sheet (I don’t have the expertise nor time), possibly in cooperation with this project.
Note that work is (again) underway to add an elevation contour map as well.
The Garmin generic maps only render paved vs unpaved:
Openmtb displays the grade of tracks.
Also have a look at the Freizeitkarte: http://freizeitkarte-osm.de/garmin/de/index.html
Cool, glad to hear this. Lot of people are asking for this. 
Shame on me: I noted the same and suggested (Well, almost volunteered) to make a night mode setup, but totally forgot…
I may be missing something, but I think the current maps do not distinguish between intermittent and perennial waterways? This is a really useful thing to distinguish. I gather it can be done with a suitable rule in the style file used for your conversions. Something like:
waterway=river [0x1f resolution 18 continue]
waterway=stream [0x18 resolution 19 continue]
waterway=river & intermittent=yes [0x26 resolution 20]
waterway=stream & intermittent=yes [0x10A02 resolution 20]
This is based on advice received at:
http://forum.openstreetmap.org/viewtopic.php?id=53986
Suitable typ file settings for the corresponding object types might be:
river [0x1f] two rows thick blue line
stream [0x18 one row thin blue line
intermittent river [0x26] two rows thick dashed blue line
intermittent stream [0x10A02] one row thin dashed blue line
Of course (if you use these hex codes to distinguish waterways tagged as intermittent in OSM) the resulting map users can choose to modify their own typ files, or use the garmin default which will render a similar appearance of waterways (as these are default hex codes for garmin).
Moreton, are you able to post examples of how your Mkgmaps look with your suggested typ file amendments in a typical area with those types of waterway?
http://www.openstreetmap.org/way/102684367#map=13/26.2749/9.1955&layers=N
This is how it looks on my maps:
An example on OSM is:
https://www.openstreetmap.org/#map=13/-28.4909/153.4227
Mapnik renders intermittent, which is the usual convention, as shown by popej. But for some reason the intermittent tag seems not to be used by many converters (popej seems to be the exception!)
Thanks moreton and popej,
I have dropped your request on the mkgmap-dev mailing list and I will implement the intermittent waterways into the generic new style.
Here is a screenshot of the default style (improved, no typ file). In the red inset picture a screenshot of my Oregon. The intermittent stream is not dashed but the label is showing the intermittent tag.
Many thanks ligfiester,
I am guessing that means the Oregon handles default rendering of [0x10A02] differently from BaseCamp.
Now that the intermittent tag is picked up and given the relevant object codes, users who are interested in the distinction should be able to use their own custom typ settings to render permanent and intermittent waterways differently on their GPSr devices, when this does not happen by default. Thanks again for enabling this.