*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
These two Google gadgets provide a means to show eBird or eTT observations over the past few days on a web site or on your Google home page. These gadgets utilize the eBird apiProvides a summary of data provided by the eBird Recent Sightings By Loc API (v1.0).This API delivers summary data about eBird and eTT observations for made at an eBird hotspot, over the past few days. Two different Google gadgets are also provided which consume this data.. Since all eTT deployments are linked to a particular eBird hot spot, these gadgets can deliver summary information to the web site of an eTT owner/subscriber.
Google Gadgets
eTT-branded Gadget
...
The sample gadget utilizing this API: http://ebird.org/wstools1.0/google/byloc/ebird-byloc.xml.
Suggestions for Improvement
- For both gadgets:
- Ability to sort by Most Recently Observed (followed by taxonomic order)
- Ability to sort by High Count (followed by taxonomic order)
- For eBird gadget:
- Show first and last name of reporting observer
- For eTT gadget:
- link to AAB species on species names
- link to map showing location of sighting (using eTT map)
- identify rarities and specialties
API
...
URL
...
description
...
status
...
notes
...
...
Return summary of recent sightings for most active hotspot over the past 24 hours
...
deployed
...
...
http://ebird.org/ws1.0/product/byloc/recent?locID=L97555&locID=L259855&daysBack=7
...
Return summary of recent sightings at the given locID(s)
...
deployed
...
Parameter Descriptions
...
parameter
...
required
...
default
...
value options
...
example value
...
description
...
status
...
locID
...
no
...
n/a
...
locID of hotspot locations
...
L97555
...
The data summary is computed using data submitted to the given locIDs (up to three). The eBird-1.0-HotSpot web service lists valid hot spot locIDs.
...
deployed
...
locale
...
no
...
en_US
...
Java standard locale codes
...
en_US
...
Language/locale of common names provided in the response (when translations are available)
...
deployed
...
daysBack
...
no
...
0
...
0, 1, 2, 3, 4, 5, 6, 7
...
7
...
...
deployed
Result Caching
Results are cached on the server for 30 minutes, so repeated calls to the same URL will usually result in exacted the same response. The time that the response was actually computed is provided in the header time stamp.
XML Result Format
...
...
Potential Improvements
...
.