Worldwide routable Garmin maps: Missing/incorrect feature requests

ligfietser · 2019-07-16T17:46:11.000Z

Thanks for your remarks, protect_class is the correct tag, protection_class not and should be corrected.
I also agree with you that social-protected-areas are not equal to nature reserves.
So in the styles an exception should be made for protect_class=21-29
I can adapt the code like this, I have to test if it works:

boundary=protected_area & protect_class>=21 & protect_class<=29 {delete boundary}
leisure=nature_reserve | boundary=protected_area | boundary=nature_reserve [0x16 resolution 20 continue]

iay · 2019-07-16T18:44:48.000Z

Thanks, that proposal makes sense to me. I should also be able to put together a test too but it may take me a few days.

I’ll go ahead and make the tag changes in the OSM data for my area; again, this will probably be a couple of days.

ligfietser · 2019-07-17T07:09:17.000Z

Ian,
I’ve tested it and committed the changes into github, so it will be implemented in future updates, thanks!

iay · 2019-07-17T08:12:27.000Z

Fantastic. I figured out how to get JOSM to show me the other local cases and have uploaded a changeset fixing those.

iay · 2019-10-24T13:16:16.000Z

ligfietser:

yes, the latest style from github will be processed, no need to contact him

The GitHub style was changed three months ago, but I’m still seeing the same issue in the Garmin.osm maps, as of the set from 2019-10-18. So the data is being updated, but it doesn’t look like the style has been. Is there anything we can do about that?

ligfietser · 2019-10-26T08:35:31.000Z

Hi iay,
Seems my changes in the style

boundary=protected_area & protect_class>=21 & protect_class<=29 {delete boundary}

don’t seem to work as expected. I have to figure out why and contact Lambertus. Thanks for reporting!

ligfietser · 2019-11-12T12:20:13.000Z

@Ian, I have asked it weeks ago but unfortunately Lambertus still does not respond and has not fixed/updated the styles from Github.
Better mail him directly or try another map provider.

Since the github styles are not updated anymore I do not see any point to maintain this either (except for my own maps) and will make this topic unsticky.

Beddhist · 2019-11-12T12:23:14.000Z

Thanks for all the work you have put into this over the years.

Regards,
Peter.

iay · 2019-11-13T17:02:42.000Z

ligfietser:

@Ian, I have asked it weeks ago but unfortunately Lambertus still does not respond and has not fixed/updated the styles from Github.
Better mail him directly or try another map provider.

If he isn’t responding to you, I don’t think he is likely to respond to me. In any case, it’s not a good long term situation.

Since the github styles are not updated anymore I do not see any point to maintain this either (except for my own maps) and will make this topic unsticky.

I understand your point of view, and I think I will look into building my own maps using your style as well. I hope you’ll keep your GutHub repository up, at least.

At one point I had something that almost reproduced the ones from garmin.osm… they looked more compressed horizontally in the BaseCamp application, and I think the difference was probably something to do with the options I was using. I can probably build something from there.

I may have asked this before, but are the scripts used by garmin.osm avaiable publicly somewhere? That would probably show up the difference pretty quickly.

ligfietser · 2019-11-13T17:31:38.000Z

@Beddhist: you’re welcome, thank you too
@Ian: yes it will remain in the github repository. Btw what do you mean with compressed? Do you mean the projection angle, at certain latitudes the maps can look distorted? You can either set this with Javawa GMTK or in Mapsource. Scripts of garmin.openstreetmap.nl are not available but the mkgmap options I have posted on github.

muralito · 2019-11-13T20:26:41.000Z

iay:

At one point I had something that almost reproduced the ones from garmin.osm… they looked more compressed horizontally in the BaseCamp application, and I think the difference was probably something to do with the options I was using. I can probably build something from there.

I may have asked this before, but are the scripts used by garmin.osm avaiable publicly somewhere? That would probably show up the difference pretty quickly.

The styles used by this scripts https://proyectos.ingeniovirtual.com.ar/projects/garmin-osm/repository mimics the osm site old style (when motorways were blue)

iay · 2019-11-22T14:55:30.000Z

ligfietser:

Btw what do you mean with compressed? Do you mean the projection angle, at certain latitudes the maps can look distorted? You can either set this with Javawa GMTK or in Mapsource. Scripts of garmin.openstreetmap.nl are not available but the mkgmap options I have posted on github.

