[mkgmap-dev] nearby POIs

Tue May 5 07:32:40 BST 2020

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 at 01D622B7.BA7DE260]

Bicycle stands (0x2f18): don't disappear

N51° 13.685' E4° 24.281'

[cid:image002.jpg at 01D622B7.BA7DE260]

-----Oorspronkelijk bericht-----
Van: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> Namens Ticker Berkin
Verzonden: maandag 4 mei 2020 16:13
Aan: mkgmap development <mkgmap-dev at 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 at jagit.co.uk]

> Sent: 04 May 2020 11:33

> To: Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at 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 at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag

> > von Ticker Berkin <rwb-mkgmap at jagit.co.uk<mailto:rwb-mkgmap at 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 at lists.mkgmap.org.uk<mailto: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<mailto: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<mailto:mkgmap-dev at lists.mkgmap.org.uk>

http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200505/9e9734b6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 83989 bytes
Desc: image001.jpg
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200505/9e9734b6/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 23168 bytes
Desc: image002.jpg
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200505/9e9734b6/attachment-0003.jpg>