There are several conflicting perspectives here. My objective is to give addresses to people who will never have one. Last year I was living in a city in Africa ( 6GVW2FXH+4H <https://www.openstreetmap.org/#map=17/7.04700/38.47910>) with a population of a half a million people. None of the streets and roads have names, nor are there any house numbers in that city or any of the surrounding rural areas where most of the population lives. As the population in Africa migrates to urban settings in the next few decades the cities will be expanding greater than governments' ability to create infrastructure, including addresses, to support the populations. Plus codes is a practical solution to provide addresses that are usable by both humans and machines. It is interesting that this effort for addressing is being trashed because it is savvy technology. Plus code can be calculated on the fly, but if they are to be used we will need to have hardcopy maps with the addresses that can be used to direct aid workers to a specific location. Just because something could be done doesn't mean that it will or should be done. If we provide easy access to an address as an attribute for OSM it will get used. I don't understand what problems would be created by adding valuable information to an address point. So far I see no practical solution for giving an address to the billions of people that do not have one, just because a tag value has intelligence and practical value is no reason to throw it away.
On Fri, Aug 10, 2018 at 6:05 AM, john whelan <jwhelan0...@gmail.com> wrote: > A simple stopgap solution would be a program that converted one to the > other where the result could be cut and pasted into another program. They > are probably called apps these days. > > If you know the code it would give you the lat and long in a format that > could be searched by Nominatim. > > Grabbing the lat and long from the map and converting it needs a process. > > Suggestions? > > Thanks John > > On Fri, 10 Aug 2018, 8:58 am john whelan, <jwhelan0...@gmail.com> wrote: > >> I would agree the import should be reverted. The data is redundant and >> there is a danger that it might not be correct. The pure lat and long data >> already in OSM can be used to calculate the code. >> >> It does add weight to the idea of making them searchable perhaps with a >> JOSM plugin and support in OSMand for off line use and Nominatim for on >> line use. >> >> Cheerio John >> >> On Fri, 10 Aug 2018, 8:50 am Michael Reichert, <osm...@michreichert.de> >> wrote: >> >>> Hi, >>> >>> Am 2018-08-09 um 22:48 schrieb Vao Matua: >>> > The Tanzania Development trust has calculated the Plus Code addresses >>> for >>> > 17 million building points in Tanzania and have added a sample village >>> > (1800 points) as a test. >>> > https://www.openstreetmap.org/changeset/59213224 >>> > >>> > The Python code on Github works great to calculate Plus Codes. >>> > >>> > We did used these tags: >>> > addr:pluscode:full (the 8+2 digit full Plus Code) >>> > addr:pluscode:area (the first 4 digits of the full Plus Code which is >>> a 1 >>> > degree by 1 degree lat long area) >>> > addr:pluscode:local (the second 4 digits + last 2 digits which used >>> with a >>> > local name becomes the local address) >>> >>> There is no need for this data in OSM because the data can be retrieved >>> automatically from latitude and longitude (plain coordinates) which are >>> already assigned to anything which has a location on the planet. >>> >>> Adding Plus Code tags to OSM objects is as useful as adding latitude=* >>> and longitude=* or any other coordinate system which can be calculated >>> from latitude and longitude. >>> >>> This import should be reverted. >>> >>> Best regards >>> >>> Michael >>> >>> >>> -- >>> Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten >>> ausgenommen) >>> I prefer GPG encryption of emails. (does not apply on mailing lists) >>> >>> _______________________________________________ >>> talk mailing list >>> talk@openstreetmap.org >>> https://lists.openstreetmap.org/listinfo/talk >>> >>
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
