Changelog

GeoLocator DP is versioned with Git tags. A data package declares the version it follows through the package-level $schema:

{
  "$schema": "https://raw.githubusercontent.com/GeoPressure/GeoLocator-DP/v1.3/geolocator-dp-profile.json"
}

GeoLocatoR upgrades a package from any earlier version when it reads one, so an archived package never needs to be rewritten by hand.

This page collects the GitHub releases in one place.

Unreleased

Fields

  • Describe edges.n as the number of flights (stationary periods spanned) in the edge, as written by GeoPressureR path2edge(), instead of a flight number.
  • Say that pressurepaths has one row per pressure measurement of the tag, at its sampling interval, not hourly rows.

Website

  • Say that a manifest may carry descriptive metadata and the computed temporal, taxonomic and numberTags, and that a package’s Zenodo record is authoritative over its manifest (GeoLocatoR#54).

v1.3

5 November 2026 — release

Fields

  • Define the frame and units of acceleration_x/y/z and magnetic_x/y/z in measurements: x, y and z are the forward, right and down axes of the bird, acceleration is in g and the magnetic field in gauss (f24fd0f). The previous labels said m/s^2 and microtesla, which no software wrote, and left the axes to the hardware. GeoPressureR >= 3.8.0 writes SOI data in this frame (forward = raw y, right = raw x, down = raw z; GeoPressureR#187); older versions stored raw or hardware-dependent axes. GeoLocatoR converts that data once, when it upgrades a package to v1.3.
  • Recommend British Antarctic Survey and PresTag for tags.manufacturer, next to the three existing names, so that every manufacturer GeoPressureR imports has a recommended spelling. The field remains free text.

Profile

  • Document in the params resource that params.json is plain JSON.

Website

  • Present the GeoLocator Data Package: title prefix as a recommendation rather than a requirement.
  • Call plot(pkg, ...) after library(GeoLocatoR): GeoLocatoR::plot() fails because plot() is an S3 method, not an export.
  • Link geopressure.org, the canonical domain, instead of geopressure.com.

Repository

  • Make the example package valid: use the defined mean_acceleration_z sensor instead of acceleration, add the tag that observations refer to, add a prefixed title and contributor roles, swap the latitude and longitude of the observations (Watamu is at 3.4° S, 40.0° E), and fix typos in tags.csv.
  • Require frictionless >= 5.21 for tests/validate_profile_and_schemas.py, and run it on Python 3.13.

v1.2

16 October 2026 — release

Fields

Website

  • Move table rules below the fields with clearer formatting, and render Markdown in category labels.
  • Build the overview from the same schemas as the table pages, and include categories and field links in tooltips.
  • Fix the manifest example link and clarify bird observations, package loading, and interim-file guidance.

Documentation

  • Move value explanations into category labels and remove duplicate lists from field descriptions.
  • Clarify trajectory identifiers and joins, replace the obsolete include reference, and fix the JSON example.

v1.1

18 September 2026 — release

Resources

  • Move the GeoLocator DP table schema URL from resource.$schema to resource.schema. In the Data Package standard, $schema is the profile of the resource descriptor while schema is the Table Schema describing the columns. schema accepts either a versioned table schema URL or an inline descriptor.
  • Require type on tabular resources, which must be table. It replaces the Data Package v1 profile: "tabular-data-resource".
  • Require $schema on tabular resources, which must be https://datapackage.org/profiles/2.0/dataresource.json. Implementations read it to decide which version of the standard a resource follows: without it, frictionless::version() reports a resource as Data Package v1 even inside a package that declares v2.

Table schemas

  • Write fieldsMatch as a string rather than an array, as the standard requires. The array form came from an error in the published Table Schema profile (frictionlessdata/datapackage#965), fixed in Data Package v2.1.
  • Set fieldsMatch to partial on tags, so that a package may carry extra columns on it, as pressurepaths already allowed. The other six tables keep superset, which lets a table leave out columns but not add them. fieldsMatch says nothing about which columns are required: on its own it lets a table omit any column it declares, including one carrying a required constraint, because the standard cannot yet express “the required columns must be present, the optional ones may be absent” (frictionlessdata/datapackage#1126). Presence of the required columns is therefore checked separately, by GeoLocatoR::validate_gldp().
  • Write primaryKey and foreignKeys fields as arrays of strings, the Data Package v2 spelling.
  • Remove the unique constraint on tags.tag_id, which duplicated the primary key.
  • Declare categories on every categorical field, giving each allowed value a label. The EURING age_class and catching_method codes were previously only partly documented in prose. measurements.sensor also carries its vocabulary term per category. The enum constraint is kept alongside, as the standard allows, because no implementation enforces categories yet.
  • Fix observations.sex and pressurepaths.type examples, which were not valid values of their own fields.

Profile

  • Select the resource schema with if/then on the resource name rather than oneOf. The accepted descriptors are unchanged, but a validation error now names the property at fault instead of reporting that the whole resource matched none of the branches.

Repository

  • Show primaryKey, foreignKeys, missingValues and fieldsMatch on each table page, list categories with their labels, and link SKOS terms by identifier rather than by URL. Say on each table page which columns may be left out and which must be present, rather than leaving the * marking a required column unexplained.
  • Fix a broken SKOS link on observations.datetime, and restore _data symlink for the measurements schema so the website renders the schema the standard ships.
  • Add example/datapackage.json and example/measurements.csv.
  • Validate the example package, and the spelling of fieldsMatch and of the keys, in tests/validate_profile_and_schemas.py.
  • Add this changelog page.

v1.0

8 April 2026 — release

Major

Minor

Website

Not implemented

  • No major changes to edges.csv, see #31.

Full changelog

v0.6

9 March 2026 — release

Rather minor edits in preparation for v1.0.

Full changelog

v0.5

30 January 2026 — release

Full changelog

v0.4

21 January 2026 — release

Full changelog

v0.3

1 October 2025 — release

Data Package definition

Minor

New contributors

Full changelog

v0.2

16 January 2025 — release

pressurepaths

  • New!

tags

observations

  • life_stage → age_class (commit, #13).
  • Remove broken_damage from device_status (#14).

measurements

  • Add wet_count and conductivity sensors (commit, #12).

Metadata

New contributors

Full changelog

v0.1

2 December 2024 — release

Initial release.

Full changelog