Hi Gerd, you are right, there is more code to add the addr for housenumber 2,3,4,6,...9,11,... mkgmap_POI_addr=* & !(addr:housenumber~'.*0' | addr:housenumber~'.*5' | addr:housenumber='1') & name!=* { add name='${mkgmap_POI_addr}' } [0x1604 resolution 24] If there are any splitter parameter relevant for this error message, I can provide that. Now I am suppressing all adresses that are currently causing this error. It covers Enschede, Wageningen, Amsterdam, Zaandam, Utrecht, Rotterdam addr:postcode=7513BH & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=6708PG & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=6708GA & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=6708AK & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=6706HC & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=1079NR & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=1503EE & addr:street=Pharus { delete addr:housenumber } addr:postcode=3526WH & addr:street=Europaplein { delete addr:housenumber } addr:postcode=3526WP & addr:street=Europaplein { delete addr:housenumber } addr:postcode=3571SM & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=3571AD & addr:housenumber~'.*-.*' { delete addr:housenumber } addr:postcode=3706AA & addr:street='Laan van Vollenhove' {delete addr:housenumber } addr:postcode=3067VM & addr:street='Hendrick Staetsweg' { delete addr:housenumber } addr:postcode=3024NK & addr:street='Kees van Dongenhof' { delete addr:housenumber } addr:postcode=3012CC & addr:street='Kruisplein' { delete addr:housenumber } addr:postcode=3072DB & addr:street='Laan op Zuid' { delete addr:housenumber } addr:postcode=3032CG & addr:street='Hofdijk' { delete addr:housenumber } Walter -----Ursprüngliche Nachricht----- From: Gerd Petermann Sent: Sunday, January 15, 2017 10:03 AM To: Development list for mkgmap Subject: Re: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to split at Hi Walter, I tried to reproduce the error messages by adding the rule to points in the default style but (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] that doesn't produce such a large number of POI in a small area. I assume you have other rules which add one POI for each of the 271 addr:housenumber nodes near 52.218652 6.881467. Anyhow, I will try to change the code to avoid that error message. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Walter Schlögl <Walter.Schloegl-Resch@aon.at> Gesendet: Samstag, 14. Januar 2017 19:13:09 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to split at Hi Gerd, I am using the housenumber option, but only if there is a building. If there is an addr tag without building I want to see every 5th housenumber directly in the map without clicking and the other numbers as hidden POI with 1x1 pixel, so that I can show the number with clicking. Walter -----Ursprüngliche Nachricht----- From: Gerd Petermann Sent: Saturday, January 14, 2017 6:32 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to split at Hi Walter, thanks for the feedback. I am using Windows, but all my favorite tools are able to handle unix style, so I never noticed. I wonder why you create those POI, is the --hosuenumbers option not working for you? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Walter Schlögl <Walter.Schloegl-Resch@aon.at> Gesendet: Samstag, 14. Januar 2017 18:24:07 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to split at Hi Gerd, many thanks, the logfile looks much better now with the windows EOL style. It seems, that not so many mkgmap users are using windows, otherwise this would have been found much earlier. I am now working on a supressions of those many adresses at the same place. It looks as if somebody has tagged every door on every level of these buildings. Walter -----Ursprüngliche Nachricht----- From: Gerd Petermann Sent: Saturday, January 14, 2017 11:21 AM To: Development list for mkgmap Subject: Re: [mkgmap-dev] SCHWERWIEGEND (MapSplitter): Area too small to split at 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@lists.mkgmap.org.uk> im Auftrag von Walter Schlögl <Walter.Schloegl-Resch@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@lists.mkgmap.org.uk> im Auftrag von Walter Schlögl <Walter.Schloegl-Resch@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@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 _______________________________________________ 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 _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev