audioBLAST! API

Data

ann-o-mate

Query annotations, including JSON-LD and Turtle descriptions as Audiovisual Core regions of interest. Individual annotations are available at /annotation/{source}/{annotation_id}.

Data Sources

Endpoints

Deployments

This endpoint allows for listing equipment deployments.

Data Sources

Endpoints

Descriptions

This endpoint allows for the querying of what the sources held within audioBLAST! say about something in prose, such as how a taxon behaves, where and when it calls and how far apart calling males are. Each description has a topic saying what it is of, and the Species Profile Model info item that topic names where it names one. What a description is about, and the references it rests on, are links (see the links endpoint), not columns here, so a description that cites a paper says which paper. With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), descriptions are given as RDF texts. Each is identified by https://api.audioblast.org/description/{source}/{id}, which gives it in the same way.

Data Sources

Descriptions are ingested from each source's descriptions and replace the descriptions that the source gave before. Topics are each source's own words, and the ingest reads the Species Profile Model info item each one names.

Endpoints

Details

This endpoint allows for the querying of the details of the records held within audioBLAST!: the things a record holds that have no column of their own, such as the tape a recording was made on, the temperature it was made at, or the field notes of a specimen. Each detail is a named value, with a unit where it is a measurement, belonging to the record of a data module (its type) with an id there. The details a record has of one name are numbered from 0 by delta.

Data Sources

Details are ingested from each source's details, and replace the details that the source gave before. Their names are each source's own, and are not yet matched to vocabulary terms, so details are not given as RDF.

Endpoints

Ecological Interactions

How one taxon interacts with another: the acoustically orientating predators and parasites that find their prey and hosts by listening for them, and the taxa that answer another's alarm call.

An interaction is a relationship, so it is held in the links table and this endpoint is a view of it: the interaction is the link's predicate, the taxa its subject and object, and the reference that established it is a link of its own from the interaction to that reference. Querying Links by an interaction predicate gives the same relationships, with their assertions, and serves them as RDF.

Data Sources

Interactions are ingested as links, from each source's links.

Endpoints

Images

This endpoint allows for the querying of the images held within audioBLAST!: the scans of the sheets a recording's metadata was written on and of the paper oscillographic traces made from it, the figures taken from papers, and the pictures of specimens and of the places recordings were made.

An image is a record rather than a value on the records that show it, so that one scan covering four recordings is described once, with the licence it is under, and linked to each of the four. What an image shows is in Links. An image whose source gives no licence has none here, which says nothing about what may be done with it.

With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), images are given as RDF in Audiovisual Core terms. Each image is identified by https://api.audioblast.org/image/{source}/{id}, which gives the image in the same way.

Data Sources

Images are ingested from each source's images, and are identified by their id within it. What an image shows is links (see the links endpoint).

Endpoints

This endpoint allows for the querying of the links between records held within audioBLAST!, e.g. references and the taxa they are about, or recordings and the references they are published in. A link relates a subject to an object, each identified by its type (a data module, term for a vocabulary term, or iri), the source that holds it and its id there, so links can join the records of different sources. Links follow the Darwin Core Resource Relationship.

Data Sources

Links are ingested from each source's links, and replace the links that the source gave before. A link that a reference established is the subject of a link to that reference, so what a relationship rests on is itself a link.

Endpoints

Locations

This endpoint allows for the querying of the places that the records held within audioBLAST! were made or collected at. A place is described once, however many recordings and specimens are of it, and its columns are named after the Darwin Core terms they hold. Which records are of a place is a link (dwciri:inDescribedPlace, see the links endpoint), not a column here. With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), places are given as RDF Darwin Core locations. Each place is identified by https://api.audioblast.org/location/{source}/{id}, which gives the place in the same way.

Data Sources

Locations are ingested from each source's locations, and are identified by their id within it. A recording that is not at a described place still carries its own country, locality and coordinates.

Endpoints

Onomatopoeia

This endpoint allows for the querying of the words that the sources held within audioBLAST! render an animal's sound with, such as bow-wow for a dog barking, kikeriki for a cockerel crowing, or a mnemonic a birdwatcher remembers a song by. Each has a kind saying what sort of rendering it is, and the class that kind names where it names one. The taxon whose sound is rendered, and the reference the rendering was taken from, are links (see the links endpoint), not columns here. With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), renderings are given as RDF texts, each one that is a word also a lexical entry. Each is identified by https://api.audioblast.org/onomatopoeia/{source}/{id}, which gives it in the same way.

Data Sources

Onomatopoeia are ingested from each source's renderings, and are identified by their id within it. A rendering is about the taxon whose sound it renders (http://purl.obolibrary.org/obo/IAO_0000136), and never denotes it: denoting is what a vernacular name does, and what reads a name onto a taxon as one of the names it is known by, so bark is not published as a name for Canis lupus familiaris. The reference a rendering was taken from is linked by dcterms:source. A rendering whose language a source doesn't give has none: the API never infers a language from a word, and musical notation is in no language at all.

Endpoints

See also

Recordings

This endpoint allows for the querying of recording metadata held within audioBLAST! With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), recordings are given as RDF in Audiovisual Core terms. Each recording is identified by https://api.audioblast.org/recording/{source}/{id}, which gives the recording in the same way.

Data Sources

Endpoints

Recordings-Taxa

Recordings linked to taxa. This is a join between the recordings and taxa tables, primarily of use in filtering recordings by taxonomic ranks higher than species.

