Open smnorris opened 11 months ago
Yes, bcdata
already pulls the catalogue description. It is not always particularly revealing, but better than nothing:
$ bcdata info WHSE_FOREST_VEGETATION.VEG_COMP_LYR_R1_POLY --indent 2 | head
{
"name": "WHSE_FOREST_VEGETATION.VEG_COMP_LYR_R1_POLY",
"count": 5973855,
"description": "This instantiated table is a join between VEG_COMP_POLY and VEG_COMP_LYR_R1_VW on FEATURE_ID.",
"schema": [
{
"data_type": "NUMBER",
"column_comments": "Provincially unique identifier for an instance of a spatial feature.",
"column_name": "FEATURE_ID",
"short_name": "FEATURE_ID",
🤨😥
$ bcdata info WHSE_FOREST_VEGETATION.BEC_BIOGEOCLIMATIC_POLY --indent 2 | head
{
"name": "WHSE_FOREST_VEGETATION.BEC_BIOGEOCLIMATIC_POLY",
"count": 15666,
"description": null,
"schema": [
{
"short_name": "FTRCLSSSK",
"column_name": "FEATURE_CLASS_SKEY",
"column_comments": "The unique key assigned to a Feature Class by the Ministry of Forests. The Feature Class Skey value for Biogeoclimatic Polygon is 435.",
"data_type": "NUMBER",
The catalogue web page does have a description and detailed purpose. Maybe just a link in the metadata is best. https://catalogue.data.gov.bc.ca/dataset/bec-map
Change the Name (but leave lyrName unchanged) to user friendly display text for the following layers in the project file:
Only a few layers but it could come direct from the catalogue api / bcdata