You are not logged in.

#251 2014-11-28 05:12:52

Russ McD
Member
From: Hereford & Chiang Mai.
Registered: 2011-04-17
Posts: 276

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

I have a request on the way Fuel station info is processed.  I presume the MKGMAP program looks for amenity=fuel. then searches name and operator, putting one, or both into the Garmin. If there is no info, then it gets labelled Unnamed Fuel Station
A lot of fuel stations in OSM (in Thai at least), just have the brand tag completed, and more recently, I am seeing the name in Thai script, with name:en in English.  I assume MKGMAP tries to translate the Thai, and possibly ignores name:en
Can the prog be amended to check the tags in order, looking for the first valid English name, but to include brand & operator?
Only one needs to be displayed on the Garmin map.
Possible, or too difficult ??
smile Russ.

Offline

#252 2014-11-28 19:08:29

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

The mkgmap rules are quite complicated, see
https://github.com/openstreetmap/mkgmap … t/inc/name

If you see ${name} this will be the name:en tag first and if no english name is given, the name tag will be used. As far as I know mkgmap cannot translate Thai.

Offline

#253 2015-01-04 16:50:25

Russ McD
Member
From: Hereford & Chiang Mai.
Registered: 2011-04-17
Posts: 276

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

OK, I took at look at the file, and see it already tries to resolve the various permutations.

On a separate issue, is there a reason why Hwy exit and entry ramps (link roads) seem to be labelled as residential by mkgmap ?
And roads tagged as highway=residential,  get the same rendering and description as highway=unclassified  ?
It seems that way, but apologies if I'm getting it wrong.... I'm playing with the Gamin TYP files, but assume the "type value" is generated by mkgmap ?

Rgds, Russ

Offline

#254 2015-01-05 15:16:18

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Russ McD wrote:

On a separate issue, is there a reason why Hwy exit and entry ramps (link roads) seem to be labelled as residential by mkgmap ?

I dont think this is intended. Can you give an example, or screenshot?


And roads tagged as highway=residential,  get the same rendering and description as highway=unclassified  ?
It seems that way, but apologies if I'm getting it wrong.... I'm playing with the Gamin TYP files, but assume the "type value" is generated by mkgmap ?

Rgds, Russ

Yes that is correct, residential, living_street, minor and unclassified roads get the same garmin type 0x06. Those typ values are specified in the style files.
The code you can find on https://github.com/openstreetmap/mkgmap … ault/lines (osm generic routable, default mkgmap style)
and https://code.google.com/p/mkgmap-style- … orld/lines (generic new).

Offline

#255 2015-01-08 09:43:05

Russ McD
Member
From: Hereford & Chiang Mai.
Registered: 2011-04-17
Posts: 276

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Well Im just about getting to understand the concept of Style & Type, so apologies if Im not fully understanding things yet !
In the new style, I see:

highway=trunk & ( network=e-road | int_ref=* ) [0x02 resolution 15-17 continue]
highway=trunk [0x02 road_class=4 road_speed=5 resolution 18]
highway=trunk_link & (mkgmap:exit_hint=true | mkgmap:dest_hint=true) [0x06 road_class=3 road_speed=2 resolution 20]
highway=trunk_link [0x09 road_class=3 road_speed=2 resolution 20]
highway=* & highway!=proposed & motorroad=yes [0x02 road_class=4 road_speed=4 resolution 18]
highway=primary & ( network=e-road | int_ref=* ) [0x03 resolution 17-18 continue]
highway=primary [0x03 road_class=3 road_speed=4 resolution 19]
highway=primary_link [0x08 road_class=3 road_speed=1 resolution 21]
highway=secondary & ( network=e-road | int_ref=* ) [0x04 resolution 18-19 continue]
highway=secondary [0x04 road_class=2 road_speed=3 resolution 20]
highway=secondary_link [0x08 road_class=2 road_speed=1 resolution 22]
highway=tertiary [0x05 road_class=1 road_speed=3 resolution 20]
highway=tertiary_link [0x08 road_class=1 road_speed=1 resolution 22]
highway=minor [0x06 road_class=1 road_speed=3 resolution 21]
highway=unclassified [0x06 road_class=0 road_speed=3 resolution 21]

The third line would INDICATE to me, that trunk links, under some circumstances, get the 0x06 type ???  Maybe I stumbled on one of those ! If it wasn't that, then maybe my TYP file was giving me the label.

But as an addendum, is there any reason why residential streets can't be given a different line type to minor/unclassified in your style  I think it would help a lot with the display.

Rgds, Russ

Offline

#256 2015-01-08 10:45:45

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

The problem is that there are more OSM road types than Garmin types, so some of them have to be the same.

Offline

#257 2015-01-08 12:02:35

Russ McD
Member
From: Hereford & Chiang Mai.
Registered: 2011-04-17
Posts: 276

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Noted, but what if we made the ramps the same type as the corresponding Highway, even if they are still only displayed at higher resolutions ?
How many line types (for ways) does Garmin actually provide ?

Offline

#258 2015-01-08 12:21:33

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Russ McD wrote:

Noted, but what if we made the ramps the same type as the corresponding Highway, even if they are still only displayed at higher resolutions ?
How many line types (for ways) does Garmin actually provide ?

Routable types are 0x01-0x13 (that includes 0x0a-0x0c) and 0x16, 0x1a, 0x0b
I don't know why some trunk links are rendered with 0x06, you can ask / search it on the mgkmap development list:
http://www.mkgmap.org.uk/dev/maillist

Offline

#259 2015-02-04 19:06:04

Skippern
Member
From: Guarapari, ES, Brazil
Registered: 2009-02-07
Posts: 89

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Is it possible to turn off capitalisation and add accents to names? In Brazil I get a lot of names like Sao Joao Da Barra, which shall be spelled São João da Barra. If it is necessary to override capitalisation for specific words, than I would suggest da, de, do, das, dos. I guess this applies to all Spanish and Portuguese speaking countries in Latin America, but might also apply further.

Without accents and special characters, names with Ç could be misinterpreted with similar names using C, for example Piaçu and Piacu.

Edit:
It capitalizes correctly for de, but as far as I can see, not for da, do, das & dos. Also I can only see names with plain latin letters, no accents and no ç. It is some time, but I believe Norwegian special letters are correct, (æ, ø, å)

Last edited by Skippern (2015-02-04 21:27:09)

Offline

#260 2015-02-04 23:58:54

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Unfortunately capitalisation is totally controlled by the Garmin firmware, I'm afraid we can't change that.
In the NLD's we also have a character "IJ" like in IJsselmeer, but Garmin renders this as Ijsselmeer.

Offline

#261 2015-02-05 00:02:35

Skippern
Member
From: Guarapari, ES, Brazil
Registered: 2009-02-07
Posts: 89

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

What about accented characters, is there a way to see letters such as ç or ã?

Offline

#262 2015-02-05 07:46:20

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

At NZOpenGPSMaps we are currently investigating using 9-bit encoding. It seems to give us some control over capitalisation on modern units, but some older models are not compatible with this and MS, as well as BaseCamp insist on doing their own capitalisation. The downside is we will have to provide two versions of the map to cater for the older GPS. I don't know whether mkgmap can do this, we use cgpsmapper.

Offline

#263 2015-02-26 08:58:08

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

The last update has a new 'problem': highway shields have disappeared and been replaced by names along the roads. So, instead of a box with a number in it we now have the number written along the road.

Regards,
Peter.

Offline

#264 2015-02-26 17:45:18

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Thanks for noticing Peter, seems that mkgmap r-3449 contained a bug, which has been fixed, see
http://gis.19327.n5.nabble.com/Commit-r … 34379.html
So in the next update it should be ok.

Offline

#265 2015-02-26 20:28:58

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Thanks for the info.

Offline

#266 2015-05-15 22:21:17

FactualOrc
Member
From: Dublin, Ireland
Registered: 2015-05-13
Posts: 9

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Dear Forum,

I have found a problem that occurs in the garmin OSM maps in regards to the "tourism=caravan_site" and the "tourism=camp_site" tags. It would appear that the Garmin 64s (and other units, as I have discovered) do not display POIs tagged as "tourism=caravan_site". Although they do display POIs concerning the other tag. I have been looking into this problem since I recently acquired my 64s when it would not display the campsites that appear on the basecamp program. I will provide links to the threads regarding my investigations

http://forums.gpsreview.net/discussion/ … gpsmap-64s
http://forum.openstreetmap.org/viewtopic.php?id=31093

Regards,
FactualOrc

Offline

#267 2015-05-15 22:30:34

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Looks like a 'feature' of this model GPS. You will have to take that up with Garmin.

However, as Garmin don't support the old map format any more I would not hold my breath.

