[Geojson] [georss] simple 3D geocode for AR

[Carl Reed]

All -

Another document that is in the IETF standards track is HTTP Enabled 
Location Delivery (HELD) draft-ietf-geopriv-http-location-delivery-15.txt . 
The document describes a Layer 7 Location Configuration Protocol (L7 LCP) 
that  is used for retrieving location information from a server within an 
access network. Again, this is not a "simple" or lightweight. However, there 
are elements that may be useful in discussions related to what Mike has 
asked. I should also note that HELD is gaining significant implementation 
acceptance in the internet infrastructure community and will be a mandated 
standard for use in the Next Generation 9-1-1 deployment.

Regards

Carl


----- Original Message ----- 
From: "Mike Liebhold" <mnl at well.com>
To: <geowanking at geowanking.org>; <georss at lists.eogeo.org>; 
<geojson at geojson.org>; "Gene Becker" <gbecker8888 at gmail.com>
Sent: Thursday, August 27, 2009 5:35 PM
Subject: [georss] simple 3D geocode for AR


>A friend wrote me with a request for clarification on a topic we've
> discussed many times here,  but every time we've approached a consensus
> the answer seems elusive.
>
> Many devleopers are starting to create applications for iPhones and
> Android phones to view location specific data  through the viewfinder
> using the -imprecise- capabilities of the built in gps and compass and
> applications platforms like Layar.
>
> The question:
>
> What is the -simplest- way to geocode a geoannotation in 3D using
> geoRSS/Atom, geojson, KML ....?
>
> (Is there a practical reason why WGS '84 shouldn't be implicit, and a
> CRS  lookup NOT be required?)
>
>
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss