Spatial (ESRI SHAPE format) files are uploaded to two locations in Phoenix Connect. One is for gross block boundary and road permit data and the other is for all other SHAPE format files. Both locations are used for ESF submissions, Map Viewing, and generating georeferenced PDF maps.
SHAPE File Prerequisites
- Files required with following extensions: dbf, prj, sbn, sbx, shp, shx
- All File names in the SHAPE dataset are case sensitive. ie. file set filenames must match exactly.
- example: block.dbf and BLOCK.shp would not be considered in the same SHAPE dataset
- A column with the name GIS_LINK must exist in each SHAPE attribute file (.dbf)
SHAPE GIS_LINK Attribute
The field (attribute) name in the spatial data used to link Phoenix Connect and spatial features must be named GIS_LINK and, the values in both the SHAPE data and Phoenix Connect GIS ID fields (see next section) must match exactly. GIS ID values should be unique within the land base.
Note: attribute name can be any case. Eg. GIS_LINK, gis_link, Gis_link, etc.
Phoenix Connect GIS IDs
The GIS IDs in Phoenix Connect are the identifiers used to:
- Find spatial features used in the creations of ESF submission files
- Display spatial features in Map Views
Area features (Opening, SU, Activity, Forest Cover)
The most common format used to link polygon features is Licence + CP + Block + SU ID or Strata ID with an underscore or hyphen character between each value. SU GIS IDs commonly have a prefix of ‘SU’ and Strata GIS ID’s a prefix of ‘ST’, however, this structure may be changed/managed by a Company Administrator using the Configuration - Settings - GIS ID page.
Examples:
A12345_67_8 for Blocks
A12345_67_8_SUA for Standard Unit A
A12345_67_8_ST1 for Strata 1
The Init GIS ID button is used to initialize GIS ID fields in Phoenix Connect and is displayed on each page containing a GIS ID field. The system can also be set to initialize GIS IDs for new records.
To populate an area feature GIS ID field in Phoenix Connect:
- Enter the value and select the Submit button
or, - Select the Init GIS ID button (format must be pre-configured in Configuration - Settings - GIS ID).
Linear (Road Sections)
The most common format used for RRS Road Section GIS IDs is RP Number + Road Section ID with an underscore or hyphen character between each value. For new Road Permit applications where the RP Number is not known yet enter ‘New’ for the RP Number and then update it later once the application is approved. For subsequent applications under an existing RP, the RP Number is used. Road Section portion always stays the same.
Examples:
new_SPUR 1 = New Road Permit with new Road Section. (RP number not in RRS)
R12345_12 = RP Amendment either adding or amending existing Road Section 12. (RP Number R12345 already in RRS)