Re:Open Location Code: Easier location encoding
by slx26 on Thursday March 15, 2018 @03:20PM
(#16595765)
"place" is very ambiguous. technically, a place might include several "regions". at the same time, a big building can have several entries, which can be referenced with different codes. and still, codes can vary in length and hence, resolution.
but I agree that the sentence itself is a bit confusing and very not technically meaningful or informative.
Re:Open Location Code: Easier location encoding
by shaftway on Thursday March 15, 2018 @05:59PM
(#16596858)
I think the point they're trying to convey is that no two codes resolve to overlapping rectangles.
In my town there are two zip codes, but both of these are handled by the same post office, so it doesn't really matter which one you use. This can cause confusion though. Ensuring that multiple codes don't resolve to the same place (i.e. rectangle) means that there isn't this confusion.
Re:Open Location Code: Easier location encoding
by llccbb on Thursday March 15, 2018 @04:35PM
(#16596303)
I am trying to wrap my head around efficient aggregation of these "places" into a more meaningful shape such as a building footprint. This seems better for this use case than what3words in that it is hierarchical and could help with blocking out large spaces.
This doesn't really seem to be true in practice. For a reasonably large building, it seems like I could end up with two codes which for all practical purposes, are equivalent.