Aboriginal Consultation Activities

Owned by Diego Cesa de Meira (Unlicensed)
Jul 31, 2019
2 min read

Description

Aboriginal Consultation Unit (ACU) works closely with Navigation Protection Program and Environment Affairs for all project submissions. Aboriginal Consultation Activities records projects which might require consultation with First Nation and its stakeholders.

Originator

  1. Transport Canada, Aboriginal Consultation Database

Use Cases

  1. As a Consultation Officer, I want to be able to identify similar projects in the vicinity of current project so that same consultation process are followed.

Source(s)

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

Description

Source

Format

Date

Update Frequency

Metadata

Cost

Link

Remarks

ACU Activities Log

Aboriginal Consultation Database (ACD)

Oracle Non-spatial

Current

Frequent

N/A

Free

EGIS Data Folder: ACD_ActivitiesLog.gdb.zip
Contact Douglas Hubbard, Aboriginal Consultation Unit

Use preprocessed GDB file as provided.

Remarks

  1. ACU Database is an Oracle Non-spatial database.

  2. Permission required to access the ACU Database for direct EGIS integration. Contact Programs Group, Aboriginal Consultation Unit Manager for more information.

  3. Cloud storage for ACU Activities Log may be restricted.

  4. Preprocessing is recommended as Lat/Long values are not consistent, missing or not validated.

  5. EGIS Data Folder: \\ncras382\Application Source Files\EGIS\Smartmap Files\

Solution:

  1. In FME, connect to the Oracle database and export to an Excel Spreadsheet.

  2. Validate the Lat/Long, make corrections as required and save it as a new version.

  3. For future updates, only new records need to be validated, thus saving time.

  4. In FME, use the Feature Merger transformer to join the new and the old dataset using CONSULTATION_FILE_ID as the primary key to append the records into the old and create a new version.

Process for EGIS integration

Oracle Direct Integration

  1. Oracle Database can be directly connected to EGIS if the portal is hosted on TC Enterprise Network.

Oracle Non-spatial Database:

  1. In FME, connect to the database using Oracle Non-spatial Reader with the connection parameters provided by ACU DBA.

  2. Use Feature Merger transformer to join the following tables using CONSULTATION_FILE_ID as primary key.
    -ACD_ActivityInformation (Main table)
    -ConsultationFile
    -GeographicalSetting
    -LegalDuty
    -SupportDocument.

  3. Transform the Lat/Long to point.

  4. Output to KML, SHP or GDB as required.

  5. Import into EGIS

TC Smart Maps:

  1. Not all GIS applications can consume KML file directly due to its unique data structures such as networklinks, folders, models etc.

  2. Please contact Lawrence Chong, Digital Services Directorate for TC Smart Maps KML dataset and format translation.

  3. TC Smart Maps KML link: \\tc.gc.ca\tcgis\GISData\Google Mashup\ACU\ACD_Activities\ACD_Activities.kmz

Customization:

  1. Schema transformation: Not required.

  2. Denormalization: Not required

  3. Value coding: Not required

  4. Attribute renaming: As required to improve readability

  5. Attribute removal: It is highly recommended as some fields are unnecessary, this will also reduce file size and improve performance

  6. Geoenrichment: Feature symbolization is recommended to improve visualization

  7. Format translation: Geocoding using Lat/Long

  8. Language translation: French version not available

  9. Update frequency: As identified