Nelson, Thanks for the email and glad you picked up on GeoRSS. We don't have any plans for this release to support georss:radius. We picked the standard because we like the flexibility and the types of geospatial data it can describe.
The W3C Geolocation API is close to my heart. I started the initiative many years ago with a site called locationaware.org that ended up being one of the forming specs for the W3C standard. We'll be using it on m.twitter.com for launch. As for altitude, its something we may consider in the future, but it's a very GPS-centric attribute as alternative positioning methods like Wifi or cellular positioning can't determine altitude. Best, Ryan On Thu, Aug 20, 2009 at 3:32 PM, Nelson Minar<[email protected]> wrote: > > Very exciting! Thanks for giving the community an early preview. > > GeoRSS supports altitude and accuracy measures for point locations as > well. in GeoRSS-Simple, it's something like > > <georss:point>45.256 -110.45</georss:point> > <georss:radius>500</georss:radius> > <georss:elev>313</georss:elev> > > (at that lat/long, within 500 meters, at an elevation 313 meters above > the WGS84 ellipsoid). > > Any plan to support that in the Twitter API? Radius is very useful for > dealing with inaccurate geolocation, and elevation (or <georss:floor>) > can help distinguish exactly where someone is. > > > > These links may be relevant to the discussion: > > W3C Geolocation API: http://dev.w3.org/geo/api/spec-source.html > (Javascript API to location. Safari supports this nicely on the > iPhone.) > > iPhone CLLocation API: > http://developer.apple.com/iphone/library/documentation/CoreLocation/Reference/CLLocation_Class/CLLocation/CLLocation.html > > Both APIs specify position as latittude, longitude, horizontal > accuracy, altitude, and vertical accuracy. >
