Hi Gerd,
that's a good point. Let's take a look at the numbers:
vacant 10542
no 2732
disused 2389
abandoned 9
vacancy 9
Vacant 7
unused 5
none 4
disused:supermarket 2
Vacant Store 1
vacant;survey 1
vacat 1
computer;vacant 1
vacant;chemist 1
abandone 1
disused:shop=car 1
disused:bicycle 1
...as well as ALL POI's with disused=yes...
...or status=closed... mappers are creative.
But as status=closed is not "official", evaluating could result in spreading
use. So forget about that.
Cheers
Manfred
> Gesendet: Freitag, 18. August 2017 um 09:53 Uhr
> Von: "Gerd Petermann"
Hi Nick,
fine, you probably need a bit more code to handle roundtrip routes (start=end)
Gerd
Von: mkgmap-dev im Auftrag von
nwillink
Gesendet: Freitag, 18. August 2017 16:58:46
An:
Hi Gerd
Brilliant , many thanks !
I use 0x6412 which Garmin has earmarked for its 'trails' .
Great stuff!
Nick
On 18/08/2017 13:35, Gerd Petermann [via GIS] wrote:
> Hi Nick,
>
> not sure what result you need, but this rule in relations sets the tag
> route_node
> and you can evaluate it in
Gerd and Andrzej,
I have doubt if the main question here is the tag not be supported by the
OSM database, but rather the way mkgmap interprets: internally in the java
code or "externally" through rules/syntax in style script.
I also don't think the fact that it is not handled internally by the
Hi Nick,
not sure what result you need, but this rule in relations sets the tag
route_node
and you can evaluate it in the points file
type=route & (route=bicycle | route = hiking | route=foot)
{
apply role=start {
add route_node=start
}
apply role=end {
add
Hi
I read the following:
Matching member roles by regular expression
Currently, apply role=value is for fixed strings.
I'm not quite sure what 'fixed strings ' means but perhaps it means that the
unique properties of individual members of a relation cannot be parsed.
This is a shame as it
Hi Bernhard,
I've changed the default style in r3993, shortly after I learned about
shop=vacant
https://wiki.openstreetmap.org/wiki/Tag%3Ashop%3Dvacant
Not sure if the default style should ignore this as well?
Gerd
Von: mkgmap-dev
Hi Andrzej,
I agree that the mkgmap prefix was not the best choice here.
There are a few more tags created in the default style which are not expected
in the OSM database and which are not evaluated in the java code:
cityxxx
dest_hint
exit_hint
maybe more ?
I thought about a prefix like tmp: