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

Reply via email to