This is good to know, as we can now avoid that model unless and until they fix it.

Regards,
Peter.

Offline

#268 2015-05-16 01:45:52

FactualOrc
Member
From: Dublin, Ireland
Registered: 2015-05-13
Posts: 9

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Beddhist,

Is there any any way I can modify the map I have downloaded to correct for this quirk?

Offline

#269 2015-05-16 03:01:10

Beddhist
Member
From: Doembang Nangbuat, TH
Registered: 2009-07-28
Posts: 435
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

I guess that depends on whether your 64s completely ignores these POIs or just doesn't display them. Can you find them by searching for the name? If so, you may want to experiment with modifying the TYP file.

Failing that, you could compile your own map. It's not that hard if it is an area not too big: you need a copy of mkgmap, download the config files from the SVN server and make up a suitable batch file. You then download OSM data and drop that on the batch file. Once your map gets over a certain size (I don't know what the limit is) then you need to split the data into tiles. I have never attempted that.

Another option is to download just the missing POIs from the Overpass web site. After transforming into a compatible format you can load them as custom POIs using Garmin POILoader. This is probably easier than the other options.

Cheers,
Peter.

Offline

#270 2015-05-16 09:03:15

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

This is strange, both OSM tags tourism=caravan_site and tourism=camp_site gets the same Garmin rendering poi [0x2b03 resolution 24], see https://github.com/ligfietser/mkgmap-st … new/points
Are you sure you look at the Generic New maps? Can you send me a link of the OSM.org map of a campsite you don't see on your device?

Offline

#271 2015-05-16 10:01:46

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

I'm investigating this issue further...
poi 0x2b03 is rendered as campground on the map, but is not found with search menu on my Garmin Oregon.
poi 0x2b05 that I use on my openfietsmap is also rendered as campground, can be found with the search menu. On my Openfietsmap I use 2b05 for camp_site and 2b03 for caravan_site. I think this a Garmin device bug rather than a mkgmap index problem because Basecamp and Mapsource can find those pois.

Offline

#272 2015-05-16 10:22:27

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

I have dropped this issue on the mgkmap-dev list, http://gis.19327.n5.nabble.com/index-pr … 44807.html
It should be an easy fix to switch for the 0x2b05 poi.
On the Garmin new Style maps I can change this myself so in the next update it will be fixed, thanks FactualOrc for reporting!

Offline

#273 2015-05-16 11:53:48

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

I did some further testing with several devices

0x2b03 (camp and caravan site default style)  renders on Dakota, Oregon 600 as tent symbol, but is not findable (only under all POIs -if you know the name). On a Nuvi 310 it renders as tent and findable under lodging. Monterra renders it as caravan and finds it under lodging/campgrounds

I adapted the default style and made a test map without typ file
https://drive.google.com/file/d/0B5LoKT … sp=sharing
0x02b05 tourism=caravan_site
0x4800 tourism=camp_site

0x2b05 = renders on Dakota, Oregon 600 as tent symbol, and is findable under lodging/campgrounds. On the Nuvi and older Etrex it renders as "bed" (lodging) and findable under lodging. Monterra renders it as tent and finds it under lodging/campgrounds
0x4800 = renders on Dakota, Oregon 600 as tent symbol, and is findable under lodging/campgrounds. On the Nuvi / older Etrex it renders as tent, but pois are not findable at all. Monterra renders it as tent, cannot find it at all.

Please test it for other units.

Last edited by ligfietser (2015-05-16 13:03:01)

Offline

#274 2015-05-16 17:15:30

FactualOrc
Member
From: Dublin, Ireland
Registered: 2015-05-13
Posts: 9

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Hi Ligfietser,

I am happy to report that the img file that you provided in your google drive does actually have working campsite poi's on my 64s! If you could render a map from this osm http://planet.openstreetmap.ie/ using the same settings I would be greatly appreciative.

Thank you very much,
FactualOrc

Offline

#275 2015-05-16 18:20:15

ligfietser
Member
Registered: 2008-10-09
Posts: 5,224
Website

Re: Worldwide routable Garmin maps: Missing/incorrect feature requests

Orc, seems like your 64s behaves the same as my Oregon 600 so I'm glad to hear it works as expected.
I'm sorry but I'm not rendering a map from planet.openstreetmap.ie  This is an extract of the same planet osm that Lambertus uses on garmin.openstreetmap, so be patient until the next map updates.

Offline

Board footer

Powered by FluxBB