VALIDATIONSTATUS
(
type: esriFieldTypeSmallInteger, alias: Validation status
, Coded Values:
[0: No calculation required, no validation required, no error]
, [1: No calculation required, no validation required, has error(s)]
, [2: No calculation required, validation required, no error]
, ...5 more...
)
VALIDATIONSTATUS
(
type: esriFieldTypeSmallInteger, alias: Validation status
, Coded Values:
[0: No calculation required, no validation required, no error]
, [1: No calculation required, no validation required, has error(s)]
, [2: No calculation required, validation required, no error]
, ...5 more...
)
Description: Intended use by personnel involved in planning and/or operational capacities for pavement and transportation management groups.Point of ContactIndividual's NameJustin HoffmanContact's Department NameTransportation Public Works - Business Support ServicesContact's Position/TitleSr. Business Process AnalystContact information940-704-7126/justin.hoffman@fortworthtexas.govAddress TypePhysicalAddress900 Monroe StreetDelivery PointGordon Swift BuildingCityFort WorthPostal Code76102CountryUSAResource MaintenanceUpdate FrequencyContinualUpdate MethodUpdated/edited by authorized TPW personnelUpdated byJustin HoffmanContact's Department NameTransportation Public Works - Business Support ServicesContact's Position/TitleSr. Business Process AnalystContact information940-704-7126/justin.hoffman@fortworthtexas.govNext UpdateUnknownTagsKeywords1TPWKeywords2pavement managementKeywords3transportation managementKeywords4streetsKeywords5speed bumpsAttribute DataField NameASSET_IDAliasNoneField DescriptionUnique asset identification for speed bumpDescription SourceIdentification generated by third-party contractor. 'SB' prefix added prior to upload by city personnel.Field NameSTREETAliasNoneField DescriptionField identifies the street where speed bump asset is located.Description SourceAssets.DBO.PavementField NameBUMP_TYPEAliasNoneField DescriptionField identifies the type of speed bumpDescription SourceType of speed bump was defined to 3 options and determined by third party contractor.Field NameCONDITIONAliasNoneField DescriptionField identifies the functional condition of speed bump assetDescription SourcePre-defined condition metrics created by city personnel and determined during survey by third party contractor.Field NameINSTALL_DATEAliasNoneField DescriptionField identifies the installation date for speed bump.Description SourceDetermined by TPW personnelField NameINSTALL_YEARAliasNoneField DescriptionField identifies the installation year for speed bump.Description SourceDetermined by TPW personnelField NameOWNERAliasNoneField DescriptionField identifies asset ownership for speed bumpDescription SourceAssets.DBO.Pavement - OWNER fieldField NameMAINTAINEDBYAliasNoneField DescriptionField identifies entity responsible in maintaining speed bumpDescription SourceAssets.DBO.Pavement - MAINTAINEDBY fieldField NameLIFECYCLEAliasNoneField DescriptionField identifies speed bump current functional lifecycleDescription SourceDetermined by TPW personnelField NamePHOTO_HYPERLINKAliasNoneField DescriptionField includes the URL hyperlink photo of speed bump assetDescription SourcePhoto collected by third-party contractor during surveyField NamePLAN_HYPERLINKAliasNoneField DescriptionField includes the URL hyperlink to associated plan set for speed bumpDescription SourceTPW personel, engineering drawings/plans associated with road constructionField NameCREATED_USERAliasNoneField DescriptionField identifies user name who created speed bump featureDescription SourceAuto-generated by ESRI ArcGIS ArcMap softwareField NameCREATED_DATEAliasNoneField DescriptionField identifies the date speed bump feature was createdDescription SourceAuto-generated by ESRI ArcGIS ArcMap softwareField NameLAST_EDITED_USERAliasNoneField DescriptionField identifies user name who last edited/modified speed bump featureDescription SourceAuto-generated by ESRI ArcGIS ArcMap softwareField NameLAST_EDITED_DATEAliasNoneField DescriptionField identifies the date the speed bump feature was last edited/modifiedDescription SourceAuto-generated by ESRI ArcGIS ArcMap softwareField NameCOMMENTSAliasNoneField DescriptionGeneral open comments fieldDescription SourcePopulated by data users/editors
VALIDATIONSTATUS
(
type: esriFieldTypeSmallInteger, alias: Validation status
, Coded Values:
[0: No calculation required, no validation required, no error]
, [1: No calculation required, no validation required, has error(s)]
, [2: No calculation required, validation required, no error]
, ...5 more...
)
VALIDATIONSTATUS
(
type: esriFieldTypeSmallInteger, alias: Validation status
, Coded Values:
[0: No calculation required, no validation required, no error]
, [1: No calculation required, no validation required, has error(s)]
, [2: No calculation required, validation required, no error]
, ...5 more...
)
VALIDATIONSTATUS
(
type: esriFieldTypeSmallInteger, alias: Validation status
, Coded Values:
[0: No calculation required, no validation required, no error]
, [1: No calculation required, no validation required, has error(s)]
, [2: No calculation required, validation required, no error]
, ...5 more...
)
VALIDATIONSTATUS
(
type: esriFieldTypeSmallInteger, alias: Validation status
, Coded Values:
[0: No calculation required, no validation required, no error]
, [1: No calculation required, no validation required, has error(s)]
, [2: No calculation required, validation required, no error]
, ...5 more...
)
VALIDATIONSTATUS
(
type: esriFieldTypeSmallInteger, alias: Validation status
, Coded Values:
[0: No calculation required, no validation required, no error]
, [1: No calculation required, no validation required, has error(s)]
, [2: No calculation required, validation required, no error]
, ...5 more...
)
TYPE
(
type: esriFieldTypeString, alias: TYPE, length: 20
, Coded Values:
[TYPE 1: Type 1: Standard 7"curb and 2' gutter (rare)]
, [TYPE 2: Type 2: Standard 7" curb and 15' gutter (the norm)]
, [TYPE 3: Type 3: Standard 6" curb and median]
, ...5 more...
)
Description: Alley FC shows the passage between properties that are used primary by utility companies or residents themselves. Data was collected in-house by pavement management group in early 2016. Prior to the hand off of Alley program to Neighborhood Services in 2016, Pavement Management group managed the Alley program and outsource the work to contractor to have the alley cleared up. Currently, Neighborhood Services department maintain the unpaved alley and Transportation Public Works - Street & Stormwater Operations maintain the paved portion of the alley. This FC is used in VUEWorks software to track which alley has been worked on by TPW. Most of the information imported to Alley FC is from CFWGIS.TRN_STREET_ALLEY layer with few additional fields added.
Copyright Text: Transportation Public Work/Mala Muongkhot