>I'm saying that OLC is just one of many methods, and it is simply a
conversion of the already stored latitude and longitude. The interface
tools are the only element that needs to support any of these
conversions. Nothing needs to be stored in the database.
Agreed but you do need to be able to
On 11/07/16 20:58, john whelan wrote:
> In Canada suite 201 would be understood to be 2nd floor suite 1 of the
> building. Where did the name of the building come into it?
Sub-building element of any addressing scheme. BUT OLC specifically
excludes adding something like that ... unless they
In Canada suite 201 would be understood to be 2nd floor suite 1 of the
building. Where did the name of the building come into it? Do you have a
suggestion for Africa that is less than a very long string of latitude and
longitude remembering that any encoding system would need to be understood
by
On 11/07/16 19:43, john whelan wrote:
> True but suite 201 followed by the location code should do the trick. I
> was thinking not so much of sending mail in the UK so much as providing
> something fairly basic to countries in Africa etc. and even in the UK I
> would at least provide a location.
On 11/07/16 18:12, john whelan wrote:
> I would basically give everyone an address in the world, its Open source
> and as far as complexity goes the UK uses what is called precise or the
> street number plus postcode which often is 9 characters and digits to
> uniquely identify an address so using
http://openlocationcode.com/
I was thinking if it's not a major problem the full 10 character code
should be easy to support in Nomination as it is based on longitude and
latitude.
I would basically give everyone an address in the world, its Open source
and as far as complexity goes the UK uses
6 matches
Mail list logo
