OpenStreetMap Forum

The Free Wiki World Map

You are not logged in.

#326 2017-03-21 22:57:15

zeb_
Member
Registered: 2013-03-19
Posts: 5

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

ligfietser wrote:

Do you mean you already have such typ file and want to give it to the community? You can try to mail Lambertus if he is willing implement it in his compilation chain.

Well, it is based on the work from CFerrero originally, which I modified. CFerrero has not updated his site for years, and removing contour from road lines does probably fall outside copyright, so it should be ok to share. I am happy to provide the files to Lambertus. I will contact him.

Offline

#327 2017-03-25 10:43:45

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

I doubt if Charlie will have any objections that you use his style, but it will do no harm if you ask his permission.
Whether Lambertus will implement the typ file or not, I'm happy to host it on github, https://github.com/ligfietser/mkgmap-st … master/typ as long as you are willing to update this file if it gets out of sync with the latest mkgmap developments?

Offline

#328 2017-07-02 06:14:38

rainerU
Member
Registered: 2011-05-06
Posts: 150

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

In Openfietsmap Light maps, type code 0x0600 is assigned to landuse=industrial and landuse=residential areas that have a name attribute. This makes these objets appear in search for cities results.  I understand that large named residential or industrial areas can have the same importance than a suburb or village for a cyclist looking for a destination but in many cases small industrial sites like single factories and small residential areas like student hostels, nursing homes and the like are polluting the search result in a way that cities and villages appear on the lower pages of the list or not at all even if they are just some kilometers away.

Therefore, I propose to assign POI type  0x0600 only to areas with a significant size, e.g. one square km.

Offline

#329 2017-07-02 09:21:47

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

I dont agree, nursing homes and the like could get a poi instead of a name on the residential area so it should be corrected in OSM in the first place.

Offline

#330 2018-01-01 21:10:25

Seagnoid
New Member
Registered: 2018-01-01
Posts: 1

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

Missing lakes!
I downloaded the latest map for New Zealand via garmin.openstreetmap.nl a few days ago and noticed that lakes are missing when zoomed in. Once I zoom out sufficiently they reappear. Could someone please have a look into this?

Thanks,
Tom

Offline

#331 2018-01-02 09:42:02

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

Can you send a link to that location?

Offline

#332 2018-03-23 21:44:30

chassaelle
Member
Registered: 2016-05-22
Posts: 4

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

I get this message from mkgmap using the OFM full style:

SCHWERWIEGEND (RestrictionRelation): DATA/hamburg-splitter-latest/13850011.osm.pbf: Turn restriction (only_straight_on) http://www.openstreetmap.org/relation/417324 (at http://www.openstreetmap.org/?mlat=53.5 … 3&zoom=17) internal error: via way doesn't contain expected points

Geofabrik extract Hamburg. No message with mkgmap default style.
Indeed routing is different. Bug, feature? Or do I miss something?

Offline

#333 2018-03-24 07:37:03

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

I think this restriction implies for cars, part of those ways are forbidden for bicycles, and thus a non routable line is used (for example this via way: https://www.openstreetmap.org/way/503043835). Mkgmap sees this and complains that something is missing. I think you can simply ignore this error.

Offline

#334 2018-03-25 19:07:33

GerdP
Member
Registered: 2015-12-18
Posts: 818

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

This is an error in mkgmap. I can reproduce it and should be able to fix it.

Offline

#335 2018-03-26 08:28:02

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

Thanks Gerd!

Offline

#336 2018-03-26 09:58:54

GerdP
Member
Registered: 2015-12-18
Posts: 818

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

OK, the error is fixed with r4141. No need to compile the map again, the message was printed for the route restriction that was already detected as invalid before but not marked as such.

Gerd

Offline

#337 2018-03-26 18:16:35

chassaelle
Member
Registered: 2016-05-22
Posts: 4

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

Thank you both!

Offline

#338 2018-04-16 11:06:16

chassaelle
Member
Registered: 2016-05-22
Posts: 4

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

with newest mkgmap 4160 and 4164 I get the following:

Error in Style: Error (polygons:112): Expression cannot be indexed

I didn´t follow the latest development deeply - is this now a bug in the style or in mkgmap?

Offline

#339 2018-04-17 00:00:13

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

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

Request : Rendering of areas marked highway=services

In Thailand, at least, we have many of the larger fuel stations marked with a boundary tagged highway=services.  Some include the area=yes tag, while many do not. A typical example can be seen here ; http://www.openstreetmap.org/#map=19/16.42704/102.87641

Is it possible to have mkgmap pick up these areas and render in suitable colour, either sharing the shading of say, industrial, or even allocating a new hex code ? 

We do have a separate issue in the above example where the Garmin routing engine does not see the service area as routable, and in this case, to add the Caltex POI to your route, takes you in and out of the same service road. In time, we will solve this by adding a link across the two roads, and if on a dual carriageway, including a one_way tag. 
Gas_stn.jpg

It would be nice if these areas can be routable (as in a similar case to an area drawn as a Plaza) but appreciate this may not be feasible - true, or not ?

Offline

#340 2018-04-17 06:03:11

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

chassaelle wrote:

with newest mkgmap 4160 and 4164 I get the following:

Error in Style: Error (polygons:112): Expression cannot be indexed

I didn´t follow the latest development deeply - is this now a bug in the style or in mkgmap?

Thats a bug, I think it is just solved in r-4165

Offline

#341 2018-04-17 06:12:10

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

Russ McD wrote:

Request : Rendering of areas marked highway=services

In Thailand, at least, we have many of the larger fuel stations marked with a boundary tagged highway=services.  Some include the area=yes tag, while many do not. A typical example can be seen here ; http://www.openstreetmap.org/#map=19/16.42704/102.87641

Is it possible to have mkgmap pick up these areas and render in suitable colour, either sharing the shading of say, industrial, or even allocating a new hex code ? 

We do have a separate issue in the above example where the Garmin routing engine does not see the service area as routable, and in this case, to add the Caltex POI to your route, takes you in and out of the same service road. In time, we will solve this by adding a link across the two roads, and if on a dual carriageway, including a one_way tag. 

It would be nice if these areas can be routable (as in a similar case to an area drawn as a Plaza) but appreciate this may not be feasible - true, or not ?

I'm not a developer of mkgmap ( better ask this on the mailing list) but I think it is the same with highway=pedestrian, it is needed to add area= yes to mark this as area so the renderer can see it is an area and it is not feasable to make the whole area routable, so you always have to draw extra ways across them.

BTW
The generic new style renders these type of highway areas:
highway=* & area=yes [0x05 resolution 22]
area:highway=* [0x0e resolution 24]

Last edited by ligfietser (2018-04-17 08:16:51)

Offline

#342 2018-05-07 01:37:00

DENelson83
Member
Registered: 2012-06-03
Posts: 2

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

I just installed OSM maps for the first time onto one of my Garmin units, an old GPSMAP 76S, and I was wondering, how would you handle points with the tag "natural=cape"?  I don't seem to see any such points appearing on the map on my Garmin unit.

Offline

#343 2018-07-20 20:56:07

RobB86
New Member
Registered: 2018-07-20
Posts: 1

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

Hi All

I have just installed the new OSM Generic Routable New GBR_03-07-2018. Everything seems to work fine, however the background has changed from the normal yellow to white. Also when night-time mode kicks in the screen does not go black but more a mix of black/white. Is there something I'm doing wrong during installation or a file that I am missing. This is on a Garmin Zumo 550. Cheers. Rob

Offline

#344 2018-07-21 09:15:32

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

@DENelson83 natural=cape is not in the list of rendered features, it can be added though
@RobB86 the new style always has this white background, maybe you are used to the generic routable?

Offline

#345 2018-11-18 06:18:56

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

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

Hi @ligfietser,

I just cloned the git repo and it's 710 MB. Is it possible to clean this out? Or should I have used a different way to download it?

Thanks,
Peter.

Offline

#346 2018-11-18 10:15:19

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

Hi Peter,
It is caused by address data (resources folder), since it is not updated I will remove it, thanks for reminding me.

Offline

#347 2018-11-18 11:42:57

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

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

Great, thanks!

Offline

#348 2018-12-03 03:26:42

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

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

OK, so here is a challenge ... I notice in Thailand, and presumably the rest of the world, when a Petrol Station/Service area closed way, is ringed with the highway=services tag (note, in the plural), it seems to create an "invisible area" for routing purposes.
If you try to create a route to any waypoint within this area, the Garmin can not do it on Mapsource.
And if you are in the field, then my Zumo 550 repeatedly states its "Unable to calculate route" until I walk out of the services area, then its fine.
I also see that the Services area, instead of displaying as a shaded area like most other areas, it is displayed as a closed service highway, both on Mapsource and the Zumo Unit.
I guess the answer lies somewhere in changing the MKGMAP program, but that's beyond my abilities.
Can anyone help ? hmm

Offline

#349 2018-12-03 07:06:24

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

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

Hi Russ,

As a first step may I suggest you try the same with Lambertus' default map, i.e. not the new style. It is my understanding that this type of map pretty much represents a default mkgmap output. If the problem occurs only in the new style, then it is up to us here to figure it out. But if it occurs in both, then you need to take that up with the mkgmap mailing list.

Checking the PTT nearby I find that the services area has been converted into alleyway, so it is routable, BUT there are no connections to the driveway. That's why routing fails. (New style, I don't have the old one here.)

I don't know whether mkgmap can create nodes at intersections. That would be a preferable solution. Otherwise, we would have to "map for the renderer", i.e. manually connect all the services, which is frowned upon.

Regards,
Peter.

Offline

#350 2018-12-03 09:46:52

ligfietser
Moderator
Registered: 2008-10-09
Posts: 5,084
Website

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

Highway=services is only meant for polygons, not for routable ways: https://wiki.openstreetmap.org/wiki/Tag … 3Dservices
If you want to route, use highway=service

Offline

Board footer

Powered by FluxBB