RIVA to GeoDatabase Mapping

Transcription

1 RIVA to GeoDatabase Mapping Summary The City of Prince George has recently updated the Database Schema for all GIS feature Classes in order to better suit the needs of our CMMS application (CityWorks). Consideration was also given to the RIVA application at the time of the geodatabase design however many asset features have had to change in order to meet the new specifications and requirements for CityWorks. This document will attempt to outline the major changes to the new\current structure of our Geodatabase in order to provide the RIVA developers with an outline of the changes within the new Geodatabase schema. The current Geodatabase is stored within SQL Server 2008 and is at version of ArcGIS Server. It has been implemented with the dbo schema. General Field Changes FacilityID: The FacilityID field can still be used as the Primary Key for all feature classes. This field still exists within each feature class related to assets however the new primary Key field is the AssetID Field. The FacilityID field is a Short Integer Field, except in the RRoad Feature Class where it is a type double field to allow for the unique ID convention and the use of decimal points. AssetID: The AssetID Field is included in every Asset related Feature Class. The AssetID field is now the Primary key for all Asset related features. This field should never be a Null value since it is the Primary Key and is also the Primary field used within the CityWorks application to relate Assets to WorkOrders & Inspections. The AssetID field is a text\string field. The reason it s a string field is to meet the requirements for the CityWorks application. LifeCycleStatus: The LifeCycleStatus field no longer indicates private ownership for any assets. The LifeCycleStatus field is now used to indicate the LifeCycle Status of a feature. The following table indicates the appropriate Domain Codes & descriptions. Code PRP Description Proposed

2 ACT ABN RMV UC Active Abandoned Removed Under Construction AssetOwner: The AssetOwner field now indicates the ownership of each asset feature. The following table indicates the appropriate Domain Codes & Descriptions. Code Description 1 CPG (City of Prince George) 0 Other -1 RDFFG (Regional District of Fraser Fort George) -2 Private -3 BCH (BC Hydro) -4 MOH (Ministry of Highways) Asset Manager: The AssetManager field indicates the responsibility for operations & maintenance of the asset. This field was added because it was indicated at development time that some assets may be privately owned but maintained by the City of Prince George. The values for this field were developed based upon the City of Prince George organizational structure at the time. Code Description 1 Asset 2 Bylaw 3 Civic Facility 4 Communications 5 Community Facility 6 Environment 7 Finance 8 Fire 9 Fleet 10 GIS 11 Human Resources 12 IT Services 13 Parks 14 Planning 15 Police 16 Real Estate 17 Recreation 18 Solid Waste 19 Subdivision 20 Transportation

3 21 Utilities -2 Private 0 Other -1 Unknown Location: The Location field was added to allow for the text description of each asset. This field is populated with a corresponding Civic Address for each feature that has been reverse geocoded based on the City of Prince George geocoding service. InstallDate: The InstallDate field indicates the date the Feature was installed. AdministrativeArea: Currently not populated. OperatingArea: Currently not populated. FeatureClasses Roads The Road centerline features are now stored within the RRoad Feature Class. There have been several changes to this dataset. The road centerlines are now attributed with a field named: RoadClass. This subtype field is sued to distinguish between the road usage classifications listed in the table below. Code Description 1 Freeway 2 Highway 3 Arterial 4 Major Collector 5 Minor Collector 6 Local 7 Alley 8 Private 9 Ramp 10 Unknown

4 The description of Alley has been used in order to differentiate between the two similar term of lanes. Since a lane could refer to the number of travel lanes along a centerline or a lane running parallel between two local roads. The other main modification relates to how the features are now segmented within GIS. No longer are the segments digitized from Intersection to Intersection exclusively. Road centerline segments are now based on several factors such as; Road Intersections, address range and lane separation. This was done to allow GIS to maintain one road centerline feature class for a multitude of purposes. (Fig:1), Cul-de-sacs are now digitized around the full perimeter of the turnaround instead of simply ending at the center of the turnaround. (Fig: 2&3), Road centerlines have been segment wherever the road travel lanes are separated by a physical feature or meridian. (Fig:4), Road centerline segments may be broken between intersections in order to allow for the change in address ranges. (Fig:5), There are many additional ramp sections that have been added in order to better reflect the travel of vehicles and allow for the addition of the extra pavement. AssetID The Asset field is used as the Primary Key or unique identifier for all road features \ segments. The numbering system is still based on the whole value being associated to a particular road name with the segments being identified by the decimal value. For example all segments associated to Aberdeen Rd are numbered with 2.x such as 2.00, 2.01, 2.02, All segments related to Southridge Ave are numbered with 901.x such as , , , etc. LegacyID The LegacyID field has been populated with the associated FacilityID value from the previous Road_CL feature class used by RIVA in the past. All new road segments that could be associated to the old segments have had the LegacyID field value calculated for reference by the RIVA application. This field can be used to associated old RIVA data to the new Road segments. SurfaceMaterial Pavement or Surface Materials are now based on the table below. Code CON HMAC CS ROCK GRV STN Description Concrete HMAC Chip-and-Seal Rock Gravel Stone

5 NumberofLanes SS OTH UNK PB Stabilized Soil Other Unknown Paver Brick The field NumberofLanes is being used to indicate the number of travel lanes along the associated segment. EOPWidth This field will be populated in order to reflect the actual paved width of the road segment. Measured from Road edge to Road Edge. ROWWidth This field will be populated in order to reflect the actual width of the road Right of Way. Measured from Property edge to property edge.

6 The following Figures will demonstrate the road segmentation within the Geodatabase for road segments. Cul-de-Sac segments broken for address ranges Cul-de-Sac segments broken for address ranges Road Segments go around the Cul-de-Sac and no longer ending at the center point. Figure 1: Example of Cul-de-Sac segmentation

7 Meridian physically separates Road Figure 2: Dual Road Centerline, Physical separation

8 Meridian physically separates Road No Physical barrier (Single Road Centerline) Figure 3: Single & Double Road Centerlines due to physical separation

9 Segmentation for Address Range Not intersection to Intersection Figure 4: Segmentation due to Address Range

10 Additional Ramps Additional Ramps Figure 5: Additional Ramps

11 Sidewalks & Walkways These Features are now located within the RPath Feature Class. They can be selected or filtered based on their SubType Code. Storm, Sewer & Water (General Changes ) The same documented general changes have occurred for all Storm, Sewer & Water related assets as listed above. Please refer to the individual SubTypes and Domain values used within the Geodatabase for further reference. In most cases SubType Codes have not been altered.