OpenStreetMap Forum

The Free Wiki World Map

You are not logged in.

Announcement

A fix has been applied to the login system for the forums - if you have trouble logging in please contact support@openstreetmap.org with both your forum username and your OpenStreetMap username so we can make sure your accounts are properly linked.

#301 2017-01-23 17:12:13

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

Not sure which map you are looking at but that is already implemented Peter:

# Flag unpaved roads.
highway=*
& (surface=cobblestone | surface=compacted | surface=dirt |
   surface=earth | surface=grass | surface=grass_paver |
   surface=gravel | surface=grit | surface=ground | surface=mud |
   surface=pebblestone | surface=sand | surface=unpaved |
   mtb:scale=* |
   tracktype ~ 'grade[2-6]' |
   smoothness ~ '.*(bad|horrible|impassable)' |
   sac_scale ~ '.*(mountain|alpine)_hiking' |
   sport=via_ferrata)
{ add mkgmap:unpaved=1 }

Offline

#302 2017-01-24 05:55:14

Beddhist
Member
From: Glenbervie, NZ
Registered: 2009-07-28
Posts: 344
Website

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

You are correct, it is. It's just that it is nearly invisible, like here:

Image%204.jpg

If you zoom in the brown dashes disappear, if you zoom out they become so small they become obscure.

Is this different from how other dirt roads are displayed? I have seen many where it is very well visible. What's more, when I put my mouse pointer on them I get two info boxes, one of them saying "unpaved". This doesn't happen here.

Thanks for your time.

Offline

#303 2017-01-24 10:02:20

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

I think it depends on the OSM highway tags. It is not a highway=track (normal dirt roads) but a tertiary, those are maybe too wide for the dashed lines?
You can change that by editing the typ file. I'm not sure why you don't see that label 'unpaved'

[_line]
Type=0x10002
UseOrientation=N
Xpm="32 7 2  1"
"! c #7B6500"
"  c none"
"!!!!!!  !!!!!!  !!!!!!  !!!!!!  "
"!!!!!!  !!!!!!  !!!!!!  !!!!!!  "
"                                "
"                                "
"                                "
"                                "
"                                "
;12345678901234567890123456789012
String1=0x04,unpaved
String2=0x03,onverhard
String3=0x02,Unbefestigt
String4=0x01,sans revêtement
ExtendedLabels=Y
FontStyle=NoLabel (invisible)
CustomColor=No
[end]

Offline

#304 2017-01-24 15:26:22

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

Beddhist wrote:

Is this different from how other dirt roads are displayed? I have seen many where it is very well visible. What's more, when I put my mouse pointer on them I get two info boxes, one of them saying "unpaved". This doesn't happen here.

I have found out that the ref tag is the cause, without ref or name tag, the label unpaved is rendered.
I dont know how to solve this, I can't remove the ref or name tag unfortunately.

Edit: found a mkgmap option 'addlabel unpaved' and committed it to the style sheet. I also made 'ice_roads' not routable. https://github.com/ligfietser/mkgmap-st … 0c38f631f5

Last edited by ligfietser (2017-01-24 16:04:41)

Offline

#305 2017-01-24 19:27:10

Beddhist
Member
From: Glenbervie, NZ
Registered: 2009-07-28
Posts: 344
Website

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

All good, thanks for that. At least, the option to not route over unpaved works.

Offline

#306 2017-02-05 21:06:31

Beddhist
Member
From: Glenbervie, NZ
Registered: 2009-07-28
Posts: 344
Website

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

Another one: paved tracks are rendered as unpaved roads. I assume the routing engines treat them as unpaved. I realise that in Europe a lot of these are closed to motor vehicles and whence routing thru them is probably undesirable. In Thailand there is a continuum from unpaved tracks to paved tracks to small roads, all usable by any vehicle that physically fits. It is desirable to get routed thru anything paved.

Regards,
Peter.

Offline

#307 2017-02-06 17:03:27

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

Depends what someone calls paved and what unpaved. That really makes a difference in what country you are. Guess the situation in Thailand is very different than Europe. For my OFM I consider tracks with grade1 or surface=asphalt as paved (same rendering as paved unclassified). Is that what you have in mind?

Offline

#308 2017-02-06 19:48:44

Beddhist
Member
From: Glenbervie, NZ
Registered: 2009-07-28
Posts: 344
Website

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

I have found that

highway=track
surface=paved

is rendered as an unpaved road and when you put the mouse pointer over it it says: "unpaved road".

In Thailand most small roads and residential streets have a concrete surface.

Offline

#309 2017-02-06 22:00:50

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

You are absolutely right Peter. Looking at the generic new styles, the rule that is causing this issue is this one:

(highway=bridleway | highway=path | highway=track | highway=unsurfaced)
& surface!=* & tracktype!=* & smoothness!=* & sac_scale!=*
{ add mkgmap:unpaved=1 }

If my interpretation is correct, it says that all those types of highway are considered as unpaved, unless there is a surface, tracktype, smoothness AND sac_scale parameter! This rule makes no sense at all so must be corrected. The mkgmap default rule is the same so I will discuss this on the mkgmap-dev list first.

Offline

#310 2017-02-06 22:13:28

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

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

In the default style the rule is preceded by this one:

