Ron Lake wrote:
I suspect that in augmented reality applications you are going to want
to express the location of the camera (determined by GPS) and the
location of things in the field of view relative to the camera.
But maybe not in the context of the Geocoding-for-AR problem. An AR device
needs to be able to compute visibility to its camera of features in
geocoded data. It follows that a camera model is required within the
device's own software, but not that the geocoded data needs representations
of cameras.
-- Chris
----- Original Message -----
From: "Ron Lake" <[email protected]>
To: "Mike Liebhold" <[email protected]>
Cc: "geojson" <[email protected]>; <[email protected]>;
"GeoRSS" <[email protected]>
Sent: Friday, August 28, 2009 3:10 PM
Subject: Re: [georss] [Geojson] simple 3D geocode for AR
Sure.
Location of the camera - where in the world are you. For this
geographic coordinates - e.g. (lat,lon) makes sense.
Now in the field of view of the camera, I can see things. I am
interested in their shape, location etc. relative to the camera or
relative to me, the holder of the camera. The most logical coordinate
system for locating such items is a rectilinear coordinate system (x-y-z
frame) centered (origin) at the focal point of the camera.
Cheers
Ron
-----Original Message-----
From: Mike Liebhold [mailto:[email protected]]
Sent: August 28, 2009 2:05 PM
To: Ron Lake
Cc: Joshua Lieberman; [email protected]; geojson; GeoRSS
Subject: Re: [georss] [Geojson] simple 3D geocode for AR
Ron Lake wrote:
The use of geographic coordinates for [location of things in the field
of view relative to the camera] likely does not. [ make sense]
Ron,
This is really counter intuitive, Can you explain what you mean?
- Mike
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Joshua Lieberman
Sent: August 28, 2009 11:03 AM
To: [email protected]
Cc: geojson; GeoRSS
Subject: Re: [georss] [Geojson] simple 3D geocode for AR
In both GeoRSS GML and GeoJSON, some explicit CRS needs to be
specified to use 3-coordinate locations. The simplest one for GeoRSS
seems to be epsg:4979 ( urn:ogc:def:crs:EPSG:4979 ). It would need a
slight modification to support the GeoJSON long-lat encoding.
Otherwise use GeoRSS Simple and the elev property.
e.g.
<georss:elev>346</georss:elev>
<georss:point>42.3234 -173.234134</georss:point>
Well-known text description of 4979
(http://spatialreference.org/ref/epsg/4979/
)
GEOGCS["WGS 84", DATUM["World Geodetic System 1984", SPHEROID["WGS
84",
6378137.0,298.257223563, AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]], PRIMEM["Greenwich",0.0,
AUTHORITY["EPSG","8901"]], UNIT["degree",0.017453292519943295],
AXIS["Geodetic latitude",NORTH], AXIS["Geodetic longitude",EAST],
AXIS["Ellipsoidal height",UP], AUTHORITY["EPSG","4979"]]
Josh
On Aug 28, 2009, at 1:05 PM, Ron Lake wrote:
Sorry my example should have been
<Point id = "P1" CRS = "http://www.blah.bla/standardCRS.xml";>
<coordinates>100 200 150</coordinates>
</Point>
But the argument is the same. Similar encodings can be made in JSON
etc.
R
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Andrew Turner
Sent: August 28, 2009 9:57 AM
To: [email protected]; GeoRSS; geojson
Subject: Re: [georss] [Geojson] simple 3D geocode for AR
Simplest?
Just include a 3rd coordinate in GeoRSS-Simple point or GeoJSON
point.
No, this is not explicitly valid. But you see where that discussion
gets us. Long windy roads of elusive semantic talk (arguably
necessary
in the lon term, but not simple or useable *now*, which is when
people
are building these tools).
If we lose interest without achieving a near term concensus,
developers will just do arbitrary, different solutions. Give them a
simple answer now, even if it makes your strict-validation-only-skin
crawl just a little bit. :)
So I say just do it, and we'll catch up with documenting it as uses
emerge.
Also, KML already supports 3D points.
Andrew
(via mobile)
On Aug 27, 2009, at 4:35 PM, Mike Liebhold <[email protected]> wrote:
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?)
_______________________________________________
Geojson mailing list
[email protected]
http://lists.geojson.org/listinfo.cgi/geojson-geojson.org
_______________________________________________
georss mailing list
[email protected]
http://lists.eogeo.org/mailman/listinfo/georss
_______________________________________________
georss mailing list
[email protected]
http://lists.eogeo.org/mailman/listinfo/georss
_______________________________________________
georss mailing list
[email protected]
http://lists.eogeo.org/mailman/listinfo/georss
_______________________________________________
georss mailing list
[email protected]
http://lists.eogeo.org/mailman/listinfo/georss
_______________________________________________
georss mailing list
[email protected]
http://lists.eogeo.org/mailman/listinfo/georss
_______________________________________________
Geowanking mailing list
[email protected]
http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
