[mkgmap-dev] Options

2015-04-28 Thread Anna Leuchter
Hello Gerd,
sorry for the delay.

better than nothing simply means that this is actually the only possibility, 
to create Points along a way to mark a hiking trail based on relations.
In fact this is not really satiesfying but it is actually the only way. That's 
the reason why i said better than nothing.

OSMCOMPOSER-Software which is a type of frontend to mkgamp has a builtin 
preprocessor, which is able to create points along way relation.
Here you have the possibilty to configure which relations you wanna use e.g 
hiking|cycling|MTB and the minimum lenght, of way beeing part or a relation to 
get a poi.
If there are multiple routes, the pois will be distributed, to fit in a way 
that they are all visible.
Ok, it's clear, depending on length and amount of pois, they will overlap.


regards
Gert


From Gerd Petermann gpetermann_muenchen at hotmail.com on Fri Apr 24 06:35:07 
BST 2015

Hi Gert,

 yes, I think it must be useful, I also see it in Minkos styles at
 http://www.openfietsmap.nl/

 I don't fully understand the better than nothing part .
 The current code adds a POI to each point, so each point has 
 a mkgmap:line2poitype=* tag with values start,end,mid, or inner 
 for the rest.

 The option should be handled with great care, it is likely to
 produce a large number of POI for highly detailed ways
 created by some imports.
 I already thought about an addtional parameter for the option,
 something like --add-pois-to-lines=n where n gives a value in meter
 for the minimum distance between two generated POI when the way
 has more than 3 points. 

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


Re: [mkgmap-dev] error message in Cologne

2015-04-28 Thread Bernd Weigelt
Hi Gerd

Can't test the new functions until monday next week, i'm out for a motorcycle 
tour :-) 

Bernd

Hier sollte eigentlich eine Signatur stehen.



-Original Message-
From: Gerd Petermann gpetermann_muenc...@hotmail.com
To: mkgmap-dev@lists.mkgmap.org.uk mkgmap-dev@lists.mkgmap.org.uk
Sent: Di., 28 Apr. 2015 8:44
Subject: Re: [mkgmap-dev] error message in Cologne

Hi Bernd,

the problem was fixed with r3549. With r3550 I've implemented
the new special tag mkgmap:numbers, see 
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmaprev=3550
for details. 

Gerd

 Date: Mon, 27 Apr 2015 12:59:30 -0700
 From: gpetermann_muenc...@hotmail.com
 To: mkgmap-dev@lists.mkgmap.org.uk
 Subject: Re: [mkgmap-dev] error message in Cologne
 
 Hi Bernd,
 
 forget it, I was able to reproduce the error message with a download of this
 area:
 http://www.openstreetmap.org/query?lat=50.06119lon=14.40275
 
 Gerd
 
 
 GerdP wrote
  Hi Bernd,
  
  please post a link to the file 65030278.o5m
  
  Gerd
  Bernd Weigelt wrote
  Hi Gerd
  
  There was only one message for my dach extract, all other extract are
  build 
  without any noise.
  
  SCHWERWIEGEND (ExtNumbers): /home/bernd/map_build/tiles/65030278.o5m:
  internal 
  error, worst house not found id=4672706, Na Neklance[731(10), 727(10), 
  805/8(10)][] 2031/1(0)
  
  The option --x-name-service-roads=n seems to be no really problem, while 
  enabled, but i'll remove it from my options for the next build, too.
  ;-)
  
  Bernd
  
  Am Montag, 27. April 2015, 20:07:54 schrieb Gerd Petermann:
  Hi Bernd,
  
  pleasse note one important change:
  I've removed the option --x-name-service-roads=n,
  it is no longer optional, mkgmap tries to find a name
  for roads with house numbers. This leads to
  some special effects, e.g. when a small unnamed footway
  is closer to the house than the named service road.
  I think about a new tag like mkgmap:number=false
  that tells mkgmap that a road should not be used for
  address search, e.g. cycleways or motorways.
  This would also speed up the search for the closest roads.
  
  Gerd
  
   From: 
 
  weigelt.bernd@
 
   To: 
 
  mkgmap-dev@.org
 
   Date: Mon, 27 Apr 2015 17:58:45 +0200
   Subject: Re: [mkgmap-dev] error message in Cologne
   
   Hi Gerd
   i'll give it a try asap
   
   thx
   Bernd
   
   Am Sonntag, 26. April 2015, 16:37:35 schrieb Gerd Petermann:
please try r3546, I think it is stable again.
I had to change the program logic to make sure that
special cases with interpolation ways do not
causes assertions.

I have still some known problems, esp.
the program logic for housenumbers assumes now that
city/ zip code info attached to the housenumbers is written to the
  img
file, but that doesn't happen yet (and is quite complicated as it
  seems
to require big changes in the existing program logic)
so address search for roads at city boundaries might still
not work.
  
  -- 
  amarok2 now playing:
  
  
  
  
  ___
  mkgmap-dev mailing list
 
  mkgmap-dev@.org
 
  http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
 
 
 
 
 
 --
 View this message in context: 
 http://gis.19327.n5.nabble.com/error-message-in-Cologne-tp5841730p5842108.html
 Sent from the Mkgmap Development mailing list archive at Nabble.com.
 ___
 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] mkgmap:city empty in large cities

2015-04-28 Thread Ben Konrath
Hi Gerd,

I was  a bit wrong with my analysis of Ottawa and Toronto. Toronto and
Ottawa should be admin level 8 and the 'cities' within Toronto and Ottawa
should be admin level 9 (as Orleans was already tagged). I've corrected the
labelling issues in OSM but I didn't add the missing 'city' boundaries
inside Ottawa.

I've attached a patch that corrects address search for Toronto and Ottawa.
You'll need updated bounds data for this to work but I have confirmed that
it's working. It would be nice to get this included in mkgamp.

Thanks, Ben
diff --git a/resources/styles/default/inc/address b/resources/styles/default/inc/address
index f01b26e..4a85973 100644
--- a/resources/styles/default/inc/address
+++ b/resources/styles/default/inc/address
@@ -59,6 +59,8 @@ mkgmap:country=CHE  mkgmap:city!=*  mkgmap:admin_level8=* { set mkgmap:city='$
  
 # Canada
 mkgmap:country=CAN  mkgmap:region!=*  mkgmap:admin_level4=* { set mkgmap:region='${mkgmap:admin_level4}' }
+mkgmap:country=CAN  mkgmap:city!=*  mkgmap:admin_level8=Toronto  mkgmap:admin_level9=* { set mkgmap:city='${mkgmap:admin_level9}' }
+mkgmap:country=CAN  mkgmap:city!=*  mkgmap:admin_level8=Ottawa  mkgmap:admin_level9=* { set mkgmap:city='${mkgmap:admin_level9}' }
 mkgmap:country=CAN  mkgmap:city!=*  mkgmap:admin_level8=* { set mkgmap:city='${mkgmap:admin_level8|subst:City of }' }
 
 # United States
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] error message in Cologne

2015-04-28 Thread Gerd Petermann
Hi Bernd,

