Mayoralties
Posted: 18 June 18 12:51 pm
Just wondering . . . Mayor of Locationless ?? In NSW you can be.
The mayor of everywhere and nowhere at the same time.Page 1 of 1
Re: Mayoralties
Posted: 19 June 18 12:14 pm
Sure, why not The mayor of everywhere and nowhere at the same time.
The mayor of everywhere and nowhere at the same time.Re: Mayoralties
Posted: 19 June 18 12:19 pm
That sounds about as plausible as a political promisecaughtatwork wrote:Sure, why not
Re: Mayoralties
Posted: 19 June 18 1:13 pm
Just saying this already exists in the NSW mayoralties......unless there's a place called Locationless...
Re: Mayoralties
Posted: 13 May 23 10:37 pm
I noticed this week that I am mayor of "Unknown" in NSW with 58 cache finds.
Looking at my finds list in a query, the first few/last found unknowns that I have looked into actually have a zone allocated to them on their page. I also tried updating the locality and dZ to see if it changed my figures, but no.
Considering the last found unknown cache was actually in Tenterfield I decided to look further into that. I am mayor of that also with 10 finds. Looking at my query list I can see which 10 are counted.
Looking at the Tenterfield dZ cache list I can see that I've found 18 caches in that area, none of which are moveables.
I'm also pretty sure if the zones or localities or whatever were working right I wouldn't be mayor of the Tenterfield region.
So my questions are:
- Why is this happening?
- Is it something that can be fixed?
Looking at my finds list in a query, the first few/last found unknowns that I have looked into actually have a zone allocated to them on their page. I also tried updating the locality and dZ to see if it changed my figures, but no.
Considering the last found unknown cache was actually in Tenterfield I decided to look further into that. I am mayor of that also with 10 finds. Looking at my query list I can see which 10 are counted.
Looking at the Tenterfield dZ cache list I can see that I've found 18 caches in that area, none of which are moveables.
I'm also pretty sure if the zones or localities or whatever were working right I wouldn't be mayor of the Tenterfield region.
So my questions are:
- Why is this happening?
- Is it something that can be fixed?
Re: Mayoralties
Posted: 15 May 23 9:38 am
Mayoralities are based on the locale not the dZone.
Re: Mayoralties
Posted: 15 May 23 1:58 pm
Okay. Thanks.
Re: Mayoralties
Posted: 15 May 23 3:34 pm
We use Nominatum from OpenStreetMap to get the locale details.
As a real world example use this geocache (one of 1700 or so caches with a locality of Unknown)
https://geocaching.com.au/cache/ga0784
A reverse lookup to get the OSM data using the cache data as the example:
https://nominatim.openstreetmap.org/rev ... 146.349033
We then use a selection of different possible values to get a locale.
First we check for "County" and if it's there we start off using that.
Then we check for "City" and if that's there, we overwrite the "County" value.
We then check "Locality" and if that's there we overwrite "City".
Next is "Village"
Then "Town"
Then "Suburb" overwrite any previous value so at best we get Suburb and at worst we get "County".
If there is no value returned for any of that data we end up with "Unknown".
Looking at the data from a human perspective, we can assume that "Hamlet" would be the best choice for "Beulah" in this example, but we also know (from looking) that Hamlet is often also incorrect, so we're at a point where we cannot guarantee a locale and end up with Unknown.
As the OSM data is sourced from many different places and different countries have different naming rules and conventions someone from the UK who adds data for Tasmania won't include a suburb, they may include a hamlet, or not.
Alas, we do the best we can with what free data we have.
As a real world example use this geocache (one of 1700 or so caches with a locality of Unknown)
https://geocaching.com.au/cache/ga0784
A reverse lookup to get the OSM data using the cache data as the example:
https://nominatim.openstreetmap.org/rev ... 146.349033
Code: Select all
{
"place_id": 137608587,
"licence": "Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",
"osm_type": "way",
"osm_id": 137202866,
"lat": "-41.46348575918817",
"lon": "146.35023610360668",
"display_name": "Beulah Road, Beulah, Kentish, Tasmania, Australia",
"address": {
"road": "Beulah Road",
"hamlet": "Beulah",
"municipality": "Kentish",
"state": "Tasmania",
"ISO3166-2-lvl4": "AU-TAS",
"country": "Australia",
"country_code": "au"
},
"boundingbox": [
"-41.464526",
"-41.462329",
"146.3412233",
"146.3536969"
]
}First we check for "County" and if it's there we start off using that.
Then we check for "City" and if that's there, we overwrite the "County" value.
We then check "Locality" and if that's there we overwrite "City".
Next is "Village"
Then "Town"
Then "Suburb" overwrite any previous value so at best we get Suburb and at worst we get "County".
If there is no value returned for any of that data we end up with "Unknown".
Looking at the data from a human perspective, we can assume that "Hamlet" would be the best choice for "Beulah" in this example, but we also know (from looking) that Hamlet is often also incorrect, so we're at a point where we cannot guarantee a locale and end up with Unknown.
As the OSM data is sourced from many different places and different countries have different naming rules and conventions someone from the UK who adds data for Tasmania won't include a suburb, they may include a hamlet, or not.
Even more confusing is the definition for a Hamet ("A hamlet is a human settlement that is smaller than a town or village") which is strictly an area without a church may end up being wrongly decalred for an area larger or smaller than a suburb.his is an underlying data issue with OSM
Alas, we do the best we can with what free data we have.
addressdetails
Address details in the xml and json formats return a list of names together with a designation label. Per default the following labels may appear:
continent
country, country_code
region, state, state_district, county, ISO3166-2-lvl
municipality, city, town, village
city_district, district, borough, suburb, subdivision
hamlet, croft, isolated_dwelling
neighbourhood, allotments, quarter
city_block, residential, farm, farmyard, industrial, commercial, retail
road
house_number, house_name
emergency, historic, military, natural, landuse, place, railway, man_made, aerialway, boundary, amenity, aeroway, club, craft, leisure, office, mountain_pass, shop, tourism, bridge, tunnel, waterway
postcode