Oil Handling Facility
Description
Oil Handling Facilities are terminals where ships will berth to load or discharge oil either as cargo or fuel. The oil handling facility must also have an arrangement with a response organization to respond to an oil spill, plus, it must have an oil spill emergency plan that requires the OHF to have equipment and resources on hand at the facility.
In 2014, the Government of Canada announced that they would be strengthening Canada's already robust tanker safety system by adding measures to reinforce marine oil spill prevention, preparedness and response, as well as liability and compensation, through its World‐Class Tanker Safety System Initiative (WCTSS).
Originator
Transport Canada – Marine Safety
Use Cases
Source(s)
Description | Source | Format | Date | Update Frequency | Metadata | Cost | Link | Remarks |
---|---|---|---|---|---|---|---|---|
Oil Handling Facilities | Transport Canada-Marine Safety | CSV | 2018 | N/A | N/A | Free | EGIS Data Folder: Marine_OilHandlingFacility.gdb.zip | -Use preprocessed GDB file as provided. |
Remarks
Due to inconsistencies, not all location was geocoded correctly, manual edits required.
Each region populate their own dataset, thus inconsistencies in data input.
EGIS Data Folder: \\ncras382\Application Source Files\EGIS\Smartmap Files\
Process for EGIS integration
CSV File Transformation:
In FME, use the Google Geocoder transformer to geocode by facility locale.
Expose the returned Lat/Long value.
Transform the Lat/Long to point.
Output to KML, SHP or GDB as required
Import into EGIS
TC Smart Maps:
Not all GIS applications can consume KML file directly due to its unique data structures such as networklinks, folders, models etc.
Please contact Lawrence Chong, Digital Services Directorate for TC Smart Maps KML dataset and format translation.
TC Smart Maps KML link: \\tc.gc.ca\tcgis\GISData\Google Mashup\Marine-NWP\OilHandlingFacility\OilHandlingFacility.kmz
Customization:
Schema transformation: As required
Denormalization: Not required
Value coding: Not required
Attribute renaming: As required to improve readability
Attribute removal: It is highly recommended as some fields are unnecessary, this will also reduce file size and improve performance
Geoenrichment: Feature symbolization is recommended to improve visualization
Format translation: Not required
Language translation: French version available
Update frequency: As identified