Contents
- Parcel Data: Versioning (year, month, version)
- Parcel Data download format
- Example URLs for quarterly updates
- Parcel Data: Province/territory or country specifier
- Example URLs for province/territory/national requests
- Parcel Data: File type
- Output field definitions
Parcel data: Versioning (year, month, version)
The Canada Parcel Boundary Data is updated quarterly. The following versioning fields allow control over which version of a file is downloaded.
| Year | The year field specifies the year the file was generated and should be formatted as YYYY, such as “2023”. |
| Month | The month field also specifies a version referring to the month the file was generated. Numbers should be formatted with a leading zero if between 1 and 9, in MM format, like “07”. If a month is requested that doesn’t align with a quarterly update, an HTTP 429 error will be returned. Please note: only the values 01, 04, 07, and 10 will be valid as these correspond to the first month of a quarter. |
| File version | The newest version of the file is automatically retrieved when the version is set to “latest”. In some cases, a manual version can be specified to retrieve a specific file version, as Parcel Data is sometimes generated multiple times within a quarterly period. If a specific version of a file is desired, the format will look like this: “2023.07.B/”, where the final character increments the version number, starting at ‘A’. |
Parcel data download format
curl -vL "https://download.api.smarty.com/parcel-data/can-ab/2026/01/gpkg/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE" -o AB_Parcel_Data.zipExample URLs for quarterly updates
Note that the month fields are 01, 04, 07, or 10.
"https://download.api.smarty.com/parcel-data/can-ab/2026/01/gpkg/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE""https://download.api.smarty.com/parcel-data/can-ab/2026/04/gpkg/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE""https://download.api.smarty.com/parcel-data/can-ab/2026/07/gpkg/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE""https://download.api.smarty.com/parcel-data/can-ab/2026/10/gpkg/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE"Parcel data: Province or country specifier
Here, the province or the entire country is specified according to the purchased plan. The following are valid options. Note that some territories are included, and the ISO-2 is lowercase:
| can-ab | can-bc | can-mb | can-nb | can-nl | can-ns | can-nt | can-nu | can-on | can-pe | can-qc | can-sk | can-yt |
| can-national | ||||||||||||
Example URLs for state/national requests
Alberta example request
"https://download.api.smarty.com/parcel-data/can-ab/2026/04/gpkg/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE"National example request (Must be in the Parquet format)
"https://download.api.smarty.com/parcel-data/can-national/2026/04/parquet/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE"Parcel data: File type
Smarty offers parcel data in several different file formats. You can choose among these by specifying the desired format directly after the month in the URL path. The possible file types and examples of their usage are below:
.gpkg
"https://download.api.smarty.com/parcel-data/can-ab/2026/04/gpkg/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE".parquet
"https://download.api.smarty.com/parcel-data/can-ab/2026/04/parquet/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE".geojson
"https://download.api.smarty.com/parcel-data/can-ab/2026/04/geojson/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE" .csv
"https://download.api.smarty.com/parcel-data/can-ab/2026/04/csv/latest?auth-id=YOUR+AUTH-ID+HERE&auth-token=YOUR+AUTH-TOKEN+HERE"**Important note: ONLY the Parquet file type can be specified when requesting the "national" parcel data
Output field definitions
| Shapefile column name | Field column name | Description | Data type |
dvsn_co de
| census_division_code | A 4-digit number corresponding to a census division boundary from the Canadian Census | varchar |
| par_num_fm | parcel_number_formatted | The parcel ID or parcel number | varchar |
| parcel_num | parcel_number | The parcel ID or parcel number with all non-A-Z and 0-9 characters removed | varchar |
| alt_parc_1 | parcel_number_alternate_1 | A parcel ID number provided by the government that isn’t considered to be the primary parcel ID number used by the government. These could be previously used parcel numbers or alternate ID numbers. | varchar |
| alt_parc_2 | parcel_number_alternate_2 | A parcel ID number provided by the government that isn’t considered to be the primary parcel ID number used by the government. These could be previously used parcel numbers or alternate ID numbers. | varchar |
| alt_parc_3 | parcel_number_alternate_3 | A parcel ID number provided by the government that isn’t considered to be the primary parcel ID number used by the government. These could be previously used parcel numbers or alternate ID numbers. | varchar |
dlv_line_1
| delivery_line_1
| The physical street address for the parcel - the address of the parcel itself. Not every parcel has a street address, especially in agricultural areas or for larger parcels. Also called the "situs address" or "site address". Contains the first delivery line (usually the street address). This can include any of the following: primary number, street predirection, street name, street suffix, street postdirection, secondary | varchar |
dlv_line_2
| delivery_line_2
| The second delivery line of the parcel address (if needed). It's common for this field to remain empty. | varchar |
orig_addr
| original_address | The parcel address fields, as originally provided by the government, encoded in JSON format prior to any cleaning | varchar |
prim_num
| primary_number | The house, PO Box, or building number of the parcel address | varchar |
pre_dir
| street_predirection
| Directional information before a parcel address street name (N, SW, etc.) | varchar |
saddstr
| street_name
| The name of the street of the parcel address | varchar |
str_sfx
| street_suffix
| Abbreviated value describing the parcel address street (St, Ave, Blvd, etc.)
| varchar |
post_dir
| street_postdirection | Directional information after a parcel address street name (N, SW, etc.) | varchar |
secondary
| secondary
| Describes location within a complex/building (Ste, Apt, etc.) and its correlated unit number and/or letter (if any) of the parcel address | varchar |
city_name
| city_name
| The parcel address city name | varchar |
postcode
| postcode | The parcel address postcode | varchar |
cntry_code
| country_code | The parcel address country code | varchar |
lev_1_div
| 1st_level_division | The parcel address 1st division (territory, province, etc.) | varchar |
lev_2_div
| 2nd_level_division | The parcel address 2nd division (county, department, division, etc.) | varchar |
lev_3_div
| 3rd_level_division | The parcel address 3rd division (city, rural, municipality, etc.). In Canada, these overlap with the 2nd-division bounds. | varchar |
| reserve | first_nations_reserve_or_federal_land | The name of the First Nations reserve or federal land on which the parcel is located | varchar |
row_parcel
| right_of_way | Indicates a Right-Of-Way parcel or similar function parcel | varchar |
last_refsh
| date_of_last_refresh
| The date the source data was most recently refreshed | date |
sqm_calc
| sqm_calculated | The parcel square meters as calculated from supplied parcel geometry
| float |
time_updte
| time_of_last_update | The timestamp of the most recent change of any kind to this row in the table (internal record changes and/or county updates). "DATE_OF_LAST_REFRESH" should be used for the parcel data's date. | timestamp |
| parcel | The geometry of the parcel boundary | wkt, wkb, embedded |