This is a bit of comparing apples to oranges. A plus code with a locality is meant to function like street addresses. If you write down a normal address (e.g. 123 Street) and the city gets renamed, you have the same problem of the address becoming invalid. If you rely on locality info and it changes, there's not much you can do about it.
If you want to guarantee that the location reference stays valid after 50 years, you'll want to use the global plus code (5PFWFWP9+J8 for your example address). This is a direct conversion from lat/long coordinates and doesn't rely on locality information. On Fri, Dec 28, 2018 at 8:34 AM MG <mapg...@outlook.com> wrote: > Hello. > > I think it will continue to exist. and it will remain a valid place-name. > > I don't think pluscodes has reached the point where it tries to be dynamic > and constantly update its self to confirm to real time changes in place > names. > If it is written down in a book and you look it up again 50 years later it > will still be able to locate it . > > > Sure its not as ubiquitous as coordinates. That being said. Coordinates > can be equally difficult to decipher when you don't know the coordinate > system, and datum etc used to collect them. In many parts of the world > there are localized coordinate systems used, which will differ and you need > to know how to make transformations across a multitude of projections and > circumstances. > > > Also i don't see this as a unique problem to plus-codes, it a geography > problem that affects many data-sets and placenames. When boundaries get > redistricted it just makes it difficult to compare a snapshot in time to a > different snapshot in time after the redistricting has taken place > especially when they are spatially significantly different and there is not > enough granular data reconstitute those changes accurately. As long as you > are tracking the change to the data set you will be able to geographically > account for the spatial changes. And you'll know that that location that > doesn't exist in today data but it existed in the 1958 version of the > data. > > Anyway. Your scenario would only be a problem if the pluscodes where in a > constant state of change, then there would need to be away to search > earlier iterations of plus codes. > > My two cents . > > > > > > > > > > > > > > On Friday, 28 December 2018 18:42:21 UTC+3, Cx wrote: >> >> Yea but what if I write it down in a book and nigga 50 years later its >> not a valid address... >> >> On Friday, December 28, 2018 at 8:50:49 PM UTC+8, Andreas B wrote: >>> >>> If "Strelley WA, Australia" ceases to exist *and* everyone forgets >>> about its former existence in some location, then it will be impossible to >>> retrieve the exact location, yes. It could still be narrowed down to either >>> one of the several hundred "????FWP9+J8" locations in Australia, or even >>> the ~120 of them in "WA, Australia", but probably not more than that. >>> >>> I wonder how realistic that really is, though. What would need to happen >>> so that everyone forgets about Strelley, but not about the way plus codes >>> are generated. Generally speaking, any set of coordinates is only useful if >>> people still know how to decipher them: Where is 0.0/x? Where is x/0.0? >>> What's the actual difference between 0.0/x and 1.0/x? >>> >> -- > Public site: http://www.openlocationcode.com/ > Github project: https://github.com/google/open-location-code > Demo site: http://plus.codes/ > --- > You received this message because you are subscribed to the Google Groups > "Plus Codes Community Forum" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to open-location-code+unsubscr...@googlegroups.com. > To post to this group, send email to open-location-code@googlegroups.com. > Visit this group at https://groups.google.com/group/open-location-code. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/open-location-code/d4b4c889-f7c9-48a1-a751-70290ba443a0%40googlegroups.com > <https://groups.google.com/d/msgid/open-location-code/d4b4c889-f7c9-48a1-a751-70290ba443a0%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Public site: http://www.openlocationcode.com/ Github project: https://github.com/google/open-location-code Demo site: http://plus.codes/ --- You received this message because you are subscribed to the Google Groups "Plus Codes Community Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-location-code+unsubscr...@googlegroups.com. To post to this group, send an email to open-location-code@googlegroups.com. Visit this group at https://groups.google.com/group/open-location-code. To view this discussion on the web, visit https://groups.google.com/d/msgid/open-location-code/CAOOjiHfMyKTB29A0NB7DrPeeiWPUAUg7PdO%3DW66YkLNRAkKkeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
