CW/Pavement_Operations (FeatureServer)

View In: ArcGIS Online Map Viewer

View Footprint In: ArcGIS Online Map Viewer

Service Description:

PavementLine is a polyline feature class. Pavement records orginiated from the prod geodatabase and underwent editing to represent pavement records according to a PWs legacy spreadsheet. The geometry came from prod.GIS.Roads for all records before any manipulation. The spreadsheet determined the functional classification (collector, arterial, local) of each street segment. Collectors and arterials were merged into one single feature depending on the start and stop location of the spreadsheet, while local streets represent pavement segments between each intersection. After determining the spatial extent of each feature, the PWs legacy spreadsheet with maintanance history (overlay, reclamite, crackseal, and concrete dates) was joined based on the GIS LINK in the spreadsheet and LgRd_ASSET_ID in GIS. The ouput feature class was a layer with the correct spatial extent and maintanace history for each pavement segment. Following, a model built in GIS determined the cg_ToStreet and cg_FromStreet for each record.

PavementLine records which have a functional classification of "Local" are associated to a neighorhood for PW to be able to preform work on all pavement segments in one neighorhood at a given time. Additioanlly, "Collectors" and "Arterials" under functional classificaiton do not have a neighborhood association as the entire line segment will be completed as repairs become due. As area is an important attribute for the PW STM division to report, it was calculated using the following equation:

cg_AreaSqFt = cg_LengthFt* LgSs_AVG_WIDTH_FT

The cg_AreaSqFt was then divided by 9 to calculate cg_AreaSqYd.

All Layers and Tables

Has Versioned Data: false

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers:

Pavement Operations (0)

Description: PavementLine is a polyline feature class. Pavement records orginiated from the prod geodatabase and underwent editing to represent pavement records according to a PWs legacy spreadsheet. The geometry came from prod.GIS.Roads for all records before any manipulation. The spreadsheet determined the functional classification (collector, arterial, local) of each street segment. Collectors and arterials were merged into one single feature depending on the start and stop location of the spreadsheet, while local streets represent pavement segments between each intersection. After determining the spatial extent of each feature, the PWs legacy spreadsheet with maintanance history (overlay, reclamite, crackseal, and concrete dates) was joined based on the GIS LINK in the spreadsheet and LgRd_ASSET_ID in GIS. The ouput feature class was a layer with the correct spatial extent and maintanace history for each pavement segment. Following, a model built in GIS determined the cg_ToStreet and cg_FromStreet for each record.PavementLine records which have a functional classification of "Local" are associated to a neighorhood for PW to be able to preform work on all pavement segments in one neighorhood at a given time. Additioanlly, "Collectors" and "Arterials" under functional classificaiton do not have a neighborhood association as the entire line segment will be completed as repairs become due. As area is an important attribute for the PW STM division to report, it was calculated using the following equation:cg_AreaSqFt = cg_LengthFt* LgSs_AVG_WIDTH_FTThe cg_AreaSqFt was then divided by 9 to calculate cg_AreaSqYd.

Service Item Id: 1314b8c047b743e0a6aaa45196444e97

Copyright Text: City of Lakewood, Colorado

Spatial Reference: 2877 (2877)

Initial Extent:

Full Extent:

Units: esriFeet

Document Info:

Enable Z Defaults: false

Supports ApplyEdits With Global Ids: true

Support True Curves : true

Only Allow TrueCurve Updates By TrueCurveClients : true

Supports Return Service Edits Option : true

Supports Dynamic Layers: false

Child Resources: Info Query Data Elements Relationships

Supported Operations: Query Query Contingent Values QueryDomains Extract Changes