[mkgmap-dev] is_in filter

Sat Feb 4 15:37:11 GMT 2017

Yes, I think that would work.
I forgot to mention another use case. highway>residential which lies 
inside residential areas. They have typically maxspeed lower than 
outside residential areas, but are not correctly tagged in many cases. 
Proposed filter could be used to lower maxspeed for those ways.

El 04/02/17 a las 16:18, Gerd Petermann escribió:
> Hi Carlos,
>
> I see a performance problem if mkgmap has to evaluate that for each element.
> I think it would be better to have a special tag like mkgmap:remove-if-in=<type>
> which would tell mkgmap to find out if the object lies (completely) within a polygon
> that has the given type. This can happen after processing all polygon elements.
> The polygons with the given type(s) could be placed in a spatial index if performance impact
> is too heavy.
> Do you think that would work as well?
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam at orangecorreo.es>
> Gesendet: Samstag, 4. Februar 2017 16:06:20
> An: Development list for mkgmap
> Betreff: [mkgmap-dev] is_in filter
>
> One matter that has been discussed several times on this list is the
> need to remove buildings. While removing buildings is becoming
> absolutely necessary in many cities, due to massive building imports, it
> may be quite convenient to keep them at rural or low densely populated
> areas. Would it be possible to have a filter to know if a building is
> inside/outside an area tagged landuse=residential, so that a different
> rendering may be applied. Ideally area size could be also evaluated.
> Perhaps some logic currently existing in mkgmap, used to assign
> addresses from bounds, could be reused.