├── pages ├── old ├── images │ ├── delivery_kit │ │ ├── xyz_whse │ │ │ └── WHSE_SCHEMA_NAME │ │ │ │ ├── revert_to_previous │ │ │ │ └── readme.txt │ │ │ │ ├── dataload │ │ │ │ ├── readme.txt │ │ │ │ ├── bcgw-i.bcgov__idwdlvr1.bcgov.sde │ │ │ │ └── dbCreds.json │ │ │ │ ├── ddl │ │ │ │ └── readme.txt │ │ │ │ └── scripts │ │ │ │ ├── xyz_whse_remove_mdsys_rows.sql │ │ │ │ └── xyz_whse_compute_mdsys_extents.sql │ │ ├── gsr_whse │ │ │ ├── WHSE_IMAGERY_AND_BASE_MAPS │ │ │ │ └── N.N.N_descriptive_name_of_release │ │ │ │ │ ├── revert_to_previous │ │ │ │ │ └── readme.txt │ │ │ │ │ ├── dataload │ │ │ │ │ ├── readme.txt │ │ │ │ │ ├── bcgw-i.bcgov__idwdlvr1.bcgov.sde │ │ │ │ │ └── dbCreds.json │ │ │ │ │ ├── ddl │ │ │ │ │ └── readme.txt │ │ │ │ │ └── scripts │ │ │ │ │ ├── gsr_whse_remove_mdsys_rows.sql │ │ │ │ │ └── gsr_whse_compute_mdsys_extents.sql │ │ │ └── setup │ │ │ │ └── gsr_whse.N.N.N.README │ │ └── media │ │ │ └── Gogs_Instructions_For_Vendors_media │ │ │ └── media │ │ │ ├── Thumbs.db │ │ │ ├── image1.png │ │ │ ├── image10.png │ │ │ ├── image11.png │ │ │ ├── image12.png │ │ │ ├── image2.png │ │ │ ├── image3.png │ │ │ ├── image5.png │ │ │ ├── image6.png │ │ │ ├── image7.png │ │ │ ├── image8.png │ │ │ ├── image9.png │ │ │ └── Sign In with OpenID Connect.PNG │ ├── Tby.PNG │ ├── red_x.png │ ├── add_org.png │ ├── edit_org.png │ ├── grey_na.png │ ├── add_group.png │ ├── admin_tab.png │ ├── edit_group.png │ ├── fme_setup.png │ ├── grey_dash.png │ ├── image_code.png │ ├── image_fork.png │ ├── acc_settings.png │ ├── add_group_1.png │ ├── add_group_2.png │ ├── add_member_1.png │ ├── add_member_2.png │ ├── delete_member.png │ ├── edit_dataset.png │ ├── edit_resource.png │ ├── green_check.png │ ├── image_DataBC.png │ ├── image_clone.png │ ├── image_counter.png │ ├── image_fork_to.png │ ├── image_issues.png │ ├── image_testers.png │ ├── upload_file.png │ ├── user_details.jpg │ ├── delete_dataset.png │ ├── image_copy_url.png │ ├── image_keywords.png │ ├── image_new_issue.png │ ├── image_push_code.png │ ├── publish_record.png │ ├── Before_You_Start.docx │ ├── add_org_or_group.png │ ├── data_preparation.png │ ├── delete_resource_1.png │ ├── delete_resource_2.png │ ├── image_add_resource.png │ ├── image_feature_type.png │ ├── image_gogs_login.png │ ├── image_pullrequest.png │ ├── image_tester_inbc.png │ ├── mandatory_standard.png │ ├── upload_save_file.png │ ├── wf_BCGWReadiness.png │ ├── wf_DatsetLogfile.png │ ├── image_BCGWReadiness.png │ ├── image_github_topleft.png │ ├── image_reset_password.png │ ├── image_shared_folders.png │ ├── image_unlock_account.png │ ├── image_vertex_creator.png │ ├── preferred_guideline.png │ ├── wf_MetadataCreation.png │ ├── wf_MetadataReadiness.png │ ├── image_BCGW_Add_Dataset.JPG │ ├── image_bcdc_description.png │ ├── image_comparing_changes.png │ ├── image_ora_feature_type.png │ ├── image_submit_new_issue.png │ ├── wf_BCGWDataPublication.PNG │ ├── MXD_Red_Exclamation_Mark.JPG │ ├── image_create_pull_request.png │ ├── image_git_fetch_upstream.png │ ├── image_gogs_buttons_to_use.png │ ├── image_linking_mdb_sources.png │ ├── mandatory_standard_small.png │ ├── preferred_guideline_small.png │ ├── Start_with_the_end_in_mind.JPG │ ├── account_settings_api_key_1.png │ ├── account_settings_api_key_2.png │ ├── image_create_pull_request2.png │ ├── image_git_fetch_upstream_2.png │ ├── image_linking_fgdb_sources.png │ ├── image_linking_xlsx_sources.png │ ├── image_transformers_linking.png │ ├── BCGW_Data_Retirement_Workflow.PNG │ ├── image_bcdc_data_and_resources.png │ ├── Dataset_Model_Current_TEMPLATE.xlsx │ ├── image_ArcCatalog_Set_Data_Sources.png │ ├── image_allow_feature_type_editing.png │ ├── image_embed_connection_parameters.png │ ├── wms_wfs_getting_started │ │ ├── agp_logo.png │ │ ├── qgis_logo.png │ │ ├── agp_wms_styles.png │ │ ├── qgis_identify.png │ │ ├── qgis_refresh.png │ │ ├── qgis_wfs_icon.png │ │ ├── qgis_wms_icon.png │ │ ├── qgis_wms_view.png │ │ ├── agp_wfs_bbox_forest.png │ │ ├── agp_wfs_connection.png │ │ ├── agp_wms_connection.png │ │ ├── agp_wms_health_view.png │ │ ├── qgis_identify_wms.png │ │ ├── qgis_wfs_connection.png │ │ ├── qgis_wms_connection.png │ │ ├── qgis_wms_health_add.png │ │ ├── agp_wfs_research_view.png │ │ ├── qgis_data_source_mgr.png │ │ ├── qgis_wfs_regdist_add.png │ │ ├── qgis_wfs_research_add.png │ │ ├── agp_wfs_groundwater_bbox.png │ │ ├── agp_wfs_new_connection.png │ │ ├── agp_wfs_research_labels.png │ │ ├── agp_wms_new_connection.png │ │ ├── qgis_new_wfs_connection.png │ │ ├── qgis_new_wms_connection.png │ │ ├── qgis_wfs_research_labels.png │ │ ├── qgis_wfs_research_view.png │ │ ├── agp_wfs_research_attributes.png │ │ ├── agp_wfs_research_categorized.png │ │ ├── qgis_wfs_research_attributes.png │ │ ├── qgis_wfs_research_categorized.png │ │ ├── agp_wfs_groundwater_connection.png │ │ ├── agp_wfs_new_connection_settings.png │ │ ├── agp_wms_new_connection_settings.png │ │ ├── agp_wfs_groundwater_attributes_20000.png │ │ └── agp_wfs_groundwater_attributes_query.png │ ├── Dataset_Model_ddl_Current_TEMPLATE.xlsx │ ├── GSR_Dataset_Model_Current_TEMPLATE.xlsx │ ├── image_BCGW_ArcCat_Replace_Data_Source.png │ ├── Steps_for_placing_data_in_the_warehouse.JPG │ ├── image_information_management_through_the_BCGW.png │ └── data_preparation.drawio ├── assets │ └── images │ │ ├── bclogo.png │ │ ├── check.jpg │ │ ├── check.png │ │ ├── checklarge.jpg │ │ └── BCID_H_rgb_pos.png ├── pages │ └── assets │ │ └── images │ │ ├── check.jpg │ │ ├── check.png │ │ ├── bclogo.png │ │ ├── checklarge.jpg │ │ └── BCID_H_rgb_pos.png ├── dps_maphub_account_details.md ├── dsg.md ├── dsg_security_access.md ├── _sass │ ├── overrides.scss │ └── custom │ │ └── custom.scss ├── dps_bcdc_restricted_notice.md ├── dsg_bcgw.md ├── dps_loc.md ├── dsg_bcdc.md ├── dps_bcdc_api_w_how_to_use.md ├── dsg_loc_address_geocoding_standards.md ├── dg.md ├── dps_bcdc.md ├── dps_webmapping.md ├── dps.md ├── dps_bcdc_w_how_to_use_the_ui.md ├── dps_data_distribution.md ├── dps_loc_address_geocoder.md ├── open_data.md ├── dps_bcgw_w_data_retirement.md ├── template.md ├── dps_maphub_terms_of_use.md ├── dps_webmapping_providers_w.md ├── dps_licences.md ├── open_data_licence_create.md ├── dps_bcdc_w_webservice_api.md ├── map_getting_started_arcgispro_wms.md ├── dps_data_distribution_providers_w_.md ├── dps_bcdc_w_dataset.md ├── dps_bcdc_w_application.md ├── map_getting_started_qgis_wms.md ├── dps_maphub_glossary.md ├── dps_bcgw.md ├── dps_bcdc_api_w_resource_mgmt.md ├── map_getting_started_arcgispro_wfs.md ├── dps_bcdc_api_w_record_mgmt.md ├── dps_webmapping_downstream_w.md ├── map_wms_wfs_getting_started.md ├── map_getting_started_qgis_wfs.md ├── dsg_bcdc_metadata_standards.md ├── dps_bcdc_classic_w_api_metadata_mgmt.md ├── we_value_your_contributions.md ├── dps_bcdc_classic_w_webservice_api.md ├── dps_bcdc_classic_w_application.md ├── dsg_bcgw_data_classification_hierarchy.md └── dsg_before_you_start.md ├── Gemfile ├── .gitignore ├── COMPLIANCE.yaml ├── README.md ├── index.md ├── _config.yml └── assets └── js └── search-data.json /pages/old: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/revert_to_previous/readme.txt: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /pages/images/Tby.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/Tby.PNG -------------------------------------------------------------------------------- /pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/dataload/readme.txt: -------------------------------------------------------------------------------- 1 | This is where FME fmw's are put. -------------------------------------------------------------------------------- /pages/images/red_x.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/red_x.png -------------------------------------------------------------------------------- /pages/images/add_org.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/add_org.png -------------------------------------------------------------------------------- /pages/images/edit_org.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/edit_org.png -------------------------------------------------------------------------------- /pages/images/grey_na.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/grey_na.png -------------------------------------------------------------------------------- /pages/images/add_group.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/add_group.png -------------------------------------------------------------------------------- /pages/images/admin_tab.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/admin_tab.png -------------------------------------------------------------------------------- /pages/images/edit_group.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/edit_group.png -------------------------------------------------------------------------------- /pages/images/fme_setup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/fme_setup.png -------------------------------------------------------------------------------- /pages/images/grey_dash.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/grey_dash.png -------------------------------------------------------------------------------- /pages/images/image_code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_code.png -------------------------------------------------------------------------------- /pages/images/image_fork.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_fork.png -------------------------------------------------------------------------------- /pages/assets/images/bclogo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/assets/images/bclogo.png -------------------------------------------------------------------------------- /pages/assets/images/check.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/assets/images/check.jpg -------------------------------------------------------------------------------- /pages/assets/images/check.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/assets/images/check.png -------------------------------------------------------------------------------- /pages/images/acc_settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/acc_settings.png -------------------------------------------------------------------------------- /pages/images/add_group_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/add_group_1.png -------------------------------------------------------------------------------- /pages/images/add_group_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/add_group_2.png -------------------------------------------------------------------------------- /pages/images/add_member_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/add_member_1.png -------------------------------------------------------------------------------- /pages/images/add_member_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/add_member_2.png -------------------------------------------------------------------------------- /pages/images/delete_member.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delete_member.png -------------------------------------------------------------------------------- /pages/images/edit_dataset.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/edit_dataset.png -------------------------------------------------------------------------------- /pages/images/edit_resource.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/edit_resource.png -------------------------------------------------------------------------------- /pages/images/green_check.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/green_check.png -------------------------------------------------------------------------------- /pages/images/image_DataBC.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_DataBC.png -------------------------------------------------------------------------------- /pages/images/image_clone.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_clone.png -------------------------------------------------------------------------------- /pages/images/image_counter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_counter.png -------------------------------------------------------------------------------- /pages/images/image_fork_to.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_fork_to.png -------------------------------------------------------------------------------- /pages/images/image_issues.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_issues.png -------------------------------------------------------------------------------- /pages/images/image_testers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_testers.png -------------------------------------------------------------------------------- /pages/images/upload_file.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/upload_file.png -------------------------------------------------------------------------------- /pages/images/user_details.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/user_details.jpg -------------------------------------------------------------------------------- /pages/images/delete_dataset.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delete_dataset.png -------------------------------------------------------------------------------- /pages/images/image_copy_url.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_copy_url.png -------------------------------------------------------------------------------- /pages/images/image_keywords.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_keywords.png -------------------------------------------------------------------------------- /pages/images/image_new_issue.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_new_issue.png -------------------------------------------------------------------------------- /pages/images/image_push_code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_push_code.png -------------------------------------------------------------------------------- /pages/images/publish_record.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/publish_record.png -------------------------------------------------------------------------------- /pages/assets/images/checklarge.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/assets/images/checklarge.jpg -------------------------------------------------------------------------------- /pages/images/Before_You_Start.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/Before_You_Start.docx -------------------------------------------------------------------------------- /pages/images/add_org_or_group.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/add_org_or_group.png -------------------------------------------------------------------------------- /pages/images/data_preparation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/data_preparation.png -------------------------------------------------------------------------------- /pages/images/delete_resource_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delete_resource_1.png -------------------------------------------------------------------------------- /pages/images/delete_resource_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delete_resource_2.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/revert_to_previous/readme.txt: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/ddl/readme.txt: -------------------------------------------------------------------------------- 1 | This is where DDL generated through Oracle Designer is put. -------------------------------------------------------------------------------- /pages/images/image_add_resource.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_add_resource.png -------------------------------------------------------------------------------- /pages/images/image_feature_type.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_feature_type.png -------------------------------------------------------------------------------- /pages/images/image_gogs_login.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_gogs_login.png -------------------------------------------------------------------------------- /pages/images/image_pullrequest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_pullrequest.png -------------------------------------------------------------------------------- /pages/images/image_tester_inbc.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_tester_inbc.png -------------------------------------------------------------------------------- /pages/images/mandatory_standard.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/mandatory_standard.png -------------------------------------------------------------------------------- /pages/images/upload_save_file.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/upload_save_file.png -------------------------------------------------------------------------------- /pages/images/wf_BCGWReadiness.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wf_BCGWReadiness.png -------------------------------------------------------------------------------- /pages/images/wf_DatsetLogfile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wf_DatsetLogfile.png -------------------------------------------------------------------------------- /pages/pages/assets/images/check.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/pages/assets/images/check.jpg -------------------------------------------------------------------------------- /pages/pages/assets/images/check.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/pages/assets/images/check.png -------------------------------------------------------------------------------- /pages/images/image_BCGWReadiness.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_BCGWReadiness.png -------------------------------------------------------------------------------- /pages/images/image_github_topleft.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_github_topleft.png -------------------------------------------------------------------------------- /pages/images/image_reset_password.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_reset_password.png -------------------------------------------------------------------------------- /pages/images/image_shared_folders.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_shared_folders.png -------------------------------------------------------------------------------- /pages/images/image_unlock_account.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_unlock_account.png -------------------------------------------------------------------------------- /pages/images/image_vertex_creator.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_vertex_creator.png -------------------------------------------------------------------------------- /pages/images/preferred_guideline.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/preferred_guideline.png -------------------------------------------------------------------------------- /pages/images/wf_MetadataCreation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wf_MetadataCreation.png -------------------------------------------------------------------------------- /pages/images/wf_MetadataReadiness.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wf_MetadataReadiness.png -------------------------------------------------------------------------------- /pages/pages/assets/images/bclogo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/pages/assets/images/bclogo.png -------------------------------------------------------------------------------- /pages/assets/images/BCID_H_rgb_pos.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/assets/images/BCID_H_rgb_pos.png -------------------------------------------------------------------------------- /pages/images/image_BCGW_Add_Dataset.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_BCGW_Add_Dataset.JPG -------------------------------------------------------------------------------- /pages/images/image_bcdc_description.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_bcdc_description.png -------------------------------------------------------------------------------- /pages/images/image_comparing_changes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_comparing_changes.png -------------------------------------------------------------------------------- /pages/images/image_ora_feature_type.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_ora_feature_type.png -------------------------------------------------------------------------------- /pages/images/image_submit_new_issue.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_submit_new_issue.png -------------------------------------------------------------------------------- /pages/images/wf_BCGWDataPublication.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wf_BCGWDataPublication.PNG -------------------------------------------------------------------------------- /pages/pages/assets/images/checklarge.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/pages/assets/images/checklarge.jpg -------------------------------------------------------------------------------- /pages/images/MXD_Red_Exclamation_Mark.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/MXD_Red_Exclamation_Mark.JPG -------------------------------------------------------------------------------- /pages/images/image_create_pull_request.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_create_pull_request.png -------------------------------------------------------------------------------- /pages/images/image_git_fetch_upstream.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_git_fetch_upstream.png -------------------------------------------------------------------------------- /pages/images/image_gogs_buttons_to_use.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_gogs_buttons_to_use.png -------------------------------------------------------------------------------- /pages/images/image_linking_mdb_sources.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_linking_mdb_sources.png -------------------------------------------------------------------------------- /pages/images/mandatory_standard_small.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/mandatory_standard_small.png -------------------------------------------------------------------------------- /pages/images/preferred_guideline_small.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/preferred_guideline_small.png -------------------------------------------------------------------------------- /Gemfile: -------------------------------------------------------------------------------- 1 | source "https://rubygems.org" 2 | gem "github-pages", group: :jekyll_plugins 3 | gem "just-the-docs" 4 | 5 | gem "webrick", "~> 1.8" 6 | -------------------------------------------------------------------------------- /pages/images/Start_with_the_end_in_mind.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/Start_with_the_end_in_mind.JPG -------------------------------------------------------------------------------- /pages/images/account_settings_api_key_1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/account_settings_api_key_1.png -------------------------------------------------------------------------------- /pages/images/account_settings_api_key_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/account_settings_api_key_2.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/dataload/readme.txt: -------------------------------------------------------------------------------- 1 | This is where FME fmw's are put. -------------------------------------------------------------------------------- /pages/images/image_create_pull_request2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_create_pull_request2.png -------------------------------------------------------------------------------- /pages/images/image_git_fetch_upstream_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_git_fetch_upstream_2.png -------------------------------------------------------------------------------- /pages/images/image_linking_fgdb_sources.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_linking_fgdb_sources.png -------------------------------------------------------------------------------- /pages/images/image_linking_xlsx_sources.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_linking_xlsx_sources.png -------------------------------------------------------------------------------- /pages/images/image_transformers_linking.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_transformers_linking.png -------------------------------------------------------------------------------- /pages/pages/assets/images/BCID_H_rgb_pos.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/pages/assets/images/BCID_H_rgb_pos.png -------------------------------------------------------------------------------- /pages/images/BCGW_Data_Retirement_Workflow.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/BCGW_Data_Retirement_Workflow.PNG -------------------------------------------------------------------------------- /pages/images/image_bcdc_data_and_resources.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_bcdc_data_and_resources.png -------------------------------------------------------------------------------- /pages/images/Dataset_Model_Current_TEMPLATE.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/Dataset_Model_Current_TEMPLATE.xlsx -------------------------------------------------------------------------------- /pages/images/image_ArcCatalog_Set_Data_Sources.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_ArcCatalog_Set_Data_Sources.png -------------------------------------------------------------------------------- /pages/images/image_allow_feature_type_editing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_allow_feature_type_editing.png -------------------------------------------------------------------------------- /pages/images/image_embed_connection_parameters.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_embed_connection_parameters.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_logo.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_logo.png -------------------------------------------------------------------------------- /pages/images/Dataset_Model_ddl_Current_TEMPLATE.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/Dataset_Model_ddl_Current_TEMPLATE.xlsx -------------------------------------------------------------------------------- /pages/images/GSR_Dataset_Model_Current_TEMPLATE.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/GSR_Dataset_Model_Current_TEMPLATE.xlsx -------------------------------------------------------------------------------- /pages/images/image_BCGW_ArcCat_Replace_Data_Source.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_BCGW_ArcCat_Replace_Data_Source.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wms_styles.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wms_styles.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_identify.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_identify.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_refresh.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_refresh.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_icon.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wms_icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wms_icon.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wms_view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wms_view.png -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | _site/** 2 | _site/ 3 | .bundle/config 4 | .bundle/ 5 | .jekyll-cache/Jekyll 6 | .jekyll-cache/ 7 | .DS_store 8 | .Gemfile.lock 9 | *.lock 10 | /.vs 11 | -------------------------------------------------------------------------------- /pages/images/Steps_for_placing_data_in_the_warehouse.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/Steps_for_placing_data_in_the_warehouse.JPG -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/ddl/readme.txt: -------------------------------------------------------------------------------- 1 | This is where DDL generated through Oracle Designer is put. -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_bbox_forest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_bbox_forest.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wms_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wms_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wms_health_view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wms_health_view.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_identify_wms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_identify_wms.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wms_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wms_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wms_health_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wms_health_add.png -------------------------------------------------------------------------------- /pages/images/image_information_management_through_the_BCGW.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/image_information_management_through_the_BCGW.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_research_view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_research_view.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_data_source_mgr.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_data_source_mgr.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_regdist_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_regdist_add.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_research_add.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_research_add.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_groundwater_bbox.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_groundwater_bbox.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_new_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_new_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_research_labels.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_research_labels.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wms_new_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wms_new_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_new_wfs_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_new_wfs_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_new_wms_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_new_wms_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_research_labels.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_research_labels.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_research_view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_research_view.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_research_attributes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_research_attributes.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_research_categorized.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_research_categorized.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_research_attributes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_research_attributes.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/qgis_wfs_research_categorized.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/qgis_wfs_research_categorized.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_groundwater_connection.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_groundwater_connection.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_new_connection_settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_new_connection_settings.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wms_new_connection_settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wms_new_connection_settings.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_groundwater_attributes_20000.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_groundwater_attributes_20000.png -------------------------------------------------------------------------------- /pages/images/wms_wfs_getting_started/agp_wfs_groundwater_attributes_query.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/wms_wfs_getting_started/agp_wfs_groundwater_attributes_query.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/Thumbs.db: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/Thumbs.db -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image1.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image10.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image10.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image11.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image11.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image12.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image12.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image2.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image3.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image5.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image6.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image6.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image7.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image7.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image8.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image8.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image9.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/image9.png -------------------------------------------------------------------------------- /pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/dataload/bcgw-i.bcgov__idwdlvr1.bcgov.sde: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/dataload/bcgw-i.bcgov__idwdlvr1.bcgov.sde -------------------------------------------------------------------------------- /pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/Sign In with OpenID Connect.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/media/Gogs_Instructions_For_Vendors_media/media/Sign In with OpenID Connect.PNG -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/dataload/bcgw-i.bcgov__idwdlvr1.bcgov.sde: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bcgov/data-publication/HEAD/pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/dataload/bcgw-i.bcgov__idwdlvr1.bcgov.sde -------------------------------------------------------------------------------- /pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/scripts/xyz_whse_remove_mdsys_rows.sql: -------------------------------------------------------------------------------- 1 | -- 2 | -- remove USER_SDO_GEOM_METADATA rows for the datasets dropped as part of an uninstall 3 | -- 4 | 5 | DELETE FROM user_sdo_geom_metadata WHERE table_name = 'fillInTableOrView'; 6 | -- repeat for all spatial tables and views 7 | COMMIT; 8 | -------------------------------------------------------------------------------- /COMPLIANCE.yaml: -------------------------------------------------------------------------------- 1 | name: compliance 2 | description: | 3 | This document is used to track this project's PIA and STRA 4 | compliance. 5 | spec: 6 | - name: PIA 7 | status: in-progress 8 | last-updated: '2020-05-04T18:41:55.424Z' 9 | - name: STRA 10 | status: in-progress 11 | last-updated: '2020-05-04T18:41:55.424Z' 12 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/scripts/gsr_whse_remove_mdsys_rows.sql: -------------------------------------------------------------------------------- 1 | -- 2 | -- remove USER_SDO_GEOM_METADATA rows for the datasets dropped as part of an uninstall 3 | -- 4 | 5 | DELETE FROM user_sdo_geom_metadata WHERE table_name = 'fillInView'; 6 | -- repeat for all spatial views 7 | COMMIT; 8 | -------------------------------------------------------------------------------- /pages/dps_maphub_account_details.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: AGO User account details 4 | grand_parent: Web-based Mapping 5 | parent: BC Map Hub - Publication Workflow 6 | nav_order: 811 7 | has_toc: false 8 | --- 9 | 10 | # ArcGIS Online Digital Application - User account details 11 | 12 | ![Single and Multi User account details](images/user_details.jpg) 13 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Publishing to the DataBC Program 2 | Standards, tips, and tricks to help you on your way. 3 | 4 | See Documentation - [https://bcgov.github.io/data-publication](https://bcgov.github.io/data-publication) 5 | 6 | [![img](https://img.shields.io/badge/Lifecycle-Maturing-007EC6)](https://github.com/bcgov/repomountie/blob/master/doc/lifecycle-badges.md) 7 | [![img](https://img.shields.io/badge/Lifecycle-Stable-97ca00)](https://github.com/bcgov/repomountie/blob/master/doc/lifecycle-badges.md) 8 | -------------------------------------------------------------------------------- /pages/dsg.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Appendix - Common Items 4 | nav_order: 10 5 | has_children: true 6 | has_toc: false 7 | --- 8 | 9 | # COMMON DATA STANDARDS AND GUIDELINES 10 | 11 | The pages in this section decribe common standards and guidelines for data published via the DataBC Program's products. 12 | 13 | Explore the BC Data Catalogue, BC Geographic Warehouse and Location Services sections for service specific standards and guidelines. 14 | 15 | ---------------------------------- 16 | -------------------------------------------------------------------------------- /pages/dsg_security_access.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Security and Access 4 | nav_order: 82 5 | parent: Common Data Standards and Guidelines 6 | has_children: true 7 | nav_exclude: true 8 | has_toc: false 9 | --- 10 | 11 | # SECURITY AND ACCESS 12 | 13 | The pages in this section describe Security and Access standards and guidelines for data published via the DataBC Program's products. 14 | 15 | + [BCGW Proxy Naming Standards](dsg_security_access_proxy_creation_standards.md) 16 | + [BCGW Role Naming Standards](dsg_security_access_role_naming_creation.md) 17 | + ADAM Role Naming Standards 18 | + For iMapBC and IMF2: Prefix __MPCM__ and then follow the BCGW Role Naming Standards 19 | + For Distribtion: Prefix __DWDS__ and then follow the BCGW Role Naming Standards 20 | 21 | ------------------------------------------------------- 22 | -------------------------------------------------------------------------------- /pages/_sass/overrides.scss: -------------------------------------------------------------------------------- 1 | a:not([class]){ 2 | background-image: none; 3 | } 4 | 5 | a:not([class]):hover{ 6 | text-decoration: none; 7 | } 8 | 9 | .page-content a { 10 | text-decoration: underline; 11 | } 12 | 13 | .site-title { 14 | font-size: 20px !important; 15 | } 16 | 17 | .navigation-list-link a:hover{ 18 | text-decoration: underline; 19 | } 20 | 21 | blockquote { 22 | background: #efefef; 23 | padding: 10px 10px 1px 10px; 24 | border-left: 5px solid #ccc; 25 | margin-left: 0px; 26 | } 27 | 28 | table { 29 | display: table; 30 | min-width: 100%; 31 | background-color: $blue-100; 32 | color: #b07f13; 33 | border-style: solid; 34 | } 35 | 36 | .side-bar { 37 | width: 400px; 38 | align-items: flex-start; 39 | flex-wrap: nowrap; 40 | position: fixed; 41 | } 42 | 43 | .main { 44 | width: calc( 45 | (100%-400px)); 46 | margin-left: 400px; 47 | } 48 | -------------------------------------------------------------------------------- /pages/dps_bcdc_restricted_notice.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | nav_order: 4 | title: template 5 | parent: 6 | grand_parent: 7 | has_toc: false 8 | nav_exclude: true 9 | --- 10 | 11 | Download of this Data is restricted or not accessible at this time. 12 | 13 | Please review metadata record for the following: 14 | 15 | + The Access and Security section on the record for understanding of what is intended. 16 | 17 | + At times some datasets have business views that are accessible, this is usually linked in the description. 18 | 19 | + Some datasets are accessible upon request, example: 20 | 21 | __Archaeology Data:__ 22 | 23 | https://www2.gov.bc.ca/gov/content?id=17EB21F8122D4061842C6B2CA468CFD5 24 | 25 | __TRIM Data__ 26 | 27 | [Email GeoBC](mailto:GeoBCInfo@gov.bc.ca) 28 | 29 | If you are unable to reach the Data Contact, please contact the [DataBC Team](mailto:Data@gov.bc.ca) for assistance. 30 | -------------------------------------------------------------------------------- /pages/dsg_bcgw.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: BCGW Standards and Guidelines 4 | nav_order: 24 5 | parent: BC Geographic Warehouse 6 | has_children: true 7 | nav_exclude: true 8 | has_toc: false 9 | --- 10 | [View in Data Publication and Services site](https://bcgov.github.io/data-publication/pages/dsg_bcgw.html) 11 | 12 | # BC GEOGRAPHIC WAREHOUSE - STANDARDS AND GUIDELINES 13 | 14 | The pages in this section provide information on the standards and guidelines for the BC Geographic Warehouse (BCGW). 15 | 16 | 1. [Layer File Presentation](https://bcgov.github.io/data-publication/pages/dsg_bcgw_layer_file_presentation.html) provides guidance on how to build ArcGIS layerfiles for presentation in iMap and the Layer Library in ArcGIS. 17 | 1. [Roles and Responsibilities](https://bcgov.github.io/data-publication/pages/dsg_bcgw_roles_responsibilities.html) describes the required persons and how they are involved in the Data Delivery process. 18 | -------------------------------------------------------------------------------- /pages/dps_loc.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Location Services 4 | nav_order: 6 5 | has_children: true 6 | has_toc: false 7 | --- 8 | 9 | # LOCATION SERVICES 10 | 11 | Location Services are a suite of web services that locate civic addresses and place names, enable sharing areas of interest and road network routing. 12 | 13 | These services reference authoritative data and are designed to be integrated into business workflows and applications. 14 | + [BC Address Geocoder](https://bcgov.github.io/data-publication/pages/dps_loc_address_geocoder.html) 15 | + [BC Route Planner](https://www2.gov.bc.ca/gov/content?id=9D99E684CCD042CD88FADC51E079B4B5) 16 | + [Geomark Web Service](https://www2.gov.bc.ca/gov/content?id=F6BAF45131954020BCFD2EBCC456F084) 17 | 18 | 19 | For more information, visit [Location Services](https://www2.gov.bc.ca/gov/content?id=45603554C95E4E5E8C78C16FAF07A1FD). 20 | 21 | For help using or accessing these services, please [open a ticket with the Data Systems & Services request system](https://dpdd.atlassian.net/servicedesk/customer/portal/1/group/7). 22 | 23 | ------------------------------------------------------- 24 | -------------------------------------------------------------------------------- /pages/dsg_bcdc.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Standards & Guidelines 4 | nav_order: 35 5 | parent: BC Data Catalogue 6 | has_children: true 7 | nav_exclude: true 8 | has_toc: false 9 | --- 10 | 11 | # BC DATA CATALOGUE - STANDARDS AND GUIDELINES 12 | 13 | The pages in this section provide information on the standards and guidelines for data publication in the BC Data Catalogue (BCDC). 14 | 15 | 1. [File-Based Content](https://bcgov.github.io/data-publication/pages/dsg_bcdc_file_based_content.html) identifies the file formats which must be used when publishing Open Datasets and provides guidelines for specific physical file formats in order to optimize datasets for machine processing. 16 | 1. [Metadata Standards](https://bcgov.github.io/data-publication/pages/dsg_bcdc_metadata_standards.html) describes recommended metadata standards and provides a high-level summary of metadata requirements for data objects when publishing data to the BC Data Catalogue. 17 | 1. [Roles and Responsibilities](https://bcgov.github.io/data-publication/pages/dsg_bcdc_roles_responsibilities.html) describes why the roles and responsibilities of the Data Custodians, Managers and Stewards are important and the obligations of each of these. 18 | -------------------------------------------------------------------------------- /pages/dps_bcdc_api_w_how_to_use.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Content Mgmt/Use - API 4 | nav_order: 34 5 | parent: BC Data Catalogue 6 | has_children: true 7 | has_toc: false 8 | --- 9 | 10 | # **BC Data Catalogue API** 11 | 12 | The BC Data Catalogue is built using an open source data portal software called [CKAN](https://github.com/ckan/ckan/blob/master/README.rst). 13 | Some users may prefer to use the API to manage thier content in the BC Data Catalogue, while others may prefer to use the application itself. 14 | This page provides guidance on the use of the Catalogue API to manage resources and data within the BC Data Catalogue. 15 | 16 | \* You do not need an API key nor an account if you are only accessing publicly available data. All records published under the Open Government Licence - British Columbia and its variations are publicly available. 17 | 18 | If you have questions about accessing data in the B.C. Data Catalogue, please submit a support request via our [request portal](https://dpdd.atlassian.net/servicedesk/customer/portal/1). 19 | 20 | 21 | * [Common API Calls](./dps_bcdc_api_w_common_calls.md) 22 | * [Record Management using the API](./dps_bcdc_api_w_record_mgmt.md) 23 | * [Resource Management using the API](./dps_bcdc_api_w_resource_mgmt.md) 24 | -------------------------------------------------------------------------------- /pages/dsg_loc_address_geocoding_standards.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Address & Geocoding Standards 4 | nav_order: 611 5 | parent: BC Address Geocoder 6 | grand_parent: Location Services 7 | has_toc: false 8 | --- 9 | 10 | # ADDRESS AND GEOCODING STANDARDS 11 | The [_BC Address Geocoder_](https://www2.gov.bc.ca/gov/content?id=118DD57CD9674D57BDBD511C2E78DC0D) can be used to resolve the physical locations (i.e., latitude and longitude) and correct, standardized form of civic and non-civic addresses in British Columbia. 12 | 13 | + It is based on the [_Physical Address and Geocoding Standards _Conceptual Model_](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/physical_address_and_geocoding_standards_-_conceptual_model.pdf), 14 | + Which conforms to the [_Mailing, Delivery, and Residential Address Data Standards_](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/address_data_standards_-_mailing_delivery_residential.pdf) 15 | + Published by the [_BC Office of the Chief Information Officer_](https://www2.gov.bc.ca/gov/content?id=4726AAEF681C40B192CFA11A00236A83). 16 | 17 | ------------------------------------------------------- 18 | -------------------------------------------------------------------------------- /pages/dg.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Data Policies, Standards, and Guidelines 4 | nav_order: 11 5 | has_children: false 6 | has_toc: false 7 | --- 8 | 9 | # DATA POLICIES, STANDARDS, AND GUIDELINES 10 | 11 | [Data Management Policy](https://www2.gov.bc.ca/gov/content?id=706EBC0C26B146EBB8641813DB32946B) 12 | 13 | [British Columbia First Nations' Data Governance Initiative](https://www.bcfndgi.com/) 14 | 15 | The following standards and guidelines are available for reference until they are updated, replaced or retired: 16 | 17 | + [Data Custodianship Guidelines for the Government of British Columbia](https://www2.gov.bc.ca/assets/gov/data/data-management/data_custodianship_guidelines_for_the_government_of_bc.pdf) 18 | + [Guidelines for Best Practices in Data Management – Roles and Responsibilities](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/datamgmtrolesresp-2012mar-finalv2-asrb.pdf) 19 | + [Data Administration Standards](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/data_administration_standards.pdf) 20 | + [Application Programming Interface (API) Guidelines](https://developer.gov.bc.ca/Data-and-APIs/BC-Government-API-Guidelines) 21 | 22 | ------------------------------------------------------- 23 | -------------------------------------------------------------------------------- /pages/dps_bcdc.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: BC Data Catalogue 4 | nav_order: 3 5 | has_children: true 6 | has_toc: false 7 | --- 8 | 9 | # B.C. Data Catalogue 10 | 11 | The B.C. Data Catalogue is the place to find B.C. Government data, applications and web services. Government ministries and many broader public sector agencies publish their data resources in the Catalogue. This data can be used to make informed decisions and create opportunities for the benefit of all British Columbians. 12 | 13 | The Catalogue describes thousands of government datasets and is designed to help users find, access, explore and reuse this extensive collection of data. All ministries and some Broader Public Sector agencies register data in the Catalogue. 14 | 15 | Catalogued "data" is broadly encompassing and includes raw data, applications and web services. Much of the data are released under the Open Government License - British Columbia that permits a wide range of uses, including commercial use and re-distribution. 16 | 17 | The data described in the Catalogue spans many sectors related to government’s delivery of services, including Natural Resources, Finance, Economy, Education, Health and Safety, Justice, Transportation and Social Services. 18 | 19 | Catalogue users can subscribe to Catalogue updates and contact government Data Custodians, who are responsible for the information and can help answer questions about the data. 20 | 21 | The B.C. Data Catalogue is powered by CKAN open source software and is managed by DataBC. 22 | 23 | ------------------------------------------------------- 24 | -------------------------------------------------------------------------------- /index.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Data Publication and Services 4 | nav_order: 1 5 | has_children: false 6 | has_toc: false 7 | --- 8 | 9 | # DATA PUBLICATION AND SERVICES 10 | 11 | The DataBC Program encourages and enables the strategic management and sharing of data across the government enterprise and with the public. It is responsible for the BC Data Catalogue, the Open Data initiative and the B.C. Spatial Data Infrastructure and associated products and services. 12 | 13 | Access to trusted, high quality data is essential for the success of British Columbia - expressed in effective government decision making, a robust economy, and improved well-being for all of its citizens. 14 | 15 | The BC Data Catalogue provides the easiest access to government's data holdings, as well as applications and web services. Thousands of the datasets discoverable in the Catalogue are available under the Open Government Licence - British Columbia. 16 | 17 | The Province's area, varied topography and predominantly natural resource based economy has positioned B.C. as a leader in geographic information management and generates a wealth of geographic information that is discoverable in the BC Data Catalogue. The DataBC Program provides access to this information through a suite of unique applications and services that comprise the B.C. Spatial Data Infrastructure. 18 | 19 | The information provided in this site describes the services that the DataBC Program provides for data publication, along with supporting governance, standards, guidelines and client workflows. 20 | 21 | ------------------------------------------------------- 22 | -------------------------------------------------------------------------------- /pages/dps_webmapping.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Web-based Mapping 4 | nav_order: 8 5 | has_children: true 6 | has_toc: false 7 | --- 8 | 9 | # WEB-BASED MAPPING 10 | 11 | Visualize and analyze the wealth of B.C. geographic information using a variety of web-based map tools and map services. 12 | 13 | To learn more about the tools and services available that help make B.C. Government's data accessible to online users, see [BC Map Services](https://www2.gov.bc.ca/gov/content?id=95D78D544B244F34B89223EF069DF74E), [Web-based Mapping](https://www2.gov.bc.ca/gov/content?id=347AC53EB6F84601841241BD51FF3871) and [Web-Mapping Framework Options](https://bcgov.github.io/bcwebmaps-options/web-mapping-frameworks). 14 | 15 | 16 | + [BC Map Hub (AGO)](https://www2.gov.bc.ca/gov/content?id=DE0602BB42664AA28C9F059D45CC1CC2) 17 | + [BC Map Hub (ArcGIS Online) Content Publishing Information](dps_maphub_w.md) 18 | + [ArcGIS Online Digital Application - Terms of use](dps_maphub_terms_of_use.md) 19 | + [ArcGIS Online Digital Application - Glossary](dps_maphub_glossary.md) 20 | + [ArcGIS Online Digital Application - User account details](dps_maphub_account_details.md) 21 | + [iMapBC](https://www2.gov.bc.ca/gov/content?id=C52F8C3BFE8C4110A63171337F363F43) 22 | + [Internet Mapping Framework 2 (IMF2)](https://bcgov.github.io/bcwebmaps-options/web-mapping-frameworks/imf2.html) 23 | + [Simple Map Kit (SMK)](https://bcgov.github.io/bcwebmaps-options/web-mapping-frameworks/smk.html) 24 | + [WMS/WFS](https://www2.gov.bc.ca/gov/content?id=95D78D544B244F34B89223EF069DF74E) 25 | + [Tips and tricks for using WMS and WFS](tips_tricks_webservices.md) 26 | -------------------------------------------------------------------------------- /pages/dps.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Data Publication and Services 4 | nav_order: 1 5 | has_children: false 6 | has_toc: false 7 | nav_exclude: true 8 | 9 | # this page is currently a duplication of the index.md 10 | 11 | --- 12 | 13 | ![](images/image_DataBC.png) 14 | # DATA PUBLICATION AND SERVICES 15 | 16 | DataBC encourages and enables the strategic management and sharing of data across the government enterprise and with the public. It is responsible for the BC Data Catalogue, the Open Data initiative and the B.C. Spatial Data Infrastructure and associated products and services. 17 | 18 | Access to trusted, high quality data is essential for the success of British Columbia - expressed in effective government decision making, a robust economy, and improved well-being for all of its citizens. 19 | 20 | The BC Data Catalogue provides the easiest access to government's data holdings, as well as applications and web services. Thousands of the datasets discoverable in the Catalogue are available under the Open Government License - British Columbia. 21 | 22 | The province's area, varied topography and predominantly natural resource based economy has positioned B.C. as a leader in geographic information management and generates a wealth of geographic information that is discoverable in the BC Data Catalogue. DataBC provides access to this information through a suite of unique applications and services that comprise the B.C. Spatial Data Infrastructure. 23 | 24 | The information provided in this site describes the services that DataBC provides for data publication, along with supporting governance, standards, guidelines and client workflows. 25 | -------------------------------------------------------------------------------- /pages/dps_bcdc_w_how_to_use_the_ui.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Content Mgmt/Use - UI 4 | nav_order: 33 5 | parent: BC Data Catalogue 6 | has_children: true 7 | has_toc: false 8 | --- 9 | 10 | # **BC Data Catalogue User Interface (UI)** 11 | 12 | [Resource Management](./dps_bcdc_w_resource_mgmt_ui.md) 13 | 14 | + There are four defined resource types: 15 | + [Application](https://bcgov.github.io/data-publication/pages/dps_bcdc_w_resource_mgmt_ui.html#application) 16 | + [Document/Tabular Data](https://bcgov.github.io/data-publication/pages/dps_bcdc_w_resource_mgmt_ui.html#document-and-tabular-data) 17 | + [Geographic Data](https://bcgov.github.io/data-publication/pages/dps_bcdc_w_resource_mgmt_ui.html#geographic-data) 18 | + [Web Service/API](https://bcgov.github.io/data-publication/pages/dps_bcdc_w_resource_mgmt_ui.html#webservice-and-api) 19 | 20 | -------- 21 | ## BC Data Catalogue User Advanced Search 22 | 23 | Within the search bar, once can pass queries 24 | 25 | **Records published during a certain date range** (deprecated) 26 | 27 | ```record_publish_date:[2021-01-01T00:00:00.000Z TO 2022-01-01T00:00:00.000Z]``` 28 | 29 | **Records published as the Open Data Licence - British Columbia** 30 | 31 | ```license_id:2``` 32 | 33 | + To find a full list of licence IDs, visit the [BCDC Licences JSON](https://github.com/bcgov/ckanext-bcgov-schema/blob/master/ckanext/bcgov_schema/bcdc_licenses.json) page on GitHub 34 | 35 | **Object Names** 36 | 37 | ``` WHSE_ADMIN_BOUNDARIES.ADM_NR_DISTRICTS_SP ``` 38 | 39 | + Search results are not exact matches 40 | 41 | **Combination of two** 42 | 43 | ```WHSE_ADMIN_BOUNDARIES.ADM_NR_DISTRICTS_SP license_id:2``` 44 | -------------------------------------------------------------------------------- /pages/dps_data_distribution.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Data Distribution 4 | nav_order: 5 5 | has_children: true 6 | has_toc: false 7 | --- 8 | 9 | # DATA DISTRIBUTION 10 | 11 | B.C. Government data stored in the BC Geographic Warehouse (BCGW) can be downloaded for local use. 12 | 13 | Data Distribution services include direct download of packaged content (meaning you get the data exactly as it is provided) and configurable content (meaning you have control over things like the output projection and the file format). In either case, once the data is downloaded you will have a static dataset and may need to repeat the download process as the data changes within B.C. government systems. You can use your Business BCeID to access content flagged to be accessible to your account. 14 | 15 | When downloading configurable content, you will be asked for your email address. This is required as the system will need to extract the data from the B.C. Geographic Warehouse, clip the data if requested, reproject the data, and export it into the requested file format. This process may take considerable time depending on the data ordered and the system backlog, so the system asks for your email and releases the server connection so you can keep working. The system will email you initially to inform you that the order was received, then again once the order is ready. The B.C. Government does not share your email information between systems, except where it relates to the data you have downloaded and the Data Distribution services. 16 | 17 | Data can currently be downloaded from the following applications: 18 | + [B.C. Data Catalogue](https://catalogue.data.gov.bc.ca/dataset?) (packaged content and configurable content) 19 | + iMapBC (configurable content) 20 | 21 | ------------------------------------------------------- 22 | -------------------------------------------------------------------------------- /pages/dps_loc_address_geocoder.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: BC Address Geocoder 4 | nav_order: 61 5 | parent: Location Services 6 | has_children: true 7 | has_toc: false 8 | --- 9 | 10 | # BC ADDRESS GEOCODER 11 | 12 | The BC Address Geocoder is a REST web service that can be used to resolve the physical locations (i.e., latitude and longitude) and correct, standardized form of civic and non-civic addresses in British Columbia. 13 | 14 | For more information about this service see the [BC Address Geocoder webpage](https://www2.gov.bc.ca/gov/content?id=118DD57CD9674D57BDBD511C2E78DC0D). 15 | 16 | The BC Address Geocoder service can be used to resolve the physical locations (i.e., latitude and longitude) and correct, standardized form of civic and non-civic addresses in British Columbia. Access to the service is through: 17 | 1. The REST API: see the [BC Address Geocoder Developer Guide](https://github.com/bcgov/ols-geocoder/blob/gh-pages/geocoder-developer-guide.md) 18 | 2. Batch Geocoding: 19 | - [Geocoder Address List Editor](https://bcgov.github.io/ols-devkit/ale/) (for up to 1000 addresses) 20 | - [Batch Geocoder (Restricted Access)](https://apps.gov.bc.ca/pub/cpf/secure/ws/apps/geocoder/) for large address lists 21 | 22 |
23 | 24 | If you have questions about accessing the geocoder service, please [open a ticket with the Data Systems & Services request system](https://dpdd.atlassian.net/servicedesk/customer/portal/1/group/7/create/15). 25 | 26 |
27 | 28 | Ministry and Broader Public Sector (BPS) can contribute their own data for the geocoder to reference by [publishing to the BC Geographic Warehouse](dsg_before_you_start.md): i.e., the [Geographic Sites Registry (GSR)](https://catalogue.data.gov.bc.ca/dataset/d5c6b8ed-c272-4c9e-8813-590a47b5c01c) - once published in this set of data, the locations automatically get used in the Geocoder. 29 | 30 | 31 | ------------------------------------------------------- 32 | -------------------------------------------------------------------------------- /pages/open_data.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Open Data 4 | nav_order: 9 5 | has_children: true 6 | has_toc: false 7 | --- 8 | 9 | # Open Data 10 | 11 | In July 2011, the B.C. Government introduced its [Open Information and Open Data Policy](https://www2.gov.bc.ca/assets/gov/british-columbians-our-governments/services-policies-for-government/information-management-technology/information-privacy/resources/policies-guidelines/open-information-open-data-policy.pdf), becoming the first province in Canada to publish its data under an _open license_. 12 | 13 | Opening up Government data is key to enabling engagement with citizens by using new technologies to connect the Public to Government and to one another. Making Government data available online invites individuals, businesses and organizations to use this data in creating new innovative opportunities and solving problems for the betterment of all British Columbians. 14 | 15 | The B.C. Government produces and maintains thousands of datasets that represent a broad range of information about natural resources, the economy, justice, education and social programs. 16 | 17 | ## Resources 18 | 19 | The following is a list of resources to support the use of the open license with the B.C. Government: 20 | 21 | + [_Open Government Licence - British Columbia_](https://www2.gov.bc.ca/gov/content?id=A519A56BC2BF44E4A008B33FCF527F61) 22 | + [_Open Data Assessment and Checklist - Blank (DOCX, 30 KB)_](https://www2.gov.bc.ca/assets/download/97CF56DB283D4AE08968E4A4C7538D65) 23 | + [_API Terms of Use for Information provided under the OGL-BC_](https://www2.gov.bc.ca/gov/content?id=D1EE0A405E584363B205CD4353E02C88) 24 | + [_Open Data Physical Dataset Format Standard (PDF, 181 KB)_](http://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/open_data_physical_dataset_extract.pdf) 25 | 26 | ------------------------------------------------------- 27 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/scripts/xyz_whse_compute_mdsys_extents.sql: -------------------------------------------------------------------------------- 1 | 2 | -- 3 | -- Include the following SQL for each table and view where the extent is unknown or known not to be the entire Province. 4 | -- 5 | 6 | UPDATE user_sdo_geom_metadata 7 | SET diminfo = ( SELECT MDSYS.SDO_DIM_ARRAY( 8 | MDSYS.SDO_DIM_ELEMENT('X', minx, maxx, 0.001), 9 | MDSYS.SDO_DIM_ELEMENT('Y', miny, maxy, 0.001)) as diminfo 10 | FROM ( SELECT TRUNC( MIN( v.x ) - 1,0) as minx, 11 | ROUND( MAX( v.x ) + 1,0) as maxx, 12 | TRUNC( MIN( v.y ) - 1,0) as miny, 13 | ROUND( MAX( v.y ) + 1,0) as maxy 14 | FROM (SELECT SDO_AGGR_MBR(a.SHAPE) as mbr 15 | FROM fillInTable a) b, 16 | TABLE(mdsys.sdo_util.getvertices(b.mbr)) v 17 | ) 18 | ) 19 | WHERE table_name = 'fillInTable' AND column_name = 'SHAPE' -- or GEOMETRY 20 | / 21 | COMMIT 22 | / 23 | 24 | -- 25 | -- If a view is known to have the same extent as another table whose extent has been calculated above, then this SQL can be used for the view: 26 | -- 27 | 28 | DELETE FROM user_sdo_geom_metadata WHERE table_name = 'fillInView' 29 | / 30 | 31 | INSERT INTO user_sdo_geom_metadata SELECT 'fillInView','SHAPE'/'GEOMETRY',diminfo,srid FROM user_sdo_geom_metadata WHERE table_name = 'fillInTable' 32 | / 33 | 34 | -- 35 | -- If a table or view is known to have an extent of the whole Province, then this SQL can be used. 36 | -- 37 | 38 | UPDATE user_sdo_geom_metadata 39 | SET diminfo = MDSYS.SDO_DIM_ARRAY( 40 | MDSYS.SDO_DIM_ELEMENT('X', 200000, 1900000, 0.001), 41 | MDSYS.SDO_DIM_ELEMENT('Y', 300000, 1800000, 0.001)) 42 | WHERE table_name = 'fillInTableOrView' AND column_name = 'SHAPE' -- or GEOMETRY 43 | / 44 | COMMIT 45 | / 46 | 47 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/scripts/gsr_whse_compute_mdsys_extents.sql: -------------------------------------------------------------------------------- 1 | 2 | -- 3 | -- Include the following SQL for each view where the extent is unknown or known not to be the entire Province. 4 | -- 5 | 6 | UPDATE user_sdo_geom_metadata 7 | SET diminfo = ( SELECT MDSYS.SDO_DIM_ARRAY( 8 | MDSYS.SDO_DIM_ELEMENT('X', minx, maxx, 0.001), 9 | MDSYS.SDO_DIM_ELEMENT('Y', miny, maxy, 0.001)) as diminfo 10 | FROM ( SELECT TRUNC( MIN( v.x ) - 1,0) as minx, 11 | ROUND( MAX( v.x ) + 1,0) as maxx, 12 | TRUNC( MIN( v.y ) - 1,0) as miny, 13 | ROUND( MAX( v.y ) + 1,0) as maxy 14 | FROM (SELECT SDO_AGGR_MBR(a.SHAPE) as mbr 15 | FROM fillInView a) b, 16 | TABLE(mdsys.sdo_util.getvertices(b.mbr)) v 17 | ) 18 | ) 19 | WHERE table_name = 'fillInView' AND column_name = 'SHAPE' 20 | / 21 | COMMIT 22 | / 23 | 24 | -- 25 | -- If a view ("Second View") is known to have the same extent as another view ("First View") whose extent has been calculated above, then this SQL can be used for the view: 26 | -- 27 | 28 | DELETE FROM user_sdo_geom_metadata WHERE view_name = 'fillInSecondView' 29 | 30 | INSERT INTO user_sdo_geom_metadata SELECT 'fillInSecondView','SHAPE'/'GEOMETRY',diminfo,srid FROM user_sdo_geom_metadata WHERE table_name = 'fillInFirstView' 31 | 32 | -- 33 | -- If a view is known to have an extent of the whole Province, then this SQL can be used. 34 | -- 35 | 36 | UPDATE user_sdo_geom_metadata 37 | SET diminfo = MDSYS.SDO_DIM_ARRAY( 38 | MDSYS.SDO_DIM_ELEMENT('X', 200000, 1900000, 0.001), 39 | MDSYS.SDO_DIM_ELEMENT('Y', 300000, 1800000, 0.001)) 40 | WHERE table_name = 'fillInView' AND column_name = 'SHAPE' -- or GEOMETRY 41 | / 42 | COMMIT 43 | / 44 | 45 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/xyz_whse/WHSE_SCHEMA_NAME/dataload/dbCreds.json: -------------------------------------------------------------------------------- 1 | { 2 | "_comment": [ 3 | " DestinationCreds ", 4 | " The template is designed to recieve a database key word ", 5 | " like PROD|TEST|DELIV. Then based on the value of the keyword the config ", 6 | " file identifies what the destination database is. When in production ", 7 | " the template will retrieve the password from Password Manager Pro via ", 8 | " its rest api. When in development credentials are retrieved from this ", 9 | " file. The instance defined in the config file needs to match the ", 10 | " destination instance defined below for the credential retrieval ", 11 | " to function correctly " ], 12 | "destinationCreds" : [ 13 | { "servicename": "idwdlvr1.bcgov", 14 | "username": "WHSE_MONTREAL_CANADIANS", 15 | "password": "thisIsNotThePassword" 16 | }, 17 | {"servicename": "idwdlvr1.bcgov", 18 | "username": "WHSE_MONTREAL_CANADIANS_2", 19 | "password": "thisIsNotThePassword" 20 | } 21 | ], 22 | "_comment" : [ 23 | " Source_Creds_comment ", 24 | " Once in production this file will no longer exist and ", 25 | " The credentials will be retireved from Password Manager Pro. While ", 26 | " in development the template script will look read the source fmw ", 27 | " database instance and schmea, and match those values with the values ", 28 | " in one of the hashs below to retrieve the password. Currently there ", 29 | " only one hash defined but you can include as many as you require "], 30 | "sourceCredentials" : [ 31 | {"servicename": "envprod1.nrs.bcgov", 32 | "username": "USERNAME", 33 | "password": "thisIsNotThePassword" 34 | }, 35 | {"SqlServerDbName": "nameOfSqlServerDB", 36 | "SqlServerDbHost": "databaseHost", 37 | "username": "UsernameOrSchemaName", 38 | "password": "thisIsNotThePassword" 39 | } 40 | ] 41 | } -------------------------------------------------------------------------------- /pages/images/data_preparation.drawio: -------------------------------------------------------------------------------- 1 | 7Zpbc5s6EMc/jWd6HpIBYeHw6EvcPLTTzklP8yxjGWsqkItxbffTH62QQGCcxAm208aeXmB30WX3xx8QdLxhvPmYksX8s5hS3kHOdNPxRh2EkOMj+R9YtrnFdZG2RCmbaltpuGe/qTY62rpiU7qsBGZC8IwtqsZQJAkNs4qNpKlYV8Nmgld7XZCI7hjuQ8KN9RqX9gc2zeZmIn5QOu4oi+a68xvk544JCX9EqVgluscO8mbql7tjYtrSU13OyVSsLZN32/GGqRBZvhVvhpRDek3izHHZ1oy24w3mWczljis3lXu852D3OQfLyaU0yezu9rXn4+8PDn4YB78f/qPx1ZdNt8evurqXX4SvTC/I57LBwXJBkkr//s8VzHQwE0l2tVQg9GWA6y82pVNuRfp/1crEGD4TlmQ0IUlIjU+OdVKPl7a8Y2Ou5UCVi8KUHOlez1lG7xckBO9aEg7jNlWCgGWWih90KLhIpSURCS2MhhVfT0mj7Tl63xwkqRirn7QTzqJE2jidZdVqyEGHLIk+KccIQxuMc6sNX/0a62ZqQNOMbiyTruNHKmKapVsZor040MzrkzZwNGlri38TM7fQxzqO6JMuKpouwZEbmp0DODKoVziqlc7Oll2jKVnOi4qaDIcyO1SmbgBZYfJ072tHzKZTTvM2FtByvIlA2q5zMUHXq2+rNOnDDrQNGVJnjnLfUQId9VS3GwTlxjuUlDJQAcNFu2DAT4Ex42xxpycH29/NRCuodXexCGTtHKcdLHzPqWBxg3axQCbGxsLtHosLN7hwsZ8FTiaUD4qrUE2maqQMh77fFim4VxWQXvf8pPQupLxIQTyvPS7qCiJbPjsX+MJFSwoi8+D0+m0pSJUUfHN+Uv5SUKpFdFG/P8BHEZYjCEg38M+NBXoXWCCv28Wj1nSlDYXwayiYK/z5UPDeBQr9267roT9FITzv5txYdN8FFmMUeO7tW1YIhINzo/C33mzW7iGcnhccisLJFKKOhdtwa+k5J8XCb8Citr5pDJDCly+bjkhGpPNrShfWimje5s5C6eTUq6QWReYJ48CF0+J8eHTp9EQQNWrL8R5P9i+1T54NjKp/MzP63c4bpcP13xQdvRdeeY5HR9NjyqF07KJBF1zAvK/k3xHlTKZI7o6/0WX2ZlFp7Q1MG3er/tN3q25wUlCaHmKO8sbuE9nSVJaK5hekpcwiyZhIDnp998TIwrzEMKo0mpAPMmvyj8yM07j1D2xCs46a0ozEjG/zw2ORiKVCsxJSztppnjSuvxzHshhgVe91iz1THKzKIy0j2IaBYSgAljV9KtYtYg2TL2oGlc3kDBQe+AfyLQ1QRWwSbgLyyYO3TI3c66vQHAo7SO1F+bYREqykBNtigo2clJ0r48Q+vhxzdUiFwIDBUaGWyIBRyQzYtdCUgbbYgFUpSenIBQccfj7nQnQqwYXwgNVzClsZCuM0AgTeXILAo0QITEqGwOLmA7CkCKy4lgOtP88ho3AVUJQihUGmikglVaaZbWlXkmXs6yIpeeuBdYyWr8LZtXxSxgp7ZA2gzqzaLcC1jdXTScftnHdn/Qjgj7kqFYvtjyytnfiq1LSGcpSrkr7bHTFZQDZZHXxBuqD06A1O04L9iVHa/7B9HJT+ldc2Fh5+a3MhqUqSW/2mAPcC82ne+Vi6ORlL9pPW11RMV+EFqFcCVXtIb/oY4bQ4of1LOC3jNGYJ4UqbfjG6vlD0CoqcKkVNnzqdmKL9Sz0tUzQUcbxKLte210NUu+Fu+rLS9duBqKOflUqf9ZTk3f4P 2 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/WHSE_IMAGERY_AND_BASE_MAPS/N.N.N_descriptive_name_of_release/dataload/dbCreds.json: -------------------------------------------------------------------------------- 1 | { 2 | "_comment": [ 3 | " DestinationCreds ", 4 | " The template is designed to recieve a database key word ", 5 | " like PROD|TEST|DELIV. Then based on the value of the keyword the config ", 6 | " file identifies what the destination database is. When in production ", 7 | " the template will retrieve the password from Password Manager Pro via ", 8 | " its rest api. When in development credentials are retrieved from this ", 9 | " file. The instance defined in the config file needs to match the ", 10 | " destination instance defined below for the credential retrieval ", 11 | " to function correctly " ], 12 | "destinationCreds" : [ 13 | { "servicename": "idwdlvr1.bcgov", 14 | "username": "WHSE_MONTREAL_CANADIANS", 15 | "password": "thisIsNotThePassword" 16 | }, 17 | {"servicename": "idwdlvr1.bcgov", 18 | "username": "WHSE_MONTREAL_CANADIANS_2", 19 | "password": "thisIsNotThePassword" 20 | } 21 | ], 22 | "_comment" : [ 23 | " Source_Creds_comment ", 24 | " Once in production this file will no longer exist and ", 25 | " The credentials will be retireved from Password Manager Pro. While ", 26 | " in development the template script will look read the source fmw ", 27 | " database instance and schmea, and match those values with the values ", 28 | " in one of the hashs below to retrieve the password. Currently there ", 29 | " only one hash defined but you can include as many as you require "], 30 | "sourceCredentials" : [ 31 | {"servicename": "envprod1.nrs.bcgov", 32 | "username": "USERNAME", 33 | "password": "thisIsNotThePassword" 34 | }, 35 | {"SqlServerDbName": "nameOfSqlServerDB", 36 | "SqlServerDbHost": "databaseHost", 37 | "username": "UsernameOrSchemaName", 38 | "password": "thisIsNotThePassword" 39 | } 40 | ] 41 | } -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | remote_theme: "pmarsceill/just-the-docs" 2 | #theme: "just-the-docs" 3 | aux_links: 4 | "Edit on Github": 5 | - "//github.com/bcgov/Data-Standards/" 6 | 7 | footer_content: " 8 | BC Gov 14 | " 15 | 16 | header_content: " 17 | BC Gov 23 | " 24 | 25 | heading_anchors: true 26 | #color_scheme: "dark" 27 | 28 | # Set a path/url to a logo that will be displayed instead of the title 29 | logo: "pages/assets/images/BCID_H_rgb_pos.png" 30 | 31 | # Supports true (default) or false 32 | search_enabled: true 33 | 34 | search: 35 | # Split pages into sections that can be searched individually 36 | # Supports 1 - 6, default: 2 37 | heading_level: 2 38 | # Maximum amount of previews per search result 39 | # Default: 3 40 | previews: 3 41 | # Maximum amount of words to display before a matched word in the preview 42 | # Default: 5 43 | preview_words_before: 5 44 | # Maximum amount of words to display after a matched word in the preview 45 | # Default: 10 46 | preview_words_after: 10 47 | # Set the search token separator 48 | # Default: /[\s\-/]+/ 49 | # Example: enable support for hyphenated search words 50 | tokenizer_separator: /[\s/]+/ 51 | # Display the relative url in search results 52 | # Supports true (default) or false 53 | rel_url: true 54 | # Enable or disable the search button that appears in the bottom right corner of every page 55 | # Supports true or false (default) 56 | button: true 57 | 58 | mermaid: 59 | # Version of mermaid library 60 | # Pick an available version from https://cdn.jsdelivr.net/npm/mermaid/ 61 | # version: "9.1.3" 62 | # version: "10.1.0" 63 | version: "9.4.3" 64 | # apparently only version 9.* works 65 | 66 | # For copy button on code 67 | enable_copy_code_button: true 68 | 69 | markdown: kramdown 70 | highlighter: rouge 71 | 72 | kramdown: 73 | input: GFM 74 | syntax_highlighter: rouge 75 | 76 | callouts_level: quiet # or loud 77 | callouts: 78 | highlight: 79 | color: yellow 80 | important: 81 | title: Important 82 | color: blue 83 | new: 84 | title: New 85 | color: green 86 | note: 87 | title: Note 88 | color: purple 89 | warning: 90 | title: Warning 91 | color: red -------------------------------------------------------------------------------- /pages/dps_bcgw_w_data_retirement.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Retirement Workflow 4 | nav_order: 43 5 | parent: BC Geographic Warehouse 6 | has_children: false 7 | has_toc: false 8 | --- 9 | 10 | # BC GEOGRAPHIC WAREHOUSE (BCGW) DATA RETIREMENT WORKFLOW 11 | 12 | 13 | |**AUDIENCE**| | | | 14 | |:---:|:---:|:---:|:---:| 15 | | *Data Publishers* | *Business Analysts* | *Business Portfolio Managers* | *Application Administrators* | *Data Consumers* 16 | 17 | ### BCGW Data Retirements 18 | Data Custodians are ultimately responsible for the Data Lifecycle of their data, which includes but is not limited to the maintenance, accuracy, licensing and the decision to replace, retire or archive their data. 19 | 20 | To retire data from the BCGW, please open a ticket with the [ Data Systems & Services request system](https://dpdd.atlassian.net/servicedesk/customer/portal/1/group/5/create/26). 21 | 22 | ### Notifications 23 | From the information provided by the custodian, a ***Notice of Intent*** is created that includes metadata links to replacement datasets if available. After review a ***Notice of Decision*** is sent out. 24 | 25 | These notifications are sent out interested parties to provide advance notice that a dataset will be removed or replaced in the BC Geographic Warehouse. Emergency disabling or temporary disabling of datasets can happen but will require rationale. 26 | 27 | Notifications are sent out by the DataBC Data Retirement team and [hosted in the BC Data Catalogue](https://catalogue.data.gov.bc.ca/dataset/3b1c8bbf-4a17-43f0-a5e4-b3e518ef77d1) 28 | 29 | #### Notice of Intent (NOI) Timelines 30 | * Annually, with a **4 week** allowance for users to contact the data managers with any concerns. 31 | * Data managers may request removal of a dataset from the NOI during this period. 32 | 33 | #### Notice of Decision (NOD) Timelines 34 | * Annually, with a **2 week** notice before the retirement implementation begins. 35 | 36 | ### Retirement Implementation 37 | #### Dataset Access Revoked 38 | * Security - access to datasets will be revoked 39 | * Delivery and Test BCGW will be revoked **one week** before **Production** 40 | 41 | #### Data Structure Archival 42 | * DataBC does not archive the data prior to removal from the BC Geographic Warehouse. It is the responsibility of the business area to retain a copy of the data, if required. 43 | * _Requests for exports of the data content can be accommodated, where business areas do not have GIS support._ 44 | * DataBC will export a copy of the structure of the data (the data model) and provide these to the data custodian, upon request. 45 | 46 | #### Dataset Removal 47 | * Datasets are then physically removed from the BC Geographic Warehouse. 48 | -------------------------------------------------------------------------------- /pages/template.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | nav_order: 4 | title: template 5 | parent: 6 | grand_parent: 7 | has_toc: false 8 | nav_exclude: true 9 | --- 10 | # HEADER - LEVEL 1 (THIS IS THE TITLE - IN ALL CAPS) 11 | 12 | Short introductory section (a sentence or two), including the purpose. 13 | 14 | |**AUDIENCE**| | | | | 15 | |:---:|:---:|:---:|:---:|:---:| 16 | | *Audience 1* | *Audience 2* | *Audience 3* | *Audience 4* | *Audience 5* | 17 | 18 | ## Table of Contents 19 | + [**HEADER - LEVEL 2**](#header---level-2) 20 | + [HEADER - LEVEL 3](#header---level-3) 21 | + [HEADER - LEVEL 4](#header---level-4) 22 | + [HEADER - LEVEL 5](#header---level-5) 23 | 24 | ----------------------- 25 | 26 | ## DOCUMENTATION REVIEW 27 | 28 | Include a list of documents that are **required** for the reader to review. 29 | 30 | ----------------------- 31 | 32 | ## HEADER - LEVEL 2 33 | 34 | Generally, the sections will be defined at the Level 2 Header. 35 | 36 | This section contains general formatting information for pages published in this repo. 37 | 38 | ----------------------- 39 | 40 | ### HEADER - LEVEL 3 41 | 42 | Numbered lists can be automatically numbered and represented like this: 43 | 1. This is the first list item 44 | 1. This is the second list item 45 | 1. This is the last list item 46 | It is helpful to use the auto-numbering as you can re-order list items and do not need to worry about re-numbering the list items. 47 | 48 | ----------------------- 49 | 50 | #### HEADER - LEVEL 4 51 | 52 | **Bullets, Hyperlinks, Bold and Italic** 53 | 54 | When using bullets, they can be represented using the plus sign or an asterisk and indented using a tab: 55 | * All definitions should be moved to the [**Glossary**](glossary.md), linked to the particular text and italicized e.g., [_Data Custodian_](glossary.md#data-custodian) 56 | + Hyperlinks: 57 | + Hyperlinks to pages within this repo should be linked using the .md as well as the specific section (where applicable) and **bolded** e.g., BC Data Catalogue > BCDC Standards and Guidelines > [**Roles and Responsibilities**](dsg_bcdc_roles_responsibilities.md#the-data-steward) 58 | * Hyperlinks to external pages shoudl be represented using a permalink where possible and using the URL if no permalink is available. e.g., [Data Catalogue](https://data.gov.bc.ca/) 59 | 60 | ----------------------- 61 | 62 | ##### HEADER - LEVEL 5 63 | 64 | Add in a Return to Top link at the bottom of long sections to help users navigate easier. 65 | Use a series of short dashes as a line separating sections. These could be used solely within a level 2 section for shorter pages or in-between levels 2-3-4-5 for longer pages. 66 | 67 | ----------------------- 68 | 69 | [RETURN TO TOP][1] 70 | 71 | [1]: #top 72 | -------------------------------------------------------------------------------- /pages/dps_maphub_terms_of_use.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: AGO Terms of use 4 | grand_parent: Web-based Mapping 5 | parent: BC Map Hub - Publication Workflow 6 | nav_order: 811 7 | has_toc: false 8 | --- 9 | 10 | # ArcGIS Online Digital Application - Account Holders Terms of Use: 11 | 12 | You have applied for an ArcGIS Online Account to access the B.C's Map Hub. Before receiving access you are required to read and agree with the following usage conditions: 13 | 14 | - I am currently an employee, contactor, agent or representative of the Province of British Columbia. 15 | - I understand that sharing my ArcGIS Online Account credentials is in violation of this access agreement and if my account credentials are found to have been shared, my account will be "disabled" and will require my supervisor to request reactivation. Exception: Proxy account credentials may by shared to known users up to the # specified 16 | by the account holder on the account request form. 17 | - I understand that on an annual basis my ArcGIS Online Account access will be reviewed, if my account has not be accessed for a pre-determined period of time (such as a year), it will be "disabled", and will require my supervisor to request reactivation. 18 | - I understand that data presented in a map or application is covered under a license agreement (such as the Open Government License-BC) or Crown Copyright, usage is subject to the terms as specified in the ArcGIS Online item’s details page or related BC Data Catalogue metadata record. 19 | - I will follow the prescribed guidelines and process for publication of content to the public. 20 | - If the ArcGIS Online Role assigned to me allows me to build or update content (maps, apps, data, etc.) or use premium content, I understand that my Ministry/Agency will be responsible for payment of my credit usage. 21 | - I understand that the cost of my ArcGIS Account seat will be subject to Terms set out by the Esri License Coordinator/Information, Innovation and Technology Division, Chief Technology Officer and Delivery Management 22 | Branch. 23 | - I understand that sensitive, and/or personal information (as defined by FOIPPA), will not be uploaded/hosted/stored on B.C.'s Map Hub. 24 | - I understand that I will have access to the B.C.'s Map Hub Image folder(s) to save images for use in ArcGIS Online. I will remove images that are obsolete and/or are used in maps or applications that are archived. 25 | - I understand that the public may be able to view my B.C.’s Map Hub account profile and I will maintain the “Bio” section accordingly. 26 | - I understand that my access to the B.C.'s Map Hub may be limited or suspended if I violate the terms of this agreement. 27 | -------------------------------------------------------------------------------- /pages/dps_webmapping_providers_w.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Layer Presentation Services 4 | nav_order: 82 5 | parent: Web-based Mapping 6 | has_children: true 7 | has_toc: false 8 | --- 9 | 10 | # LAYER PRESENTATION SERVICES 11 | 12 | This page describes the requirements and options for presenting spatial data from the BC Geographic Warehouse (BCGW) in multiple web-mapping services. 13 | 14 | |**AUDIENCE** 15 | |:---|:---|:---|:---| 16 | |[*Data Publisher*](https://bcgov.github.io/data-publication/pages/glossary.html#data_publisher)|[*Custodian*](https://bcgov.github.io/data-publication/pages/glossary.html#custodian)|[*Data Manager*](https://bcgov.github.io/data-publication/pages/glossary.html#data_manager)|[*Data Steward*](https://bcgov.github.io/data-publication/pages/glossary.html#data_steward) 17 | 18 | ## Table of Contents 19 | 20 | + [**CONFIGURABLE PRODUCTS**](#configurable-products) 21 | + [**REQUIREMENTS**](#requirements) 22 | + [**LIMITATIONS**](#limitations) 23 | + [**CONFIGURATION OPTIONS**](#configuration-options) 24 | 25 | ----------------------- 26 | 27 | ## CONFIGURABLE PRODUCTS 28 | 29 | ## REQUIREMENTS 30 | Spatial datasets in the BCGW may be configured for web-mapping services, this requires: 31 | 32 | 1. A published spatial dataset in the BC Geographic Warehouse. 33 | 1. A metadata record. 34 | 1. A profile defined as one of the Security options below. 35 | - Named Users is the only profile that requires additional configuration. 36 | 1. A presentation layer as created with the [Layer File Presentation document](./dsg_bcgw_layer_file_presentation.md) 37 | - And published through to iMapBC production. 38 | 39 | ## LIMITATIONS 40 | 41 | + Large datasets or with wide variety of size differences may see perfomance issues. 42 | - For certain datasets, like regional boundaries, a generalized dataset can be created to be used in web-mapping service. 43 | 44 | ## CONFIGURATION OPTIONS 45 | ![](/images/grey_dash.png) 46 | 47 | |Type|Subtype | Layer File Library| iMapBC
for published presentations | WMS | Network Link KML |BC Maphub Feature Layer 48 | |:---|:---:|:---:|:---:|:---:|:---:|:---:| 49 | |**Security** | Public | ![](/images/green_check.png)| ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/green_check.png) 50 | |**Security** | IDIR | ![](/images/green_check.png)| ![](/images/green_check.png) | ![](/images/green_check.png) | | Not Available * 51 | |**Security** | Business BCeID | ![](/images/green_check.png)| ![](/images/green_check.png) | | | Not Available * 52 | |**Security** | Named Users
can be a mix of IDIR and Business BCeID | ![](/images/green_check.png)| ![](/images/green_check.png) | Not Available | Not Available | Not Available * 53 | || 54 | |**Area of Interest** | Entire dataset| ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/green_check.png)
uses Default (Outline, All, etc) |![](/images/green_check.png) | ![](/images/green_check.png) 55 | |**Area of Interest** |Subset dataset| ![](/images/green_check.png)
using Definition Queries| ![](/images/green_check.png)
using Definition Queries | ![](/images/green_check.png)
using Definition Queries | Not Available | Not Available 56 | || 57 | |**Tabular** | | Not Available
joins are not supported | Not Available |Not Available|Not Available|Not Available 58 | -------------------------------------------------------------------------------- /assets/js/search-data.json: -------------------------------------------------------------------------------- 1 | --- 2 | permalink: /assets/js/search-data.json 3 | --- 4 | { 5 | {%- assign i = 0 -%} 6 | {% for page in site.html_pages %} 7 | {%- if page.title and page.search_exclude != true -%} 8 | {%- assign page_content = page.content -%} 9 | {%- assign heading_level = site.search.heading_level | default: 2 -%} 10 | {%- for j in (2..heading_level) -%} 11 | {%- assign tag = '' -%} 19 | {%- assign title = titleAndContent[0] | replace_first: '>', '

' | split: '

' -%} 20 | {%- assign title = title[1] | strip_html -%} 21 | {%- assign content = titleAndContent[1] -%} 22 | {%- assign url = page.url -%} 23 | {%- if title == page.title and parts[0] == '' -%} 24 | {%- assign title_found = true -%} 25 | {%- else -%} 26 | {%- assign id = titleAndContent[0] -%} 27 | {%- assign id = id | split: 'id="' -%} 28 | {%- if id.size == 2 -%} 29 | {%- assign id = id[1] -%} 30 | {%- assign id = id | split: '"' -%} 31 | {%- assign id = id[0] -%} 32 | {%- capture url -%}{{ url | append: '#' | append: id }}{%- endcapture -%} 33 | {%- endif -%} 34 | {%- endif -%} 35 | {%- unless i == 0 -%},{%- endunless -%} 36 | "{{ i }}": { 37 | "doc": {{ page.title | jsonify }}, 38 | "title": {{ title | jsonify }}, 39 | "content": {{ content | replace: ' **Server** and select **New WFS Server**. 18 | ![New WMS connection button](images/wms_wfs_getting_started/agp_wms_new_connection.png) 19 | 3. Set the **Server URL** to `https://openmaps.gov.bc.ca/geo/ows?SERVICE=WMS&REQUEST=GetCapabilities`, leaving the other settings as is. 20 | ![New WMS connection dialogue in ArcGIS Pro](images/wms_wfs_getting_started/agp_wms_new_connection_settings.png) 21 | 4. Click **OK**. 22 | 5. In the **Catalog** pane, expand **Servers** and then continue to expand the new WMS connection, `DataBC Public Web Map Service on openmaps.gov.bc.ca.wms`, and the groups within. Allow a moment for the layers list to load. You should see: 23 | 24 | ![WMS layer list](images/wms_wfs_getting_started/agp_wms_connection.png) 25 | 26 | 6. Identify the dataset you'd like to add. Dataset names should correspond to the [BC Data Catalogue](https://catalogue.data.gov.bc.ca/). For this example, we will add Health Authority Boundaries. 27 | 7. To reduce scrolling through the layer list, click one of the first layers, then type `hea`, which should then jump to and select `Health Authority Boundaries`. Unfortunately, the search function does not include server layers. 28 | 8. Right click the layer name, and select **Add to Current Map** or **Add to New** > **Map**. 29 | 9. Explore the data - zoom in, pan around. Labels are visible for some services at pre-defined scales. If you expand the new layer in the **Contents** pane, you will see the layer legend. 30 | 31 | ![Health Authority WMS service in ArcGIS Pro](images/wms_wfs_getting_started/agp_wms_health_view.png) 32 | 33 | {: .note-title} 34 | > WMS Styles 35 | > 36 | > ArcGIS Pro adds the layer using the default style. Other style options can be accessed by clicking the layer name (`Health Authority Boundaries`) in the **Contents** pane, then opening the **WMS Sublayer** tab and clicking **Symbology** in the **Drawing** group. 37 | > 38 | > ![Accessing style options](images/wms_wfs_getting_started/agp_wms_styles.png) 39 | > 40 | > ArcGIS Pro only shows the style `Name`, which is just an ID number. The layer specific `GetCapabilities` request (e.g. [https://openmaps.gov.bc.ca/geo/pub/WHSE_ADMIN_BOUNDARIES.BCHA_HEALTH_AUTHORITY_BNDRY_SP/ows?service=WMS&request=GetCapabilities](https://openmaps.gov.bc.ca/geo/pub/WHSE_ADMIN_BOUNDARIES.BCHA_HEALTH_AUTHORITY_BNDRY_SP/ows?service=WMS&request=GetCapabilities)) shows the `Title` for each style. For `Health Authority Boundaries`, `372` (`Outlined`) shows only boundaries, while `373` (`Colour_Themed`) shows a coloured fill for each health area. `372_373`, the default, is a combination of both. A similar pattern is followed for most datasets. 41 | 42 | 10. DataBC's WMS service supports `GetFeatureInfo` requests to view individual feature information. While this feature works just fine in QGIS, unfortunately ArcGIS Pro does not make the request correctly, so it is not possible to view any feature info beyond what is shown through symbology and labels. 43 | 44 | Read more about [the nature and limitations of WMS](map_getting_started_qgis_wms.html#the-nature-and-limitations-of-wms) or jump into the [WFS tutorial](map_getting_started_arcgispro_wfs.md). 45 | 46 | ----------------------- 47 | 48 | [RETURN TO TOP][1] 49 | 50 | [1]: #top 51 | -------------------------------------------------------------------------------- /pages/dps_data_distribution_providers_w_.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Distribution Workflow - Providers 4 | nav_order: 52 5 | parent: Data Distribution 6 | has_toc: false 7 | --- 8 | 9 | # DATA DISTRIBUTION WORKFLOW FOR PROVIDERS 10 | 11 | This page describes the requirements and options for distributing data from the BC Geographic Warehouse (BCGW). 12 | 13 | This service allows for data in the BCGW to be orderable in a variety of formats using the BC Data Catalogue (BCDC) and iMapBC. 14 | 15 | |**AUDIENCE**| | | | | 16 | |:---|:---|:---|:---|:---| 17 | |[*Data Publisher*](https://bcgov.github.io/data-publication/pages/glossary.html#data_publisher)|[*Custodian*](https://bcgov.github.io/data-publication/pages/glossary.html#custodian)|[*Data Manager*](https://bcgov.github.io/data-publication/pages/glossary.html#data_manager)|[*Data Steward*](https://bcgov.github.io/data-publication/pages/glossary.html#data_steward)|[*Metadata Editor*](https://bcgov.github.io/data-publication/pages/glossary.html#metadata_editor)| 18 | 19 | ## Table of Contents 20 | 21 | + [**CONFIGURABLE PRODUCTS**](#configurable-products) 22 | + [**REQUIREMENTS**](#requirements) 23 | + [**LIMITATIONS**](#limitations) 24 | + [**CONFIGURATION OPTIONS**](#configuration-options) 25 | 26 | ----------------------- 27 | 28 | ## CONFIGURABLE PRODUCTS 29 | 30 | ## REQUIREMENTS 31 | All datasets in the BCGW that are configured for distribution require 32 | 33 | 1. A published dataset in the BC Geographic Warehouse. 34 | 2. A metadata record. 35 | 3. A profile defined as one of the Security options below. 36 | - Named Users is the only profile that requires additional configuration. 37 | 38 | As well if for download from iMapBC additionally require 39 | 1. A presentation layer as created with the [Layer File Presenation document](./dsg_bcgw_layer_file_presentation.md). 40 | 41 | ## LIMITATIONS 42 | 43 | + Max downloadable zipped file size is 2 GB. 44 | + Only the format options listed below are what is configured. 45 | - Addition file format types can be requested. Each business case will be reviewed to determine feasibility and value. 46 | 47 | ## CONFIGURATION OPTIONS 48 | ![](/images/grey_dash.png) 49 | 50 | |Type|Subtype | BC Data Catalogue
for published metadata | iMapBC
for published presentations | 51 | |:---|:---:|:---:|:---:| 52 | |**Security** | Public | ![](/images/green_check.png) | ![](/images/green_check.png) 53 | |**Security** | IDIR | ![](/images/green_check.png) | ![](/images/green_check.png) 54 | |**Security** | Business BCeID | ![](/images/green_check.png) | ![](/images/green_check.png) 55 | |**Security** | Named Users
can be a mix of IDIR and Business BCeID | ![](/images/green_check.png) | ![](/images/green_check.png) 56 | || 57 | |**Format** | CSV
only option for tabular| ![](/images/green_check.png) | ![](/images/green_check.png) 58 | |**Format** | ESRI File Geodatabse
(fgdb) | ![](/images/green_check.png) | ![](/images/green_check.png) 59 | |**Format** | ESRI Shape File
(shp) | ![](/images/green_check.png) | ![](/images/green_check.png) 60 | |**Format** | GeoJSON | ![](/images/green_check.png) | ![](/images/green_check.png) 61 | || 62 | |**Spatial** | | ![](/images/green_check.png) | ![](/images/green_check.png) 63 | |**Area of Interest** | Entire dataset | ![](/images/green_check.png) | ![](/images/green_check.png) 64 | |**Area of Interest** | Subset dataset | ![](/images/green_check.png) | ![](/images/green_check.png) 65 | |**Projection**|BC Albers |![](/images/green_check.png) | ![](/images/green_check.png) 66 | |**Projection**|UTM Zone 7 through 11 |![](/images/green_check.png) | ![](/images/green_check.png) 67 | |**Projection**|Geographc Lat/Long |![](/images/green_check.png) | ![](/images/green_check.png) 68 | || 69 | |**Tabular** | | ![](/images/green_check.png) | Not available 70 | |**Attribute Query** | Subset dataset | Not available | ![](/images/green_check.png)
as defined in a definition query 71 | 72 | -------------------------------------------------------------------------------- /pages/dps_bcdc_w_dataset.md: -------------------------------------------------------------------------------- 1 | ```--- 2 | layout: default 3 | title: Tabular Data 4 | nav_order: 5 | parent: How to use the UI 6 | grand_parent: BC Data Catalogue 7 | has_children: false 8 | has_toc: false 9 | --- 10 | ``` 11 | ## DOCUMENT or TABULAR DATA RESOURCE MANAGEMENT 12 | 13 | **Corresponds to the Beta BC Data Catalogue release that will go to production soon.** 14 | 15 | For the classic catalogue specific user pages see [BCDC Classic Workflow](https://bcgov.github.io/data-publication/pages/dps_bcdc_classic_w.html). 16 | 17 | 18 | --------------- 19 | **Resources** 20 | + See the full list of value options for drop down fields, see the [BCDC Schema](https://cat.data.gov.bc.ca/api/3/action/scheming_dataset_schema_show?type=bcdc_dataset) 21 | + See all documented changes in the [Change Log](https://github.com/bcgov/ckan-ui/blob/master/pages/beta_schema_changes.md#application-resource-level-changes) 22 | 23 | 24 | --------------- 25 | 26 | **To add a resource:** 27 | 1. Click the **Add Resource** button on the toolbar at the record level. 28 | 1. Fill out all the required fields for each resource type as described below. 29 | 30 | 31 | --------------- 32 | \* indicates required fields 33 | 34 | **Title\***: Is the title of the resource as it will appear on the metadata record. 35 | 36 | **_Resource_** 37 | 38 | + **URL**: Is a link to a file or resource stored elsewhere, e.g., a website or FTP site. 39 | - For resources that are not available unless authorized a link to a webpage or form to instruct consumers how to obtain access, e.g. [Request Archaeology Information](https://catalogue.data.gov.bc.ca/dataset/a6d58d20-8e19-46ba-b5a0-f02e436fa765/resource/cbbd35ea-8ddb-4cb4-b717-d897e5303dc3) 40 | 41 | + **File**: Is when a file is uploaded directly into the Catalogue Data Store. 42 | 43 | 44 | --------------- 45 | 46 | **Type\***: Is the resource type that defines the available fields for a resource. 47 | + Select **Document/Tabular Data** 48 | 49 | + **Changes**: 50 | - Database Value: 'Dataset' has changed to 'document' 51 | 52 | --------------- 53 | 54 | **Resource Description**: Is a detailed description of the resource. 55 | 56 | **Supplemental Information**: Any additional relevant information about the resource can be included here. 57 | 58 | **Resource Update Cycle\***: Describes how often the resource is updated. 59 | 60 | + **Changes**: 61 | - **NEW Values** "Nightly" (`nightly`); "Unknown" (`unknown`) 62 | 63 | **_Temporal Extent_** 64 | 65 | + If your dataset is temporal in nature, you may provide the relevant dates in this area 66 | - **Beginning Date** is the start date for the period the data is captured for. 67 | - **End Date** is the end date for the period the data is captured for. 68 | 69 | **Resource Storage Format\***: Describes the file extension for the resource. 70 | 71 | + **Changes**: 72 | - **NEW Values** "geopackage" (`gpkg`); "multiple" (`multiple`) 73 | 74 | **Resource Storage Location\***: Is the location where the resource is stored. 75 | 76 | For files that have been uploaded using the Upload File above, choose Catalogue Data Store. 77 | 78 | + **Changes**: 79 | - **Database value** all database entries are now lower case. e.g., `BC Data Catalogue` has changed to `bc data catalogue` 80 | 81 | 82 | **JSON Table Schema** 83 | 84 | + **Changes**: **NEW** 85 | 86 | **Resource Type\***: Is the type of resource: Data, Reports or Abstraction. 87 | 88 | **Resource Access Method\***: Describes how the end-user can access the data. 89 | 90 | + **Changes**: 91 | - **NEW Value** "Other" (`other`) 92 | 93 | Click **Save** when done 94 | 95 | + Additional resources can be added by repeating the process above or adding other resource types. 96 | 97 | 98 | ## OTHER RESOURCES TYPES 99 | - [Application](./dps_bcdc_w_application.md) 100 | - [Document/Tabular Data](./dps_bcdc_w_dataset.md/) 101 | - [Geographic Data](./dps_bcdc_w_geographic_dataset.md) 102 | - [Webservice/API](./dps_bcdc_w_webservice_api.md) 103 | -------------------------------------------------------------------------------- /pages/dps_bcdc_w_application.md: -------------------------------------------------------------------------------- 1 | ```--- 2 | layout: default 3 | title: Application 4 | nav_order: 5 | parent: How to use the UI 6 | grand_parent: BC Data Catalogue 7 | has_children: false 8 | has_toc: false 9 | --- 10 | ``` 11 | 12 | ## APPLICATION RESOURCE MANAGEMENT IN THE BC DATA CATALOGUE 13 | 14 | **Corresponds to the Beta BC Data Catalogue release that will go to production soon.** 15 | 16 | For the classic catalogue specific user pages see [BCDC Classic Workflow](https://bcgov.github.io/data-publication/pages/dps_bcdc_classic_w.html). 17 | 18 | --------------- 19 | **Resources** 20 | + See the full list of value options for drop down fields, see the [BCDC Schema](https://cat.data.gov.bc.ca/api/3/action/scheming_dataset_schema_show?type=bcdc_dataset) 21 | + See all documented changes in the [Change Log](https://github.com/bcgov/ckan-ui/blob/master/pages/beta_schema_changes.md#application-resource-level-changes) 22 | 23 | --------------- 24 | 25 | **To add a resource:** 26 | 1. Click the **Add Resource** button on the toolbar at the record level. 27 | 1. Fill out all the required fields for each resource type as described below. 28 | 29 | 30 | --------------- 31 | \* indicates required fields. 32 | 33 | **Title\***: Is the title of the resource as it will appear on the metadata record. 34 | 35 | **_Resource_** 36 | 37 | + **URL**: Is a link to a applicaiton location 38 | - Secure applications may also be listed. 39 | 40 | + **File**: Is when a file is uploaded directly into the Catalogue Data Store. 41 | - Files specific to an application most likely would not be defined as an application resource but another type, e.g, Document/Tabular Data. 42 | 43 | --------------- 44 | 45 | **Type\***: Is the resource type that defines the available fields for a resource. 46 | 47 | + Select **Application** 48 | 49 | + **Changes**: 50 | - Database Value: 'Application' has changed to 'application' 51 | 52 | --------------- 53 | 54 | **Resource Description**: Is a detailed description of the resource. 55 | 56 | **Supplemental Information**: Any additional relevant information about the resource can be included here. 57 | 58 | **Resource Update Cycle\***: Describes how often the resource is updated. 59 | 60 | + **Changes**: 61 | - **NEW Values** "Nightly" (`nightly`); "Unknown" (`unknown`) 62 | 63 | **_Temporal Extent_** 64 | 65 | + If your dataset is temporal in nature, you may provide the relevant dates in this area 66 | - **Beginning Date** is the start date for the period the data is captured for. 67 | - **End Date** is the end date for the period the data is captured for. 68 | 69 | **Resource Storage Format\***: Describes the file extension for the resource. 70 | 71 | + **Changes**: 72 | - **NEW Values** "geopackage" (`gpkg`); "multiple" (`multiple`) 73 | 74 | **Resource Storage Location\***: Is the location where the resource is stored. 75 | 76 | + For files that have been uploaded using the _Upload File_ above, choose Catalogue Data Store. 77 | 78 | + **Changes**: 79 | - **Database value** all database entries are now lower case. e.g., `BC Data Catalogue` has changed to `bc data catalogue` 80 | 81 | **JSON Table Schema** 82 | 83 | + **Changes**: **NEW** 84 | 85 | **Resource Type\***: Is the type of resource. 86 | 87 | + This field is being reviewed to determine if still provides value. 88 | + For Applications this may not be applicable and thus choose "Not Applicable". 89 | 90 | **Resource Access Method\***: Describes how the end-user can access the application. 91 | 92 | + **Changes**: 93 | - **NEW Value** "Other" (`other`) 94 | 95 | Click **Save** when done 96 | 97 | 98 | + Additional resources can be added by repeating the process above or adding other resource types. 99 | 100 | 101 | ## OTHER RESOURCES TYPES 102 | - [Application](./dps_bcdc_w_application.md) 103 | - [Document/Tabular Data](./dps_bcdc_w_dataset.md/) 104 | - [Geographic Data](./dps_bcdc_w_geographic_dataset.md) 105 | - [Webservice/API](./dps_bcdc_w_webservice_api.md) 106 | -------------------------------------------------------------------------------- /pages/_sass/custom/custom.scss: -------------------------------------------------------------------------------- 1 | //// 2 | //// Typography 3 | //// 4 | 5 | //$body-font-family: -apple-system, BlinkMacSystemFont, "helvetica neue", helvetica, roboto, noto, "segoe ui", arial, sans-serif; 6 | //$mono-font-family: "SFMono-Regular", Menlo, Consolas, Monospace; 7 | //$root-font-size: 16px; // Base font-size for rems 8 | // $root-font-size: 18px; //Changing this font size causes just the docs responsive styling to get buggy 9 | //$body-line-height: 1.4; 10 | //$content-line-height: 1.5; 11 | //$body-heading-line-height: 1.15; 12 | 13 | //// 14 | //// Colors 15 | //// 16 | 17 | //$white: #fff; 18 | 19 | //$grey-dk-000: #959396; 20 | //$grey-dk-100: #5c5962; 21 | //$grey-dk-200: #44434d; 22 | //$grey-dk-250: #302d36; 23 | //$grey-dk-300: #27262b; 24 | 25 | //$grey-lt-000: #f5f6fa; 26 | //$grey-lt-100: #eeebee; 27 | //$grey-lt-200: #ecebed; 28 | //$grey-lt-300: #e6e1e8; 29 | 30 | //$purple-000: #7253ed; 31 | //$purple-100: #5e41d0; 32 | //$purple-200: #4e26af; 33 | //$purple-300: #381885; 34 | 35 | //$blue-000: #2c84fa; 36 | //$blue-100: #2869e6; 37 | //$blue-200: #264caf; 38 | //$blue-300: #183385; 39 | 40 | //$green-000: #41d693; 41 | //$green-100: #11b584; 42 | //$green-200: #009c7b; 43 | //$green-300: #026e57; 44 | 45 | //$yellow-000: #ffeb82; 46 | //$yellow-100: #fadf50; 47 | //$yellow-200: #f7d12e; 48 | //$yellow-300: #e7af06; 49 | 50 | //$red-000: #f77e7e; 51 | //$red-100: #f96e65; 52 | //$red-200: #e94c4c; 53 | //$red-300: #dd2e2e; 54 | 55 | //$body-background-color: $white; 56 | $sidebar-color: $grey-lt-000; 57 | //$sidebar-color: #f1f1f1; 58 | //$sidebar-color: $blue-300; 59 | $sidebar-width: $unset; 60 | //$search-background-color: $white; 61 | $table-background-color: $white; 62 | //$table-background-color: $blue-100; 63 | //$code-background-color: $grey-lt-000; 64 | 65 | //$body-text-color: $grey-dk-100; 66 | //$body-text-color: #313132; 67 | //$body-heading-color: $grey-dk-300; 68 | $body-heading-color: $blue-300; 69 | //$search-result-preview-color: $grey-dk-000; 70 | //$nav-child-link-color: $grey-dk-100; 71 | $nav-child-link-color: grey-lt-000; 72 | //$link-color: $purple-000; 73 | //$link-color: #1a5a96; 74 | $link-color: $blue-100; 75 | //$btn-primary-color: $purple-100; 76 | //$base-button-color: #f7f7f7; 77 | 78 | //// 79 | //// Spacing 80 | //// 81 | 82 | //$spacing-unit: 1rem; // 1rem == 16px 83 | 84 | //$spacers: ( 85 | //sp-0: 0, 86 | //sp-1: $spacing-unit * 0.25, 87 | //sp-2: $spacing-unit * 0.5, 88 | //sp-3: $spacing-unit * 0.75, 89 | //sp-4: $spacing-unit, 90 | //sp-5: $spacing-unit * 1.5, 91 | //sp-6: $spacing-unit * 2, 92 | //sp-7: $spacing-unit * 2.5, 93 | //sp-8: $spacing-unit * 3, 94 | //sp-9: $spacing-unit * 3.5, 95 | //sp-10: $spacing-unit * 4 96 | //); 97 | 98 | //$sp-1: map-get($spacers, sp-1); // 0.25 rem == 4px 99 | //$sp-2: map-get($spacers, sp-2); // 0.5 rem == 8px 100 | //$sp-3: map-get($spacers, sp-3); // 0.75 rem == 12px 101 | //$sp-4: map-get($spacers, sp-4); // 1 rem == 16px 102 | //$sp-5: map-get($spacers, sp-5); // 1.5 rem == 24px 103 | //$sp-6: map-get($spacers, sp-6); // 2 rem == 32px 104 | //$sp-7: map-get($spacers, sp-7); // 2.5 rem == 40px 105 | //$sp-8: map-get($spacers, sp-8); // 3 rem == 48px 106 | //$sp-9: map-get($spacers, sp-9); // 4 rem == 48px 107 | //$sp-10: map-get($spacers, sp-10); // 4.5 rem == 48px 108 | 109 | //// 110 | //// Borders 111 | //// 112 | 113 | //$border: 1px solid; 114 | //$border-radius: 4px; 115 | //$border-color: $grey-lt-100; 116 | $border-color: #ddd; 117 | 118 | //// 119 | //// Grid system 120 | //// 121 | 122 | //$gutter-spacing: $sp-6; 123 | //$gutter-spacing-sm: $sp-4; 124 | //$nav-width: 264px; 125 | //$nav-width-md: 248px; 126 | $nav-width: 200px; 127 | $nav-width-md: 150px; 128 | $content-width: 1000px; 129 | //$header-height: 60px; 130 | //$search-results-width: 500px; 131 | 132 | //// 133 | //// Media queries in pixels 134 | //// 135 | 136 | //$media-queries: ( 137 | //xs: 320px, 138 | //sm: 500px, 139 | //md: $content-width, 140 | //lg: $content-width + $nav-width, 141 | //xl: 1400px 142 | //); 143 | -------------------------------------------------------------------------------- /pages/map_getting_started_qgis_wms.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: QGIS - Loading a WMS Layer 4 | grand_parent: Web-based Mapping 5 | parent: WMS/WFS - Getting Started 6 | nav_order: 881 7 | has_toc: false 8 | --- 9 | 10 | # QGIS - LOADING A WMS LAYER 11 | 12 | The QGIS documentation provides an [excellent walk-through](https://docs.qgis.org/latest/en/docs/training_manual/online_resources/wms.html) on how to load a WMS layer. These instructions are adapted from the QGIS docs with additional details on the DataBC services. 13 | 14 | 1. Open QGIS and create a new project. 15 | 2. Open ![Data Source Manager icon](images/wms_wfs_getting_started/qgis_data_source_mgr.png) Data Source Manager > ![WMS icon](images/wms_wfs_getting_started/qgis_wms_icon.png) **WMS/WMTS** tab. 16 | 3. Create a **New** connection. 17 | 4. Provide a **name** like `DataBC Layers` and set the **URL** to `https://openmaps.gov.bc.ca/geo/ows?SERVICE=WMS&REQUEST=GetCapabilities`, leaving the other settings as is. 18 | ![New WMS connection dialogue in QGIS](images/wms_wfs_getting_started/qgis_new_wms_connection.png) 19 | 5. Click **OK**. 20 | 6. Click **Connect** and allow a moment for the layers to load. You should see: 21 | ![WMS layer list](images/wms_wfs_getting_started/qgis_wms_connection.png) 22 | 7. Use the **search** bar to find a dataset of interest. For this example, we will add Health Authority Boundaries. 23 | ![Settings to add the Health Authority Boundaries layer](images/wms_wfs_getting_started/qgis_wms_health_add.png) 24 | 8. Click on the `372_373` - `Health_Area_Boundaries` layer. Then change the **Coordinate Reference System** to match your map - if you are using a typical web basemap, chances are it is in `EPSG:3857 - WGS 84 / Pseudo-Mercator`. 25 | 26 | {: .note-title} 27 | > WMS Styles 28 | > 29 | > The multiple options shown for a given dataset are different *styles* for the same data, e.g. `Outlined` (Name `372`) shows only boundaries, while `Colour_Themed` (`373`) shows a coloured fill for each health area. `372_373` is a combination of both. A similar pattern is followed for most datasets. 30 | 31 | 9. Click **Add** to load the layer. 32 | 10. **Close** the Data Source Manager window. 33 | 11. Drag the new layer to the top of the list in the **Layers** panel. 34 | 12. Right click the new layer and click **Zoom to Layer(s)**. 35 | 13. Explore the data - zoom in, pan around. Labels are visible for some services at pre-defined scales. Any symbology is shown in a legend in the layer list. 36 | ![Health Authority WMS service in QGIS](images/wms_wfs_getting_started/qgis_wms_view.png) 37 | 14. The ![Identify tool](images/wms_wfs_getting_started/qgis_identify.png) [identify tool](https://docs.qgis.org/3.28/en/docs/user_manual/introduction/general_tools.html#identify) allows viewing individual feature information. 38 | ![Identify Results for WMS Health Authority layer](images/wms_wfs_getting_started/qgis_identify_wms.png) 39 | 40 | ## The nature and limitations of WMS 41 | The WMS layer looks like it’s made up of vectors, yet it seems to be a raster, and you can’t change its symbology. Why is that? 42 | 43 | This is how a WMS works: it’s a map, similar to a normal map on paper, that you receive as an image. What usually happens is that you have vector layers, which QGIS renders as a map. But using a WMS, those vector layers are on the WMS server, which renders it as a map and sends that map to you as an image. QGIS can display this image, but can’t change its symbology, because all that is handled on the server. 44 | 45 | This has several advantages, because you don’t need to worry about the symbology. It’s already worked out, and should be nice to look at on any competently designed WMS. 46 | 47 | On the other hand, you can’t change the symbology if you don’t like it, and if things change on the WMS server, then they’ll change on your map as well. This is why you sometimes want to use a Web Feature Service (WFS) instead, which gives you vector layers separately, and not as part of a WMS-style map. 48 | 49 | Jump into the [WFS tutorial](map_getting_started_qgis_wfs.md) to learn more! 50 | 51 | ----------------------- 52 | 53 | [RETURN TO TOP][1] 54 | 55 | [1]: #top 56 | -------------------------------------------------------------------------------- /pages/dps_maphub_glossary.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: AGO Glossary 4 | grand_parent: Web-based Mapping 5 | parent: BC's Map Hub - Publication Workflow 6 | nav_order: 815 7 | has_toc: false 8 | --- 9 | 10 | 11 | # ArcGIS Online Digital Application - Glossary 12 | ## Account Types 13 | **Single-User** accounts can be Enterprise (use your IDIR to sign-in) or non-Enterprise (you manage your own password). If you're a Python user and wish to use it with ArcGIS Online choose the non-Enterprise type. 14 |

15 | **Multi-User** (aka Proxy) accounts: 16 | - Require the number of users to be specified and tracked. 17 | - Have limited privileges to facilitate access to BC's Map Hub content when individuals do not have a need for their own account. 18 | - Are typically shorter term Project specific accounts, often used to facilitate review and approval of content in BC's Map Hub. 19 | - Are owned and managed by an existing Single-User Creator account on BC's Map Hub. 20 | - May incur charges related to credit consumption such as storage or premium service usage. 21 | - Profile will be set to "Private" (e.g. "Who can see your profile"). 22 |
23 | 24 | **Proxy Account Owner Responsibilities:** 25 | - Creating a specific Group for the map/app. 26 | - Inviting the Proxy Account to the Group and ensuring the Account is able to access required project resources. 27 | - Ensuring the individuals provided the Proxy Account credentials are Internal Government users or known external users only. 28 | - Ensuring the individuals provided the Proxy Account are limited to minimal viable accessibility/functionality as required by the project. 29 | - Ensuring that the Proxy Account profile property "Who can see your profile?" remains set to "No one (private)". 30 | 31 | ## User Types 32 | Esri categorizes accounts by **User Type**. User Types provide a level of control over what privileges and capabilities are available to the account and are integral to Esri's pricing structure. 33 |

34 | **Viewer** - restricted to viewing and using layers, maps, scenes and apps. 35 |

36 | **Contributor (formerly Editor)** - In addition to Viewer capabilities, Contributors are able to edit data via desktop applications or mobile devices when Wi-Fi or network access is available. This role reflects an expansion in capabilities, allowing for more comprehensive management and editing within our GIS projects. 37 |

38 | **Fieldworker** - In addition to Editor capabilities, Fieldworker have access to Field apps including Collector and Survey123 allowing for data collection in the field without wifi or network connectivity. 39 |

40 | **Creator** - In addition to Fieldworker capabilities, Creator are able to configure their own solutions including creating Maps and Apps, and also have the ability to share content to others. This role now includes additional resources such as ArcGIS Pro Basic and ArcGIS Image, supporting more robust creation and management of GIS content. 41 | 42 | ## User Roles 43 | The custom **User Roles** on BC's Map Hub further controls what privileges are available to the account(i.e. privileges to edit data, create content, use premium content, share content...) 44 |

45 | **Emergency Role Accounts** are available only to business units that require immediate sharing to everyone/public privileges to support needs during imminent emergencies (not intended for day to day business operations). When time permits, content shared to public by Emergency Roles authors requires publishing request/checklist if authors intend to keep content for longer term. Else content must be unshared from public. 46 | 47 | ## Privileges 48 | **Privileges** are assigned to User Roles and further define what a user can do in ArcGIS Online. 49 |

50 | Premium Content privileges are currently disabled but may be available on a case by case. Premium content consumes service credits. We encourage users with access to use ArcMap/ArcPro where service credits are not required. 51 | 52 | ## Public Content 53 | Sharing content to public requires completion of metadata, GCPE and Director approvals and submission of checklist/request form. Admins will share content on behalf of users who submit requests. Users who intend to make content available to public should ensure they are familiar with they process and allocate time to prepare content and complete the checklist in good time. 54 | -------------------------------------------------------------------------------- /pages/dps_bcgw.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: BC Geographic Warehouse 4 | nav_order: 4 5 | has_children: true 6 | has_toc: false 7 | --- 8 | 9 | # BC GEOGRAPHIC WAREHOUSE 10 | 11 | The B.C. Geographic Warehouse (BCGW) is a central government repository of spatial and non-spatial data that is needed by Government, industry and the public in order to make decisions. The data includes Base Mapping information, such as heights of land, rivers, lakes, roads, place name and administrative boundaries, as well as government program information, like forest cover, ecosystems, economic and health indicators. 12 | 13 | The BCGW is a foundation for the B.C. Spatial Data Infrastructure and all of the data in it is made ready for a wide variety of uses through a rigorous and standardized publication process that embraces the principles of Data Custodianship. 14 | 15 | ### Why the BCGW? 16 | 17 | The BCGW is managed by DataBC. It supports the Province's electronic services strategy as it is designed and operated for the purposes of hosting and cataloguing sets of data (mostly spatial data) on behalf of custodial ministries and other government custodial agencies. 18 | 19 | The BCGW's access tools include ArcGIS for direct GIS access to spatial data, iMapBC and other web-based mapping tools, Discovery and Distribution Services for locating and downloading data. 20 | 21 | The main purpose of the BCGW is to make data available to users in a form that best supports data integration, sharing and exchange, analysis and decision-making. In general, this is the purpose of any data warehouse. 22 | 23 | Specifically, the BCGW accomplishes the following: 24 | 25 | + **Wide access** 26 | + In principle, any authorized person can gain access from anywhere on the internet, and browse, view, order and download data. 27 | + **Suited for purpose** 28 | + By means of data transformation, the BCGW allows data to be formatted and presented in a form useful to different audiences. 29 | + **Integration** 30 | + It allows data to be viewed, combined and analyzed with other data. 31 | + **User empowerment** 32 | + It includes some simple but effective data viewing and analysis tools. 33 | 34 | By virtue of these features, the BCGW can provide substantial benefits for both _Data Custodians_ and _Data Managers_. In particular it responds to _Data Custodians'_ obligations to provide wide access to current, complete and authoritative data. It does this in a controlled manner, allowing graduated access from generalized browsing and viewing through to in-depth content access. 35 | 36 | ### How does the BCGW Work? 37 | 38 | The BCGW is somewhat similar to a distribution warehouse that you find in a manufacturing supply chain. 39 | 40 | The BCGW's data publishing and distribution process works as follows: 41 | 42 | + Government ministries and agencies (the data providers) produce data, which they publish to the BCGW. (This is like component manufacturers creating goods and shipping them to a warehouse.) 43 | + At the warehouse, the data is: 44 | + repackaged for consumer use - i.e., for the broad audience that uses the BCGW; 45 | + checked for valid format and structure; and then 46 | + stored and made available for browsing and viewing via an online catalogue. 47 | + Data consumers browse and select data products from the warehouse, which are distributed to them, generally using download via the internet. 48 | 49 | #### Information Management through the BCGW 50 | 51 | ![Information Management through the BCGW](images/image_information_management_through_the_BCGW.png) 52 | 53 | ## MAKING USE OF THE BCGW 54 | 55 | ### Benefits 56 | 57 | The BCGW provides the opportunity and means for _Data Custodians_ to present their data to a wide audience of users. 58 | 59 | In this respect, the BCGW is enabling technology. It provides two sets of services - one set to assist _Data Custodians_ to present their data, the other set to help user access and use the data. 60 | 61 | These are the benefits: 62 | 63 | + Relieves _Data Custodians_ and managers of many of the costs and headaches of making their data widely accessible 64 | + Easier user access to manage by virtue of a standard security model 65 | + Provides ability to structure, integrate and package data to better suit user needs 66 | + Improves the user experience by offering a standard user interface and set of familiar tools 67 | + Allows easier viewing and integration with other BCGW data 68 | -------------------------------------------------------------------------------- /pages/dps_bcdc_api_w_resource_mgmt.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Resource Management 4 | nav_order: 343 5 | parent: Content Mgmt/Use - API 6 | grand_parent: BC Data Catalogue 7 | has_children: false 8 | has_toc: true 9 | --- 10 | 11 | # **BC Data Catalogue Resource API management** 12 | ------------- 13 | 14 | ||**Audience** | | 15 | |:---:|:---:|:---:| 16 | | [*Catalogue Editors*](../glossary.html#metadata_editor) | [*Catalogue Admin*](../glossary.html#metadata_admin) | *Catalogue Developers* | 17 | 18 | ## Table of Contents 19 | + [**How to manage Resources using the Catalogue API**](#how-to-manage-resources-using-the-catalogue-api) 20 | + [How to create a resource with the API](#how-to-create-a-resource-with-the-api) 21 | + [How to update a resource with the API using resource_update](#how-to-update-a-resource-with-the-api-using-resource_update) 22 | + [How to update a resource with the API using resource_patch](#how-to-update-a-resource-with-the-api-using-resource_patch) 23 | 24 | 25 | ----------------------- 26 | **Resources** 27 | + See the full list of value options for drop down fields, see the [BCDC Schema](https://catalogue.data.gov.bc.ca/api/3/action/scheming_dataset_schema_show?type=bcdc_dataset) 28 | + See all documented changes in the [Change Log](https://github.com/bcgov/ckan-ui/blob/master/pages/beta_schema_changes.md#application-resource-level-changes) 29 | 30 | ----------------------- 31 | 32 | ## How to manage Resources using the Catalogue API 33 | 34 | To use the Catalogue API to manage and create metadata resources one must be an editor/publisher. Review [How to Become a Provider to the Catalogue](dps_bcdc_w.md#HOW-TO-BECOME-A-PROVIDER-TO-THE-CATALOGUE) for more information. 35 | 36 | See the [common calls](/dps_bcdc_api_w_common_calls.html) page to find how to get your API key, organization and other information you may require. 37 | 38 | 39 | 40 | ### How to create a resource with the API 41 | 42 | * Listed are all mandatory fields but there are other fields that can be populated and encourage that they are. 43 | 44 | ``` 45 | import ckanapi 46 | 47 | # to change host between prod and test, use the following: production = 'catalogue'; test = 'cat' 48 | 49 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 50 | 51 | resp = ckan.action.resource_create( 52 | package_id='YOUR-PACKAGE-ID-HERE', 53 | upload=open('/Users/Documents/test_resource_csv_upload.csv'), 54 | name='my-resource-name-updated', 55 | bcdc_type='document', 56 | resource_update_cycle='monthly', 57 | format='csv', 58 | resource_storage_location='catalogue data store', 59 | resource_type='data', 60 | resource_access_method='direct access') 61 | 62 | 63 | print(resp) 64 | ``` 65 | ### How to update a resource with the API using resource_update 66 | 67 | * All mandatory fields must be included to use this function. 68 | * Recommend reviewing the json schema for a listing of all available fields and if mandatory or not. 69 | * The following is an example of loading a resource to the catalogue itself and fields defined for the Dataset/Tabular (bcdc_type="document"). Geographic Datasets require more fields. 70 | 71 | 72 | ``` 73 | import ckanapi 74 | 75 | # to change host between prod and test, use the following: production = 'catalogue'; test = 'cat' 76 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 77 | 78 | resp = ckan.action.resource_update( 79 | id='RESOURCE-ID-TO-UPDATE-HERE', 80 | upload=open('/Users/Documents/test_resource_csv_upload.csv'), 81 | name='my-resource-name-updated', 82 | bcdc_type='document', 83 | resource_update_cycle='monthly', 84 | format='csv', 85 | resource_storage_location='catalogue data store', 86 | resource_type='data', 87 | resource_access_method='direct access') 88 | 89 | 90 | print(resp) 91 | ``` 92 | 93 | ### How to update a resource with the API using resource_patch 94 | 95 | * Is used to update just specific fields or the resource itself if . 96 | 97 | ``` 98 | import ckanapi 99 | 100 | # to change host between prod and test, use the following: production = 'catalogue'; test = 'cat' 101 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 102 | 103 | resp = ckan.action.resource_patch( 104 | id='RESOURCE-ID-TO-UPDATE-HERE', 105 | name='my-resource-name-updated', 106 | description='my-resource-descrition-update') 107 | 108 | 109 | print(resp) 110 | ``` 111 | 112 | [RETURN TO TOP][1] 113 | 114 | [1]: #bc-data-catalogue-resource-api-management 115 | -------------------------------------------------------------------------------- /pages/map_getting_started_arcgispro_wfs.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: ArcGIS Pro - Loading a WFS Layer 4 | grand_parent: Web-based Mapping 5 | parent: WMS/WFS - Getting Started 6 | nav_order: 884 7 | has_toc: false 8 | --- 9 | 10 | # ARCGIS PRO - LOADING A WFS LAYER 11 | 12 | Here is a quick walk-through on how to load a WFS layer in ArcGIS Pro, with some additional details on the DataBC services. 13 | 14 | Learn more about WFS in ArcGIS Pro in the [Esri documentation](https://pro.arcgis.com/en/pro-app/latest/help/data/services/use-wfs-services.htm). 15 | 16 | {: .highlight-title} 17 | > ⚠ Limited features returned 18 | > 19 | > As of 2024/01/08, ArcGIS Pro 3.1.3 cannot use [paging](tips_tricks_webservices.md#pagination) on DataBC services using WFS 2.0.0 (the default version) without additional configuration. 20 | > 21 | > This limits the number of features ArcGIS Pro can load for a single WFS layer to about 7000. If you need to load a larger dataset, first work through this tutorial, then check out the guide to [loading large datasets](map_getting_started_arcgispro_wfs_large_datasets.md) (or look at using [QGIS](map_getting_started_qgis_wfs.md) or the [bcdata R package](https://github.com/bcgov/bcdata)). 22 | > 23 | > In this tutorial, we set the WFS version to `1.1.0` to allow adding any dataset without displaying any errors, however features will be capped and there will be little indication that features are missing. 24 | 25 | 1. Open ArcGIS Pro. 26 | 2. On the ribbon's **Insert** tab, click **Connections** > **Server** and select **New WFS Server**. 27 | ![New WFS connection button](images/wms_wfs_getting_started/agp_wfs_new_connection.png) 28 | 3. Set the **Server URL** to `https://openmaps.gov.bc.ca/geo/ows?SERVICE=WFS&REQUEST=GetCapabilities`, and **Version** to `1.1.0`. 29 | ![New WFS connection dialogue in ArcGIS Pro](images/wms_wfs_getting_started/agp_wfs_new_connection_settings.png) 30 | 4. Click **OK**. 31 | 5. In the **Catalog** pane, expand **Servers** and then the new WFS connection, `WFS on openmaps.gov.bc.ca.wfs`. Allow a moment for the layers list to load. You should see: 32 | 33 | ![WFS layer list](images/wms_wfs_getting_started/agp_wfs_connection.png) 34 | 35 | 6. Identify the dataset you'd like to add. Dataset names should correspond to the [BC Data Catalogue](https://catalogue.data.gov.bc.ca/). For this example, we will add BC Research Centres. 36 | 7. To reduce scrolling through the layer list, click one of the first layers, then type `bc` and then page down to `BC Research Centres`. Unfortunately, the search function does not include server layers. 37 | 8. Right click the layer name, and select **Add to Current Map** or **Add to New** > **Map**. 38 | 9. Explore the data - zoom in, pan around, and try selecting features. 39 | ![WFS data shown on map](images/wms_wfs_getting_started/agp_wfs_research_view.png) 40 | 10. Right click the layer in the **Contents** pane and click **Attribute Table** (CTRL+T). As a feature service (rather than a map service like WMS), it is possible to see attribute data, select features, and perform geoprocessing. 41 | ![Attribute table for research centres](images/wms_wfs_getting_started/agp_wfs_research_attributes.png) 42 | 43 | {: .note-title} 44 | > Are all the features loaded? 45 | > 46 | > If the Attribute Table shows exactly 3000 features, it's very likely ArcGIS Pro is hitting the maximum features returned setting for the layer. The default value is 3000 features, but you can try setting this as high as 7000 in the **Layer Properties** > **WFS**. Higher values will cause data source errors. 47 | 48 | 11. WFS allows for custom layer styling. Change the styling from `Single Symbol` to `Unique Values` based on the `RESEARCH_CENTRE_AFFILIATION` field. 49 | ![Research centres symbolized by affiliation](images/wms_wfs_getting_started/agp_wfs_research_categorized.png) 50 | 51 | 12. Similarly, we can add labels. 52 | ![Research centres with labels added](images/wms_wfs_getting_started/agp_wfs_research_labels.png) 53 | 54 | 13. Definition queries can be used to filter the features displayed but only the features initially loaded will be included, so unfortunately filtering will not help with loading larger datasets. 55 | 56 | To filter features, go to **Layer Properties** > **Definition Query**, click **New definition query**. Modify the query to `Where RESEARCH_CENTRE_AFFILIATION is equal to University`. 57 | 14. Click **Apply** and then **OK**. 58 | 59 | Want to load more features? Continue to the walk-through on [loading large datasets](map_getting_started_arcgispro_wfs_large_datasets.md) in ArcGIS Pro. 60 | 61 | ----------------------- 62 | 63 | [RETURN TO TOP][1] 64 | 65 | [1]: #top 66 | -------------------------------------------------------------------------------- /pages/dps_bcdc_api_w_record_mgmt.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Record Management 4 | nav_order: 342 5 | grand_parent: BC Data Catalogue 6 | parent: Content Mgmt/Use - API 7 | has_children: false 8 | has_toc: false 9 | --- 10 | 11 | # **BC Data Catalogue Record API management** 12 | 13 | ------------- 14 | 15 | ||**Audience** | | 16 | |:---:|:---:|:---:| 17 | | [*Catalogue Editors*](../glossary.html#metadata_editor) | [*Catalogue Admin*](../glossary.html#metadata_admin) | *Catalogue Developers* | 18 | 19 | ## Table of Contents 20 | + [**How to manage records using the Catalogue API**](#how-to-manage-records-using-the-catalogue-api) 21 | + [How to create a record with the API](#how-to-create-a-package-with-the-api) 22 | + [How to update a record with the API using package_patch](#how-to-update-a-package-with-the-api-using-package_patch) 23 | 24 | ----------------------- 25 | **Resources** 26 | + See the full list of value options for drop down fields, see the [BCDC Schema](https://catalogue.data.gov.bc.ca/api/3/action/scheming_dataset_schema_show?type=bcdc_dataset) 27 | + See all documented changes in the [Change Log](https://github.com/bcgov/ckan-ui/blob/master/pages/beta_schema_changes.md#application-resource-level-changes) 28 | 29 | ----------------------- 30 | 31 | ## How to manage records using the Catalogue API 32 | To use the Catalogue API to manage and create metadata records one must be an editor/publisher. Review [How to Become a Provider to the Catalogue](dps_bcdc_w.md#HOW-TO-BECOME-A-PROVIDER-TO-THE-CATALOGUE) for more information. 33 | 34 | See the [common calls](/dps_bcdc_api_w_common_calls.html) page to find how to get your API key and other information you may require. 35 | 36 | ### How to create a package with the API 37 | 38 | * Listed are all mandatory fields but there are other fields that can be populated and encourage that they are. 39 | 40 | _under construction_ 41 | 42 | ``` 43 | import ckanapi 44 | 45 | 46 | # To change host between prod and test, use the following: production = 'catalogue'; test = 'toyger' 47 | # To see possible values for pick lists the schema is available at: 48 | * https://github.com/bcgov/ckanext-bcgov-schema/blob/master/ckanext/bcgov_schema/bcdc_dataset.json 49 | 50 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 51 | 52 | resp = ckan.action.package_create( 53 | type="bcdc_dataset", # This is a fixed value 54 | title="Title of my Dataset", # Can be anything 55 | name="title-of-my-dataset", # Should be title in all lowercase with dashes 56 | owner_org="ORG_ID_HERE", # ID of organization 57 | notes="Notes on dataset", # Useful notes on dataset 58 | license_id="2", # Licence ID (example is Open Government License - BC) 59 | # Contacts is bit harder to read needs because its an array of JSON objects in an escaped string 60 | # Make sure to surround all keys and values with escaped quotes \" 61 | # name - your name 62 | # email - your email 63 | # org - your organization ID, probably same as above 64 | # role - your role as a contact, possible values in schema (linked above) 65 | # displayed - true or false, at least one must be true 66 | contacts="[{\"name\":\"Your Name\",\"email\":\"name@your.domain\",\"org\":\"ORG_ID_HERE\",\"role\":\"pointOfContact\",\"displayed\":true}]", 67 | security_class="PUBLIC", # Possible values in schema (linked above) 68 | view_audience="Public", # Possible values in schema (linked above) 69 | download_audience="Public", # Possible values in schema (linked above) 70 | metadata_visibility="Public", # Possible values in schema (linked above) 71 | tag_string="test", # Comma separated, needs at least one value 72 | publish_state="DRAFT", # Should always be DRAFT 73 | resource_status="planned" # Possible values in schema (linked above) 74 | ) 75 | print(resp) 76 | ``` 77 | 78 | ### How to update a package with the API using package_patch 79 | 80 | * Is used to update just specific fields within a package. 81 | 82 | ``` 83 | import ckanapi 84 | 85 | # to change host between prod and test, use the following: production = 'catalogue'; test = 'cat' 86 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 87 | 88 | resp = ckan.action.package_patch( 89 | package_id='PACKAGE-ID-TO-UPDATE-HERE', 90 | name="my-packagee-name-updated", 91 | description="my-package-descrition-updated") 92 | 93 | 94 | print(resp) 95 | ``` 96 | 97 | ------------------------------------------------------- 98 | 99 | [RETURN TO TOP][1] 100 | 101 | [1]: #bc-data-catalogue-record-api-management 102 | -------------------------------------------------------------------------------- /pages/dps_webmapping_downstream_w.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Downstream Workflow 4 | grand_parent: Web-based Mapping 5 | parent: Layer Presentation Services 6 | nav_order: 822 7 | has_toc: false 8 | --- 9 | 10 | _This page is intended to be a resource that describes the current, high-level state flow of downstream data visualization._ 11 | 12 | At the heart of all of BC's widely available data access services is the BC Geographic Warehouse. The Mapping Presentation Configuration Manager (MPCM) is a repository of Esri LYR format files that define the desired graphic presentation of data layers when consumed in a map using Desktop software such as ArcMap **or** in a web mapping application. 13 | 14 | .LYR file format is a binary file format that is proprietary to Esri. The MPCM application is used by DataBC Data Administrators/Architects as part of the data publication process. With input from the Data Custodian or Subject Matter Experts representatives, LYR files are created so that a common optimal symbology is provided in the Corporate Layer File Library for ArcMap users. In addition, LYR files are imported into MPCM and Esri libraries within the product allow the for extraction of critical presentation information which is then loaded into a database schema model and exposed via an ArcGIS Server-based data service hosted by DataBC Mapping Services. This is effectively an empty map service that is dynamic - that is to say that layers can be called in by a layerID and be made available to web mapping applications such as iMapBC. 15 | 16 | The Production MPCM/PROD stage service endpoint which lists all of the available layers and their corresponding IDs can be viewed here: 17 | 18 | [https://apps.gov.bc.ca/pub/mpcm/services/catalog/PROD](https://apps.gov.bc.ca/pub/mpcm/services/catalog/PROD) 19 | 20 | Specifics about a given layer can be found by appending a '/' and a layerID to the URL as such: 21 | 22 | [https://apps.gov.bc.ca/pub/mpcm/services/catalog/PROD/2](https://apps.gov.bc.ca/pub/mpcm/services/catalog/PROD/2) 23 | 24 | **MPCM to Geoserver (WMS/WFS)** 25 | 26 | Geoserver builds run on a schedule. 27 | 28 | Delivery on Tuesday morning: start time is 2-3 AM (can take up to 3 hours to run). 29 | 30 | Test on Wednesday morning: start time is 2-3 AM (can take up to 3 hours to run). 31 | 32 | Production on Thursday: start time is 2-3 AM (can take up to 3 hours to run). 33 | 34 | The schedules can be enabled and disabled. A schedule may be disabled when there is a change freeze. If unsure of whether something has been run, status in Jenkins can be checked as that is the mechanism for running the script. 35 | 36 | The script takes what is in MPCM Production/PROD stage and translates the content into WMS layers. Associated layers styles are stored in a file with an extension .sld. This translations is not perfect as the complex lyr stles are not aways translated with the amount of detail that would be seen in the lyr files. In some cases we can manually build a SLD and override the SLD with the custom style at run time. 37 | 38 | **ArcGIS Online “mini-maxl” Services** 39 | 40 | When the respective Geoserver builds are run and complete without errors, the mini-maxl script can run to build the assocated mini-maxl map services. This is currently run on demand but can be automated. 41 | 42 | Only publicly accessible layers are added to the schema based services. 43 | 44 | You can view status/last run info in Jenkins as well. 45 | 46 | **ArcGIS Online Item Creation** 47 | 48 | Every piece of content in ArcGIS Online has an Item Details page, e.g. 49 | 50 | **Regional Districts** 51 | Item ID page: 52 | 53 | [https://governmentofbc.maps.arcgis.com/home/item.html?id=bb7f0c48789943fbb6e3a0afb9fd4e01](https://governmentofbc.maps.arcgis.com/home/item.html?id=bb7f0c48789943fbb6e3a0afb9fd4e01) 54 | 55 | Created: Mar 19, 2019 Updated: Aug 20, 2021 56 | 57 | "mini-maxl" Service URL is included in the details on the Item ID page 58 | (add ‘?f=pjson’ at the end of the supplied URL as the HTML view of the service is disabled): 59 | [https://maps.gov.bc.ca/arcserver/rest/services/whse/bcgw_pub_whse_legal_admin_boundaries/MapServer/16?f=pjson](https://maps.gov.bc.ca/arcserver/rest/services/whse/bcgw_pub_whse_legal_admin_boundaries/MapServer/16?f=pjson) 60 | 61 | **KML** 62 | 63 | KML files are build as part of the respective GeoServer build. Only public layers are built as kml files. 64 | 65 | **_Need Assistance?_** 66 | 67 | When issues are identified or an on demand run is needed, please create a JSM ticket so that it lands in MAP’s queue and can be assessed for urgency and actioned in due course. Until we build out a few more options in the JIRA Service Manager to cover off Data Access Services inquiries, please use this section: [https://dpdd.atlassian.net/servicedesk/customer/portal/1/group/6](https://dpdd.atlassian.net/servicedesk/customer/portal/1/group/6) 68 | -------------------------------------------------------------------------------- /pages/map_wms_wfs_getting_started.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: WMS/WFS - Getting Started 4 | parent: Web-based Mapping 5 | nav_order: 88 6 | has_children: true 7 | has_toc: false 8 | --- 9 | 10 | # GETTING STARTED WITH WMS AND WFS 11 | 12 | Getting up and running with WMS and WFS services can be intimidating. The goal of this guide is to demystify the basic use of these services in QGIS and ArcGIS Pro. 13 | 14 | Note: This guide was prepared using QGIS 3.28.9 and ArcGIS Pro 3.1.3. 15 | 16 | |**AUDIENCE**| 17 | |:---:| 18 | | *Data consumers* | 19 | 20 | ## Table of Contents 21 | - [Introduction to WMS and WFS](#introduction-to-wms-and-wfs) 22 | - [Accessing WMS and WFS Services](#accessing-wms-and-wfs-services) 23 | - [GetCapabilities Requests](#getcapabilities-requests) 24 | 25 | 26 | ![QGIS logo](images/wms_wfs_getting_started/qgis_logo.png) **QGIS** 27 | - [Loading a WMS Layer](map_getting_started_qgis_wms.md) 28 | - [Loading a WFS Layer](map_getting_started_qgis_wfs.md) 29 | 30 | ![ArcGIS Pro logo](images/wms_wfs_getting_started/agp_logo.png) **ArcGIS Pro** 31 | - [Loading a WMS Layer](map_getting_started_arcgispro_wms.md) 32 | - [Loading a WFS Layer](map_getting_started_arcgispro_wfs.md) 33 | 34 | ----------------------- 35 | ## Introduction to WMS and WFS 36 | 37 | [Web Map Services (WMS)](https://en.wikipedia.org/wiki/Web_Map_Service) and [Web Feature Services (WFS)](https://en.wikipedia.org/wiki/Web_Feature_Service) are standardized protocols for serving geospatial data, set by the Open Geospatial Consortium (OGC). OGC standards are widely supported by various GIS platforms, especially when compared against Esri Map and Feature Services, which are optimized for the ArcGIS platform. 38 | 39 | **WMS** focuses on rendering maps as **images**, allowing users to visualize geospatial data using preset styles. Identify queries to see attributes can be made for individual features. 40 | 41 | **WFS**, on the other hand, enables the retrieval and manipulation of **vector features**. WFS provides feature geometry, allowing for geospatial analysis, as well as attribute data to support analysis and user-defined styling. 42 | 43 | Here's a summary of some of the differences: 44 | 45 | | Feature | WMS (Web Map Service) | WFS (Web Feature Service) | 46 | |-------------------|------------------------------------|--------------------------------------| 47 | | Data Type | Raster data (images/maps) | Vector data (geospatial features) | 48 | | Purpose | Map visualization | Feature retrieval and manipulation | 49 | | Query Capability | Limited | Extensive, easier to use (filter and sort by attributes) | 50 | | Data Format | Image formats (PNG, JPEG) | GML, KML, JSON, CSV | 51 | | Styling | Choose from provided options | Flexible | 52 | | Use Cases | Basemaps, visual data inspection | Geospatial analysis, custom map creation | 53 | | Example Use | Add a streams basemap using an existing style | Create buffer areas around streams with active water use licenses | 54 | 55 | ## Accessing WMS and WFS Services 56 | 57 | All publicly available geospatial datasets (870 as of 2024/01/03) are available through WMS and WFS services. We can make use of a single handy URL to load all layers for each service type: 58 | 59 | WMS: `https://openmaps.gov.bc.ca/geo/ows?SERVICE=WMS&REQUEST=GetCapabilities` 60 | 61 | WFS: `https://openmaps.gov.bc.ca/geo/ows?SERVICE=WFS&REQUEST=GetCapabilities` 62 | 63 | Feel free to move on to the walk-throughs on loading WMS into your software of choice ([QGIS](map_getting_started_qgis_wms.md) / [ArcGIS Pro](map_getting_started_arcgispro_wms.md)), or read the section below for a little more background on these connection URLs. 64 | 65 | ### GetCapabilities Requests 66 | In general, GIS software will make use of a `GetCapabilities` request to connect to a WMS or WFS service. This request provides metadata about the available services, their capabilities, and the data they offer. Once the software knows the capabilities of the service, you can generally go about your business without you needing to delve into the inner workings of the service. 67 | 68 | The `GetCapabilities` URLs provided above list the capabilities for *all* public layers served by DataBC. You can also find WMS `GetCapabilities` requests for individual layers on the [BC Data Catalogue](https://catalogue.data.gov.bc.ca/). For example, the Groundwater Wells [resource page](https://catalogue.data.gov.bc.ca/dataset/groundwater-wells/resource/c9b8b97f-1dfc-4558-bf10-713df749a7e0) lists: 69 | 70 | `https://openmaps.gov.bc.ca/geo/pub/WHSE_WATER_MANAGEMENT.GW_WATER_WELLS_WRBC_SVW/ows?service=WMS&request=GetCapabilities` 71 | 72 | The WFS `GetCapabilities` request can be formed by simply replacing `service=WMS` with `service=WFS`. 73 | 74 | ----------------------- 75 | 76 | [RETURN TO TOP][1] 77 | 78 | [1]: #top 79 | -------------------------------------------------------------------------------- /pages/map_getting_started_qgis_wfs.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: QGIS - Loading a WFS Layer 4 | grand_parent: Web-based Mapping 5 | parent: WMS/WFS - Getting Started 6 | nav_order: 882 7 | has_toc: false 8 | --- 9 | 10 | # QGIS - LOADING A WFS LAYER 11 | 12 | The QGIS documentation also provides an [excellent walk-through](https://docs.qgis.org/latest/en/docs/training_manual/online_resources/wfs.html) on how to load a WFS layer. These instructions are adapted from the QGIS docs with additional details on the DataBC services. 13 | 14 | 1. Open QGIS and create a new project. 15 | 2. Open ![Data Source Manager icon](images/wms_wfs_getting_started/qgis_data_source_mgr.png) Data Source Manager > ![WFS icon](images/wms_wfs_getting_started/qgis_wfs_icon.png) **WFS/OGC API-Features** tab. 16 | 3. Create a **New** connection. 17 | 4. Provide a **name** like `DataBC Layers` and set the **URL** to `https://openmaps.gov.bc.ca/geo/ows?SERVICE=WFS&REQUEST=GetCapabilities`, and under WFS Options set **Version** to `2.0`. 18 | ![New WFS connection dialogue in QGIS](images/wms_wfs_getting_started/qgis_new_wfs_connection.png) 19 | 5. Click **OK**. 20 | 6. Click **Connect** and allow a moment for the layers to load. You should see: 21 | ![WFS layer list](images/wms_wfs_getting_started/qgis_wms_connection.png) 22 | 7. Use the **search** bar to find a dataset of interest. For this tutorial we will add `BC Research Centres`. Find this layer and click on it. 23 | ![Settings to add the BC Research Centres layer](images/wms_wfs_getting_started/qgis_wfs_research_add.png) 24 | 8. Turn on **Use title for layer name** - this will show the plain-language dataset title instead of the BC Geographic Warehouse table name in the layer list. 25 | 9. Turn off **Only request features overlapping the view extent** - we want to retrieve all features across the province. 26 | 27 | {: .highlight-title} 28 | > ⚠ Loading large datasets 29 | > 30 | > There is a hard limit on the maximum number of features the DataBC servers will return (10 000 at time of writing). Even when not hitting the feature limit, large and complex requests will often take too long to load, time out, and give a `Connection closed` error in QGIS. 31 | > 32 | > To avoid incomplete data loads, it is often best to turn on **Only request features overlapping the view extent** and zoom to your area of interest before adding the layer. Toggling off **Render** can provide a smoother map navigation experience, or you may choose to use **Extract/clip by extent** to save loaded features locally. 33 | > 34 | > Occasionally it is necessary to reload features in the visible extent using ![Refresh icon](imamges/../images/wms_wfs_getting_started/qgis_refresh.png) refresh (F5). 35 | > 36 | > Comparing against the WMS layer for the same dataset can provide a good cross-reference to visually confirm all features have been loaded. 37 | 38 | 10. Click **Add** to load the layer. 39 | 11. **Close** the Data Source Manager window. 40 | 12. Right click the new layer and click **Zoom to Layer(s)**. 41 | ![WFS data shown on map](images/wms_wfs_getting_started/qgis_wfs_research_view.png) 42 | 13. Explore the data - zoom in, pan around, and try selecting features. 43 | 14. Right click the layer in the **Layers** panel and click **Open Attribute Table** (F6). As a feature service (rather than a map service like WMS), it is possible to see attribute data, select features, and perform geoprocessing. 44 | ![Attribute table for research centres](images/wms_wfs_getting_started/qgis_wfs_research_attributes.png) 45 | 46 | {: .note-title} 47 | > Viewing the attribute table 48 | > 49 | > The normal **Open Attribute Table** function will try and load all features (even if the displayed layer is only requesting features by view extent) which is problematic for large datasets and can lead to failed requests or crashes. Instead, use **Open Attribute Table (visible only)**, available from the Layer menu up top, or via CTRL+F6. The selection only option (SHIFT+F6) is also helpful. 50 | 51 | 15. WFS allows for custom layer styling. Change the styling from `Single Symbol` to `Categorized` based on value `RESEARCH_CENTRE_AFFILIATION`, then click classify. 52 | ![Research centres symbolized by affiliation](images/wms_wfs_getting_started/qgis_wfs_research_categorized.png) 53 | 54 | 16. Similarly, we can add labels. 55 | ![Research centres with labels added](images/wms_wfs_getting_started/qgis_wfs_research_labels.png) 56 | 57 | 17. We can filter the data we request from the WFS service to improve load times and reduce traffic. In the **Data Source Manager**, select the `BC Research Centres` layer, then click **Build query** at the bottom. Modify the query to `SELECT * FROM "WHSE_IMAGERY_AND_BASE_MAPS.GSR_RESEARCH_CENTRES_SVW" WHERE "RESEARCH_CENTRE_AFFILIATION" = 'University'`. 58 | 59 | 18. Click **OK** and then **Add** the layer. A filter symbol will show next to the layer name showing the dataset is being filtered. The query can be modified from layer Properties > Source > **Query Builder**. 60 | 61 | {: .highlight-title} 62 | > ⚠ Duplicate features 63 | > 64 | > For unclear reasons, QGIS can sometimes load duplicate features from the DataBC WFS services. To avoid this issue we can add a simple SQL filter to get unique features: 65 | > 66 | > `SELECT DISTINCT * FROM ""` 67 | 68 | ----------------------- 69 | 70 | [RETURN TO TOP][1] 71 | 72 | [1]: #top 73 | -------------------------------------------------------------------------------- /pages/dsg_bcdc_metadata_standards.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Metadata Best Practices 4 | nav_order: 101 5 | parent: Appendix - Common Items 6 | has_toc: false 7 | --- 8 | 9 | # Metadata Best Practices 10 | 11 | This page describes recommended metadata best practices and provides a high-level summary of metadata requirements for data objects when publishing data to the BC Data Catalogue. To learn more about The Core Administrative and Descriptive Metadata Standards and Guidelines, please visit [Learn more about the metadata standard](https://www2.gov.bc.ca/gov/content?id=F528E060681144BBBB83246ECB238823). 12 | 13 | |**AUDIENCE**| | | | 14 | |:---:|:---:|:---:|:---:| 15 | | *Data Publishers* | *Metadata Editors* | *DataBC Data Modellers* | *DataBC Catalogue Team* | 16 | 17 | ## Table of Contents 18 | + [**What is Metadata and Why is it Important?**](#what-is-metadata-and-why-is-it-important) 19 | + [Benefits of Metadata](#benefits-of-metadata) 20 | + [Metadata should be:](#metadata-should-be) 21 | + [**Mandatory Metadata for The BC Data Catalogue**](#mandatory-metadata-for-the-bc-data-catalogue) 22 | + [**Mandatory Metadata for BC Geographic Warehouse Resources**](#mandatory-metadata-for-bc-geographic-warehouse-resources) 23 | + [**Mandatory Metadata for Resources Not in The BC Geographic Warehouse**](#mandatory-metadata-for-resources-not-in-the-bc-geographic-warehouse) 24 | + [**Resources**](#resources) 25 | 26 | ----------------------- 27 | 28 | ## What is Metadata and Why is it Important? 29 | 30 | **Definition**: [_Metadata_](glossary.md#metadata) 31 | 32 | Metadata is data (or information) which describes some aspect of data. Everything from database table descriptions, data relationship mapping, storing who created/updated data, purpose of the data, can be classified as metadata. 33 | 34 | ### Benefits of Metadata 35 | 36 | In the DataBC Program, we value the importance of using metadata to describe the data we serve and we strongly encourage activities that support and create valuable metadata documentation. 37 | 38 | + Provides business context and helps bring an understanding to the data 39 | + Facilitates data re-use and sharing 40 | + Defines data structure (i.e.: data flow, data relationships, data dependencies) 41 | + Enables historical data tracking (i.e.: audit columns) 42 | + Facilitates data design discussions 43 | + Provides data consistency 44 | + Supports user self-service to understand the purpose and characteristics of a data set 45 | + Can be used to help troubleshoot data issues; i.e. 46 | + who is the data custodian / person responsible for the data? 47 | + what is the security classification? 48 | + will the change impact other data? 49 | 50 | There are international standards for metadata that DataBC follows. This provides interoperability with other data service utilities, meaning that descriptions of your data can be widely published and accessed (assuming your security profile allows this). 51 | 52 | ### Metadata should be: 53 | 54 | + Easy to access and understand for consumers within and outside the organization. 55 | + Produced throughout the application development life cycle. 56 | + Of high quality, and managed effectively. 57 | + Open to improvement, and have a feedback mechanism by which consumers can inform the custodian of incorrect or out of date metadata. 58 | 59 | --------------- 60 | 61 | ## Mandatory Metadata for The BC Data Catalogue 62 | 63 | Metadata fields that are mandatory in the catalogue are identied 64 | 65 | 1. From the User Interface (UI) 66 | + As an asterisk (\*). 67 | + Refer to the UI [Record](dps_bcdc_w_record_mgmt_ui.md) and [Resource](dps_bcdc_w_resource_mgmt_ui.md) Management pages for more details. 68 | 1. From the API 69 | + See the link to the JSON Schema listed in the _Resources_ section of the API [Record](dps_bcdc_api_w_record_mgmt.md) or [Resource](dps_bcdc_api_w_resource_mgmt.md) Management pages. 70 | 71 | --------- 72 | 73 | ## Mandatory Metadata for BC Geographic Warehouse Resources 74 | 75 | Table and column descriptions are required for all objects in the BC Geographic Warehouse. These descriptions are created by the BCGW data modeller, in consultation with the custodian and DataBC data administration staff. The medium for defining the descriptions is the [Dataset Model](dps_bcgw_w.md#dataset-model). 76 | 77 | ## Mandatory Metadata for Resources Not in The BC Geographic Warehouse 78 | 79 | Spreadsheets (Excel or CSV files) uploaded to the BC Data Catalogue must be documented sufficiently so that people looking at the spreadsheet can understand what the columns mean. A good way of providing this information is to supply a *data dictionary* resource, explaining the purpose and content of the other resources. See for example, a [_data dictionary_](https://catalogue.data.gov.bc.ca/dataset/bc-data-catalogue-content/resource/824f2a99-d738-4b63-a492-a906d4c37be0) for the [_BC Data Catalogue Content_](https://catalogue.data.gov.bc.ca/dataset/42f7ca99-e7f3-40f7-93d7-f2500cccc315). 80 | 81 | ----------------------------------------------------------- 82 | 83 | ## RESOURCES 84 | 85 | The following links will provide you with additional information regarding metadata standards: 86 | 87 | + [_British Columbia Core Administrative and Descriptive Metadata Standard_](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/311_core_metadata_standard.pdf) 88 | 89 | + [_Dublin Core Metadata Initiative_](https://www.dublincore.org/specifications/dublin-core/dcmi-terms/) 90 | 91 | + [_North American Profile of ISO 19115:2003_](https://webstore.ansi.org/Standards/INCITS/INCITS4532009) 92 | 93 | ----------------------------------------------------------- 94 | 95 | [RETURN TO TOP][1] 96 | 97 | [1]: #metadata-standards 98 | -------------------------------------------------------------------------------- /pages/dps_bcdc_classic_w_api_metadata_mgmt.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: API Management 4 | nav_order: 391 5 | parent: Publication Workflow - Classic 6 | grand_parent: BC Data Catalogue 7 | nav_exclude: true 8 | has_toc: false 9 | --- 10 | 11 | # USING THE BC DATA CATALOGUE API FOR METADATA MANAGEMENT 12 | 13 | The BC Data Catalogue is built using an open source data portal software called [CKAN](https://github.com/ckan/ckan/blob/master/README.rst). Some users may prefer to use the API to manage thier content in the BC Data Catalogue, while others may prefer to use the applicaiton itself. This page provides guidance on the use of the Catalogue API to manage metadata and data within the BC Data Catalogue. 14 | 15 | |**AUDIENCE**| 16 | |:---:| 17 | | *Metadata Editors* | 18 | 19 | ## Table of Contents 20 | + [**ARCHITECTURE**](#architecture) 21 | + [**HOW TO MANAGE METADATA RECORDS AND RESOURCES USING THE CATALOGUE API**](#how-to-manage-metadata-records-and-resources-using-the-catalogue-api) 22 | + [How to create a resource with the API](#how-to-create-a-resource-with-the-api) 23 | + [How to update a resource with the API](#how-to-update-a-resource-with-the-api) 24 | + [How to get the organization ID with the organization name](#how-to-get-the-organization-id-with-the-organization-name) 25 | + [How to get package names and package IDs within an organization](#how-to-get-package-names-and-package-ids-within-an-organization) 26 | + [How to get the resource names and resource IDs withing a package](#how-to-get-the-resource-names-and-resource-ids-withing-a-package) 27 | 28 | ----------------------- 29 | 30 | ## ARCHITECTURE 31 | 32 | The base product on which BCDC is dependent is https://github.com/ckan/ckan - it is an open source application that uses extensions in a plug-in architecture to extend and customize it. 33 | 34 | Our main customization is done through a theme extension that we manage https://github.com/bcgov/ckanext-bcgov. 35 | 36 | The application is supported by technical infrastructure and that has a number of integrations with other systems through a combination of database and API level connections. 37 | 38 | ## HOW TO MANAGE METADATA RECORDS AND RESOURCES USING THE CATALOGUE API 39 | 40 | To use the Catalogue API to manage and create metadata records one must be an editor/publisher. Review [How to Become a Provider to the Catalogue](dps_bcdc_w.md#HOW-TO-BECOME-A-PROVIDER-TO-THE-CATALOGUE) for more information. 41 | 42 | **Name of the org:** 43 | 44 | To obtain the GUID sub-org it requires the title name of the org 45 | 46 | 1. **Option 1**: 47 | 1. Navigate to a record you manage 48 | 1. Click on the live link of the sub-org or branch name 49 | 1. Copy the text in the url, e.g, "information-management-cfd" from https://catalogue.data.gov.bc.ca/organization/information-management-cfd 50 | 1. **Option 2**: 51 | 1. Open up the Catalogue Organizations tree 52 | 1. Navigate and click on the sub-org/branch name 53 | 1. Copy the text in the url, e.g, "information-management-cfd" from https://catalogue.data.gov.bc.ca/organization/information-management-cfd 54 | 55 | **Your API Key**: 56 | 1. Log into the Catalogue 57 | 1. Click on your name in the upper right 58 | 1. Bottom left corner is your personal API Key 59 | 60 | The following python syntax is used as an example from a specific organization 61 | 62 | ### How to create a resource with the API 63 | ``` 64 | import ckanapi 65 | 66 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 67 | 68 | resp = ckan.action.resource_create( 69 | package_id='YOUR-PACKAGE-ID-HERE', 70 | upload=open('/Users/Documents/test_resource_csv_upload.csv'), 71 | resource_storage_location="Catalogue Data Store", 72 | name="my-resource-name", 73 | edc_resource_type="Data", 74 | format="csv", 75 | resource_update_cycle="monthly", 76 | resource_storage_access_method="Direct Access") 77 | 78 | 79 | print(resp) 80 | ``` 81 | ### How to update a resource with the API 82 | ``` 83 | import ckanapi 84 | 85 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 86 | 87 | resp = ckan.action.resource_update( 88 | id='RESOURCE-ID-TO-UPDATE-HERE', 89 | upload=open('/Users/Documents/test_resource_csv_upload.csv'), 90 | resource_storage_location="Catalogue Data Store", 91 | name="my-resource-name-updated", 92 | edc_resource_type="Data", 93 | format="csv", 94 | resource_update_cycle="monthly", 95 | resource_storage_access_method="Direct Access") 96 | 97 | 98 | print(resp) 99 | ``` 100 | 101 | ### How to get the organization ID with the organization name 102 | ``` 103 | import ckanapi 104 | 105 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 106 | 107 | org = ckan.action.organization_show(id="information-management-cfd") 108 | print(org['name'], org['id']) 109 | ``` 110 | 111 | ### How to get package names and package IDs within an organization 112 | ``` 113 | import ckanapi 114 | 115 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 116 | 117 | pkgs = ckan.action.package_search(fq="owner_org:a1a9c5cc-b601-4190-b206-13ba08c54292",rows=1000) 118 | for pkg in pkgs['results']: 119 | print(pkg['name'], pkg['id']) 120 | 121 | ``` 122 | 123 | ### How to get the resource names and resource IDs withing a package 124 | ``` 125 | import ckanapi 126 | 127 | ckan = ckanapi.RemoteCKAN('https://catalogue.data.gov.bc.ca', apikey='YOUR-APIKEY-HERE') 128 | 129 | pkg_data = ckan.action.package_show(id="b67255a7-8040-43c0-935c-d74f168af215") 130 | for resource in pkg_data['resources']: 131 | print(resource['name'], resource['id']) 132 | ``` 133 | 134 | ------------------------------------------------------- 135 | 136 | [RETURN TO TOP][1] 137 | 138 | [1]: #using-the-bc-data-catalogue-api-for-metadata-management 139 | -------------------------------------------------------------------------------- /pages/we_value_your_contributions.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Provide Feedback 4 | nav_order: 14 5 | has_toc: false 6 | --- 7 | 8 | # WE VALUE YOUR CONTRIBUTIONS 9 | 10 | Our goal in publishing these documents was to create a complete, clear, and correct repository of guides to help DataBC Program contributors and consumers. We welcome your contributions! 11 | 12 | This page describes two mechanisms for providing input on the documentation published on this site: 13 | + reporting errors in the documentation, and 14 | + suggesting additions to existing pages or 15 | + the addition of new pages. 16 | 17 | ----------------------- 18 | 19 | ## Table of Contents 20 | + [**REPORTING ISSUES WITH THE DOCUMENTATION**](#reporting-issues-with-the-documentation) 21 | + [**CHANGING PAGES OR ADDING NEW ONES**](#changing-pages-or-adding-new-ones) 22 | + [How to Access GitHub](#how-to-access-github) 23 | + [How to Download a Git Client](#how-to-download-a-git-client) 24 | + [How to Clone the bcgov/data-publication Repository](#how-to-clone-the-bcgovdata-publication-repository) 25 | + [How to Pull down a Repository to a File System](#how-to-pull-down-a-repository-to-a-file-system) 26 | + [How to Create or Change Pages](#how-to-create-or-change-pages) 27 | + [How to Push to GitHub](#how-to-push-to-github) 28 | + [How to Issue a Pull Request](#how-to-issue-a-pull-request) 29 | 30 | ----------------------- 31 | 32 | ## REPORTING ISSUES WITH THE DOCUMENTATION 33 | 34 | If you would like to point out an error or make a comment on the content, this can most easily be done by creating an issue: 35 | 1. Click the ![Issues](images/image_issues.png) tab. 36 | 1. Click the ![New issue](images/image_new_issue.png) button. 37 | 1. Enter a **Title** that is brief to describe the issue. 38 | 1. Enter a **Description** of the issue and what URL it is on. 39 | 1. Click the ![Submit new issue](images/image_submit_new_issue.png) button. 40 | 41 | ----------------------------------------------------------- 42 | 43 | ## CHANGING PAGES OR ADDING NEW ONES 44 | 45 | You can add new pages or replace existing ones by going through the process outlined in the following sections. 46 | 47 | ### How to Access GitHub 48 | 49 | You will need a user id for https://github.com. You can get one by going to that website and clicking on the "Sign up for GitHub" button. 50 | 51 | For BC Government employees read the [BC Policy Framework For GitHub](https://github.com/bcgov/BC-Policy-Framework-For-GitHub). 52 | 53 | ### How to Download a Git Client 54 | 55 | Download a git client from https://git-scm.com/download. You will use the "git" command to do most of your work 56 | 57 | ### How to Clone the bcgov/data-publication Repository 58 | 59 | 1. Log into github.com and navigate to [https://github.com/data-publication](https://github.com/bcgov/data-publication) 60 | 1. Click the ![Fork](images/image_fork.png) button in the upper right. 61 | 1. A pop-up may appears with the question **Where should we fork data-publication**, click on your userid. 62 | 63 | A copy of the data-publication will now be in your repository, e.g., _userid/data-publication_ 64 | 65 | ### How to Pull down a Repository to a File System 66 | 67 | 1. Copy the repo URL to your clipboard: 68 | 1. Click the ![Code](images/image_code.png) button. 69 | 1. Click the clipboard image ![clipboard_image](images/image_copy_url.png) as this copies the URL listed beside it 70 | 1. On your workstation, create a new directory to store and modify the repository files. 71 | 1. Either using a program of your choice or open a DOS/PowerShell to that directory. 72 | 1. Enter the command to create a `data-publication` subdirectory: 73 | ``` 74 | git clone 75 | ``` 76 | 1. Enter the following commands to move to and sync content from the master repository: 77 | ``` 78 | cd data-publication 79 | git remote add --track master upstream git://github.com/bcgov/data-publication.git 80 | git fetch upstream 81 | git merge upstream/master 82 | ``` 83 | If both are in sync the follow message will display "Already up to date". 84 | 85 | ### How to Create or Change Pages 86 | 87 | 1. Fork the repository as described above. 88 | 2. If any significant time has passed since you downloaded the files in the last section, you should make sure that your copy of the repository is up to date with the contents of the master bcgov/data-publication repository. 89 | 90 | To do this, issue the following to commands: 91 | ``` 92 | git fetch upstream 93 | git merge upstream/master 94 | ``` 95 | 96 | 1. Using a text editor make changes to the markdown (.md) files, add new markdown files, etc. 97 | 1. Any images should be stored in the images subdirectory. 98 | 99 | ### How to Push to GitHub 100 | 101 | Your changes, additions, etc. on your local filesystem copy now have to be transferred up to your fork on GitHub. Do this by executing the following commands: 102 | 103 | ``` 104 | git add -A 105 | git commit -m "briefDescriptionOfTheChanges" 106 | git push 107 | ``` 108 | 109 | ### How to Issue a Pull Request 110 | 111 | 1. Open or refresh your repository in a browser. 112 | 1. There will be a note saying your _This branch is X commits ahead of bcgov:master_. 113 | 1. Click the ![Pull request](images/image_pullrequest.png) button beside this. 114 | 1. This page will show the change comparison. 115 | 1. Click the ![Create pull request](images/image_create_pull_request.png) button. 116 | 1. Enter a **Title** that is brief to describe the changes. 117 | 1. Enter a **Description** of the changes made. 118 | 1. Click the final ![Create pull request](images/image_create_pull_request2.png) button. 119 | 120 | DataBC will review and either incorporate your changes or contact you if there is a reason the changes cannot be incorporated. 121 | 122 | ------------------------------------------------------- 123 | 124 | [RETURN TO TOP][1] 125 | 126 | [1]: #we-value-your-contributions 127 | -------------------------------------------------------------------------------- /pages/dps_bcdc_classic_w_webservice_api.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Web Service - API 4 | nav_order: 396 5 | parent: Publication Workflow - Classic 6 | grand_parent: BC Data Catalogue 7 | nav_exclude: true 8 | has_toc: false 9 | --- 10 | 11 | ## PUBLISHING A WEB SERVICE - API TO THE BC DATA CATALOGUE 12 | 13 | ### Create Dataset 14 | 15 | **State**: When creating a new metadata record, the state will be set to DRAFT. 16 | 17 | **Title**: This is the title of your metadata record. 18 | 19 | **URL**: This is automatically generated once the title is filled in. 20 | 21 | **Organization**: This is the Ministry or Organization under which the metadata record is created. 22 | 23 | **Sub-Organization**: This is the Sub-Organization (often the Branch or Division) under which the metadata record is created. 24 | 25 | **Description**: Provide a meaningful description of the Web Service - API here. Be sure to include any information that would be relevant to an end-user of your Web Service - API. 26 | 27 | **More info**: Any pertinent information can be added here. Often this is used to provide links to related web sites. 28 | 29 | **Keywords**: Enter meaningful keywords here. Think of what users may use for search terms to find the Web Service - API in the Catalogue. 30 | 31 | --------------- 32 | 33 | ### **Contacts** 34 | 35 | Add contacts for the following **Roles**: 36 | 1. [Custodian](./glossary.md/#custodian) (required) 37 | 1. [Point of Contact](./glossary.md/#point_of_contact) (required) 38 | 1. [Business Expert](./glossary.md/#business_expert) (optional) 39 | 1. [Distributor](./glossary.md/#distributor) (optional) 40 | 41 | **Name**: Contact full name 42 | 43 | **Email**: Contact email address 44 | 45 | **Organization**: Contact organization 46 | 47 | **Sub-Organization**: Contact Sub-Organization 48 | 49 | **Role**: Contact role type (as per the list above) 50 | 51 | **Contact Displayed**: Check this box to display the contact to all catalogue users (public access). Unchecked, this contact information will only be visible to Catalogue Admin's. 52 | 53 | --------------- 54 | 55 | ### **Data Currency/Update** 56 | 57 | **Resource Status** is the status of the Web Service - API as described by one of the types below: 58 | 59 | |Data Update Status| Description 60 | |:---|:---| 61 | |Ongoing|Web Service - API's that are regularly updated should be described as ongoing.| 62 | |Completed|Web Service - API's with no plan for future updates should be described as completed. 63 | |Destroyed|Web Service - API's that no longer exist should be described as destroyed.| 64 | |Historical Archive|Web Service - API's that exist, but have been archived (can also be desribed as no longer relevant) should be described as historical archive. 65 | |Obsolete|Web Service - API's that that have been replaced with another Web Service - API should be described as destroyed. 66 | |Planned|Web Service - API's that do not currently exist, but are planned for the future, should be described as planned. 67 | |Required| 68 | |Under development|Web Service - API's that exist but are not yet completed should be described as under development. 69 | 70 | --------------- 71 | 72 | ### **Access & Security** 73 | 74 | **Who can access this application?** desribes the security level for access to the application. 75 | 76 | |Access Type| Description 77 | |:---|:---| 78 | |Public| All users are able to access the application. 79 | |Named Users| Only specific named users can access the application. 80 | |Government and Business BCeID| Only people with government and BCeID credentials can access the application. 81 | |Government| Only government credentials can access the application. 82 | 83 | ------------------------------ 84 | 85 | **Who can view this record?** describes who can view the metadata record. 86 | 87 | |Access Type| Description 88 | |:---|:---| 89 | |Public | All users of the catalogue can view the metadata record. 90 | |IDIR | Only IDIR credentials can view the metadata record. 91 | 92 | ------------------------------ 93 | 94 | **Security Classification** 95 | 96 | |BCDC Security Classication| [Information Security Classification Levels](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/information_security_classification_standard_july_17_2018.pdf)| Description 97 | |:---|:---|:---| 98 | |High - Cabinet, High - Confidential, High - Sensitivity|Protected C | Confidential. Extremely grave harm to an individual, organization or government. Examples: Information about police agents and other informants, Cabinet records or Cabinet-related records 99 | |Medium - Personal, Medium - Sensitivity|Protected B | Confidential. Serious harm to an individual, organization or government. Examples: Law enforcement and medical records, personnel evaluations and investigations, financial records, information subject to solicitor-client privilege or other legal privilege 100 | |Low - Sensitivity|Protected A | Confidential. Harm to an individual, organization or government. Examples: Home addresses, dates of birth, other low-risk personal information 101 | |Low - Public|Public|No harm to an individual, organization or government. Examples: Job postings, communications to claim clerks, business contact information, research and background papers (without copyright restrictions) 102 | 103 | ------------------------------ 104 | 105 | ***NEXT: ADD DATA*** 106 | 107 | ------------------------------ 108 | 109 | ### Add Data 110 | 111 | **File**: Either upload a file that will be stored in the Catalogue Data Store, or use a link (URL) to your application. 112 | + Upload File: Select this to upload a resource to the Catalogue Data Store. 113 | 114 | + Link: Enter the URL of your application here. 115 | 116 | **Resource Name** is the name of the resource as it will appear on the metadata record. 117 | 118 | Click **Finished** when complete. This will save your metadata record for the application in DRAFT status. 119 | 120 | ------------------------------ 121 | 122 | [RETURN TO TOP][1] 123 | 124 | [1]: #publishing-a-web-service---api-to-the-bc-data-catalogue 125 | -------------------------------------------------------------------------------- /pages/dps_bcdc_classic_w_application.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Application 4 | nav_order: 392 5 | parent: Publication Workflow - Classic 6 | grand_parent: BC Data Catalogue 7 | nav_exclude: true 8 | has_toc: false 9 | --- 10 | 11 | ## PUBLISHING AN APPLICATION TO THE BC DATA CATALOGUE 12 | 13 | ### Create Dataset 14 | 15 | **State**: When creating a new metadata record, the state will be set to DRAFT. 16 | 17 | **Title**: This is the title of your metadata record. 18 | 19 | **URL**: This is automatically generated once the title is filled in. 20 | 21 | **Organization**: This is the higher level organization responsible for the items described in the metadata. 22 | 23 | **Sub-Organization**: This is the custodial organization (often the Branch or Division) responsible for data or items. 24 | 25 | **Description**: Provide a meaningful description of the application here. Be sure to include any information that would be relevant to an end-user of your application. 26 | 27 | **More info**: Provide links to related web pages. 28 | 29 | **Keywords**: Enter meaningful keywords here. Think of what users may use for search terms to find the application in the Catalogue. 30 | 31 | --------------- 32 | 33 | ### **Contacts** 34 | 35 | Add contacts for the following **Roles**: 36 | 1. [Custodian](./glossary.md/#custodian) (required) 37 | 1. [Point of Contact](./glossary.md/#point_of_contact) (required) 38 | 1. [Business Expert](./glossary.md/#business_expert) (optional) 39 | 1. [Distributor](./glossary.md/#distributor) (optional) 40 | 41 | **Name**: Contact full name 42 | 43 | **Email**: Contact email address 44 | 45 | **Organization**: Contact organization 46 | 47 | **Sub-Organization**: Contact Sub-Organization 48 | 49 | **Role**: Contact role type (as per the list above) 50 | 51 | **Contact Displayed**: Check this box to display the contact to all catalogue users (public access). Unchecked, this contact information will only be visible to Catalogue Admin's. 52 | 53 | --------------- 54 | 55 | ### **Data Currency/Update** 56 | 57 | **Resource Status** is the status of the application as described by one of the types below: 58 | 59 | |Data Update Status| Description 60 | |:---|:---| 61 | |Ongoing|Applications that are regularly updated should be described as ongoing.| 62 | |Completed|Applications with no plan for future updates should be described as completed. 63 | |Destroyed|Applications that no longer exist should be described as destroyed.| 64 | |Historical Archive|Applications that exist, but have been archived (can also be desribed as no longer relevant) should be described as historical archive. 65 | |Obsolete|Applications that that have been replaced with another application should be described as destroyed. 66 | |Planned|Applications that do not currently exist, but are planned for the future, should be described as planned. 67 | |Required| 68 | |Under development|Applications that exist but are not yet completed should be described as under development. 69 | 70 | --------------- 71 | 72 | ### **Access & Security** 73 | 74 | **Who can access this application?** desribes the security level for access to the application. 75 | 76 | |Access Type| Description 77 | |:---|:---| 78 | |Public| All users are able to access the application. 79 | |Named Users| Only specific named users can access the application. 80 | |Government and Business BCeID| Only people with government and BCeID credentials can access the application. 81 | |Government| Only government credentials can access the application. 82 | 83 | ------------------------------ 84 | 85 | **Who can view this record?** describes who can view the metadata record. 86 | 87 | |Access Type| Description 88 | |:---|:---| 89 | |Public | All users of the catalogue can view the metadata record. 90 | |IDIR | Only IDIR credentials can view the metadata record. 91 | 92 | ------------------------------ 93 | 94 | **Security Classification** 95 | 96 | |BCDC Security Classication| [Information Security Classification Levels](https://www2.gov.bc.ca/assets/gov/government/services-for-government-and-broader-public-sector/information-technology-services/standards-files/information_security_classification_standard_july_17_2018.pdf)| Description 97 | |:---|:---|:---| 98 | |High - Cabinet, High - Confidential, High - Sensitivity|Protected C | Confidential. Extremely grave harm to an individual, organization or government. Examples: Information about police agents and other informants, Cabinet records or Cabinet-related records 99 | |Medium - Personal, Medium - Sensitivity|Protected B | Confidential. Serious harm to an individual, organization or government. Examples: Law enforcement and medical records, personnel evaluations and investigations, financial records, information subject to solicitor-client privilege or other legal privilege 100 | |Low - Sensitivity|Protected A | Confidential. Harm to an individual, organization or government. Examples: Home addresses, dates of birth, other low-risk personal information 101 | |Low - Public|Public|No harm to an individual, organization or government. Examples: Job postings, communications to claim clerks, business contact information, research and background papers (without copyright restrictions) 102 | 103 | ------------------------------ 104 | 105 | ***NEXT: ADD DATA*** 106 | 107 | ------------------------------ 108 | 109 | ### Add Data 110 | 111 | **File**: Either upload a file that will be stored in the Catalogue Data Store, or use a link (URL) to your application. 112 | + Upload File: Select this to upload supporting resources only to the Catalogue Data Store. 113 | 114 | + Link: Enter the URL of your application here. 115 | 116 | **Resource Name** is the name of the resource as it will appear on the metadata record. 117 | STANDARD FILE NAMING 118 | It is suggested to use a standard file name as it would appear in your file system and describe the resource using the other available fields. 119 | 120 | Click **Finished** when complete. This will save your metadata record for the application in DRAFT status. 121 | 122 | ------------------------------ 123 | 124 | [RETURN TO TOP][1] 125 | 126 | [1]: #publishing-an-application-to-the-bc-data-catalogue 127 | -------------------------------------------------------------------------------- /pages/dsg_bcgw_data_classification_hierarchy.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Data Classification Hierarchy 4 | parent: BC Geographic Warehouse 5 | has_toc: false 6 | --- 7 | 8 | # DATA CLASSIFICATION HIERARCHY 9 | 10 | Data that is stored in the BC Geographic Warehouse is classified into like groupings (known as schemas). These groupings are are also used for layerfile presenations in iMapBC and the Layerfile Library. This page describes the data classification hierarchy and definitions. 11 | 12 | |**AUDIENCE**| | | | 13 | |:---:|:---:|:---:|:---:| 14 | | *Data Publishers* | *BCGW Users* | *iMapBC Users* | *ArcGIS Users* | 15 | 16 | ## CATEGORY LEVEL DEFINITIONS 17 | 18 | |**Category Name**|**Sub-Category Name**|**Definition**| 19 | |:---:|:---:|:---| 20 | |**Legal Information and Administrative Boundaries**| |Data which represents ownership, the right to carry on an activity or the right to access/use specified areas, or the conceptual data representing jurisdiction or responsibility for a specified area.| 21 | | | _Administrative Boundaries_|Data relating subdivisions of the province for organizational reasons and used for administration purposes by one or more organizations. e.g.: districts, regions, parks, etc.| 22 | | |_Land Ownership and Status_|Data relating to the ownership of land and the parcels into which the land has been subdivided. Includes the location and extent of registered titles, easements and utility rights-of-way, and surveyed highways and forest roads.| 23 | | |_Licences and Permits_|Data relating to the right to access or use land for a specified purpose.| 24 | |**Imagery and Base Maps** ||Data which aids in the locating of natural and man-made features and that provides the required level of coverage in support of the development and management of land-related information.| 25 | | |_Imagery_|Data related to a picture of the earth taken at some particular range within the electromagnetic spectrum (i.e. visible light, IR, etc.) from an earth-orbital satellite or air-craft.| 26 | | |_Geographical Names_|Data relating to the official names associated with specific features in the Province.| 27 | | |_Base Maps_|Data containing geographic features used for locational reference.| 28 | | |_Geodetic Survey_|Data relating to the geospatial reference used for positioning within the Province. The term geodetic meaning: concerned with the precise location (latitude, longitude, height) of points and figures on the earth's surface.| 29 | | |_Physical Infrastructure_|Data about human-made physical structures, which support economic and social activities. e.g.: utilities; communication; transportation; buildings.| 30 | ||_Transportation_|Data relating to networks used for the purposes of transportation. Transportation includes water, air, rail and road.| 31 | |**Land and Natural Resources Information**||Data about the physical, atmospheric, hydrological and biological components of the environment and the methodology used to gather those data| 32 | | |_Air and Climate_|Data relating to patterns of wind, temperature, precipitation, etc., over a period of time, for a specified area.| 33 | | |_Fish, Wildlife and Plant Species_|Data relating to the inventory of fish, wildlife, and/or plant species (including species at risk), and the quantity and quality of a species habitat.| 34 | | |_Fresh Water and Marine_|Data related to the management, inventory and classification of water resources.| 35 | | |_Forests_, _Grasslands_ _and_ _Wetlands_|Data related to the inventory and classification of vegetation information into identifiable systems of biotic and abiotic components, including sensitive ecosystems and natural plant communities at-risk.| 36 | | |_Geology and Soils_|Data relating to the structure and composition of the earth, its physical and organic history, especially as evidenced by rocks and rock information as well as data relating to the naturally occurring, unconsolidated mineral or organic material at least 10 cm thick that occurs at the earth's surface and is capable of supporting plant growth.| 37 | |**Human, Cultural & Economic Activities**||Data relating to monitoring and managing the impact of humans on the natural environment. e.g.: water quality, soil quality and air quality.| 38 | | |_Archaeology and Culture_|Data relating to the location/extent, planning, management, monitoring, and preservation of cultural heritage resource or areas of significance from prehistoric and historic times| 39 | | |_Agriculture_|Data relating to monitoring and managing the impact of humans resulting from cultivation of the land.| 40 | | |_Aquaculture_|Data relating to the harvesting and raising of aquatic plants and/or animals.| 41 | | |_Mining and Petroleum_|Data relating to the inventory, planning, management, and monitoring of the extraction and depletion of mineral, sand, gravel, coal and petroleum resources.| 42 | | |_Parks, Recreation and Tourism_|Data relating to the planning, management, monitoring or protection of resources used for the voluntary pursuit of leisure activities and tourism in areas used for recreational purposes.| 43 | | |_Waste_|Data relating to the management, collection, treatment, and disbursement of waste matter from commercial, residential or industrial establishments.| 44 | | |_Land Use Plans_|Data resource management direction as well as designation of resource management units for the purposes of Land Use Planning.| 45 | | |_Socio-Economic_|Data relating to people, economic activities, status of land use within a designated area. Includes taxation, assessment, land use, and demography. e.g. “Major Projects”| 46 | | |_Health_|Data relating to health: health services, human ecology, and safety. For example, resources describing human disease and illness, factors affecting health, hygiene, mental and physical health, substance abuse, and health services, including vital statistics.| 47 | | |_Education_|Data relating to schools, universities and colleges.| 48 | | |_Social Services_|Data relating to society: characteristics of societies and cultures. For example, resources describing natural settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, crime and justice, recreational areas and activities, social impact assessments, and census information.| 49 | | |_Justice and Emergency_|Data relating to crimes and the judiciary system as well as emergency management and the coroner’s service.| 50 | 51 | ---------------------------- 52 | -------------------------------------------------------------------------------- /pages/dsg_before_you_start.md: -------------------------------------------------------------------------------- 1 | --- 2 | layout: default 3 | title: Before You Start 4 | nav_order: 2 5 | has_toc: false 6 | --- 7 | 8 | # BEFORE YOU START 9 | 10 | -------------- 11 | 12 | Do you have a dataset that you'd like to publish through the [_DataBC Program_](https://data.gov.bc.ca/)? Before your data is published, we will need to gather some information from you. The questions on this page will help the [DataBC Data Architecture Services](faq.md#data-architecture-services) team learn about your requirements and to determine whether the DataBC Program can meet them. 13 | 14 | |**AUDIENCE**| 15 | |:---:| 16 | | *Data Publishers* | 17 | 18 | ----------------------- 19 | 20 | ## DATA PUBLICATION CHANNELS 21 | 22 | The DataBC Program makes data available through combinations of several different channels: 23 | 24 | + [_BC Data Catalogue_](https://catalogue.data.gov.bc.ca) 25 | + [_Data Distribution Services_](https://www2.gov.bc.ca/gov/content?id=B19E16070B824DB481F49CEE3B9AF1F8) through the BC Data Catalogue, iMapBC and (___coming soon___) the Order Fulfiller Interface (OFI) Application Programming Interface (API) 26 | + [_BC Geographic Warehouse_](https://www2.gov.bc.ca/gov/content?id=18B291A12B4F42EA98169892F4B46D61) 27 | + _Web based Mapping_ 28 | + [_BC Map Hub_](https://www2.gov.bc.ca/gov/content?id=DE0602BB42664AA28C9F059D45CC1CC2) 29 | + [_BC Map Services (WMS and WFS)_](https://www2.gov.bc.ca/gov/content?id=95D78D544B244F34B89223EF069DF74E) 30 | + [_iMapBC_](https://www2.gov.bc.ca/gov/content?id=C52F8C3BFE8C4110A63171337F363F43) 31 | 32 | In addition, other agencies provide mechanisms for accessing DataBC data: 33 | 34 | + the Geographic Terminal Servers (GTS - available through [dts.gov.bc.ca](https://dts.gov.bc.ca)) 35 | + [_BCData R package_](https://github.com/bcgov/bcdata) 36 | 37 | 38 | 39 | Hosting data in these products allows for access through these services and/or products 40 | **Under Construction** 41 | 42 | |Service | BC Data Catalogue| BC Geographic Warehouse | BC MapHub | 43 | |:---|:---:|:---:|:---:| 44 | |**Webmapping** - iMapBC|![](/images/grey_dash.png)|![](/images/green_check.png)|![](/images/grey_dash.png) 45 | |**Webmapping** - iMapBC - Secure|![](/images/grey_dash.png)|![](/images/green_check.png)|![](/images/grey_dash.png) 46 | |**Webmapping** - SMK|![](/images/grey_dash.png)|![](/images/green_check.png)|![](/images/grey_dash.png) 47 | |**Webmapping** - WMS|![](/images/green_check.png)| ![](/images/green_check.png)|![](/images/green_check.png)| 48 | |**Webmapping** - WFS| Not listed at this time |![](/images/green_check.png)| ![](/images/green_check.png) 49 | |**Webmapping** - BC MapHub| ![](/images/green_check.png)| ![](/images/green_check.png)| ![](/images/green_check.png) 50 | |**Direct connect** - GTS| ![](/images/green_check.png)| ![](/images/green_check.png)| ![](/images/green_check.png) 51 | |**Direct connect** - Layer library| ![](/images/grey_dash.png)| ![](/images/green_check.png)| ![](/images/grey_dash.png) 52 | |**Download service** - Data Catalogue| ![](/images/green_check.png)| ![](/images/green_check.png)| ![](/images/green_check.png) 53 | |**Download service** - iMapBC| ![](/images/green_check.png)| ![](/images/green_check.png)| ![](/images/grey_dash.png) 54 | |**BC Data Catalogue**| ![](/images/green_check.png)| ![](/images/green_check.png) 55 | 56 | There are five options for where data gets stored in the DataBC Program, each with its own benefits and drawbacks: 57 | 58 | | | BC Geographic Warehouse | BC Data Catalogue | BC MapHub | pub.data.gov.bc.ca | External site | 59 | |:---|:---:|:---:|:---:|:---:|:---:| 60 | **Security** - Public | ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/green_check.png)
through the public publication request form | ![](/images/green_check.png) | ![](/images/green_check.png) | 61 | **Security** - IDIR | ![](/images/green_check.png)
for metadata only | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 62 | **Security** - Named Users | ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 63 | **Security** - Role-based | ![](/images/green_check.png) | ![](/images/green_check.png)
in combination with Public, IDIR, Named Users | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 64 | **Security** - BCeID | ![](/images/grey_dash.png) | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 65 | **Format** | BCGW dataset (Oracle object), ArcGIS Rest, atom, cded, cvs, e00, fgdb, geojson, georss, gft, html, json, kml, kmz, openapi-json, pdf, rdf, shp, tsv, txt, wms, wmts, xls, xlsx, xml, zip, other | Oracle object (spatial and non-spatial) | WMS, WFS, Shapefile, CSV, TXT, GPX, GeoJSON | Any | Any 66 | **File Size** | | catalogue file store < 150 MB and datasets configured via Distribution Service: < 2 GB zipped | < 500 MB | > 150 MB | Any 67 | **Download** - entire dataset | ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/green_check.png)
for BCGW datasets: re-directed to the BC Data Catalogue
for standalone datasets: direct download | ![](/images/green_check.png) | ![](/images/green_check.png) 68 | **Download** - subset dataset | ![](/images/grey_dash.png) | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 69 | **Spatial data** - view in iMap BC | ![](/images/grey_dash.png) | ![](/images/green_check.png) | ![](/images/grey_na.png) | ![](/images/grey_na.png) | ![](/images/grey_na.png) 70 | **Spatial data** - view in desktop mapping applications (i.e. ArcGIS, QGIS) | ![](/images/green_check.png)
once downloaded | ![](/images/green_check.png) | ![](/images/green_check.png)
can open data in ArcGIS via BC MapHub | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 71 | **Spatial data** - view WMS (Web-Map Service) | ![](/images/green_check.png)
once downloaded | ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 72 | **Spatial data** - view WFS (Web Feature Service) | ![](/images/green_check.png)
once downloaded | ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 73 | **Spatial data** - view in BC MapHub | ![](/images/grey_dash.png) | ![](/images/green_check.png) | ![](/images/green_check.png) | ![](/images/grey_dash.png) | ![](/images/grey_dash.png) 74 | **Non-spatial data (csv)** - view preview | ![](/images/green_check.png) | ![](/images/grey_na.png) | ![](/images/grey_na.png) | ![](/images/grey_na.png) | ![](/images/grey_na.png) 75 | **Non-spatial data (csv)** - view point data on a map | ![](/images/green_check.png) | ![](/images/grey_na.png) | ![](/images/green_check.png) | ![](/images/grey_na.png) | ![](/images/grey_na.png) 76 | 77 | [RETURN TO TOP][1] 78 | 79 | [1]: #before-you-start 80 | -------------------------------------------------------------------------------- /pages/images/delivery_kit/gsr_whse/setup/gsr_whse.N.N.N.README: -------------------------------------------------------------------------------- 1 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2 | THIS IS A TEMPLATE - REPLACE ALL LINES WITH ~~~ IN THEM 3 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4 | 5 | DESCRIPTION 6 | =========== 7 | 8 | Purpose : This package provides BCGW objects for GSR_WHSE version ~~~N.N.N~~~ 9 | Release : ~~~GSR_WHSE.N.N.N~~~ 10 | Created : ~~~MONTH YEAR~~~ 11 | Author : ~~~WHO-AM-I (WHERE-I-WORK)~~~ 12 | 13 | OBJECTS CREATED/MODIFIED 14 | ======================== 15 | 16 | SPATIAL VIEWS 17 | ------------- 18 | 19 | ~~~WHSE_IMAGERY_AND_BASE_MAPS.VIEW_NAME_1_SV~~~ 20 | 21 | NON-SPATIAL VIEWS 22 | ----------------- 23 | 24 | ~~~WHSE_IMAGERY_AND_BASE_MAPS.VIEW_NAME_2_VW~~~ 25 | 26 | SOFTWARE/HARDWARE REQUIREMENTS 27 | ============================== 28 | 29 | Database: BCGW 30 | Oracle: ORACLE12C 31 | ArcSDE: 10.4.1 32 | 33 | THE FOLLOWING SCHEMA INFORMATION WAS PROVIDED BY DATABC PRIOR TO THIS DELIVERY 34 | ============================================================================== 35 | 36 | Schema: WHSE_IMAGERY_AND_BASE_MAPS 37 | Database roles: SRM_WHSE_IMG_BM_BASE_PUB 38 | 39 | THE FOLLOWING FILES HAVE BEEN PROVIDED FOR THE DELIVERY 40 | ======================================================= 41 | 42 | DDL FILES (ddl directory) 43 | ------------------------- 44 | 45 | GSR_WHSE.sql 46 | GSR_WHSE.grt 47 | GSR_WHSE.vw 48 | 49 | DML FILES (scripts directory) 50 | --------------------------------------------------- 51 | 52 | none 53 | 54 | FME FMW FILES (dataload directory) 55 | ---------------------------------- 56 | 57 | ~~~VIEW_NAME_1_staging_csv_bcgw.fmw~~~ 58 | 59 | FILES TO BE RUN IN THE EVENT THAT DELIVERY HAS TO BE UNDONE (revert_to_previous directory) 60 | ------------------------------------------------------------------------------------------ 61 | 62 | none 63 | 64 | INSTALL INSTRUCTIONS 65 | ==================== 66 | 67 | 1. ACCESSING FILES AND PREPARING FOR THE INSTALL 68 | ------------------------------------------------ 69 | In order to install the application the respective files need to be accessed from the Gogs repository, 70 | and contents moved to the appropriate directories. Instructions for working with DataBC's Gogs environment can be found here: 71 | https://gogs.data.gov.bc.ca/datasets/templates/src/master/delivery_kit/Gogs_Instructions_For_Vendors.md 72 | 73 | 1.1 Extract the delivery from the following Gogs repository: 74 | 75 | https://gogs.data.gov.bc.ca/datasets/gsr_whse.git 76 | 77 | 1.2 Copy the files to their target directories as required. 78 | 79 | 2. CREATE THE DATABASE OBJECTS (Data Delivery Specialist does this) 80 | ------------------------------------------------------------------- 81 | 82 | The following section describes the steps needed to create the objects. However, prior to executing these steps, confirm if 83 | objects of the same name already exist in the same schema as described below. If so, skip to the section UNINSTALL INSTRUCTIONS. 84 | Execute those instructions as necessary to remove the prior copies of the objects. Once complete, return to this step and 85 | continue with the installation. 86 | 87 | 2.1 Change to the N.N.N_XXXXX\ddl folder 88 | 2.2 Connect to the target database as WHSE_IMAGERY_AND_BASE_MAPS using sqlplus, Toad, SQL*Developer, etc.) 89 | 2.3 Create the views. 90 | 91 | 2.3.1 Run the following: start GSR_WHSE.sql (NOTE: Output will be spooled to the GSR_WHSE.lst file.) 92 | 2.3.2 Review the spooled output to check if any errors were encountered. If no errors are found then delete the spool file. 93 | 94 | 2.4 Exit sqlplus, Toad, SQL*Developer, etc. 95 | 96 | 3. REGISTER WITH SDE: Create SDE layers for spatial tables and spatial views (Data Delivery Specialist does this) 97 | ----------------------------------------------------------------------------------------------------------------- 98 | 99 | The following section describes the steps needed to register the spatial layers. 100 | 101 | Using ArcCatalog, 102 | - Open a database connection in ArcCatalog as the schema owner 103 | - Select the spatial table 104 | - Right click and select Manage / Register with Geodatabase 105 | - After a brief delay, a "Register with Geodatabase" panel will pop-up 106 | - For "Object ID Field", select the proper ArcGIS rowid column (normally OBJECTID) 107 | - For "Shape Field", select the proper geometry column (normally SHAPE or GEOMETRY) 108 | - For "Geometry Type", select POINT 109 | - For "Coordinate System", specify 3005 110 | - For "Extent", leave blank 111 | - Click the OK button. 112 | 113 | 4. RELOAD ALL TABLES and refresh materialized views (DA does this) 114 | ------------------------------------------------------------------- 115 | 116 | 4.1 Run the metadata loads: 117 | 118 | Run the following FMW's in the BCGW_REP_ON_REQUEST repository: 119 | gsr_custodians_staging_csv_bcgw.fmw 120 | gsr_business_categories_staging_csv_bcgw.fmw 121 | gsr_occupant_types_staging_csv_bcgw.fmw 122 | gsr_noncore_columns_staging_csv_bcgw.fmw 123 | gsr_column_mappings_staging_csv_bcgw.fmw 124 | 125 | 126 | 4.2 FMW for this occupant type has been prepped and is sitting in {DA-FILLS-THIS-IN} 127 | 128 | ~~~VIEW_NAME_1_staging_csv_bcgw.fmw~~~ 129 | 130 | 5. Update Oracle Spatial Metadata 131 | --------------------------------- 132 | 133 | 5.1 Change to the N.N.N_XXXXX\scripts folder 134 | 135 | To update the metadata, connect to the target database as the schema owner using sqlplus, Toad, SQL*Developer, etc. and execute 136 | ~~~gsr_whse_compute_mdsys_extents.sql~~~ 137 | 138 | 139 | 140 | UNINSTALL INSTRUCTIONS 141 | ====================== 142 | 143 | This section describes the steps that need to be taken if the delivery is making changes to objects that already exist in the BCGW. 144 | 145 | Ensure that any data in SDE tables/layers is backed up or not required. 146 | 147 | Log into ArcCatalog as the schema owner and delete the following layers, in the following order: 148 | 149 | ~~~VIEW_NAME_2_SV~~~ 150 | ~~~VIEW_NAME_1_SV~~~ 151 | 152 | 153 | REVERSION INSTRUCTIONS 154 | ====================== 155 | 156 | This section describes the steps that need to be taken if it is decided to undo a delivery and revert the BCGW to the previous version. 157 | 158 | SQL and registration scripts must be supplied in the "revert_to_previous" directory. The process for reloading/restoring data must be described as well. In the case of tables loaded through FME, the tables can be reloaded using the FME fmw for the tables(s) currently stored in FME Server. 159 | 160 | 161 | For views that just need to be deleted from the database for the delivery to be in a previous state: 162 | 163 | 1) Log into ArcCatalog as the Schema owner and navigate to the objects and delete. 164 | 165 | 166 | NOTIFICATION 167 | ============ 168 | 169 | Alert the Project Manager, the Application Manager, and the Business Analyst that the delivery 170 | is complete. Any changes to ArcSDE layers should be communicated to ArcIMS/IMF support. 171 | 172 | --------------------------------------------------------------------------------