Re: [mkgmap-dev] Changes to require name defined in the style file
Hi Brett,
Maybe you cna have a look at the Lambertus generic new style maps.
Recently I have put a dashed overlay line next to the highways to indicate the
surface is unpaved.
highway ~
'.*(trunk|primary|secondary|tertiary|unclassified|residential|minor|road).*'
mkgmap:unpaved=1 { add mkgmap:road-speed = '-1' } [0x10002 resolution 21
continue with_actions]
highway ~ '.*(byway|living_street|service|cycleway).*' mkgmap:unpaved=1
[0x10002 resolution 23 continue with_actions]
The styles you can find here:
http://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fstyles%2Fworld
Strange as it might appear in Europe but gravel roads that can be
impassible by normal cars are classed as National Highways in
Australia. Still have not worked out the best way to render gravel
roads but still keep their road level rating. Duplicating all the road
lines for gravel will likely mean running out of Garmin hex codes for
line type. Also OSM surface rules are rather weird. Bit like the
hiking classifications that are very word long, but at least they are
a standard. Tempted by the technic used by some for bridges to render
gravel roads.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Changes to require name defined in the style file
Hi
Looks like a brilliant and timely solution. Finally buckled and today brought a
4wd. Now more mapping to do!
Thanks once again, I will put this in my style sheet.
Cheers Brett
Brett Russell
237 Oldaker Street
Devonport Tas 7310
Phone: (03) 6424 8033
Mobile: 0419 374 971
On 29 Mar 2014, at 7:44 pm, Minko ligfiet...@online.nl wrote:
Hi Brett,
Maybe you cna have a look at the Lambertus generic new style maps.
Recently I have put a dashed overlay line next to the highways to indicate
the surface is unpaved.
highway ~
'.*(trunk|primary|secondary|tertiary|unclassified|residential|minor|road).*'
mkgmap:unpaved=1 { add mkgmap:road-speed = '-1' } [0x10002 resolution 21
continue with_actions]
highway ~ '.*(byway|living_street|service|cycleway).*' mkgmap:unpaved=1
[0x10002 resolution 23 continue with_actions]
The styles you can find here:
http://code.google.com/p/mkgmap-style-sheets/source/browse/#svn%2Ftrunk%2Fstyles%2Fworld
Strange as it might appear in Europe but gravel roads that can be
impassible by normal cars are classed as National Highways in
Australia. Still have not worked out the best way to render gravel
roads but still keep their road level rating. Duplicating all the road
lines for gravel will likely mean running out of Garmin hex codes for
line type. Also OSM surface rules are rather weird. Bit like the
hiking classifications that are very word long, but at least they are
a standard. Tempted by the technic used by some for bridges to render
gravel roads.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Restriction relations and additional (cycle) ways
Hi, the via-ways branch is almost done, but I wonder what to do when make-opposite-cycleways is used or when the style creates multiple routable lines for one OSM way. The Garmin format for restrictions reqires nodes and arcs. The OSM format specifies from and to ways and via nodes or ways. Assume that a via way of an only_left restriction has also an opposite cycleway. Should mkgmap create all possible combinations of restrictions to make sure that also bicycles are only routed left ? Or should it make sure that the bicycle ways are not affected? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Restriction-relations-and-additional-cycle-ways-tp5801555.html Sent from the Mkgmap Development mailing list archive at Nabble.com. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Restriction relations and additional (cycle) ways
Hi, I just noticed that I forgot the existence of the except tag and that mkgmap only supports type=restriction relations, not something type=restriction:bicycle. So, I have to do some more coding... Gerd GerdP wrote Hi, the via-ways branch is almost done, but I wonder what to do when make-opposite-cycleways is used or when the style creates multiple routable lines for one OSM way. The Garmin format for restrictions reqires nodes and arcs. The OSM format specifies from and to ways and via nodes or ways. Assume that a via way of an only_left restriction has also an opposite cycleway. Should mkgmap create all possible combinations of restrictions to make sure that also bicycles are only routed left ? Or should it make sure that the bicycle ways are not affected? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Restriction-relations-and-additional-cycle-ways-tp5801555p5801578.html Sent from the Mkgmap Development mailing list archive at Nabble.com. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Turn restriction angle checks
On Sat, Mar 29, 2014 at 08:05:15AM -0700, GerdP wrote: the via-ways branch is almost done I just cloned and built it, and already addressed one error message that it emitted (redundant turn restriction, prohibiting turn against oneway direction). In the same crossing, there was a wrong turn restriction that an automated check might detect too: \ (oneway) \ On a crossing like this, there is a very sharp turn (135 degrees to right from the diagonal road to the horizontal road), and the turn restriction said no_left_turn. I guess it should have said no_right_turn. I changed it to only_straight_on (role=from and role=to being the diagonal road). Marko ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Restriction relations and additional (cycle) ways
Hi Gerd, IMO it should goes like that: - Each duplication of a road should duplicate restrictions. - Any modification of access flags for original or duplicated roads should be performed accordingly on restrictions. - Redundant restrictions should be removed, this can happen because of changes in access flags or when restriction goes wrong-way. Assume that a via way of an only_left restriction has also an opposite cycleway. Should mkgmap create all possible combinations of restrictions to make sure that also bicycles are only routed left ? I don't understand this problem. If OSM restriction only_left_turn include bicycle, then you should create Garmin restrictions to route bicycles too. I see your next post, will processing of restriction:bicycle solve this question? -- Best regards, Andrzej ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Name-tag-list parameter not used in relations processing
Selon GerdP gpetermann_muenc...@hotmail.com:
Hi Paco,
you can try it, I've uploaded the binary :
http://files.mkgmap.org.uk/download/192/mkgmap.jar
Gerd
Hi Gerd,
I'm afraid the patch isn't effective.
For your information, the relations file contains :
network=icn state!=proposed {
apply {
set icn_from_relation=yes;
set icn_name='${name}';
set icn_ref='${ref}';
};
echotags Relation ICN;
}
and the corresponding lines file :
highway=* icn_from_relation=yes {name '${icn_ref}
(${icn_name|not-equal:icn_ref})' | '${icn_ref}'; echotags ICN way; } [0x00
resolution 15-15 continue]
Mkgmap r3116, without name-tag-list parameter set :
[java] 2345035 - [route=bicycle,type=route,name=EuroVelo 3 - part
France,ref=EV3,network=icn] Relation ICN
[java] 254539829 - [motorcar=yes,mkgmap:label:1=EV3 (EuroVelo 3 - part
France),mkgmap:admin_level2=FRA,mkgmap:admin_level3=France
métropolitaine,mkgmap:admin_level4=Picardie,icn_from_relation=yes,mkgmap:admin_level6=Oise,icn_ref=EV3,mkgmap:admin_level8=Pontpoint,mkgmap:admin_level7=Senlis,name=Trans'Oise,surface=paved,highway=cycleway,foot=designated,mkgmap:street=Trans'Oise,mkgmap:country=FRA,mkgmap:city=Pontpoint,icn_name=EuroVelo
3 - part
France,bicycleroute=yes,source=GPS,mkgmap:region=Picardie,toll=no,tollroad=no,bicycle=yes]
ICN way
Mkgmap r3116, name-tag-list parameter set to name:fr,name,int_name :
[java] 2345035 - [route=bicycle,type=route,name=EuroVelo 3 - part
France,name:fr=La route des pèlerins - portion France,ref=EV3,network=icn]
Relation ICN
[java] 254539829 - [motorcar=yes,mkgmap:label:1=EV3 (EuroVelo 3 - part
France),mkgmap:admin_level2=FRA,mkgmap:admin_level3=France
métropolitaine,mkgmap:admin_level4=Picardie,icn_from_relation=yes,mkgmap:admin_level6=Oise,icn_ref=EV3,mkgmap:admin_level8=Pontpoint,mkgmap:admin_level7=Senlis,name=Trans'Oise,surface=paved,highway=cycleway,foot=designated,mkgmap:street=Trans'Oise,mkgmap:country=FRA,mkgmap:city=Pontpoint,icn_name=EuroVelo
3 - part
France,bicycleroute=yes,source=GPS,mkgmap:region=Picardie,toll=no,tollroad=no,bicycle=yes]
ICN way
Mkgmap r3118, with jar file overwritten with your patched jar, without
name-tag-list-parameter:
[java] 2345035 - [route=bicycle,type=route,name=EuroVelo 3 - part
France,ref=EV3,network=icn] Relation ICN
[java] 254539829 - [motorcar=yes,mkgmap:label:1=EV3 (EuroVelo 3 - part
France),mkgmap:admin_level2=FRA,mkgmap:admin_level3=France
métropolitaine,mkgmap:admin_level4=Picardie,icn_from_relation=yes,mkgmap:admin_level6=Oise,icn_ref=EV3,mkgmap:admin_level8=Pontpoint,mkgmap:admin_level7=Senlis,name=Trans'Oise,surface=paved,highway=cycleway,foot=designated,mkgmap:street=Trans'Oise,mkgmap:country=FRA,mkgmap:city=Pontpoint,icn_name=EuroVelo
3 - part
France,bicycleroute=yes,source=GPS,mkgmap:region=Picardie,toll=no,tollroad=no,bicycle=yes]
ICN way
Mkgmap r3118, with jar file overwritten with your patched jar, name-tag-list
parameter set to name:fr,name,int_name :
[java] 2345035 - [route=bicycle,type=route,name=EuroVelo 3 - part
France,name:fr=La route des pèlerins - portion France,ref=EV3,network=icn]
Relation ICN
[java] 254539829 - [motorcar=yes,mkgmap:label:1=EV3 (EuroVelo 3 - part
France),mkgmap:admin_level2=FRA,mkgmap:admin_level3=France
métropolitaine,mkgmap:admin_level4=Picardie,icn_from_relation=yes,mkgmap:admin_level6=Oise,icn_ref=EV3,mkgmap:admin_level8=Pontpoint,mkgmap:admin_level7=Senlis,name=Trans'Oise,surface=paved,highway=cycleway,foot=designated,mkgmap:street=Trans'Oise,mkgmap:country=FRA,mkgmap:city=Pontpoint,icn_name=EuroVelo
3 - part
France,bicycleroute=yes,source=GPS,mkgmap:region=Picardie,toll=no,tollroad=no,bicycle=yes]
ICN way
What I want is to get for way 254539829 the tag mkgmap:label:1=La route des
pèlerins - portion France. So I expect the relation to automatically get the
tag name=La route des pèlerins - portion France.
Or did I misunderstood the way this parameter works ?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
