[mkgmap-dev] Some options from -c not applied

2010-11-18 Thread Carlos Dávila
I'm using the args file attached below with -c option, having two problems:
1: area name in the resulting map is Morocco for all tiles (MapSource).
2: SPAIN-18.TYP is correctly applied to Spain tiles, but MOROC-19.TYP is 
not applied to Morroco's map.
Do you know what I'm doing wrong? Isn't it possible to use two different 
TYP files in the same mkgmap run?

family-id=18
product-id=1
family-name=OpenStreetMap España
country-name=ESPAÑA
country-abbr=ESP
area-name=España
latin1
code-page=1252

mapname: 63240001
description: ES-Madrid
input-file: ../mapas/ultimo-n/63240001.osm.gz

mapname: 63240002
description: ES-Valladolid
input-file: ../mapas/ultimo-n/63240002.osm.gz

mapname: 63240003
description: ES-Valencia
input-file: ../mapas/ultimo-n/63240003.osm.gz

mapname: 63240004
description: ES-Sevilla
input-file: ../mapas/ultimo-n/63240004.osm.gz

mapname: 63240005
description: ES-Barcelona
input-file: ../mapas/ultimo-n/63240005.osm.gz

mapname: 63240006
description: ES-Santander
input-file: ../mapas/ultimo-n/63240006.osm.gz

mapname: 63240007
description: ES-Zaragoza
input-file: ../mapas/ultimo-n/63240007.osm.gz

mapname: 63240008
description: ES-Vigo
input-file: ../mapas/ultimo-n/63240008.osm.gz

input-file: typ/SPAIN-18.TYP

name-tag-list=int_name,name
lower-case
charset=windows-1256
code-page=1256
family-id=19
product-id=1
family-name=OpenStreetMap Morocco
country-name=Morocco
country-abbr=MAR
area-name=Morocco

mapname: 63240009
description: MA-Rabat
input-file: morocco.osm

input-file: typ/MOROC-19.TYP
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] 2 pois for a single polygon/multipolygon

2010-11-18 Thread WanMil
The mp is tagged wrong. 
http://wiki.openstreetmap.org/wiki/Multipolygon#Tagging points out that 
the tags are taken from the relation if it has at least one tag beside 
type=multipolygon. mkgmap follows this rule strictly since r1711.

The relation is tagged with name=Manila City Hall so the resulting 
polygons of the multipolygon are tagged only with name=Manila City Hall.

Please follow the single and easy rule: Put all tags of the multipolygon 
to the relation and not to the outer ways.

The bug that multiple POIs are created multipolygons could be easily 
fixed. I wasn't aware of this problem. I will post a patch within the 
next days.

Have fun!
WanMil


 This way is tagged as a amenity=townhall and a multipolygon relation:
 http://www.openstreetmap.org/browse/way/24159829
 http://www.openstreetmap.org/browse/relation/452620

 In my style:
 polygons:
 building=* | man_made=* | amenity=* | tourism=* [0x13 resolution 24]

 and in the points:
 amenity=townhall [0x3003 resolution 21]
 building=* [0x6402 resolution 24]

 I have the add-pois-areas switch enabled

 This resulted to two POI icons (the little PH flag) in garmin
 http://farm2.static.flickr.com/1290/5184379090_bbeeeaffc8_b.jpg

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


Re: [mkgmap-dev] ! not working -- problem with conditions in style-file.

2010-11-18 Thread Torsten Leistikow
Felix Hartmann schrieb am 17.11.2010 22:30:
 Below is the outcome I want to have for tracktype=1 and respectively 
 tracktype=5
 if tracktypeadded=yes THEN build 0x07 (no matter if tracktype exists, 
 and no matter which value it has).
 if tracktype=5 THEN do build 0x07 (if tracktype does not exist, or 
 tracktype has any value but 1-4 then it should also go through)
 if tracktype=1 but tracktypeadded!=yes THEN do not build 0x07

I am not sure, I understand your intention correctly. So I will provide a table
for the tracktype value and the expected outcome (tracktypeadded!=yes is always
assumed, since this extra condition shouldn't be the problem):


tracktype   -build 0x07
not set   no
1 no
2 no
3 no
4 no
5 yes
any other value   no

This should be achieved by (tracktypeadded=yes | tracktype=5)

This look so easy, so I probably have misunderstood your intention. So please
provide such a table with your expected outcome.

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


Re: [mkgmap-dev] ! not working -- problem with conditions in style-file.

2010-11-18 Thread Felix Hartmann


On 18.11.2010 16:52, Torsten Leistikow wrote:
 Felix Hartmann schrieb am 17.11.2010 22:30:
 Below is the outcome I want to have for tracktype=1 and respectively
 tracktype=5
 if tracktypeadded=yes THEN build 0x07 (no matter if tracktype exists,
 and no matter which value it has).
 if tracktype=5 THEN do build 0x07 (if tracktype does not exist, or
 tracktype has any value but 1-4 then it should also go through)
 if tracktype=1 but tracktypeadded!=yes THEN do not build 0x07
 I am not sure, I understand your intention correctly. So I will provide a 
 table
 for the tracktype value and the expected outcome (tracktypeadded!=yes is 
 always
 assumed, since this extra condition shouldn't be the problem):


 tracktype   -build 0x07
 not set   no
 1 no
 2 no
 3 no
 4 no
 5 yes
 any other value   no

 This should be achieved by (tracktypeadded=yes | tracktype=5)

 This look so easy, so I probably have misunderstood your intention. So please
 provide such a table with your expected outcome.

 Gruss
 Torsten

table should look like this for tracktype!4

tracktype   -build 0x07
not set   yes
1no
1 no
2 no
3 no
4 no
5 yes
5yes
any other value   yes

(any other value, meaning non numeric).
this can currently be achieved by ( tracktypeadded=yes | (tracktype!=* | 
tracktype4 ))

but I think for the above command the easier structure would be ( 
tracktypeadded=yes | tracktype!5 )


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


Re: [mkgmap-dev] ! not working -- problem with conditions in style-file.

2010-11-18 Thread Torsten Leistikow
Felix Hartmann schrieb am 18.11.2010 17:18:
 table should look like this for tracktype!4
 
 tracktype   -build 0x07
 not set   yes
 1  no
 1 no
 2 no
 3 no
 4 no
 5   yes
 5yes
 any other value   yes
 
 (any other value, meaning non numeric).
 this can currently be achieved by ( tracktypeadded=yes | (tracktype!=* | 
 tracktype4 ))

I think not not, any non-numeric value for tracktype would give a different
result than your table.

 but I think for the above command the easier structure would be ( 
 tracktypeadded=yes | tracktype!5 )

I think inventing such an operator would be a bad idea. It would be much easier
to have a genenral negation i.e.

!(expression)

But in general you can rework any boolean expression by exchanging the
operators, so that you coul go without a simple negation.

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


Re: [mkgmap-dev] Sea generation

2010-11-18 Thread WanMil
I have created a new branch coast.
As a first step I have committed a new option --coastlinefile that 
allows to define one or more osm files containing coastlines.

I don't know what I have to do to publish the branch build to the 
webpage. Steve? Can you help?

WanMil


 Hi all,

 I have started to rework the sea generation code. There have been
 several reports of problems with flooded tiles in the last weeks so I
 think it is neccessary to improve some parts of it.

 The first thing I've started is to implement a flooded tile blocker. The
 algorithm has been discussed a while ago on this list. It uses a
 quadtree implementation which is able to return all points contained by
 a polygon. The quadtree is filled with all highway points. If a sea
 polygon contains too many points that belong to highways something is
 wrong and the sea polygon is discarded.

 That's the idea... Let's see how it works.
 The quadtree might also be used to correct wrong sea polygons. But
 that's one of the further steps.

 Do you have any other ideas how to improve the sea generation and how to
 make it more failsafe? Then please let me know.

 Have fun!
 WanMil

 ___
 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


Re: [mkgmap-dev] Some options from -c not applied

2010-11-18 Thread Ralf Kleineisel
On 11/18/2010 02:05 PM, Carlos Dávila wrote:

 I'm using the args file attached below with -c option, having two problems:
 1: area name in the resulting map is Morocco for all tiles (MapSource).
 2: SPAIN-18.TYP is correctly applied to Spain tiles, but MOROC-19.TYP is 
 not applied to Morroco's map.
 Do you know what I'm doing wrong? Isn't it possible to use two different 
 TYP files in the same mkgmap run?

It does work for me. Try to move the lines with the typ files to the end
of your config file.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] Sea generation

2010-11-18 Thread Steve Ratcliffe
Hi

 I don't know what I have to do to publish the branch build to the
 webpage. Steve? Can you help?

Its entirely automatic... but wasn't using ant-1.7 so it was not
building fully.  It is there now and should never be more than about 
half an hour out of date.

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


Re: [mkgmap-dev] Some options from -c not applied

2010-11-18 Thread Carlos Dávila
El 18/11/10 19:54, Ralf Kleineisel escribió:
 On 11/18/2010 02:05 PM, Carlos Dávila wrote:


 I'm using the args file attached below with -c option, having two problems:
 1: area name in the resulting map is Morocco for all tiles (MapSource).
 2: SPAIN-18.TYP is correctly applied to Spain tiles, but MOROC-19.TYP is
 not applied to Morroco's map.
 Do you know what I'm doing wrong? Isn't it possible to use two different
 TYP files in the same mkgmap run?
  
 It does work for me. Try to move the lines with the typ files to the end
 of your config file.
It worked with both typ at the end. Thanks
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


Re: [mkgmap-dev] ! not working -- problem with conditions in style-file.

2010-11-18 Thread Steve Ratcliffe
Hi

 I think inventing such an operator would be a bad idea. It would be much 
 easier
 to have a genenral negation i.e.

 !(expression)

The style rules already allow general negation.

If I've understood the conversation, then:

  !(tracktype  5)

does exactly what Felix wants it to do.

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


Re: [mkgmap-dev] ! not working -- problem with conditions in style-file.

2010-11-18 Thread Steve Ratcliffe

Hi

 However I think something like this won't work
 So would(!(tracktype5)|condition2=yes)work? Meaning either
 tracktype not equal smaller 5 or condition2=yes - one of the two has to
 match for it to not stop the action.

Yes it would work.

Here is an example, only WAY 2 is not converted.  WAY 2 and 5 differ
only in condition2=yes

WAY 1
highway=track

WAY 2
highway=track
tracktype=3

WAY 3
highway=track
tracktype=5

WAY 4
highway=track
tracktype=fjdk

WAY 5
highway=track
tracktype=3
condition2=yes

lines

highway=track  (!(tracktype5)|condition2=yes) [0x1]

polygons

results
WAY 1: Line 0x1, name=null, ref=null, res=24-24 (1/1),(2/2),


WAY 3: Line 0x1, name=null, ref=null, res=24-24 (1/1),(2/2),

WAY 4: Line 0x1, name=null, ref=null, res=24-24 (1/1),(2/2),

WAY 5: Line 0x1, name=null, ref=null, res=24-24 (1/1),(2/2),
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev