---
title: "County Metadata (Verse)"
method: GET
path: "/ca/verse"
tags: ["Canada"]
---

# County Metadata (Verse)

`GET /ca/verse`

This endpoint retrieves all Canadian records from our verse schema. These records are admins2's that tell the last time we did a full data pull from the source.

## Query parameters

- `return_geometry` boolean

## Response `200`

A list of current Regrid attributes

- CanadaVerseSchema
  - `type` string
  - `geometry` object, nullable — GeoJSon object The coordinate reference system for all GeoJSON coordinates is a geographic coordinate reference system, using the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees. This is equivalent to the coordinate reference system identified by the Open Geospatial Consortium (OGC) URN An OPTIONAL third-position element SHALL be the height in meters above or below the WGS 84 reference ellipsoid. In the absence of elevation values, applications sensitive to height or depth SHOULD interpret positions as being at local ground or sea level.
    - `type` 'Point' | 'MultiPoint' | 'LineString' | 'MultiLineString' | 'Polygon' | 'MultiPolygon', required
    - `bbox` number[]
    - `coordinates` LinearRing[], required
      - Position[] — A linear ring is a closed LineString with four or more positions. The first and last positions are equivalent, and they MUST contain identical values; their representation SHOULD also be identical. A linear ring is the boundary of a surface or the boundary of a hole in a surface. A linear ring MUST follow the right-hand rule with respect to the area it bounds, i.e., exterior rings are counterclockwise, and holes are clockwise.
        - number[] — GeoJSon fundamental geometry construct. A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element. Implementations SHOULD NOT extend positions beyond three elements because the semantics of extra elements are unspecified and ambiguous. Historically, some implementations have used a fourth element to carry a linear referencing measure (sometimes denoted as "M") or a numerical timestamp, but in most situations a parser will not be able to properly interpret these values. The interpretation and meaning of additional elements is beyond the scope of this specification, and additional elements MAY be ignored by parsers.
  - `properties` object
    - `id` integer
    - `path` string
    - `admin0` string
    - `admin1` string
    - `admin2` string
    - `admin2_slug` integer
    - `admin2_center` integer
    - `admin3` string
    - `sqmi` integer
    - `sqkm` integer
    - `geoid` string
    - `population` string, nullable
    - `table_name` string
    - `total_objects` integer
    - `last_refresh` string, date
    - `canonical_path` string
    - `filename_stem` string
    - `date_added` string, nullable
    - `shapefile_size_flag` string, nullable
    - `assessor_data_date` string, date
    - `usps_data_date` string, date
  - `id` integer

---

[API](https://skmtc.net/regrid/apis/regrid-openapi-specification.md) · [All operations](https://skmtc.net/regrid/apis/regrid-openapi-specification/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/regrid/regrid-openapi-specification/versions/e4abb9a7fcfe/schema)