logo separator

[mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to split at

From Gerd Petermann GPetermann_muenchen at hotmail.com on Sat Jan 14 10:21:02 GMT 2017

Hi Walter,

okay, now I understand. All messages produced with the logger have unix style endings, while
"normal" messages produced with system.out.* have the system dependent line endings.
I've found one place in UsefullFormatter which used a hard coded '\n' and changed that in r3753.
Hope that fixes this problem.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Walter Schlögl <Walter.Schloegl-Resch at aon.at>
Gesendet: Samstag, 14. Januar 2017 10:44:18
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to        split at

Hi Gerg,

I am using the command 2>>Filename.txt

Since all other lines in this file are having the correct cr-lf end
and only these lines are having the unix lf end without cr
I am sure that the command itself is working correct
and mkgmap is generating the wrong line end for this message.

Yes, I am generating a POI for every 5th addr tag.
At these places there are nearly hundred of addr tags at the same location.
I could identify these 18 places and suppress only those addr tags,
but I would prefer a more general solution if there is one.

This command generates visible addr POIs for the housenumbers 1, 5, 10, 15,
20, ....
but only, if there is no building.

(addr:housenumber~'.*0' | addr:housenumber~'.*5' | addr:housenumber='1' |
addr:unit=* | addr:door=*)
                { name     '${addr:unit}/${addr:door}' |
                      '${addr:housenumber}/${addr:unit}' |
                     '${addr:door}' |
                     '${addr:unit}' |
                     '${addr:housenumber}'}                    [0x1E04
resolution 24]

If there is a building, it will get the addr via --poi-address.

Walter


-----Ursprüngliche Nachricht-----
From: Gerd Petermann
Sent: Saturday, January 14, 2017 7:36 AM
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to
split at

Hi Walter,

hmm, all log messages are written with the same routine, each message is one
line,
and they should all have the correct line ending.
When you say logfile, is that the output written to stderr or do you use
java option
like -Dlog.config=logging.properties to configure the details?
See http://wiki.openstreetmap.org/wiki/Mkgmap/dev#Enabling_Debugging
for more info about that.
If you use a command like  this
java -jar mkgmap.jar .... > mkgmap.log 2>mgkmap.err
the two files mkgmap.log and mkgmap.err should also have cr-lf style.

Reg. the message itself : It seems that your style genenrates a POI for each
of the 271 addr:xxx
nodes in this area. I think the algo in MapSplitter can be changed to handle
that. Will try that later.

Gerd



________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
Walter Schlögl <Walter.Schloegl-Resch at aon.at>
Gesendet: Freitag, 13. Januar 2017 23:37:12
An: Development list for mkgmap
Betreff: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to split
at

If there are too many address tags (or maybe also other tags) mkgmap
generates a lot of error messages.
For all these error messages the <CR><LF> is missing at the end, if it runs
under windows.
Would it be possible to add the correct EOL chars so that the logfile keeps
it's readability?
All other messages outputted with echo are having a correct <CR><LF> at the
end.

If anybody has a solution how to reduce these errors it would also be
helpfull.
Here are the areas I have found in my logfile.

SCHWERWIEGEND (MapSplitter): 50120092.o5m: Area too small to split at
http://www.openstreetmap.org/?mlat=52.218511&mlon=6.881390&zoom=17 (reduce
the density of points, length of lines, etc.)
SCHWERWIEGEND (MapBuilder): 50120092.o5m: Too many POIs at location
http://www.openstreetmap.org/?mlat=52.218554&mlon=6.881454&zoom=17 - 210-901
Emmastraat will be ignored
...

More areas are in attached logfile excerpt.

Walter
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


More information about the mkgmap-dev mailing list