That was probably too vague for people to understand what I was saying.

I built a map for my area using your styles and mkgmap options from github. I loaded this map as well as the garmin.openstreetmap.org map for the same area (well, actually for the whole of the UK, which may be relevant) into Garmin Basecamp on my Mac.

The results were almost, but not quite, identical. The most obvious difference was that although a given number of pixels vertically on the screen seemed to correspond to the same set of features in both maps, that wasn’t true horizontally: one map was compressed horizontally relative to the other, so that the same screen distance corresponded to more features on one map than on the other.

So close!

I did play around with JaVaWa GMTK a while back but I don’t really understand the projection angle thing. It’s also something I have to fire up a virtual machine to run, as it’s a 32-bit application and Macs have gone 64-bit-only now. Mapsource is, I think, Windows-only? I’ve also seen a lot of posts that imply that the projection angle is set in the Windows registry, which obviously isn’t going to apply…

I said the fact that my test map was just for the area around my city might be relevant. I’ve seen posts implying that the projection angle Basecamp picks in the absence of an explicit setting depends on the area covered by the map. So my problem may just go away if I make my own map of the whole UK. I will have to see if I can get some time to try that.

(I say “my problem” here, but it’s not really an issue in practice as it’s only a small variation between maps… but it tells me I’m not understanding something that might be important later, which bugs me a bit.)

Any other thoughts welcome.

ligfietser · 2019-11-22T15:11:57.000Z

Ah ok, so that’s the projection angle issue, you can’t set it in mkgmap, it is somewhere stored in the Basecamp settings.
Don’t know how to change that, you have to mail Javawa, he is an expert and familiar with Macs.

iay · 2019-11-22T15:20:37.000Z

ligfietser:

Ah ok, so that’s the projection angle issue, you can’t set it in mkgmap, it is somewhere stored in the Basecamp settings.
Don’t know how to change that, you have to mail Javawa, he is an expert and familiar with Macs.

I think I did mail him about something six months or so back. I then found a page on his web site that says he had a stroke a couple of years back and that’s why he isn’t maintaining his programs, so I felt bad about bothering him again. Is he in fact still active in the community?

ligfietser · 2019-11-23T00:00:32.000Z

Yes, he is still active on the Dutch gps.nl forum, maybe you can search for a solution there or even post a question, I dont think they dont mind that you write it in English there: https://forum.gps.nl/viewforum.php?f=122

ligfietser · 2019-11-26T07:23:07.000Z

Ian,
In the meantime, Javawa has figured out a workaround for the Mac and posted it on his website: http://www.javawa.nl/projectionmac.html

iay · 2019-11-26T15:46:19.000Z

ligfietser:

Ian,
In the meantime, Javawa has figured out a workaround for the Mac and posted it on his website: http://www.javawa.nl/projectionmac.html

I sent him some mail on the forum, but this looks like it should work. Many thanks, I hadn’t noticed it!

iay · 2019-12-18T21:56:21.000Z

ligfietser:

Ah ok, so that’s the projection angle issue

I managed to figure out how to change the projection angle setting on my maps (it’s tricky if you’re using the App Store version of BaseCamp, so I might write that up somewhere). If I set several maps to the same projection angle, I do get the same scaling, so that’s definitely what was going on.

All I’m missing is an idea of what the “projection angle” means… I thought if, for example, I set it to my latitude, that might correct the map so that square features on the ground showed up square, but that seems to be very far from true (everything is very stretched horizontally). Do you know of anything that describes which angle this represents? Googling around just tells me that there are a lot of different map projections, but I can’t find which one Garmin uses, or what parameter this might represent.

ligfietser · 2019-12-23T10:45:27.000Z

Can’t answer your questions. Not sure but I have read somewhere Garmin uses https://en.wikipedia.org/wiki/Transverse_Mercator_projection
Does this make sense?

GerdP · 2020-01-22T08:28:13.000Z

Hi ligfietser,
please participate in current mkgmap discussion regarding handling of railway=abandoned in the default style. It seems nobody likes the idea that we may add a routable line for this even if no highway tag is found.
I’ve now noticed that the “generic new” style was already changed accordingly.