[mkgmap-dev] nearby POIs

Mon May 4 14:35:31 BST 2020

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>
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> im Auftrag
> von Ticker Berkin <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
> 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