Hi X, We designed OLC as a solution for unnamed streets, or places where street addresses aren't possible/don't exist. We didn't include a 3rd dimension because:
1. it's not necessary in probably >90% of addresses 2. we didn't see any unit being widely used or useful (floor number? meters? meters over ground? meters over sea level? which sea level?) 3. even floor numbers aren't consistent across countries, some use 1 as the ground floor and others use 0, or G, or L, etc. So we left it out. For your case, maybe use OLC as the XY location and then meters or barometric pressure for height? Doug Rinckes, Technical Program Manager, Google Switzerland GmbH; 9GHJ+P88 Z ürich <https://www.google.com/maps/search/9GHJ%2BP88%20Zürich> On Thu, Nov 2, 2017 at 2:17 AM, X <x...@skyward.io> wrote: > Greetings, > > We are interested in using OLC to index a geographically partitioned and > distributed open source GIS system for unmanned aircraft systems. OLC seems > like a natural fit for a variety of reasons (varied resolution, cogent grid > system, concise address, open standard, etc). However, we operate in three > dimensions (as do our underwater unmanned system colleagues and our > building information management system colleagues). I'm not sure how this > also pertains to the addressing problem worldwide, but I have lived in > places with no clear address scheme that included multi story buildings. > This is the case even using OLC for our business where our office location > is on the 2nd floor. In many of these cases, a vertical dimension would be > helpful. > > We could do our own implementation by appending some sort of elevation or > z-axis, but I'm curious if there are thoughts from the team on a three > dimensional implementation of the system. > > Thank you, > > 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 > "open-location-code" 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/d8f12db8-a73c-4e6c-8518- > 25b0b2399c84%40googlegroups.com > <https://groups.google.com/d/msgid/open-location-code/d8f12db8-a73c-4e6c-8518-25b0b2399c84%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 "open-location-code" 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/CAGFr2LK_naZTtkSoSc0tLxvS2sob%2B8o4S8%2BRP0DhmZC67RNR8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
