Re: [mkgmap-dev] default style and highway=services

[Bernd Weigelt]

Hi

i found some highway=rest_area, they should be handles by this rule, too

Bernd


Am Dienstag, 5. September 2017, 14:35:27 CEST schrieb Gerd Petermann:
> Hi all,
> 
> I've just noticed that there is no special rule for this tag
> https://wiki.openstreetmap.org/wiki/Tag:highway=services
> in the default style. In fact, it is often handled by the "mop up" rule
> highway=* & area!=yes [0x07 road_class=0 road_speed=0 resolution 23]
> because many mappers forget to add area=yes as suggested in the wiki.
> 
> I think we should add a rule like
> highway=services & area!=* & is_closed() = true {add area=yes}
> 
> somewhere before the mop up rule.
> Comments?
> 
> Gerd
> 
> 
> 
> 
> --
> Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
> ___
> 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] Rule not working consistently

[Felix Hartmann]

Anyone got any idea why the following rule is not working as expected?

name:int!=* & ( name:en=* | int_name=* | name:fr=* | name_en=* | name_int=*
| name:es=* | name:pt=* | name:de=* | name:it=* | name:nl=* | name:dk=* )
{set name:int='${name:en}' | name:int='${int_name}' |
name:int='${name_int}' |  name:int='${name_en}' | name:int='${name:de}' |
name:int='${name:fr}' | name:int='${name:es}' | name:int='${name:pt}' |
name:int='${name:it}' | name:int='${name:nl}' | name:int='${name:dk}' }

If I use it - and then later set
name:int=* {set name='${name:int}'}

I end up having many places in my map where instead of using the actual
name:int value I get "name:int" instead. Sometimes it does work however -
so I'm at a loss why.


If I instead write out the rules one after another it does work well - is
the rule to long? is there some bug in mkgmap? Do I have some super strange
spelling mistake in it?
(so if I write
name:int!=* & name:en=* { set name:int='${name:en}' }
name:int!=* & int_name=* { set name:int='${int_name}' }
..
it works correctly (but I think this will be slow to process and is simply
many more lines to write.)


Is the rule too long? Is there some bug in mkmgap? do I have a typo even
though I checked it for ages? It really just works for some objects and for
some it will instead put name:int into the label instead even though all
name tags are identical.




-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Rule not working consistently

[Steve Ratcliffe]

On 13/09/17 18:17, Felix Hartmann wrote:

Anyone got any idea why the following rule is not working as expected?

name:int!=* & ( name:en=* | int_name=* | name:fr=* | name_en=* | 
name_int=* | name:es=* | name:pt=* | name:de=* | name:it=* | name:nl=* | 
name:dk=* ) {set name:int='${name:en}' | name:int='${int_name}' | 
name:int='${name_int}' |  name:int='${name_en}' | name:int='${name:de}' 
| name:int='${name:fr}' | name:int='${name:es}' | name:int='${name:pt}' 
| name:int='${name:it}' | name:int='${name:nl}' | name:int='${name:dk}' }


The syntax for set is:

  set name:int = '${name:en}' | '${int_name}' | ...

and not

  set name:int = '${name:en}' | name:int='${int_name}' | ...

Steve

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] mkgmap NPE

[Carlos Dávila]

Map compiles correctly now

El 11/09/17 a las 19:41, Carlos Dávila escribió:

Hi Gerd
Thanks for the quick fix. I can't test it until tomorrow or after 
tomorrow. I will report then.



El 11/09/17 a las 11:14, Gerd Petermann escribió:

Hi Carlos,

thanks for reporting, I think I found a work-around in r3996. Problem 
was caused by this node
https://www.openstreetmap.org/node/5068689766 which is connected to 
this addr:interpolation way

https://www.openstreetmap.org/way/519922639
The problem also seems to disappear when I add name=Hadeed Road to
https://www.openstreetmap.org/way/20029
I did not find out why this situation causes a null pointer :-(

Gerd

Von: mkgmap-dev  im Auftrag 
von Carlos Dávila 

Gesendet: Sonntag, 10. September 2017 19:08:31
An: Development list for mkgmap
Betreff: [mkgmap-dev] mkgmap NPE

Hello
I'm getting a NPE building a map of Asia:
java.lang.NullPointerException
  at
uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.useAddrPlaceTag(HousenumberGenerator.java:873) 


  at
uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.generate(HousenumberGenerator.java:626) 


  at
uk.me.parabola.mkgmap.osmstyle.StyledConverter.end(StyledConverter.java:658) 


  at
uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:243) 


  at
uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:157) 


  at
uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:154)
  at 
uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:52)

  at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:263)
  at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:259)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 


  at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 


  at java.lang.Thread.run(Thread.java:745)
Tile causing the error can be downloaded from:
http://alternativaslibres.org/51700527.o5m
mkgmap command: export MAPA=Asia FID=70 ABR=ASI NAMETAG=name
LANGUAGE=non_latin; java -Xmx7G -ea -Dlog.config=logging.properties -jar
mkgmap-r3995/mkgmap.jar --output-dir=./tmp --bounds=bounds.zip
--precomp-sea=sea.zip --max-jobs --route --latin1 --code-page=1252
--area-name=$MAPA --family-name="OpenStreetMap $MAPA"
--family-id=1${FID} --product-id=1 --series-name="OSM-$MAPA"
--overview-mapname=$ABR-1${FID} --overview-mapnumber=51${FID}
--name-tag-list=$NAMETAG --process-destination --process-exits
--housenumbers --reduce-point-density=4 --polygon-size-limits="24:12,
18:10, 16:0" --add-pois-to-areas --report-similar-arcs
--report-dead-ends=2 --link-pois-to-ways
--location-autofill=is_in,nearest --drive-on=detect --check-roundabouts
--check-roundabout-flares --license-file=license_ODbL.txt
--copyright-message="OpenStreetMap contributors, ODbL. See:
http://www.openstreetmap.org/copyright"; 51700527.o5m 


___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Recent Garmin Firmware "cannot authenticate maps" when they are unicode

[franco_bez]

One last thought:

maybe it's not a bug in mkgmap, and maybe there is no way to fix this on our
side.
But in any way there will be more and more people affected as the number of
new Garmin devices increases.

So we should issue a warning message when maps are built with the unicode
option.

Something like:

"The use of the option unicode will cause problems on recent Garmin devices.
Consider using another encoding instead."

What do You think ?

Ciao,
 Franco 



--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Recent Garmin Firmware "cannot authenticate maps" when they are unicode

[Felix Hartmann]

this can go into documentation not the compile process itself I think. The
warning should be for real warnings that happen because of bugs/problems.

On 13 September 2017 at 21:57, franco_bez  wrote:

> One last thought:
>
> maybe it's not a bug in mkgmap, and maybe there is no way to fix this on
> our
> side.
> But in any way there will be more and more people affected as the number of
> new Garmin devices increases.
>
> So we should issue a warning message when maps are built with the unicode
> option.
>
> Something like:
>
> "The use of the option unicode will cause problems on recent Garmin
> devices.
> Consider using another encoding instead."
>
> What do You think ?
>
> Ciao,
>  Franco
>
>
>
> --
> Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>



-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Rule not working consistently

[Felix Hartmann]

Oh thanks - I was really blind here.

On 13 September 2017 at 19:31, Steve Ratcliffe  wrote:

> On 13/09/17 18:17, Felix Hartmann wrote:
>
>> Anyone got any idea why the following rule is not working as expected?
>>
>> name:int!=* & ( name:en=* | int_name=* | name:fr=* | name_en=* |
>> name_int=* | name:es=* | name:pt=* | name:de=* | name:it=* | name:nl=* |
>> name:dk=* ) {set name:int='${name:en}' | name:int='${int_name}' |
>> name:int='${name_int}' |  name:int='${name_en}' | name:int='${name:de}' |
>> name:int='${name:fr}' | name:int='${name:es}' | name:int='${name:pt}' |
>> name:int='${name:it}' | name:int='${name:nl}' | name:int='${name:dk}' }
>>
>
> The syntax for set is:
>
>   set name:int = '${name:en}' | '${int_name}' | ...
>
> and not
>
>   set name:int = '${name:en}' | name:int='${int_name}' | ...
>
> Steve
>
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>



-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Rule not working consistently

[Felix Hartmann]

I do wonder still why it worked sometimes even though syntax was wrong.

On 14 September 2017 at 00:15, Felix Hartmann 
wrote:

> Oh thanks - I was really blind here.
>
> On 13 September 2017 at 19:31, Steve Ratcliffe 
> wrote:
>
>> On 13/09/17 18:17, Felix Hartmann wrote:
>>
>>> Anyone got any idea why the following rule is not working as expected?
>>>
>>> name:int!=* & ( name:en=* | int_name=* | name:fr=* | name_en=* |
>>> name_int=* | name:es=* | name:pt=* | name:de=* | name:it=* | name:nl=* |
>>> name:dk=* ) {set name:int='${name:en}' | name:int='${int_name}' |
>>> name:int='${name_int}' |  name:int='${name_en}' | name:int='${name:de}' |
>>> name:int='${name:fr}' | name:int='${name:es}' | name:int='${name:pt}' |
>>> name:int='${name:it}' | name:int='${name:nl}' | name:int='${name:dk}' }
>>>
>>
>> The syntax for set is:
>>
>>   set name:int = '${name:en}' | '${int_name}' | ...
>>
>> and not
>>
>>   set name:int = '${name:en}' | name:int='${int_name}' | ...
>>
>> Steve
>>
>> ___
>> mkgmap-dev mailing list
>> mkgmap-dev@lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>
>
>
> --
> Felix Hartman - Openmtbmap.org & VeloMap.org
> Schusterbergweg 32/8
> 6020 Innsbruck
> Austria - Österreich
>



-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Rule not working consistently

[Felix Hartmann]

ah of course it worked as long as name:en was present - but not for any
other like int_name or so on.

On 14 September 2017 at 00:16, Felix Hartmann 
wrote:

> I do wonder still why it worked sometimes even though syntax was wrong.
>
> On 14 September 2017 at 00:15, Felix Hartmann 
> wrote:
>
>> Oh thanks - I was really blind here.
>>
>> On 13 September 2017 at 19:31, Steve Ratcliffe 
>> wrote:
>>
>>> On 13/09/17 18:17, Felix Hartmann wrote:
>>>
 Anyone got any idea why the following rule is not working as expected?

 name:int!=* & ( name:en=* | int_name=* | name:fr=* | name_en=* |
 name_int=* | name:es=* | name:pt=* | name:de=* | name:it=* | name:nl=* |
 name:dk=* ) {set name:int='${name:en}' | name:int='${int_name}' |
 name:int='${name_int}' |  name:int='${name_en}' | name:int='${name:de}' |
 name:int='${name:fr}' | name:int='${name:es}' | name:int='${name:pt}' |
 name:int='${name:it}' | name:int='${name:nl}' | name:int='${name:dk}' }

>>>
>>> The syntax for set is:
>>>
>>>   set name:int = '${name:en}' | '${int_name}' | ...
>>>
>>> and not
>>>
>>>   set name:int = '${name:en}' | name:int='${int_name}' | ...
>>>
>>> Steve
>>>
>>> ___
>>> mkgmap-dev mailing list
>>> mkgmap-dev@lists.mkgmap.org.uk
>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>
>>
>>
>>
>> --
>> Felix Hartman - Openmtbmap.org & VeloMap.org
>> Schusterbergweg 32/8
>> 6020 Innsbruck
>> Austria - Österreich
>>
>
>
>
> --
> Felix Hartman - Openmtbmap.org & VeloMap.org
> Schusterbergweg 32/8
> 6020 Innsbruck
> Austria - Österreich
>



-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Recent Garmin Firmware "cannot authenticate maps" when they are unicode

[Gerd Petermann]

Hi all,

The documentation and help already contains this
--unicode
This is equivalent to --code-page=65001. Note that
some devices don't support unicode maps produced by mkgmap.

I added the hint while working on the optimize-index branch, it is in the 
branch since r3968.
Please suggest improvements if this is not enough.

Gerd


Von: mkgmap-dev  im Auftrag von Felix 
Hartmann 
Gesendet: Donnerstag, 14. September 2017 00:14:34
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Recent Garmin Firmware "cannot authenticate maps" 
when they are unicode

this can go into documentation not the compile process itself I think. The 
warning should be for real warnings that happen because of bugs/problems.

On 13 September 2017 at 21:57, franco_bez 
mailto:franco@web.de>> wrote:
One last thought:

maybe it's not a bug in mkgmap, and maybe there is no way to fix this on our
side.
But in any way there will be more and more people affected as the number of
new Garmin devices increases.

So we should issue a warning message when maps are built with the unicode
option.

Something like:

"The use of the option unicode will cause problems on recent Garmin devices.
Consider using another encoding instead."

What do You think ?

Ciao,
 Franco



--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev



--
Felix Hartman - Openmtbmap.org & VeloMap.org
Schusterbergweg 32/8
6020 Innsbruck
Austria - Österreich
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev