taxonomy service

100%

taxonomy service

✓ Published0🌍 Public

Last edited Apr 21, 2011

Created on Apr 21, 2011

This example implements a taxonomy search service for species data, returning filtered results by taxonomic ranks such as kingdom, phylum, class, order, family, genus, and species. It queries a Google App Engine datastore using the `Species` and `SpeciesIndex` models, applying up to two user-specified filters and optional range-map constraints. The service supports key-based lookups and offset/limit pagination, then serializes each result into JSON with rank, name, classification, authority, and alternate names. It uses the `simplejson` library for parsing stored JSON fields and the datastore’s `db.Key.from_path` for direct entity retrieval.

AI-generated description

Similar vizzes

Loading thumbnail…

First implementation of a taxonomy model for the Map of Life project

The visualization implements a taxonomy model for the Map of Life project, showing hierarchical species classification from kingdom to subspecies. It renders a force-directed graph using d3.forceSimulation, with nodes representing taxonomic ranks and links encoding parent-child relationships. The code defines two App Engine datastore classes, Species and SpeciesIndex, storing authority names, classification strings, and hierarchical fields like phylum, class, order, family, genus, and species. The visualization likely queries these datastore entities to populate the graph, displaying the branching structure of biological taxonomy through interconnected nodes and edges.

Aandrewxhill

69% match

Loading thumbnail…

Gist 1127799

This example demonstrates an indexing strategy for querying large datasets in Google App Engine, using the `db.Model` classes `CellIndex` and `Cell`. It shows how to retrieve only the keys of `CellIndex` records that match a filter on `ndfi_low`, then access the parent `Cell` entity to get its full stored data, avoiding serialization of all properties. The code uses the App Engine datastore API with `CellIndex.all(keys_only=True).filter()`, and relies on a `BlobStore` for the parent’s data.

Aandrewxhill

60% match

Loading thumbnail…

Gist 956273

A graph visualization maps ecological occurrence sets and multipolygon indexes through their shared terms, using a force-directed layout to reveal clusters of related species and regions. The code builds the network from App Engine datastore models, connecting occurrences to their parent sets via reference properties. It renders nodes and edges using d3.forceSimulation, with spatial positioning driven by simulated physics rather than geographic projection, while styling reflects term rank and type metadata from the stored entities.

Aandrewxhill

55% match

Loading thumbnail…

Gist 954622

This visualization maps a network of species occurrence records and their associated ecoregion polygons. It shows how occurrence sets cluster together through shared taxonomic and geographic references, using an interactive force-directed layout. The code relies on d3.forceSimulation to position nodes representing occurrence sets and polygons, while d3.geoPath renders the underlying geographic boundaries from the stored polygon data. Data is pulled from Google App Engine’s datastore models, including OccurrenceSet and OccurrencePolygon, with the visualization highlighting relationships between species names, sources, and ecoregion types.

Aandrewxhill

55% match

Loading thumbnail…

Gist 896930

This example shows how biological species names and their associated geographic data types can be linked through shared layer identifiers. A force-directed layout, likely using d3.forceSimulation, maps the relationships between search terms, source types (GBIF points and MOL ranges), and matched species names. The visualization connects name matches like “Puma concolor” to overlapping layer IDs, while distinguishing whether each layer originates from GBIF or MOL. It demonstrates a data model for reconciling multiple taxonomic and spatial datasets, though the actual rendering logic is not included in the provided code.

Aandrewxhill

54% match

Loading thumbnail…

Animals | CartoDB.js

This example visualizes animal sightings on an interactive map using CartoDB.js. It displays all animals by default and dynamically adds a layer selector list that groups animals by type, with counts derived from SQL queries against the `all_animals` table. Clicking a type filters the map by updating the SQL for sublayers and the data layer, drawing connected lines via `ST_MakeLine` on the selected subset. The code uses CartoDB’s `createVis` and `SQL` APIs to load the map and query data from the `seatheanimals` user account.

Aandrewxhill

53% match

Loading thumbnail…

Gist 1127779

This example demonstrates a data-modeling pattern for the App Engine datastore using Python and the db.Model API. It shows how to structure a `Note` entity with a `ReferenceProperty` to a `Cell` entity, enabling reverse lookup of all notes attached to a cell via `Cell.notes`. The code also illustrates an alternative approach using parent-child relationships, where `Note.parent()` returns the owning `Cell`. Finally, it suggests constructing cell keys as composite strings like `'z/x/y/year/month/day'` to support efficient searches by coordinates and time.

Aandrewxhill

52% match

Loading thumbnail…

Some test API calls to get JSON with geocoordinates from the Global Biodiversity Information Facility (GBIF)

This example demonstrates how to query the Global Biodiversity Information Facility (GBIF) API to retrieve georeferenced species occurrence data, specifically filtering by scientific name and geographic bounding box. It shows the raw JSON responses for both a single occurrence identifier and bulk searches for Quercus macrocarpa within specified latitude and longitude ranges. The visualization highlights the data-fetching process using URL-encoded parameters like `%20` for spaces and comma-separated coordinate ranges. The code relies on standard HTTP requests to the GBIF REST API, returning structured JSON that could be subsequently plotted with a library like D3 or Leaflet, though no client-side rendering is performed here.

CCliffordAnderson

51% match