Resights an existing Sighting. The method parameters are identical to those for the CreateSighting method except that here the description parameter is optional. If a description is omitted, the Sighting will have the same description as the original Sighting.
The Sighting’s location must be within 100 metres of the original Sighting otherwise a resighting_too_far error will be returned.
If a Sighting is on-hold then it can only be resighted by the User who created it - a held_sighting error will be returned for other users.
The Sighting to re-sight is specified by the user_id and the sighting_id in the url.
HTTP Method: POST
|access_token||String(32)||Yes||A valid access token.|
|accuracy||Float||No||The accuracy in metres of the latitude and longitude reading. Should be omitted if not known.|
|altitude||Float||No||The altitude in metres. Should be omitted if not known.|
|altitude_accuracy||Float||No||The accuracy in metres of the altitude reading. Should be omitted if not known|
|blobtracker_id||String(200)||No||The blobtracker_id returned by the Upload method of the evidence image to use for this Sighting.|
|description||String(200)||No||The description of the Sighting. If omitted the Sighting will have the same description as the original Sighting.|
|heading||Float||No||The heading of the user when the Sighting was made. Should be omitted if not known.|
|hold||Boolean||No||Whether the Sighting should be placed on-hold.|
|latitude||Float||Yes||The latitude of the Sighting.|
|locator_id||Long||No||Zero or more Locator Ids which this Sighting should be submitted to.|
|longitude||Float||Yes||The longitude of the Sighting.|
|publish_to_facebook||Boolean||No||Whether the Sighting should be published to the user’s Facebook feed. If the user hasn’t linked their Resighting account to Facebook then this flag has no effect.|
|sandbox||Boolean||No||Whether the method should run in sandbox mode - no writes will be made to the datastore.|
|speed||Float||No||The speed the user was traveling when the Sighting was made, if known.|
|tweet_sighting||Boolean||No||Whether the Sighting should be tweeted. If the user hasn’t linked their Resighting account to Twitter then this flag has no effect.|
The number of minutes that the user’s timezone is offset from UTC. This allows us to adjust the Sighting date/time correctly.
Valid values are from -720 (UTC-12:00) to 840 (UTC+14:00).
Returns a Sighting object and HTTP status 200, or an Error object and HTTP status 4xx or 5xx. If the sandbox parameter was set then the returned object will contain dummy data and a boolean attribute named sandbox which will have the value True. See the section on sandboxing for more details.
curl https://resighting-api.appspot.com/api/1/sightings/bf10ad015e7b4ceea9279c1b9e8889a5/492003/resightings --data access_token=ACCESS_TOKEN --data latitude=48.83752 --data longitude=2.30146 --data tz_offset=120