The autocomplete values for the taxonomic ranks are limited to those taxa matched to recordings, for more complete taxonomic autocomplete use Taxa

.

Data Sources

The sources used are a subset of those from Recordings.

Endpoints

References

This endpoint allows for the querying of the bibliographic references held within audioBLAST!

Data Sources

References are ingested from BibTeX or CSV, and are identified by their id within each source (for BibTeX, the entry's key).

Endpoints

Specimens

This endpoint allows for the querying of the specimens and observations that the recordings held within audioBLAST! are of. Their columns are named after the Darwin Core terms they hold. With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), specimens are given as RDF Darwin Core occurrences. Each specimen is identified by https://api.audioblast.org/specimen/{source}/{id}, which gives the specimen in the same way.

Data Sources

Specimens are ingested from each source's specimens, and are identified by their id within it. The recording a specimen was recorded in, and the taxon it is identified as, are links (see the links endpoint).

Endpoints

Taxa

This endpoint allows for the querying of the taxonomic hierarchy held within audioBLAST! RDF responses include incoming and outgoing links to recordings, traits and references, with relationship provenance, and the vernacular names a taxon is known by as dwc:vernacularName, each in the language it is in.

Data Sources

Endpoints

See also

Traits

This endpoint allows for the querying of the organism traits held within audioBLAST! With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), traits are given as RDF: Darwin Core MeasurementOrFacts whose types link to terms at vocab.audioblast.org. Each trait is identified by https://api.audioblast.org/trait/{source}/{id}, which gives the trait in the same way. RDF responses include incoming and outgoing relationships from the links table, including source references and taxa.

Data Sources

Endpoints

Traits-Taxa

Traits linked to taxa. This is a join between the recordings and taxa tables, primarily of use in filtering recordings by taxonomic ranks higher than species.

The autocomplete values for the taxonomic ranks are limited to those taxa matched to recordings, for more complete taxonomic autocomplete use Taxa

.

Data Sources

The sources used are a subset of those from Recordings.

Endpoints

Vernacular names

This endpoint allows for the querying of the vernacular names of the taxa held within audioBLAST!: the names a taxon is known by in a language, such as Warzenbeißer for Decticus verrucivorus. Their columns are named after the Darwin Core terms they hold. With output=JSON-LD or output=Turtle (or, without output, an Accept header asking for application/ld+json or text/turtle), names are given as RDF, each as a Darwin Core vernacular name whose dwc:vernacularName carries the language it is in. Each name is identified by https://api.audioblast.org/vernacular-name/{source}/{id}, which gives the name in the same way.

Data Sources

Vernacular names are ingested from each source's vernacular names, and are identified by their id within it. The taxon a name names, and the reference it was taken from, are links (see the links endpoint): the taxon by http://purl.obolibrary.org/obo/IAO_0000219 (denotes), a subproperty of is about, as Darwin Core's vernacularName takes the name rather than the taxon; the reference by dcterms:source. A name is as its source gives it, with the article a reference wrote it with, and one whose language a source doesn't give has none: the API never infers a language from a name.

Endpoints

See also

Analysis

ACI

Explain how this works...

Analysis details

ACI() function of R package seewave.

Vocabulary links

https://vocab.audioblast.org/cv/analysis#seewaveACI

Endpoints

Acoustic Diversity Index

Explain how this works...

Analysis details

acoustic_diversity() function of R package soundecology.

Endpoints

Waveform analysis using audiowaveform

Explain how this works...

Endpoints

Rainfall analysis using the bedoya method

Explain how this works...

Analysis details

rainfallDetection(method="bedoya2017") function of R package sonicscrewdriver.

References

Endpoints

Bioacoustic index

Explain how this works...

Analysis details

bioacoustic_index() function of R package soundecology.

Endpoints

Birdnet embeddings (default)

Endpoints

Birdnet identifications (default)

Endpoints

Birdnet identifications (with lat/lon)

Endpoints

Acoustic Evenness

Explain how this works...

Analysis details

acoustic_evenness() function of R package soundecology.

Endpoints

Acoustic Entropy

Explain how this works...

Analysis details

H() function of R package seewave.

Endpoints

Amplitude index

Explain how this works...

Analysis details

M() function of R package seewave.

Endpoints

NDSI

Explain how this works...

Analysis details

NDSI() function of R package seewave.

Endpoints

Spectral Entropy

Explain how this works...

Analysis details

sh() function of R package seewave.

Endpoints

Time Domain Signal Coding

Time domain signal coding is...

Analysis details

tdsc() function of R package tdsc.

Endpoints

Temporal Entropy

Explain how this works...

Analysis details

th() function of R package seewave.

Endpoints

Standalone

Generic access to analysis information

Provide information about analyses performed

Endpoints

Generic access to data information

Provide information about data contained in audioBlast

Endpoints

Embed

Allows embedding of audio files on the web.

Endpoints

Loaded modules

Provide information about loaded modules

Endpoints

Phylogenetic Emoji

Finds an emoji for a scientific name.

Endpoints

Pythia search term processor

Oracle for providing search hints.

Endpoints

Sequential soundscapes

Generic access point for multiple data types relating to sequential soundscape deployments.

Endpoints

Generic stats on soundscapes

Provides stats on soundscapes

Endpoints

Sun calculations

Provides information about dawn, dusk, day, night, etc.

Analysis details

daysPhases() function of R package sonicscrewdriver.

Endpoints