Data Governance Scenarios

Owned by Diego Cesa de Meira (Unlicensed)
Last updated: Aug 16, 2019
3 min read

Overview

There are three main scenarios through which data will be integrated into the Enterprise GIS*:

  1. The data are provided by their respective custodians as data services. To integrate these into the Enterprise GIS, we create links that point to the data service endpoints.

  2. The data are provided as files in a format and schema that can be ingested directly into the Enterprise GIS by a technician.

  3. The data are provided in a format that requires schema translation and / or format conversion before they can be ingested into the Enterprise GIS.

The following use cases describe each scenario more fully using examples of datasets from TC Smart Maps.

1. Use Case: 2015 Federal Electoral Districts Boundaries

As an EGIS administrator, I need to make the 2015 Federal Electoral Districts Boundaries available as a feature layer for EGIS users.

The 2015 Federal Electoral Districts Boundaries dataset is a polygon layer representing the Federal Electoral Districts (FEDs) proclaimed in 2013 and contested in the 2015 Federal General Election. Each FED is represented as a polygon feature in the layer. The dataset is originated by Elections Canada.

The 2015 FED Boundaries are available as an Esri REST service through the Open Government Portal . The dataset has a Federal Geospatial Platform (FGP) metadata record and a set of accompanying documentation that describes the dataset's governance.

The EGIS Administrator performs the following tasks to publish the 2015 FED Boundaries service to EGIS:

  1. Create a new item in EGIS that links to the 2015 FED Boundaries Esri REST endpoint.

  2. Copy the content of the FGP metadata record to the EGIS metadata record.

2. Use Case: Forward Sortation Areas

As an EGIS administrator, I need to make Forward Sortation Area boundaries available as a feature layer for EGIS users.

Forward Sortation Area (FSA) boundaries are polygons representing the geographic extent covered by the first three characters of a postal code. FSA's are defined by Canada Post, but the FSA Boundary File is maintained by Statistics Canada for the purpose of administering the Census.

The FSA Boundary file is available on the Statistics Canada website . In addition to the shapefile that contains the FSA boundary data, the download contains a complete** metadata record, and an additional document that describes the dataset's governance.

In this scenario, the data, metadata, and governance are maintained by an external organization, but the data are available in file format, rather than as a service. The EGIS administrator must prepare the data to be published as a service that will be hosted in EGIS.

 

The EGIS Administrator performs the following tasks to publish the FSA Boundary File as a service in EGIS:

  1. Download the FSA Boundary File from Statistics Canada. The ZIP file (and other artifacts created in this process) are stored in a cloud file share.

  2. Extract the contents of the downloaded ZIP file.

  3. Add the shapefile to an ArcGIS Pro project.

  4. Define the properties of the FSA boundary layer. The properties define how the layer will look and behave when published.

  5. Save the FSA boundary layer file. The FSA boundary layer file will serve as a template should the FSA boundary layer need to be re-published.

  6. Publish the FSA boundary layer to EGIS as a web layer.

In addition to the governance and metadata provided by Statistics Canada, the above process shall also be subject to governance. Note that some of these tasks lend themselves to automation.

3: Use Case

 

 

* At this time, these scenarios cover the datasets that can be found in TC Smart Maps. Other scenarios covering internal TC clients may be discovered as these clients are onboarded.

** as defined by the ISO-19115:2003 North American profile .