Hi Mike & Gerd I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point with, in points: amenity=bench [0x6605 resolution 24 continue] and the resultant map is showing benches close to each other (< 10 m) and, in the log file I'm getting messages like: INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2d02 The Dungeon for element generated from 159255400 INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2a07 Wah Ying for element generated from 468906008 The "generated from" number doesn't seem to correspond to a relevant OSM node and the message doesn't have the trailing "and moved..." that I would have expected. Ticker
Hi Ticker, the new option doesn't work well, Mike and I are working on it. See http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html The log messages are for POIs generated from areas, so the "generated from" ids are either ways or multipolygon relations. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 4. Mai 2020 12:04 An: mkgmap development Betreff: [mkgmap-dev] nearby POIs Hi Mike & Gerd I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point with, in points: amenity=bench [0x6605 resolution 24 continue] and the resultant map is showing benches close to each other (< 10 m) and, in the log file I'm getting messages like: INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2d02 The Dungeon for element generated from 159255400 INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2a07 Wah Ying for element generated from 468906008 The "generated from" number doesn't seem to correspond to a relevant OSM node and the message doesn't have the trailing "and moved..." that I would have expected. Ticker _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
OK, looking up the # as a way instead gives a polygon that matches the description and would generate a typ code as per the message I was more worried about it logging messages about POI with typ codes that I hadn't mentioned in rules and not saying anything about the one I had. I get the same behaviour with just --nearby-poi-rules=0x6605:30 Ticker On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html The log messages are for POIs generated from areas, so the "generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 4. Mai 2020 12:04 An: mkgmap development Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10 m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2d02 The Dungeon for element generated from 159255400 INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2a07 Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant OSM node and the message doesn't have the trailing "and moved..." that I would have expected.
Ticker _______________________________________________ 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
Hi Ticker, there are two closed ways with name="The Dungeon", both have the common node 1713482599 which is tagged entrance=main, so the POIGeneratorHook creates two nodes at the same location and the style creates identical POI for them. One of the duplicates is removed again. This also happened before, but it was logged in StyledConverter. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 4. Mai 2020 12:33 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs OK, looking up the # as a way instead gives a polygon that matches the description and would generate a typ code as per the message I was more worried about it logging messages about POI with typ codes that I hadn't mentioned in rules and not saying anything about the one I had. I get the same behaviour with just --nearby-poi-rules=0x6605:30 Ticker On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html The log messages are for POIs generated from areas, so the "generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 4. Mai 2020 12:04 An: mkgmap development Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10 m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2d02 The Dungeon for element generated from 159255400 INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2a07 Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant OSM node and the message doesn't have the trailing "and moved..." that I would have expected.
Ticker _______________________________________________ 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
Hi Ticker, have you got a --nearby-poi-rules-config option as well? Cheers, Mike -----Original Message----- From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk] Sent: 04 May 2020 11:33 To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] nearby POIs OK, looking up the # as a way instead gives a polygon that matches the description and would generate a typ code as per the message I was more worried about it logging messages about POI with typ codes that I hadn't mentioned in rules and not saying anything about the one I had. I get the same behaviour with just --nearby-poi-rules=0x6605:30 Ticker On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html The log messages are for POIs generated from areas, so the "generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 4. Mai 2020 12:04 An: mkgmap development Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10 m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2d02 The Dungeon for element generated from 159255400 INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2a07 Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant OSM node and the message doesn't have the trailing "and moved..." that I would have expected.
Ticker _______________________________________________ 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
Hi Mike No, I just have --nearby-poi-rules=0x6605:30 Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter Ticker On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers, Mike
-----Original Message----- From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk] Sent: 04 May 2020 11:33 To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes that I hadn't mentioned in rules and not saying anything about the one I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html The log messages are for POIs generated from areas, so the "generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 4. Mai 2020 12:04 An: mkgmap development Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10 m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2d02 The Dungeon for element generated from 159255400 INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x2a07 Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant OSM node and the message doesn't have the trailing "and moved..." that I would have expected.
Ticker _______________________________________________ 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
Hi, I have been testing the nearby poi rules as well with 4485 A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905) On the cmd line --nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete-poi On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not. Can I help testing better by increasing some logging? How could I do that? Kind regards, joris Silo's (0x2a19) don't disappear / N51° 11.992' E4° 24.916' An occasional lift gate (0x6905) does disappear [cid:image001.jpg@01D622B7.BA7DE260] Bicycle stands (0x2f18): don't disappear N51° 13.685' E4° 24.281' [cid:image002.jpg@01D622B7.BA7DE260] -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs Hi Mike No, I just have --nearby-poi-rules=0x6605:30 Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter Ticker On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto:rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi all, attached is a patch that seems to work. I've kept the logging as memory is not such a big problem. I've not yet tested special cases like duplicated barrier nodes or a group of nodes where only some are within the tile boundary. Please check if your problems are solved with this version, a binary is here: http://files.mkgmap.org.uk/download/469/mkgmap.jar Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Dienstag, 5. Mai 2020 08:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs Hi, I have been testing the nearby poi rules as well with 4485 A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905) On the cmd line --nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete-poi On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not. Can I help testing better by increasing some logging? How could I do that? Kind regards, joris Silo’s (0x2a19) don’t disappear / N51° 11.992' E4° 24.916' An occasional lift gate (0x6905) does disappear [cid:image001.jpg@01D622B7.BA7DE260] Bicycle stands (0x2f18): don’t disappear N51° 13.685' E4° 24.281' [cid:image002.jpg@01D622B7.BA7DE260] -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs Hi Mike No, I just have --nearby-poi-rules=0x6605:30 Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter Ticker On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto:rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd That got rid of my multiple benches. Just looking at the log for the few other POI it also got rid of. It would be useful for the log message to include the distance between the POIs Ticker On Tue, 2020-05-05 at 09:19 +0000, Gerd Petermann wrote:
Hi all,
attached is a patch that seems to work. I've kept the logging as memory is not such a big problem. I've not yet tested special cases like duplicated barrier nodes or a group of nodes where only some are within the tile boundary.
Please check if your problems are solved with this version, a binary is here: http://files.mkgmap.org.uk/download/469/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Dienstag, 5. Mai 2020 08:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs
Hi,
I have been testing the nearby poi rules as well with 4485
A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905)
On the cmd line
--nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete-poi
On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not.
Can I help testing better by increasing some logging? How could I do that?
Kind regards, joris
Silo’s (0x2a19) don’t disappear / N51° 11.992' E4° 24.916'
An occasional lift gate (0x6905) does disappear
[cid:image001.jpg@01D622B7.BA7DE260]
Bicycle stands (0x2f18): don’t disappear
N51° 13.685' E4° 24.281'
[cid:image002.jpg@01D622B7.BA7DE260]
-----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs
Hi Mike
No, I just have --nearby-poi-rules=0x6605:30
Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter
Ticker
On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk<mai lto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto: rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: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
Hi In my sample I got 3 POIs removed with codes I didn't specify. Two of these were duplicate areas in OSM and last was INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x3200 gate for element http://www.openstreetmap.org/node/2038594304 which is a {barrier=gate,bicycle=yes,motor_vehicle=private} on a footway. Maybe the footway is split at the gate to handle access and/or mkgmap:road-speed and the POI gets duplicated. Anyway, none of these indicate a problem. Ticker On Tue, 2020-05-05 at 11:03 +0100, Ticker Berkin wrote:
Hi Gerd
That got rid of my multiple benches.
Just looking at the log for the few other POI it also got rid of.
It would be useful for the log message to include the distance between the POIs
Ticker
On Tue, 2020-05-05 at 09:19 +0000, Gerd Petermann wrote:
Hi all,
attached is a patch that seems to work. I've kept the logging as memory is not such a big problem. I've not yet tested special cases like duplicated barrier nodes or a group of nodes where only some are within the tile boundary.
Please check if your problems are solved with this version, a binary is here: http://files.mkgmap.org.uk/download/469/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Dienstag, 5. Mai 2020 08:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs
Hi,
I have been testing the nearby poi rules as well with 4485
A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905)
On the cmd line
--nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete-poi
On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not.
Can I help testing better by increasing some logging? How could I do that?
Kind regards, joris
Silo’s (0x2a19) don’t disappear / N51° 11.992' E4° 24.916'
An occasional lift gate (0x6905) does disappear
[cid:image001.jpg@01D622B7.BA7DE260]
Bicycle stands (0x2f18): don’t disappear
N51° 13.685' E4° 24.281'
[cid:image002.jpg@01D622B7.BA7DE260]
-----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs
Hi Mike
No, I just have --nearby-poi-rules=0x6605:30
Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter
Ticker
On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk<m ai lto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.ht ml
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto: rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: 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
Hi Ticker, the node http://www.openstreetmap.org/node/2038594304 is really duplicated, see http://www.openstreetmap.org/node/5364865281 Anyway, it might be a good special case to check if routing works. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 5. Mai 2020 17:15 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs Hi In my sample I got 3 POIs removed with codes I didn't specify. Two of these were duplicate areas in OSM and last was INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x3200 gate for element http://www.openstreetmap.org/node/2038594304 which is a {barrier=gate,bicycle=yes,motor_vehicle=private} on a footway. Maybe the footway is split at the gate to handle access and/or mkgmap:road-speed and the POI gets duplicated. Anyway, none of these indicate a problem. Ticker On Tue, 2020-05-05 at 11:03 +0100, Ticker Berkin wrote:
Hi Gerd
That got rid of my multiple benches.
Just looking at the log for the few other POI it also got rid of.
It would be useful for the log message to include the distance between the POIs
Ticker
On Tue, 2020-05-05 at 09:19 +0000, Gerd Petermann wrote:
Hi all,
attached is a patch that seems to work. I've kept the logging as memory is not such a big problem. I've not yet tested special cases like duplicated barrier nodes or a group of nodes where only some are within the tile boundary.
Please check if your problems are solved with this version, a binary is here: http://files.mkgmap.org.uk/download/469/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Dienstag, 5. Mai 2020 08:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs
Hi,
I have been testing the nearby poi rules as well with 4485
A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905)
On the cmd line
--nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete-poi
On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not.
Can I help testing better by increasing some logging? How could I do that?
Kind regards, joris
Silo’s (0x2a19) don’t disappear / N51° 11.992' E4° 24.916'
An occasional lift gate (0x6905) does disappear
[cid:image001.jpg@01D622B7.BA7DE260]
Bicycle stands (0x2f18): don’t disappear
N51° 13.685' E4° 24.281'
[cid:image002.jpg@01D622B7.BA7DE260]
-----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs
Hi Mike
No, I just have --nearby-poi-rules=0x6605:30
Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter
Ticker
On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk<m ai lto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.ht ml
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto: rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: 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
Hi Gerd I missed this. I looked at the footway from the gate and it had the expected gate. The other gate is on the edge of the park polygon! Ticker On Tue, 2020-05-05 at 16:18 +0000, Gerd Petermann wrote:
Hi Ticker,
the node http://www.openstreetmap.org/node/2038594304 is really duplicated, see http://www.openstreetmap.org/node/5364865281
Anyway, it might be a good special case to check if routing works.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 5. Mai 2020 17:15 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs
Hi
In my sample I got 3 POIs removed with codes I didn't specify. Two of these were duplicate areas in OSM and last was
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x3200 gate for element http://www.openstreetmap.org/node/2038594304
which is a {barrier=gate,bicycle=yes,motor_vehicle=private} on a footway. Maybe the footway is split at the gate to handle access and/or mkgmap:road-speed and the POI gets duplicated.
Anyway, none of these indicate a problem.
Ticker
On Tue, 2020-05-05 at 11:03 +0100, Ticker Berkin wrote:
Hi Gerd
That got rid of my multiple benches.
Just looking at the log for the few other POI it also got rid of.
It would be useful for the log message to include the distance between the POIs
Ticker
On Tue, 2020-05-05 at 09:19 +0000, Gerd Petermann wrote:
Hi all,
attached is a patch that seems to work. I've kept the logging as memory is not such a big problem. I've not yet tested special cases like duplicated barrier nodes or a group of nodes where only some are within the tile boundary.
Please check if your problems are solved with this version, a binary is here: http://files.mkgmap.org.uk/download/469/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Dienstag, 5. Mai 2020 08:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs
Hi,
I have been testing the nearby poi rules as well with 4485
A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905)
On the cmd line
--nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete -poi
On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not.
Can I help testing better by increasing some logging? How could I do that?
Kind regards, joris
Silo’s (0x2a19) don’t disappear / N51° 11.992' E4° 24.916'
An occasional lift gate (0x6905) does disappear
[cid:image001.jpg@01D622B7.BA7DE260]
Bicycle stands (0x2f18): don’t disappear
N51° 13.685' E4° 24.281'
[cid:image002.jpg@01D622B7.BA7DE260]
-----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs
Hi Mike
No, I just have --nearby-poi-rules=0x6605:30
Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter
Ticker
On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk <m ai lto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759. ht ml
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailt o: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto: rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: 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
Hi Ticker, feel free to correct it. I've downloaded the data. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 5. Mai 2020 18:49 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs Hi Gerd I missed this. I looked at the footway from the gate and it had the expected gate. The other gate is on the edge of the park polygon! Ticker On Tue, 2020-05-05 at 16:18 +0000, Gerd Petermann wrote:
Hi Ticker,
the node http://www.openstreetmap.org/node/2038594304 is really duplicated, see http://www.openstreetmap.org/node/5364865281
Anyway, it might be a good special case to check if routing works.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 5. Mai 2020 17:15 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs
Hi
In my sample I got 3 POIs removed with codes I didn't specify. Two of these were duplicate areas in OSM and last was
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler ../mapHants/74210001.osm.pbf: Removed duplicate POI with type 0x3200 gate for element http://www.openstreetmap.org/node/2038594304
which is a {barrier=gate,bicycle=yes,motor_vehicle=private} on a footway. Maybe the footway is split at the gate to handle access and/or mkgmap:road-speed and the POI gets duplicated.
Anyway, none of these indicate a problem.
Ticker
On Tue, 2020-05-05 at 11:03 +0100, Ticker Berkin wrote:
Hi Gerd
That got rid of my multiple benches.
Just looking at the log for the few other POI it also got rid of.
It would be useful for the log message to include the distance between the POIs
Ticker
On Tue, 2020-05-05 at 09:19 +0000, Gerd Petermann wrote:
Hi all,
attached is a patch that seems to work. I've kept the logging as memory is not such a big problem. I've not yet tested special cases like duplicated barrier nodes or a group of nodes where only some are within the tile boundary.
Please check if your problems are solved with this version, a binary is here: http://files.mkgmap.org.uk/download/469/mkgmap.jar
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Dienstag, 5. Mai 2020 08:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs
Hi,
I have been testing the nearby poi rules as well with 4485
A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905)
On the cmd line
--nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete -poi
On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not.
Can I help testing better by increasing some logging? How could I do that?
Kind regards, joris
Silo’s (0x2a19) don’t disappear / N51° 11.992' E4° 24.916'
An occasional lift gate (0x6905) does disappear
[cid:image001.jpg@01D622B7.BA7DE260]
Bicycle stands (0x2f18): don’t disappear
N51° 13.685' E4° 24.281'
[cid:image002.jpg@01D622B7.BA7DE260]
-----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs
Hi Mike
No, I just have --nearby-poi-rules=0x6605:30
Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter
Ticker
On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk <m ai lto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759. ht ml
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailt o: mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto: rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto: 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
FWIW: I have done some testing as well. Or: trying to understand. *Use Case (1): Area* Area: building=hotel, tourism=hotel Node: tourism=hotel Area2poi + Node > 2 POI's (Hotel), 7 meters distance. NOT Resolved, by any of next options: - 0x2b01/named:3, 0x2b01/unnamed:3 - */named:3, */unnamed:3 - 0x2b01/named:30, 0x2b01/unnamed:30 - */named:30, */unnamed:30 *Use Case (2): Way* Way: [historic=ruins] + [tourism=attraction] (6.38 meters). Line2poi > start, mid, end > 3 POI's. Expected, NOT Resolved by: - */named:3, */unnamed:3 Not Expected, Resolved by: - */named:30, */unnamed:30 (Distance = 30, way is 6.38 meters: 30 > 6.38) Not expected, Resolved by: - 0x2c03/named:30, 0x2c03/unnamed:30 (Distance = 30, way is 6.38 meters: 30
6.38)
Remark: I see only one POI on the Map. Which is OK. But when Searching (in BaseCamp) I see two POI's (in Index). Garmin? When I Select 2x POI and "Create Waypoint" (one after the other) I only get one Waypoint. Garmin? And... Waypoint icon (library) is different from MY - custom - icon ("historical building" ). Garmin? *Use Case (3): Nodes* Unrelated Nodes: [natural=tree] Patch will Resolve (!) is OK. Distance = x is Respected (!) is OK. IMO-Remark (1): Testing for bench, picnic_table is (IMO) testing only. Deleting nearby POI bench/picnic_table is - also – a loss of – useful – information. But it's a mkgmap-Renderers prerogative to either delete or not delete. IMO-Remark (2): Deleting nearby POI bench/picnic_table would be OK (IMO) if a COUNT can be added to the remaining POI. Similar to: "capacity=xx". But even then: I won't delete nearby POI bench/picnic_table. I also won't delete nearby buildings; -) Remark/Question (3): Rendering [natural=tree] (restricted by IS_IN() function or having species=*) and declutter by nearby-poi-rules is only OK if (and only IF) I can remove trees (and barriers) from index. I am not capable to get this to work: *poi-excl-index=0x6618* (or: poi-excl-index=0x6600-x6700). Therefore: rendering trees will make searching impossible because of the huge number of trees (search for ALL POI). *Use Case (4): Duplicate "main feature tags".* "Ideally, every OSM element or object should be tagged with only one main feature tag, to represent a single on-the-ground feature" https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element One Node having: tourism=hotel (0x2b01) OR amenity=restaurant (0x2a0?) + internet_access=wlan (0x2f12) will be Rendered by an Overlapping (Merged, Duplicated, Clashing) POI . This is a Renderer Error since [internet_access=wlan] should be considered as a property to hotel/restaurant, not as an – independent - on-the-ground feature POI. Error: Overlapping (Merged, Duplicated, Clashing) POI cannot be – correctly/easily - interpreted by a user and is therefore useless Rendering (on the Map). One Node having: [tourism=hotel] + [amenity=restaurant]: (or [tourism=viewpoint] + [amenity=bench]) is to be considered as Bad OSM Mapping: one main feature tag should be one node. But this is a fact of OSM life. Two "main feature tags" on "one node" will not be rendered unless "continue" is used by Renderer. In which case an Overlapping (Merged, Duplicated, Clashing, Error) POI will be rendered. (@Gerd: last week I was not able to reproduce (Hotel + continue) + Restaurant. Restaurant was "blocked"/"captured" by: "tourism=* & tourism!=no [0x2c0d resolution 24]", which is the "red dot" showing in hotel (0x2b01) + wlan (0x2f12) + unspecified tourism (0x2c0d) POI's). Two "main feature tags" on "one node" will not be rendered (which is preventing an "Overlap-Error"), but this will also imply a loss of information: a "Hotel Restaurant" will be rendered as either [hotel] or [restaurant], a "bench with a view" will be rendered as either bench or as viewpoint. This was my Feature Request: Move/Separate/Split "Overlapping/Merged/Duplicated/Clashing Error" POI, representing multiple "main feature tags". AnkEric (Eric) -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
Hello Gerd, I retested this patch with remarkable good results! Thanks for the work. It's a lovely feature which gives more space to lablenames and poi's which makes the difference. Kind regards Joris I switched from cmdline to config file and implemented #*/named:100 #Any with a name #*/unnamed:100 #Any without a name 0x641d-0x641f:20 #Fixme request 0x2d10-0x2d12:10 #Entrances 0x6602:40 #Bunker 0x2f18:10 #Bicycle parking 0x2f0b:30 #Car parking 0x2a19:20 #Silo 0x2a09:10 #Bench 0x2a0b:20 #Bin 0x2a0c:20 #Container 0x2a0e:20 #Recycling 0x2803:20 #Viewpoint 0x2a13:10 #Car charger -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Gerd Petermann Verzonden: dinsdag 5 mei 2020 11:19 Aan: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs Hi all, attached is a patch that seems to work. I've kept the logging as memory is not such a big problem. I've not yet tested special cases like duplicated barrier nodes or a group of nodes where only some are within the tile boundary. Please check if your problems are solved with this version, a binary is here: http://files.mkgmap.org.uk/download/469/mkgmap.jar Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo@hotmail.com> Gesendet: Dienstag, 5. Mai 2020 08:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] nearby POIs Hi, I have been testing the nearby poi rules as well with 4485 A while I struggled thinking misconfiguration because I see nothing happening but then after extending the ranges, an occasional poi disappears. (toilet 0x2a0d, busstop 0x2f17, custom lift-gate 0x6905) On the cmd line --nearby-poi-rules=*/unnamed:100:delete-poi,*/named:100:delete-poi On my densed big city area (Antwerpen) In that case I expect maybe a couple of thousand benches, trees and bicycle parkings disappear which do not. Can I help testing better by increasing some logging? How could I do that? Kind regards, joris Silo's (0x2a19) don't disappear / N51° 11.992' E4° 24.916' An occasional lift gate (0x6905) does disappear [cid:image001.jpg@01D622B7.BA7DE260] Bicycle stands (0x2f18): don't disappear N51° 13.685' E4° 24.281' [cid:image002.jpg@01D622B7.BA7DE260] -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 4 mei 2020 16:13 Aan: mkgmap development <mkgmap-dev@lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] nearby POIs Hi Mike No, I just have --nearby-poi-rules=0x6605:30 Gerd has explained why I see a message from NearbyPoiHandler about a POI for that wasn't 0x6605 - the logging of the removal of an exact duplicate has moved from StyledConverter Ticker On Mon, 2020-05-04 at 14:35 +0100, Mike Baggaley wrote:
Hi Ticker, have you got a --nearby-poi-rules-config option as well?
Cheers,
Mike
-----Original Message-----
From: Ticker Berkin [mailto:rwb-mkgmap@jagit.co.uk]
Sent: 04 May 2020 11:33
To: Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>>
Subject: Re: [mkgmap-dev] nearby POIs
OK, looking up the # as a way instead gives a polygon that matches the
description and would generate a typ code as per the message
I was more worried about it logging messages about POI with typ codes
that I hadn't mentioned in rules and not saying anything about the one
I had.
I get the same behaviour with just --nearby-poi-rules=0x6605:30
Ticker
On Mon, 2020-05-04 at 10:14 +0000, Gerd Petermann wrote:
Hi Ticker,
the new option doesn't work well, Mike and I are working on it. See
http://gis.19327.n8.nabble.com/nearby-POIs-tp5962630p5964759.html
The log messages are for POIs generated from areas, so the
"generated from" ids are either ways or multipolygon relations.
Gerd
________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> im Auftrag
von Ticker Berkin <rwb-mkgmap@jagit.co.uk<mailto:rwb-mkgmap@jagit.co.uk>>
Gesendet: Montag, 4. Mai 2020 12:04
An: mkgmap development
Betreff: [mkgmap-dev] nearby POIs
Hi Mike & Gerd
I'm trying --nearby-poi-rules=0x6605:30:merge-at-mid-point
with, in points:
amenity=bench [0x6605 resolution 24 continue]
and the resultant map is showing benches close to each other (< 10
m)
and, in the log file I'm getting messages like:
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2d02
The Dungeon for element generated from 159255400
INFO: uk.me.parabola.mkgmap.osmstyle.NearbyPoiHandler
../mapHants/74210001.osm.pbf: Removed duplicate POI with type
0x2a07
Wah Ying for element generated from 468906008
The "generated from" number doesn't seem to correspond to a relevant
OSM node and the message doesn't have the trailing "and moved..."
that
I would have expected.
Ticker
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (5)
-
AnkEric -
Gerd Petermann -
Joris Bo -
Mike Baggaley -
Ticker Berkin