Re: [mkgmap-dev] Broken coastline errors between V1188 and V1398

2009-11-25 Thread Michael.TheBlackCat
Hi Chris,

thanks for your well done work. I tested your script with mkgmap V 1398 
and the daily download from

http://download.geofabrik.de/osm/europe/germany/schleswig-holstein.osm.bz2

After building, i see the complete coastline as before in version 1188 
of mkgmap. Now i don't know what to do in the next step. A nice variant 
would be a code extension for mkgmap with such behavior.  Who of the 
mean mkgmap developers is able to support such code extension? Or is it 
a minor functionality/behavior which should never be implemented?

cheers

Michael



Chris-Hein Lunkhusen schrieb:
 I can confirm that this problem exists in the newer versions of mkgmap.
 Some coastlines are missing in the map.
   

   
 After playing a little bit with the data, I think it is the
 MP code thats causing the coastline to disappear.

 It seems that the error occurs, when a coastline is member
 of to many boundary-multipolygons. In my test the coastline
 was disappearing when beeing member of more than two
 boundary-MPs.

 So as a workaround: I think for boundary-multipolygons the
 multi-MP handling is not neccecary at all, because
 boundaries (normally) are rendered as lines and not as
 areas.
 

 I hacked a little OSM preprocessor in vb.net (don't speak java)
 which does the following:

 change type from multipolygon to boundarypolygon for all
 MPs with no inner-elements. This eliminates the MP
 processing for those boundary polygons.

 If someone want's to get it, - mail me.

 Chris

 ___
 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] Restriction relation problems

2009-11-25 Thread Andrew McCarthy
Hi again,

On Tue, Nov 24, 2009 at 10:11:19PM +, Mark Burton wrote:
 
 Hi Andrew,
 
   Please try using version 1404 and let us know what happens.
  
  A quick run shows all but three restrictions are now added, all three of
  which have a way as a via, which I know is unsupported (is that a
  Garmin or mkgmap issue?). I'll try the Garmin out on the road and
  confirm later today, but it's looking better already.

Unfortunately while driving this morning, my Vista HCx was still
suggesting turns that are, since r1404, showing up in Mkgmap logs as
being created. Very odd. An example:
http://www.openstreetmap.org/browse/relation/61986

Sorry :(

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


Re: [mkgmap-dev] Restriction relation problems

2009-11-25 Thread Andrew McCarthy
On Wed, Nov 25, 2009 at 10:18:20AM +, Andrew McCarthy wrote:
 Settings are
   Calculation method: Better route (would best route make a
   difference to following restrictions?)

To answer my own question, no it doesn't!

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


[mkgmap-dev] [PATCH] Display traffic_calming=* as natural=rock

2009-11-25 Thread Marko Mäkelä
The attached patch translates traffic_calming=* (speed bumps, humps etc.)
into 0x6614 at zoom levels of 200m and closer.  The Edge 705 displays them
as white small circles.

Best regards,

Marko
Index: resources/styles/default/points
===
--- resources/styles/default/points	(revision 1404)
+++ resources/styles/default/points	(working copy)
@@ -207,6 +207,8 @@
 tourism=wine_cellar [0x2c0a resolution 20]
 tourism=zoo [0x2c07 resolution 20]
 
+traffic_calming=* [0x6614 resolution 21]
+
 barrier=bollard | barrier=bus_trap
 {add access = no; add bicycle = yes; add foot = yes} [0x660f resolution 21]
 barrier=block | barrier=cycle_barier | barrier=stile | barrier=kissing_gate
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] tag test start with

2009-11-25 Thread Ben
Hi mkgmap gurus,

Im currently trying to convert some POI lists into img format with mkgmap.
Depending on the first character of the POI name, different actions 
should be performed.

I tried the following:
name=T* {name '${name}'} [0x0101 level 4]
name=M* {name '${name}'} [0x0102 level 4]
name=E* {name '${name}'} [0x0103 level 4]
what results in the error message
Error in style: Error: (points:1): Stack size is 2
Could not open style null

As far as I understand the syntax, I can only test tags for equality, 
not if they contain certain strings.

Does anyone have a good idea idea for how to achieve the desired 
differentiation?


Thanks,
Ben

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


Re: [mkgmap-dev] tag test start with

2009-11-25 Thread Thilo Hannemann
Hi Ben,

perhaps it is not really obvious from the documentation, but you can use 
regular expressions. The syntax would be

