Curie Point Depth Contours
Curie point depth (CPD) mapping in Yukon was done using public domain aeromagnetic data from Natural Resources Canada. In this study, two different CPD methodologies were employed using two different window sizes (200 km and 300 km). Qualitatively, the results were broadly consistent regardless of the method or window size. South-central Yukon exhibits shallow CPD values while northern and southeastern Yukon have deeper CPD values. This suggests that south-central Yukon has higher levels of heat flow in the mid-to-lower crust compared to the rest of the territory. The CPD results are largely consistent with heat flow measurements from the near surface. Specifically, regions with shallow CPD estimates correspond to areas with elevated heat flow measurements. Geologically, the regions with shallow CPD correspond to the Cordillera, while deep CPD areas appear to be co-located with continental platform rocks of Ancestral North America. Comparison with Yukon-specific crustal geotherms derived from other data suggest that the CPD estimates for south-central Yukon are systematically too deep by 2 to 12 km. The discrepancy is likely caused by the need to better understand and account for the fractal distribution of magnetization in the crust in Yukon. The results of this CPD study are valuable in that 95% of Yukon has been demarcated into regions of shallow CPD (higher heat flow) and deep CPD (lower heat flow). These findings should be combined with other data, such as heat generation and sediment thickness estimates, to identify the most prospective regions of elevated subsurface heat in Yukon. Contours have been created for the gridded curie point depth at 1 km intervals and are presented along with the grid.
Distributed from GeoYukon by the Government of Yukon . Discover more digital map data and interactive maps from Yukon's digital map data collection. For more information: [email protected]
Datasets available for download
Additional Info
| Field | Value |
|---|---|
| Last Updated | October 20, 2025, 02:11 (UTC) |
| Created | October 20, 2025, 02:11 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
Economy, Society |
|
Title
Title for the Dataset.
|
Curie Point Depth Contours |
|
Description
A description of the dataset.
|
Curie point depth (CPD) mapping in Yukon was done using public domain aeromagnetic data from Natural Resources Canada. In this study, two different CPD methodologies were employed using two different window sizes (200 km and 300 km). Qualitatively, the results were broadly consistent regardless of the method or window size. South-central Yukon exhibits shallow CPD values while northern and southeastern Yukon have deeper CPD values. This suggests that south-central Yukon has higher levels of heat flow in the mid-to-lower crust compared to the rest of the territory. The CPD results are largely consistent with heat flow measurements from the near surface. Specifically, regions with shallow CPD estimates correspond to areas with elevated heat flow measurements. Geologically, the regions with shallow CPD correspond to the Cordillera, while deep CPD areas appear to be co-located with continental platform rocks of Ancestral North America. Comparison with Yukon-specific crustal geotherms derived from other data suggest that the CPD estimates for south-central Yukon are systematically too deep by 2 to 12 km. The discrepancy is likely caused by the need to better understand and account for the fractal distribution of magnetization in the crust in Yukon. The results of this CPD study are valuable in that 95% of Yukon has been demarcated into regions of shallow CPD (higher heat flow) and deep CPD (lower heat flow). These findings should be combined with other data, such as heat generation and sediment thickness estimates, to identify the most prospective regions of elevated subsurface heat in Yukon. Contours have been created for the gridded curie point depth at 1 km intervals and are presented along with the grid. Distributed from GeoYukon by the Government of Yukon . Discover more digital map data and interactive maps from Yukon's digital map data collection. For more information: [email protected] |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
|
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2024-09-09 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
|
|
License
License used to access the dataset.
|
Open Government Licence - Yukon |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://open.canada.ca/data/en/dataset/d9085d7f-7e97-411d-8502-3a69e66bbef3 |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
Government of Yukon | Gouvernement du Yukon |
|
Contact Point
Who to contact regarding access?
|
Government of Yukon; Government of Yukon; Geomatics Yukon |
|
Contact Point Email
The email to contact regarding access?
|
|
|
Publisher
Publisher of the dataset.
|
|
|
Publisher Email
Email of the publisher.
|
[email protected] |
|
Author
Author of the dataset.
|
|
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
|
|
Language
Language(s) of the dataset
|
|
|
Link to dataset description
A URL to an external document describing the dataset.
|
|
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
|
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
|
|
Number of data columns
If tabular dataset, total number of unique columns.
|
|
|
Number of data cells
If tabular dataset, total number of cells with data.
|
|
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments