Suggestion for more flexibility in locator part of mkgmap

Hi Greg, Just to clarify ... the admin_levels for Ireland described here http://wiki.openstreetmap.org/wiki/Ireland/Boundaries#Boundary_Types don't seem to mention things like village boundaries - there's a big gap between admin_level=8 and admin_level=10. In situations like this, maybe the locator could be more flexible and use other kinds of boundaries too. Regards, Cliff

Hi Greg,
Just to clarify ... the admin_levels for Ireland described here http://wiki.openstreetmap.org/wiki/Ireland/Boundaries#Boundary_Types don't seem to mention things like village boundaries - there's a big gap between admin_level=8 and admin_level=10.
That's ok. OSM must deal with local specialities because they just exist. And I think that's a chance for the new locator to become more flexible.
In situations like this, maybe the locator could be more flexible and use other kinds of boundaries too.
In principle that's quite easy to do if these other boundaries are closed polygons or complete multipolygons. Please give some more details how the other kind of boundaries are mapped. Maybe you can give some examples with the real OSM ids of the special boundaries. Which tags do they use if they don't use admin_level=N? Do they cover complete polygons or are they mostly incomplete?
Regards, Cliff
Have fun! WanMil

Just to clarify ... the admin_levels for Ireland described here http://wiki.openstreetmap.org/wiki/Ireland/Boundaries#Boundary_Types don't seem to mention things like village boundaries - there's a big gap between admin_level=8 and admin_level=10.
That's ok. OSM must deal with local specialities because they just exist. And I think that's a chance for the new locator to become more flexible.
In situations like this, maybe the locator could be more flexible and use other kinds of boundaries too.
In principle that's quite easy to do if these other boundaries are closed polygons or complete multipolygons.
Sorry for resurrecting this old thread. Many rural villages, hamlets (and even some small towns) are not administrative areas or have their own town council etc so administrative boundaries are not the best choice here to be able to assign addresses correctly. To make locator more flexible for assiging addresses, could it also be extended to also support the place tag? eg mkgmap:place:village mkgmap:place:hamlet mkgmap:place:locality mkgmap:place:suburb etc Thanks -- View this message in context: http://gis.19327.n5.nabble.com/Suggestion-for-more-flexibility-in-locator-pa... Sent from the Mkgmap Development mailing list archive at Nabble.com.

Sorry for resurrecting this old thread. Many rural villages, hamlets (and even some small towns) are not administrative areas or have their own town council etc so administrative boundaries are not the best choice here to be able to assign addresses correctly.
To make locator more flexible for assiging addresses, could it also be extended to also support the place tag? eg mkgmap:place:village mkgmap:place:hamlet mkgmap:place:locality mkgmap:place:suburb etc
Thanks
How should mkgmap assign the mkgmap:place:* tags? Should it use the nearest algorithm? In this case isn't it rather the same like using location-autofill=nearest? Can you please give a real example in which this helps? I want to understand the idea. WanMil

WanMil wrote
How should mkgmap assign the mkgmap:place:* tags? Should it use the nearest algorithm? In this case isn't it rather the same like using location-autofill=nearest?
Can you please give a real example in which this helps? I want to understand the idea.
WanMil
Currently the locator only handles administrative boundary polygons. It would be more flexible if it also supported place polygons. eg We have a place=village area defined for Ballina village. An admin relation does not exist here as the village is not an administrative area in its own right. http://www.openstreetmap.org/browse/way/123401178 Ballina swimming pool http://www.openstreetmap.org/browse/node/510911604 is being assigned the address Ballina Outdoor Swimming Pool Roolagh, County Tipperary, Ireland Roolagh is a place=locality node outside the village boundary: http://www.openstreetmap.org/browse/node/566834144 If mkgmap Locator also supported place polygons we woudl be able to correctly assign the village name to addresses. -- View this message in context: http://gis.19327.n5.nabble.com/Suggestion-for-more-flexibility-in-locator-pa... Sent from the Mkgmap Development mailing list archive at Nabble.com.

WanMil wrote
How should mkgmap assign the mkgmap:place:* tags? Should it use the nearest algorithm? In this case isn't it rather the same like using location-autofill=nearest?
Can you please give a real example in which this helps? I want to understand the idea.
WanMil
Currently the locator only handles administrative boundary polygons. It would be more flexible if it also supported place polygons.
eg We have a place=village area defined for Ballina village. An admin relation does not exist here as the village is not an administrative area in its own right.
http://www.openstreetmap.org/browse/way/123401178
Ballina swimming pool http://www.openstreetmap.org/browse/node/510911604 is being assigned the address
Ballina Outdoor Swimming Pool Roolagh, County Tipperary, Ireland
Roolagh is a place=locality node outside the village boundary: http://www.openstreetmap.org/browse/node/566834144
If mkgmap Locator also supported place polygons we woudl be able to correctly assign the village name to addresses.
Why is the place polygon not tagged with boundary=administrative and an appropriate admin_level? Is this specific for Ireland? WanMil

WanMil wrote
Why is the place polygon not tagged with boundary=administrative and an appropriate admin_level? Is this specific for Ireland?
Because not all places are administrative areas. The village is not an administrative area. Places with town/city councils etc are administrative areas. -- View this message in context: http://gis.19327.n5.nabble.com/Suggestion-for-more-flexibility-in-locator-pa... Sent from the Mkgmap Development mailing list archive at Nabble.com.

WanMil wrote
Why is the place polygon not tagged with boundary=administrative and an appropriate admin_level? Is this specific for Ireland?
Because not all places are administrative areas. The village is not an administrative area. Places with town/city councils etc are administrative areas.
Ok. It is possible to change the mkgmap locator to also use place polygons. Anyhow I don't know when I will have time for that. In general I would like to have a statement of the OSM community how the names of cities, regions etc. for an address search can be extracted from the OSM data. WanMil
participants (3)
-
Clifford Nolan
-
IrlJIdel
-
WanMil