SkyTruth logo

SkyTruth Alerts

CONTACT US | LEGAL | SITEMAP
  

The SkyTruth Alerts API publishes GeoRSS and KML feeds of alert reports. This page describes the API parameters available for filtering the feeds.

Feed URLs

RSShttp://alerts.skytruth.org/rss
KMLhttp://alerts.skytruth.org/kml

Both feeds will return the most recent 100 alerts that match the filter, with the most recent alerts first. The RSS feed is Atom 2.0 with georss:point elements.

Feed Formats

RSS Feed Format
ths RSS feed is a standard Atom 2.0 feed with a georss:point element containing a lat/long pair
KML Feed Format
the KML feed is a KML 2.2 feed with a set of placemarks including HTML description content.

Query Parameters

l (optional)
A lat/long bounding box. This is a comma separated list of lats and longs that define two opposite corners of a bounding box that will filter reports to only those within the box
BBOX (optional)
A long/lat bounding box, included for Google Earth compatibility. Works the same as l except that the lat/long pairs are reversed so that longitude comes first
dates (optional)
a date or a date range. Supply one date to filter reports to only those that occured after that date. Supply two dates separated by a comma to include only reports that occrred in that time range. Date format is YYYY-MM-DD
d (optional)
an integer number of days. Filters reports to include only reports that are less than d days old
tag (optional)
a comma delimited list of tags to filter the feed by
n (optional)
maximum number of incidents to return in the result. Default is 50. Maximum allowed is 100.

Location Examples

Retrieve an RSS feed containing reports in the vicinity of Shepherdstown, WV

http://alerts.skytruth.org/rss?l=39.313401,-78.031616,39.526638,-77.583923

The first pair is the Lat/Long of one corner of the bounding box and the second pair is the Lat/Long of the opposite corner. It does not patter which pair comes first, but in each pair the LAT is first and the LONG is second.

Alternatively, you can use a Google Earth style BBOX parameter, which works the same way, except that, confusingly, the LAT and LONG are reversed in each pair, like this:

http://alerts.skytruth.org/rss?BBOX=-78.031616,39.313401,-77.583923,39.526638

Date Examples

The feed can be filtered by date to show only reports after a particular date, or only reports within a given date range. Dates are formatted YYYY-MM-DD. For example:

http://alerts.skytruth.org/kml?dates=2011-06-01

will give you a KML feed with reports on or after the first of June, 2011.

http://alerts.skytruth.org/kml?dates=2011-06-01,2011-06-03

will give you only reports from the first through the third of June, 2011

You can also use the "d" parameter to specify that you only want reports new reports that are only a few days old like this

http://alerts.skytruth.org/kml?d=5

will give you only reports that are less than 5 days old

Tag Examples

Alert reports can have tags which can be used to filter a feed as well. A tag is applied to every report to based on the original source (e.g. NRC, SkyTruth), based on SkyTruth analysis of the reports (BigSpill) and tags already present in reports from other blogs are preserved in the alert feed. You can specify multiple tags in a comma-separated list, in which case they are ORed together to return reports that match ay one of the tags in the list

http://alerts.skytruth.org/rss?tag=SkyTruth http://alerts.skytruth.org/rss?tag=Nrc,BigSpill

Read more about tags

There are many tags used in the alerts feed that can be used to filter the feed to only include certain types of reports

Source Tags

Each data source has a tag associated with it that is applied to every incident report that originates from that source. For instance, reports originating from the NRC have the tag 'NRC'. For a complete list of data sources and their corresponding tags, see the SkyTruth Alerts Sources page.

SkyTruth Analysis Tags

The SkyTruth automated expert system analyzes each report and assigns certain tags based on the content of the report.

BigSpillThe report indicates an oil spill that is larger than 100 gallons
GeocodeMismatchA lat/long was supplied in the report, but it does not match other location information such as a protraction area block id or zipcode
SheenSizeMismatchFor an oil spill that has a reported spill volume and also has a reported sheen size, this tag indicated that the volume computed from the sheen area is more than twice the size of the reported volume. The volume derived from the sheen area is computed assuming a uniform distribution over the entire sheen area with a minimum thickness of 1 micron, which is the minimum thickness necessary in otder to produce a visible sheen on open water, according to this analysis.

Imported Tags

When reports are imported, any tags associated with the report are preserved (for instance tags on imported blog posts)

Entries in the alerts feed are consolidated from a number of sources. Each alert feed entry is tagged based on the original source of the report.

SkyTruth Source Tags

NRCreports from the National Response Center. These are mostly industry self-reports from operators that are required to report accidents and emissions to the NRC
SkyTruthReports from the SkyTruth blog that have been tagged as Alerts
NOAAIncidents reported on NOAA's Incident News site documenting selected oil spills (and other incidents) where NOAA's Office of Response and Restoration (OR&R) provided scientific support for the incident response

NRC Incident Reports

Reports from the NRC are scraped daily from the NRC website. The full report text is parsed to extract key fields. Certain reports are eliminated from the feed because they are not "real" reports. These include reports that are drills, or tests of the system, as well as routine activity reports that do not document a release of materials.

After extraction, the reports are geo-coded using the best availale geo-location information in the report. Reports where the location cannot be determined are excluded from the feed.

Finally the reports are analyzed by the SkyTruth expert system. Additional fields are added to the report if there is any additional anallysis that can be included.

NRC Report Geo-Location Methods in Order of Preference

Explicit Lat/LongIf a report is found to contain an explicit lattitude and longitude pair, this is always used as the location
Protraction Area and Lease BlockOffshoe reports commonly have a protraction area (e.g. Mississippi Canyon) and a lease blosk ID number. If this is present, then the center point of the lease block is used as the location. Protraction areas and lease blocks are the way the Gulf of Mexico is divided up by BOEMRE for management of oil and gas drilling leases in federal waters.
Zip CodeMany onshore incidents contain a city, state and zip code. The center point of the zip code is used as the incident location