Short code search works by finding the locality and then retrieving the closest plus code that matches the given suffix. So "764Q+Q7 Louisville, Kentucky" reconstructs to 86CP764Q+Q7, while "764Q+Q7 Kentucky" to 86CQ764Q+Q7, because that is closer to the center of Kentucky.
A locality does not need to fit within a 1x1 degree XXXX0000+ rectangle to be a reference locality, the recovery is the closest code, rather than the code with the same first 4 characters. However, if the locality gets close to 1 degree in spread, it cannot be used as it could be used as a reference locality to two different plus codes. Houston in this case is a bit puzzling as it isn't really that large and is probably a result of poor geometry in the data. I think we'll fix that in our implementation.. On Sat, Sep 8, 2018 at 4:00 PM, Shawn K. Quinn <skqu...@rushpost.com> wrote: > On 09/08/2018 08:25 AM, Pascal Lola wrote: > > I am sure some of you are aware of this but why would 764Q+Q7 > > Louisville, Kentucky vs 764Q+Q7 Kentucky take me to completely different > > places? I am sure technically it's an intentional design, but that is a > > major user experience problem with highly critical consequences if this > > technology was to ever be adopted widely. Any thoughts on that? > > My guess is the center of Kentucky resolves to be in a different enough > place from Louisville such that the full OLC is different. One solution > to this is to either always give full codes (in this case either > 86CP764Q+Q7 or 86CQ764Q+Q7 depending on what you are referring to) or > always include the nearest city. > > We have a problem like this in Houston as it's spread out enough that > the 76X60000+ rectangle does not cover the entire city and codes near > the edges are potentially ambiguous. For example, the Flying J truck > stop near the 76X60000+/86260000+ boundary (30°N latitude I think) has a > code of X6XHXC+GV Harris County, Texas (or 76X6XHXC+GV). > > I wouldn't necessarily call it a bug nor a feature, just a quirk of the > system and others like it. > > -- > Shawn K. Quinn <skqu...@rushpost.com> > http://www.rantroulette.com > http://www.skqrecordquest.com > > -- > 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/af9f32f2-1c9c-b94f-91f1- > 053d0597e204%40rushpost.com. > 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/CALCXoY3%3DsVWFJD3n0SKvr_r7vaiHKgN30B12UmjhgdoxPz674A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
