Re: [OSM-talk] Open Location Code should we support it?

[john whelan]

>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 see where it is hence the suggestion
that Nomination could support it.

Cheerio John

On 11 July 2016 at 20:31, Lester Caine  wrote:

> 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 have changed the
> spec again?
>
> > 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 both the person creating it and the person using it?
> >
> > Are you saying there is a better solution for encoding the co-ordinates?
> 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.
>
> --
> Lester Caine - G8HFL
> -
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Open Location Code should we support it?

[Lester Caine]

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 have changed the
spec again?

> 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 both the person creating it and the person using it?
> 
> Are you saying there is a better solution for encoding the co-ordinates?
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.

-- 
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Open Location Code should we support it?

[john whelan]

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 both the person creating it and the person using it?

Are you saying there is a better solution for encoding the co-ordinates?

Thanks John

On 11 July 2016 at 15:47, Lester Caine  wrote:

> 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.
>
> The use of the Open Location Code as an alternative to a postcode by
> adding a building identify is exactly against what it was designed for,
> but there is no reason that one can't directly use the latitude and
> longitude anyway, encoding them to a short form if you want. Any
> 'recoding system' for the physical location can be used to display the
> raw numbers? But for readability, just as OLC does, one uses the town
> and country and simply provide a GPS location limited to that area. A
> bit like 'national grid' in the UK
>
> > Cheerio John
> >
> > On 11 Jul 2016 2:36 pm, "Lester Caine"  > > wrote:
> >
> > 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 ten wouldn't be that much
> more
> > > complex.
> >
> > For a UK address, the sub building name and building name can be up
> to
> > 80 characters to fit in the Royal Mail PAF record and building
> number up
> > to four digits. There are additional 'premises elements', and even
> some
> > of the thoroughfare elements may be additional to the postcode
> itself,
> > so 10 characters is never enough.
> >
> > Open Location Code lacks the ability to handle multi-story housing.
> It
> > only gets you to the apartment block. This is an area where OSM still
> > needs some more work.
>
> --
> Lester Caine - G8HFL
> -
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Open Location Code should we support it?

[Lester Caine]

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.

The use of the Open Location Code as an alternative to a postcode by
adding a building identify is exactly against what it was designed for,
but there is no reason that one can't directly use the latitude and
longitude anyway, encoding them to a short form if you want. Any
'recoding system' for the physical location can be used to display the
raw numbers? But for readability, just as OLC does, one uses the town
and country and simply provide a GPS location limited to that area. A
bit like 'national grid' in the UK

> Cheerio John
> 
> On 11 Jul 2016 2:36 pm, "Lester Caine"  > wrote:
> 
> 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 ten wouldn't be that much more
> > complex.
> 
> For a UK address, the sub building name and building name can be up to
> 80 characters to fit in the Royal Mail PAF record and building number up
> to four digits. There are additional 'premises elements', and even some
> of the thoroughfare elements may be additional to the postcode itself,
> so 10 characters is never enough.
> 
> Open Location Code lacks the ability to handle multi-story housing. It
> only gets you to the apartment block. This is an area where OSM still
> needs some more work.

-- 
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

Re: [OSM-talk] Open Location Code should we support it?

[Lester Caine]

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 ten wouldn't be that much more
> complex.

For a UK address, the sub building name and building name can be up to
80 characters to fit in the Royal Mail PAF record and building number up
to four digits. There are additional 'premises elements', and even some
of the thoroughfare elements may be additional to the postcode itself,
so 10 characters is never enough.

Open Location Code lacks the ability to handle multi-story housing. It
only gets you to the apartment block. This is an area where OSM still
needs some more work.

-- 
Lester Caine - G8HFL
-
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] Open Location Code should we support it?

[john whelan]

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 what is called precise or the
street number plus postcode which often is 9 characters and digits to
uniquely identify an address so using ten wouldn't be that much more
complex.

Thoughts?

Thanks John
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk