SourceFinch Verified · Recreation

Human-wildlife coexistence header descriptions - Parks Canada

Open CKAN records from Human-wildlife coexistence header descriptions - Parks Canada via https://open.canada.ca: up to 1,000 rows with stable identifiers for change monitoring. Personal contact columns are excluded.

Monitor this sourceAPI, CLI, SDK and MCP

What changedNo changes in 7 days

At a glance

Category
Recreation
Jurisdiction
Canada
Publisher updates
Updated by the publisher when the CKAN dataset changes
Recommended schedule
Daily for your monitor; SourceFinch verifies the recipe daily
Records per run
26 in the latest run
Record key
id
Acquired from
Open data portal: https://open.canada.ca/data/en/api/3/action/datastore_search?resource_id=7f1ce4da-f174-4394-a53d-398b30c0f69d&limit=1000
Recipe
v1.0.0, approved November 17, 2026
Version notes
First Verified version generated 2026-11-17 from batch backlog.
Verified since
November 17, 2026
Last green run
November 17, 2026
Changes, last 7 days
0 · see what changed

What the data contains

Dataset “Human-wildlife coexistence incidents managed by Parks Canada” published on https://open.canada.ca (resource 7f1ce4da-f174-4394-a53d-398b30c0f69d). Each daily run reads up to 1,000 rows through the portal's keyless JSON API (datastore_search). A monitor reports new and changed rows inside the cohort. SourceFinch is independent of the publisher.

Fields and types

Every record has these fields. The key field id identifies a record across runs, so changes are reported field by field.

FieldTypeDescription
idkeystringPublisher field `_id`. The record key.
Column_Header_ENstring, nullablePublisher field `Column Header EN`.
Column_Header_FRstring, nullablePublisher field `Column Header FR`.
Value_Description_ENstring, nullablePublisher field `Value Description EN`.
Value_Description_FRstring, nullablePublisher field `Value Description FR`.

Sample output

The first 5 of 26 records from SourceFinch's own run on November 17, 2026, exactly as delivered.

