Brad, Ah, sorry -- looks like the bolding syntax messed it up. There should be no asterisks in the API.
Best, Ryan On Thu, Aug 20, 2009 at 4:02 PM, bg<mapicuri...@gmail.com> wrote: > > Ryan, > > Thanks for the updates. Your example has ** after lat and lng. Is this > the proper format or some highlighting? > > Thanks again, > > Brad > > *<georss:point>37.780467** -122.396762**</georss:point>* > > On Aug 20, 5:55 pm, Andriy Ivanov <tigrus...@gmail.com> wrote: >> really cool! Very excited to see it! >> >> On Aug 20, 2:27 pm, "jim.renkel" <james.ren...@gmail.com> wrote: >> >> >> >> > Um, I don't see any way for a user to turn the <geo_enabled> attribute >> > on and off. Oversight, I hope? >> >> > Jim >> >> > On Aug 20, 4:18 pm, Joel Strellner <j...@twitturly.com> wrote: >> >> > > Hi Ryan, >> >> > > Will this data be available in the streaming API too? >> >> > > -Joel >> >> > > On Thu, Aug 20, 2009 at 2:11 PM, @epc <epcoste...@gmail.com> wrote: >> >> > > > Will twitter validate the coordinates (ie, what will the API do when I >> > > > pass lat=777&long=-666)? >> >> > > > If the coordinates are invalid, will the status get posted or will the >> > > > entire request get rejected with a 4xx code? >> >> > > > If a user has not enabled geolocating (<geo_enabled>false</ >> > > > geo_enabled>), what happens if I pass in coordinates for that user? >> > > > Silently ignored? >> >> > > > Geo data will be attached to individual tweets and not users, right? >> > > > This will have no effect on the <location> field in a user profile? >> > > > -- >> > > > -ed costello >