name ~ 'T.*'

for example. Note the .* instead of a single *, this is a proper regexp and 
not the simplified version. For reference I would suggest something like 
http://java.sun.com/docs/books/tutorial/essential/regex/, but I'm not sure if 
everything works in mkgmap that is described there.

Regards
Thilo

Am 25.11.2009 um 13:21 schrieb Ben:

 Hi mkgmap gurus,
 
 Im currently trying to convert some POI lists into img format with mkgmap.
 Depending on the first character of the POI name, different actions 
 should be performed.
 
 I tried the following:
 name=T* {name '${name}'} [0x0101 level 4]
 name=M* {name '${name}'} [0x0102 level 4]
 name=E* {name '${name}'} [0x0103 level 4]
 what results in the error message
 Error in style: Error: (points:1): Stack size is 2
 Could not open style null
 
 As far as I understand the syntax, I can only test tags for equality, 
 not if they contain certain strings.
 
 Does anyone have a good idea idea for how to achieve the desired 
 differentiation?
 
 
 Thanks,
 Ben
 
 ___
 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] [PATCH v1] increase Table B size

2009-11-25 Thread Clinton Gladstone
On Nov 24, 2009, at 23:18, Mark Burton wrote:

 Strangely, with the same map, but  after updating to r1404, the problem has 
 disappeared. 
 
 Sorry, can you confirm that was with the Table B size increase patch
 applied to the latest SVN?

Yes, I just checked again. The patch is applied. The error seems to have 
inexplicably disappeared. 

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


Re: [mkgmap-dev] [PATCH v1] increase Table B size

2009-11-25 Thread Mark Burton

 Yes, I just checked again. The patch is applied. The error seems to have 
 inexplicably disappeared. 

Hmm, well even if it comes back you can always do what it's telling you
and specify a value for block-size (or whatever it was). As the maps
get bigger that's probably going to be needed sometime anyway.

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


Re: [mkgmap-dev] [PATCH v1] increase Table B size

2009-11-25 Thread Clinton Gladstone
On Nov 25, 2009, at 23:49, Mark Burton wrote:

 Yes, I just checked again. The patch is applied. The error seems to have 
 inexplicably disappeared. 
 
 Hmm, well even if it comes back you can always do what it's telling you
 and specify a value for block-size (or whatever it was). As the maps
 get bigger that's probably going to be needed sometime anyway.

That was the first thing I tried. I then got an array out of bounds exception. 
Since the first error went away anyway, I did not pursue this further. I am not 
sure if the block size needs to be a multiple of something or other. I simply 
chose 9 because that seemed like a nice number. mkgmap didn't like it 
though.

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


Re: [mkgmap-dev] tag test start with

2009-11-25 Thread Ben
Thanks, Thilo!

that worked (almost) straight away.
I just needed to add an equation to start with:

name=*  name ~ 'T.*' {name '${name}'} [0x6501 level 4]

Happy mapping,
-Ben


Thilo Hannemann wrote:
 Hi Ben,
 
 perhaps it is not really obvious from the documentation, but you can use 
 regular expressions. The syntax would be
 
 name ~ 'T.*'
 
 for example. Note the .* instead of a single *, this is a proper regexp and 
 not the simplified version. For reference I would suggest something like 
 http://java.sun.com/docs/books/tutorial/essential/regex/, but I'm not sure if 
 everything works in mkgmap that is described there.
 
 Regards
 Thilo
 
 Am 25.11.2009 um 13:21 schrieb Ben:
 
 Hi mkgmap gurus,

 Im currently trying to convert some POI lists into img format with mkgmap.
 Depending on the first character of the POI name, different actions 
 should be performed.

 I tried the following:
 name=T* {name '${name}'} [0x0101 level 4]
 name=M* {name '${name}'} [0x0102 level 4]
 name=E* {name '${name}'} [0x0103 level 4]
 what results in the error message
 Error in style: Error: (points:1): Stack size is 2
 Could not open style null

 As far as I understand the syntax, I can only test tags for equality, 
 not if they contain certain strings.

 Does anyone have a good idea idea for how to achieve the desired 
 differentiation?


 Thanks,
 Ben

 ___
 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] [PATCH v1] Fix Nuvi routing regression (rebloat Table A)

2009-11-25 Thread Mark Burton

Just noticed that v1 isn't right - should issue v2 soon
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev