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

[Carl Smyth]

Carl, Mike,

A related application is in the construction of resource URLs in
geographic REST APIs and in micro-formats. We are working on this in
OGC/Open Location Services both for geographic coordinates and local
grid coordinates for tracking and micro-features. It would be nice to
have some overall framework or best practice document to prevent
duplication of effort and similar but different specs. 

I'll take a look at the IETF docs. Location encoding is a fundamental
question for geo-applications and network infrastructure.

...steve

-----Original Message-----
From: geojson-bounces at lists.geojson.org
[mailto:geojson-bounces at lists.geojson.org] On Behalf Of Carl Reed
Sent: Friday, August 28, 2009 7:54 AM
To: Mike Liebhold; geowanking at geowanking.org; georss at lists.eogeo.org;
geojson at geojson.org; Gene Becker
Subject: Re: [Geojson] [georss] simple 3D geocode for AR

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 

_______________________________________________
Geojson mailing list
Geojson at lists.geojson.org
http://lists.geojson.org/listinfo.cgi/geojson-geojson.org