no problem, have fun !
Gerd

 Date: Tue, 28 Apr 2015 18:48:53 +0200
 From: weigelt.be...@web.de
 To: mkgmap-dev@lists.mkgmap.org.uk
 Subject: Re: [mkgmap-dev] error message in Cologne
 
 Hi Gerd
 
 Can't test the new functions until monday next week, i'm out for a motorcycle 
 tour :-) 
 
 Bernd
 
 Hier sollte eigentlich eine Signatur stehen.
 
 
 
 -Original Message-
 From: Gerd Petermann gpetermann_muenc...@hotmail.com
 To: mkgmap-dev@lists.mkgmap.org.uk mkgmap-dev@lists.mkgmap.org.uk
 Sent: Di., 28 Apr. 2015 8:44
 Subject: Re: [mkgmap-dev] error message in Cologne
 
 Hi Bernd,
 
 the problem was fixed with r3549. With r3550 I've implemented
 the new special tag mkgmap:numbers, see 
 http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmaprev=3550
 for details. 
 
 Gerd
 
  Date: Mon, 27 Apr 2015 12:59:30 -0700
  From: gpetermann_muenc...@hotmail.com
  To: mkgmap-dev@lists.mkgmap.org.uk
  Subject: Re: [mkgmap-dev] error message in Cologne
  
  Hi Bernd,
  
  forget it, I was able to reproduce the error message with a download of this
  area:
  http://www.openstreetmap.org/query?lat=50.06119lon=14.40275
  
  Gerd
  
  
  GerdP wrote
   Hi Bernd,
   
   please post a link to the file 65030278.o5m
   
   Gerd
   Bernd Weigelt wrote
   Hi Gerd
   
   There was only one message for my dach extract, all other extract are
   build 
   without any noise.
   
   SCHWERWIEGEND (ExtNumbers): /home/bernd/map_build/tiles/65030278.o5m:
   internal 
   error, worst house not found id=4672706, Na Neklance[731(10), 727(10), 
   805/8(10)][] 2031/1(0)
   
   The option --x-name-service-roads=n seems to be no really problem, while 
   enabled, but i'll remove it from my options for the next build, too.
   ;-)
   
   Bernd
   
   Am Montag, 27. April 2015, 20:07:54 schrieb Gerd Petermann:
   Hi Bernd,
   
   pleasse note one important change:
   I've removed the option --x-name-service-roads=n,
   it is no longer optional, mkgmap tries to find a name
   for roads with house numbers. This leads to
   some special effects, e.g. when a small unnamed footway
   is closer to the house than the named service road.
   I think about a new tag like mkgmap:number=false
   that tells mkgmap that a road should not be used for
   address search, e.g. cycleways or motorways.
   This would also speed up the search for the closest roads.
   
   Gerd
   
From: 
  
   weigelt.bernd@
  
To: 
  
   mkgmap-dev@.org
  
Date: Mon, 27 Apr 2015 17:58:45 +0200
Subject: Re: [mkgmap-dev] error message in Cologne

Hi Gerd
i'll give it a try asap

thx
Bernd

Am Sonntag, 26. April 2015, 16:37:35 schrieb Gerd Petermann:
 please try r3546, I think it is stable again.
 I had to change the program logic to make sure that
 special cases with interpolation ways do not
 causes assertions.
 
 I have still some known problems, esp.
 the program logic for housenumbers assumes now that
 city/ zip code info attached to the housenumbers is written to the
   img
 file, but that doesn't happen yet (and is quite complicated as it
   seems
 to require big changes in the existing program logic)
 so address search for roads at city boundaries might still
 not work.
   
   -- 
   amarok2 now playing:
   
   
   
   
   ___
   mkgmap-dev mailing list
  
   mkgmap-dev@.org
  
   http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
  
  
  
  
  
  --
  View this message in context: 
  http://gis.19327.n5.nabble.com/error-message-in-Cologne-tp5841730p5842108.html
  Sent from the Mkgmap Development mailing list archive at Nabble.com.
  ___
  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 mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] mkgmap:city empty in large cities

2015-04-28 Thread Ben Konrath
Hi Gerd,

Yes, that's correct. The patch will have no effect until the bounds are
updated to OSM data that's newer than 27 April 2015.

Thanks, Ben

On Tue, Apr 28, 2015 at 10:04 AM, Gerd Petermann 
gpetermann_muenc...@hotmail.com wrote:

 Hi Ben,

 thanks for the patch. Just to make sure:
 The additional rules have no effect until one has updated bounds,
 so I can commit that without causing trouble, right?

 Gerd

 --
 Date: Tue, 28 Apr 2015 09:43:03 +0200
 From: b...@bagu.org
 To: mkgmap-dev@lists.mkgmap.org.uk
 Subject: Re: [mkgmap-dev] mkgmap:city empty in large cities

 Hi Gerd,

 I was  a bit wrong with my analysis of Ottawa and Toronto. Toronto and
 Ottawa should be admin level 8 and the 'cities' within Toronto and Ottawa
 should be admin level 9 (as Orleans was already tagged). I've corrected the
 labelling issues in OSM but I didn't add the missing 'city' boundaries
 inside Ottawa.

 I've attached a patch that corrects address search for Toronto and Ottawa.
 You'll need updated bounds data for this to work but I have confirmed that
 it's working. It would be nice to get this included in mkgamp.

 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

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

Re: [mkgmap-dev] error message in Cologne

2015-04-28 Thread Gerd Petermann
Hi Bernd,

the problem was fixed with r3549. With r3550 I've implemented
the new special tag mkgmap:numbers, see 
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmaprev=3550
for details. 

Gerd

 Date: Mon, 27 Apr 2015 12:59:30 -0700
 From: gpetermann_muenc...@hotmail.com
 To: mkgmap-dev@lists.mkgmap.org.uk
 Subject: Re: [mkgmap-dev] error message in Cologne
 
 Hi Bernd,
 
 forget it, I was able to reproduce the error message with a download of this
 area:
 http://www.openstreetmap.org/query?lat=50.06119lon=14.40275
 
 Gerd
 
 
 GerdP wrote
  Hi Bernd,
  
  please post a link to the file 65030278.o5m
  
  Gerd
  Bernd Weigelt wrote
  Hi Gerd
  
  There was only one message for my dach extract, all other extract are
  build 
  without any noise.
  
  SCHWERWIEGEND (ExtNumbers): /home/bernd/map_build/tiles/65030278.o5m:
  internal 
  error, worst house not found id=4672706, Na Neklance[731(10), 727(10), 
  805/8(10)][] 2031/1(0)
  
  The option --x-name-service-roads=n seems to be no really problem, while 
  enabled, but i'll remove it from my options for the next build, too.
  ;-)
  
  Bernd
  
  Am Montag, 27. April 2015, 20:07:54 schrieb Gerd Petermann:
  Hi Bernd,
  
  pleasse note one important change:
  I've removed the option --x-name-service-roads=n,
  it is no longer optional, mkgmap tries to find a name
  for roads with house numbers. This leads to
  some special effects, e.g. when a small unnamed footway
  is closer to the house than the named service road.
  I think about a new tag like mkgmap:number=false
  that tells mkgmap that a road should not be used for
  address search, e.g. cycleways or motorways.
  This would also speed up the search for the closest roads.
  
  Gerd
  
   From: 
 
  weigelt.bernd@
 
   To: 
 
  mkgmap-dev@.org
 
   Date: Mon, 27 Apr 2015 17:58:45 +0200
   Subject: Re: [mkgmap-dev] error message in Cologne
   
   Hi Gerd
   i'll give it a try asap
   
   thx
   Bernd
   
   Am Sonntag, 26. April 2015, 16:37:35 schrieb Gerd Petermann:
please try r3546, I think it is stable again.
I had to change the program logic to make sure that
special cases with interpolation ways do not
causes assertions.

I have still some known problems, esp.
the program logic for housenumbers assumes now that
city/ zip code info attached to the housenumbers is written to the
  img
file, but that doesn't happen yet (and is quite complicated as it
  seems
to require big changes in the existing program logic)
so address search for roads at city boundaries might still
not work.
  
  -- 
  amarok2 now playing:
  
  
  
  
  ___
  mkgmap-dev mailing list
 
  mkgmap-dev@.org
 
  http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
 
 
 
 
 
 --
 View this message in context: 
 http://gis.19327.n5.nabble.com/error-message-in-Cologne-tp5841730p5842108.html
 Sent from the Mkgmap Development mailing list archive at Nabble.com.
 ___
 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] mkgmap:city empty in large cities

2015-04-28 Thread Gerd Petermann
Hi Ben,

thanks for the patch. Just to make sure:
The additional rules have no effect until one has updated bounds,
so I can commit that without causing trouble, right?

Gerd

Date: Tue, 28 Apr 2015 09:43:03 +0200
From: b...@bagu.org
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] mkgmap:city empty in large cities

Hi Gerd,

I was  a bit wrong with my analysis of Ottawa and Toronto. Toronto and Ottawa 
should be admin level 8 and the 'cities' within Toronto and Ottawa should be 
admin level 9 (as Orleans was already tagged). I've corrected the labelling 
issues in OSM but I didn't add the missing 'city' boundaries inside Ottawa. 

I've attached a patch that corrects address search for Toronto and Ottawa. 
You'll need updated bounds data for this to work but I have confirmed that it's 
working. It would be nice to get this included in mkgamp.

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