Hi Harri,
please the same input data with r4170 and check if you find these POI in your
map:
https://www.openstreetmap.org/node/5377830015
https://www.openstreetmap.org/node/5378259234
These were causing the first 4 messages.
Gerd
Von: mkgmap-dev im Au
Version mkgmap-r4170 was committed by gerd on Fri, 20 Apr 2018
improve logging: use getCenter().toOSMURL() so that coordinates are not
reported in Garmin units.
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4170
___
mkgmap-dev mailing
Version mkgmap-r4169 was committed by gerd on Fri, 20 Apr 2018
don't print error message "Subdivision neg width" or "Subdivision neg height"
for 0 values.
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4169
___
mkgmap-dev mailing list
Hi
I tested some bigger areas like Benelux and Scandinavia and besides the severe
warnings it works fine.
Thanks again
Gr Joris
-Oorspronkelijk bericht-
Van: mkgmap-dev Namens Gerd Petermann
Verzonden: donderdag 19 april 2018 11:50
Aan: Development list for mkgmap
Onderwerp: Re: [m
Hi
These messages will disappear with the negSubDiv.patch posted today in
"area_size() function to be used in points file" thread.
Regards
Ticker
On Thu, 2018-04-19 at 18:37 +0300, Harri Suomalainen wrote:
> Confirmed, I'm getting a lot of these as well (on 4168, those did not
> appear day or tw
Confirmed, I'm getting a lot of these as well (on 4168, those did not
appear day or two ago in previous versions)
SEVERE (Subdivision): tiles_finland/63240006.osm.pbf: Subdivision neg
width 0 min= 1312766 mid= 1312766 max= 1312767 shift= 0 mask= 0 @
2946504/1312766
SEVERE (Subdivision): tiles
Hi Ticker,
thanks for the quick patch.
I don't know if a height or widht value of 0 is OK or not.
If it is I see no reason for a warning, if not it should be handled somewhere
else.
@Steve: Do you know more?
Gerd
Von: mkgmap-dev im Auftrag von Ticker
I was being a bit too severe. Zero and negative width/height
subdivisions previously were allowed through without being noticed,
with the negative quietly overflowing looking positive.
The attached patch downgrades the message for zero size to a warning
but flags an error for neg.
Regards
Ticker
Hi Joris,
thanks for testing. The severe messages were introduced with the latest patches
from Ticker:
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4167
The added source in Subdivision.java:
if (w <= 0) { // think can get this from empty/unbounded maps
Hi Gerd,
I tested this version and I do see a 'severe (subdivision) error', but the map
is created successfully and area_size is available at poi-level.
Does it make sense to already test larger maps or does this first needs
finetuning?
===
Node generated from 29044917 [building=yes, jb
Hi all,
the attached patch is an improved version of the poi_aera.patch from 2017-09-30.
Like the first version it adds the tag mkgmap:cache_area_size to the POI
generated for polygons, but now also for POI generated for multipolygons.
It also changes the value in the tag so that it is rounded to
11 matches
Mail list logo
