Hi Doug, I think you are misinterpreting the requirement here. If you have a look at existing implementations (for example JAVA: https://github.com/google/open-location-code/blob/master/java/com/google/openlocationcode/OpenLocationCode.java), you will see that the *shorten()* and *recover()* methods take lat/long as arguments for the reference location.
You don't have to ship any name:coordinates lookup tables with your OLC implementation, but can rely on the application using your implementation doing the lookup itself and providing your code with lat/long coordinates. -- 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/e9464b46-fefb-4dc9-8d77-d5be748d1d4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
