Hi Gerd
Here is another patch. I've made the changes as you suggested and the
following changes:
When highway=path is converted into a cycleway or bridleway, add
foot=yes in case the inc/access[_country] rules don't allow foot on the
resultant highway type
Restrict which historic= are shown as p
Hi Ticker,
yes please, my understanding was that the patch was not accepted.
Gerd
Von: mkgmap-dev im Auftrag von Ticker
Berkin
Gesendet: Donnerstag, 3. Januar 2019 11:59
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] default style improvemen
Hi Gerd,
we can use any formula to assign mapid. If this formula would be widely
accepted, there wouldn't be much conflicts between maps created by
different developers.
If we use the original Garmin's formula, then we would avoid conflicts
with many existing Garmin's maps too. The only requ
See this note in the style manual:
There used to be some restrictions on the kind of expression you could
use. Now the only
restriction is you must have at least one test that depends on a tag
existing. So you cannot
match on everything, regardless of tags, or test for an object that
does not have
Also this line seems to give the same error:
!(highway=* & oneway=*) { deletealltags }
Error in style: Error: (lines:12): Invalid rule expression: $highway!=*
| $oneway!=*
Hope this helps, as this is a different syntax at least and the same
result is still complained of.
On 1/3/19 2:35 PM
Using mkgmap-r4260 I tried several variations to make a rule match when
some tag does not exist:
Line: ( highway!=* | oneway!=*) { deletealltags }
Error in style: Error: (lines:12): Invalid rule expression: $highway!=*|
$oneway!=*
Similar error is given when comparing expression with this
Hi Gerd
Do you want me to do another version of this patch before you commit
it?
I'd like to get on with the next set of changes; minor things like
removing horse= can be done with these.
Regards
Ticker
On Thu, 2018-12-13 at 10:54 +, Ticker Berkin wrote:
> Hi Gerd
>
> My rationale was to