highway=*
& (surface=cobblestone | surface=compacted | surface=dirt |
   surface=earth | surface=grass | surface=grass_paver |
   surface=gravel | surface=grit | surface=ground | surface=mud |
   surface=pebblestone | surface=sand | surface=unpaved |
   mtb:scale=* |
   tracktype ~ 'grade[2-6]' |
   smoothness ~ '.*(bad|horrible|impassable)' |
   sac_scale ~ '.*(mountain|alpine)_hiking' |
   sport=via_ferrata)
{ add mkgmap:unpaved=1 } 

So I think the rule is not that wrong.

Offline

#311 2017-02-06 22:24:54

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

I dont understand it Gerd. What does "&" mean then? To me it says make highway=track unpaved if surface AND tracktype AND smoothness AND sac_scale are not empty. Otherwise I cant explain why surface=paved is set unpaved by mkgmap?

Offline

#312 2017-02-06 22:48:28

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

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

I also understand the rule like that.
It should not set mkgmap:unpaved=1 for a way with highway=track and surface=paved
I did not yet try it. If it does I'd say something is wrong in mkgmap.

Offline

#313 2017-02-06 23:03:18

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

Now I've tested it, and it worked ok. Even with avoidance. The only thing that is not correct is the generic new typ file, it still says unpaved because that is the label if there is no streetname. I can try to correct it by adding a second label.
But still, the syntax is a bit strange: & surface!=* & tracktype!=* & smoothness!=* & sac_scale!=*

Unpaved will not be applied if one of those values is not empty, and I read it as ALL of above values must be not empty.
And then it is still not correct. Say someone tagged the track with surface=soil (1014 values in OSM, but not specified as unpaved by mkgmap). It is better specify a rule like

highway=track & surface! ~ '.*(paved|asphalt|sett|concrete|paving_stones|metal|wood)' { add mkgmap:unpaved=1 } 

And what about cobblestone? Paved or unpaved?

Last edited by ligfietser (2017-02-06 23:10:12)

Offline

#314 2017-02-06 23:08:21

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

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

I'd rather add the surface=soil part to the preceding rule.

Offline

#315 2017-02-06 23:12:17

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

Agree, we cannot catch all types that people have entered.

Offline

#316 2017-02-07 02:03:11

popej
Member
Registered: 2008-09-20
Posts: 469
Website

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

ligfietser wrote:

To me it says make highway=track unpaved if surface AND tracktype AND smoothness AND sac_scale are not empty.

Actually condition like surface!=* means opposite: highway is unpaved if surface IS EMPTY and tracktype IS EMPTY and ...


popej

Offline

#317 2017-02-07 07:47:49

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

My fault, yes you are right, if all those parameters don't exists its unpaved. The preceding rule has to catch all unpaved and if surface=something else mkgmap assumes it is paved. I only need to add label=paved to this rule, but I better prefer a rule like surface=paved etc {addlabel 'paved'} rather then "if those parameters are not empty" then assume its paved and add a label paved to it

Offline

#318 2017-02-07 09:26:14

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

I have decided to change only the label in the typ file. Adding a label 'paved' will show up  as streetname if there is no name. I cannot make it invisible unless I use or add another line type, but since routable line types are all taken and I don't want a second line on top of another it's better to leave it behind.

Offline

#319 2017-02-08 06:41:31

Beddhist
Member
From: Glenbervie, NZ
Registered: 2009-07-28
Posts: 344
Website

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

So, paved tracks will now have a mouse-over label "paved", but continue to appear as unpaved roads, incl. routing avoidance?

Offline

#320 2017-02-08 09:52:24

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

No routing will not be avoided anymore, appearance will be the same, I don't think it must be rendered the same as unclassified roads otherwise why dont people tag it like that?

Offline

#321 2017-02-08 09:56:50

Beddhist
Member
From: Glenbervie, NZ
Registered: 2009-07-28
Posts: 344
Website

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

Ok, all good. Thanks for all your good work.

Actually, I am having a hard time sometimes deciding whether a particular road in Thailand is a paved track, residential or unclassified. In the end, all I can do is look at the aerial images to see whether there are a few houses on the road and whether it connects villages or just heads into the rice paddies. As I said, it is a continuum. If in doubt it is residential.

Offline

#322 2017-03-15 22:49:14

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

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

Hi, firstly, thanks for your work.

I have an old Edge 705 GPS unit. Is it possible to have a TYP option where the borders of the road sections are not drawn? On a 705 this leads to the "spaghetti problem" as seen on http://www.cferrero.net/maps/screenshots_index.html. Thanks a lot in advance.

Offline

#323 2017-03-15 23:25:47

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

Hi Zeb,
You can edit the typ file with an editor like typviewer. If you use a bicycle map try my openfietsmap, it is designed to prevent those issues as much as possible.

Offline

#324 2017-03-16 22:08:05

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

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

ligfietser wrote:

Hi Zeb,
You can edit the typ file with an editor like typviewer. If you use a bicycle map try my openfietsmap, it is designed to prevent those issues as much as possible.

I already use CFerrero TYP files with my own mkgmap scripts. But it would be great to have a similar one on http://garmin.openstreetmap.nl/ if possible?

Last edited by zeb_ (2017-03-16 22:08:36)

Offline

#325 2017-03-17 09:41:55

ligfietser
Moderator
Registered: 2008-10-09
Posts: 4,551
Website

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

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.

Offline

Board footer

Powered by FluxBB