FieldRecord 1Record 2Record 3Record 4Record 5
id12345
Column_Header_ENIncident DateLocal TimeYearIncident NumberLatitude Public
Column_Header_FRDate de l’incidentHoraire localAnnéeNuméro de l'incidentLatitude publique
Value_Description_ENIncident DateLocal TimeYearA unique alphanumeric identifier that can be used to look-up incident records between the detailed record tables or to join the tables in a relational databaseDecimal degrees latitude of the approximate incident location within 1500m (root-mean-squared error approx. 1000m).
Value_Description_FRDate de l’incidentHoraire localAnnéeUn « numéro d’incident » alphanumérique unique qui peut être utilisé pour consulter des dossiers entre des tableaux ou pour joindre les tableaux dans une base de données relationnelleLatitude en degrés décimaux de l'emplacement approximatif de l'incident à moins de 1500 m (erreur quadratique moyenne d'environ 1000 m).
Sample as JSON
[
  {
    "id": 1,
    "Column_Header_EN": "Incident Date",
    "Column_Header_FR": "Date de l’incident",
    "Value_Description_EN": "Incident Date",
    "Value_Description_FR": "Date de l’incident"
  },
  {
    "id": 2,
    "Column_Header_EN": "Local Time",
    "Column_Header_FR": "Horaire local",
    "Value_Description_EN": "Local Time",
    "Value_Description_FR": "Horaire local"
  },
  {
    "id": 3,
    "Column_Header_EN": "Year",
    "Column_Header_FR": "Année",
    "Value_Description_EN": "Year",
    "Value_Description_FR": "Année"
  },
  {
    "id": 4,
    "Column_Header_EN": "Incident Number",
    "Column_Header_FR": "Numéro de l'incident",
    "Value_Description_EN": "A unique alphanumeric identifier that can be used to look-up incident records between the detailed record tables or to join the tables in a relational database",
    "Value_Description_FR": "Un « numéro d’incident » alphanumérique unique qui peut être utilisé pour consulter des dossiers entre des tableaux ou pour joindre les tableaux dans une base de données relationnelle"
  },
  {
    "id": 5,
    "Column_Header_EN": "Latitude Public",
    "Column_Header_FR": "Latitude publique",
    "Value_Description_EN": "Decimal degrees latitude of the approximate incident location within 1500m (root-mean-squared error approx. 1000m).",
    "Value_Description_FR": "Latitude en degrés décimaux de l'emplacement approximatif de l'incident à moins de 1500 m (erreur quadratique moyenne d'environ 1000 m)."
  }
]

Evidence behind every value

  • Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash 5cb86597c01590a537fc57d8409e930e3b02feff007ef7a1dccc7ca37317ae82.
  • Every value records where it came from in that response: a JSON Pointer into the retained capture.
  • Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is ef7c679431c3ec38736f48d7cd6c761df0214d87e8e8a363279595a672884ec0, timestamped November 17, 2026.
  • The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
  • Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch: sourcefinch verify-bundle run.wacz.

Terms posture and usage rights

Terms
Automated access permitted · publisher's terms
robots.txt
Allows this path · SHA-256 4790aba35e5672c4…
AI-preference signals
None observed at review
Public record
Yes. CKAN dataset 743a0b4a-9e33-4b12-981a-9f9fd3dd1680 on https://open.canada.ca.
Reviewed
November 17, 2026; next review May 17, 2027
Licence basis
Open data licence (OGL-Canada-2.0)
Commercial use
Allowed
Redistribution
Allowed
Attribution
Required (text below)

Published on https://open.canada.ca under open government terms. Anonymous JSON/CSV API access needs no key. Robots policy is checked at generation.

Parks Canada | Parcs Canada (https://open.canada.ca). SourceFinch is independent of the publisher.

Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.

Reliability

Runs, last 30 days
1
Green
100%
Failed
0
Median run time
0.8 s
Latest run
success, November 17, 2026

Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: November 17, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.

Use it

Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).

Console

Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.

Portable recipe

Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.

{
  "schema": "sourcefinch/source@1",
  "name": "Human-wildlife coexistence header descriptions - Parks Canada",
  "url": "https://open.canada.ca/data/en/api/3/action/datastore_search?resource_id=7f1ce4da-f174-4394-a53d-398b30c0f69d&limit=1000",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "result.records[*]",
    "fields": {
      "id": "_id",
      "Column_Header_EN": "Column Header EN",
      "Column_Header_FR": "Column Header FR",
      "Value_Description_EN": "Value Description EN",
      "Value_Description_FR": "Value Description FR"
    },
    "required": [
      "id"
    ]
  },
  "schedule": "daily",
  "key_field": "id"
}

source.json

The request body used by the API, CLI and SDK examples.

{
  "name": "Human-wildlife coexistence header descriptions - Parks Canada",
  "url": "https://open.canada.ca/data/en/api/3/action/datastore_search?resource_id=7f1ce4da-f174-4394-a53d-398b30c0f69d&limit=1000",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "result.records[*]",
    "fields": {
      "id": "_id",
      "Column_Header_EN": "Column Header EN",
      "Column_Header_FR": "Column Header FR",
      "Value_Description_EN": "Value Description EN",
      "Value_Description_FR": "Value Description FR"
    },
    "required": [
      "id"
    ]
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "ckan-open-canada-human-wildlife-coexistence-header-descriptions-parks-",
    "version_id": "fb249909-f220-4e15-b935-273d19d2d25b"
  }
}

REST API

Create an API key under Console → API keys. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/ckan-open-canada-human-wildlife-coexistence-header-descriptions-parks- -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

CLI

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get ckan-open-canada-human-wildlife-coexistence-header-descriptions-parks- --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

TypeScript SDK

The SDK is not on npm yet; see /docs/sdk.

import { SourceFinch } from "@sourcefinch/sdk";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("ckan-open-canada-human-wildlife-coexistence-header-descriptions-parks-");
const source = await sf.sources.create({
  catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

MCP

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Human-wildlife coexistence header descriptions - Parks Canada: get_catalog_source ckan-open-canada-human-wildlife-coexistence-header-descriptions-parks-,
then create_source with its create_source_args (dry run first), then run_source."

Pricing

Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.

More from Parks Canada | Parcs Canada and in recreation.

SourceFinch is independent and is not affiliated with or endorsed by Parks Canada | Parcs Canada. This page describes human-wildlife coexistence header descriptions - parks canada as SourceFinch acquires it.