ArcGIS REST Services Directory Login | Get Token
Home > services > CityRegulatedFloodplains (MapServer) > Centerline API Reference
JSON

Layer: Centerline (ID: 8)

Name: Centerline

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 7 0;"><SPAN>Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network. (From ESRI Local Government Model "RoadCenterline" Feature)</SPAN></P><P><SPAN>**This dataset was significantly revised in August of 2014 to correct for street segments that were not properly split at intersections. There may be issues with using data based off of the original centerline file. </SPAN></P><P><SPAN>** The column Speed Limit was updated in November 2014 by the Transportation Intern and is believed to be accurate</SPAN></P><P><SPAN>** The column One Way was updated in November of 2014 by core GIS and is believed to be accurate.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>[MAXIMOID] A unique id field used in a work order management software called Maximo by IBM. Maximo uses GIS CL data to assign locations to work orders using this field. This field is maintained by the Transportation GIS specialists and is auto incremented when new streets are digitized. For example, if the latest digitized street segment MAXIMOID = 999, the next digitized line will receive MAXIMOID = 1000, and so on. </SPAN></SPAN></P><P><SPAN /></P><P><SPAN>STREET NAMING IS BROKEN INTO THREE FIELDS FOR GEOCODING:</SPAN></P><P><SPAN>[PREFIX] (Text,3) This field is attributed if a street name has a prefix such as W, N, E, or S.</SPAN></P><P><SPAN>[NAME] (Text,44) Domain with all street names. The name of the street without prefix or suffix.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>[ROAD_TYPE] (alias,[SUFFIX]) (Text,4) Describes the type of road aka suffix, if applicable. CAPCOG Addressing Guidelines Sec 504 U. states, “Every road shall have corresponding standard street suffix…” standard street suffix abbreviations comply with USPS Pub 28 Appendix C Street Abbreviations. Examples include, but are not limited to, Rd, Dr, St, Trl, Ln, Gln, Lp, CT. </SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN /></P><P STYLE="margin:0 0 7 0;"><SPAN>[LEFT_LOW] (Integer,10) The minimum numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 101.</SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>[LEFT_HIGH] </SPAN></SPAN><SPAN>(Integer,10) </SPAN><SPAN><SPAN>The largest numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 201.</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN><SPAN>[LOW]</SPAN></SPAN><SPAN>(Integer,10) </SPAN><SPAN><SPAN>The minimum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 100.</SPAN></SPAN></P><P STYLE="margin:0 0 7 0;"><SPAN>[HIGH] (Integer,10)The maximum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 200.</SPAN></P><P><SPAN /></P><P><SPAN>[ALIAS] (Text,30) Alternative names for roads if known. This field is useful for geocode re-matching. </SPAN></P><P><SPAN>[CLASS] (Text,15)The functional classification of the centerline. For example, Minor (Minor Arterial), Major (Major Arterial). THIS FIELD IS NOT CONSISTENTLY FILLED OUT, NEEDS AN AUDIT. </SPAN></P><P><SPAN>[FULLSTREET] (Text,30) The full name of the street concatenating the [PREFIX], [NAME], and [SUFFIX] fields. For example, "W San Antonio St."</SPAN></P><P><SPAN>[ROWWIDTH] (Double,38) Width of right-of-way along the CL segment. Data entry from Plat by Planning GIS </SPAN><SPAN>Or from Engineering PICPs/ CIPs.</SPAN></P><P><SPAN>[NUMLANES] (Double,38) Number of striped vehicular driving lanes, including turn lanes if present along majority of segment. Does not inlcude bicycle lanes. </SPAN></P><P><SPAN>[LANEMILES] (Double,38) Describes the total length of lanes for that segment in miles. It is manually field calculated as follows (( [ShapeLength] / 5280) * [NUMLANES]) and maintained by Transportation GIS.</SPAN></P><P><SPAN>[SPEEDLIMIT] (Text,5) Speed limit of CL segment if known. If not, assume 30 mph for local and minor arterial streets. If speed limit changes are enacted by city council they will be recorded in the Traffic Register dataset, and this field will be updating accordingly. Initial data entry made by CIP/Planning GIS and maintained by Transportation GIS.</SPAN></P><P><SPAN>[YRBUILT] replaced by [DateBuilt] See below. Will be deleted. 4/21/2017</SPAN></P><P><SPAN>[LASTYRRECON] (alias [RECONSTRUCTION]) (Text,10) Is the last four-digit year a major reconstruction occurred. Most streets have not been reconstructed since orignal construction, and will have &lt;NULL&gt; values. The Transportation GIS Specialist will update this field. </SPAN></P><P><SPAN>[OWNER] (Text,25) Describes the governing body or private entity that owns/maintains the CL. It is possible that some streets are owned by other entities but maintained by CoSM. Possible attributes include, CoSM, Hays Owned/City Maintained, TxDOT Owned/City Maintained, TxDOT, one of four counties (Hays, Caldwell, Guadalupe, and Comal), TxState, and Private.</SPAN></P><P><SPAN>[ST_FROM] (Text,50) Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the From- direction. Should be edited when new CL segments that cause splits are added. </SPAN></P><P><SPAN>[ST_TO] (Text,50) Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the To- direction. Should be edited when new CL segments that cause splits are added. </SPAN></P><P><SPAN>[PAV_WID] (Double,38) Pavement width of street in feet from back-of-curb to back-of-curb. This data is entered from as-built by CIP GIS. In January 2017 Transportation Dept. field staff surveyed all streets and measured width from face-of-curb to face-of-curb where curb was present, and edge of pavement to edge of pavement where it was not. This data was used to field calculate pavement width where we had &lt;null&gt; values. A value of 1 foot was added to the field calculation if curb and gutter or stand up curb were present (the face-of-curb to back-of-curb is 6 in, multiple that by 2 to find 1 foot). If no curb was present, the value enter in by the field staff was directly copied over. If values were already present, and entered from asbuilt, they were left alone. </SPAN></P><P><SPAN>[ONEWAY] (Text,50) Field describes direction of travel along CL in relation to digitized direction. If a street allows bi-directional travel it is attributed "B", a street that is one-way in the From_To direction is attributed "F", a street that is one-way in the To_From direction is attributed "T", and a street that does not allow travel in any direction is attibuted "N". </SPAN></P><P><SPAN>[ROADLEVEL] (Double,38) Field will be aliased to [MINUTES] and be used to calculate travel time along CL segments in minutes using shape length and [SPEEDLIMIT]. Field calculate using the following expression: [MINUTES] = ( ([SHAPE_LENGTH] / 5280) / ( [SPEEDLIMIT] / 60 ))</SPAN></P><P><SPAN>[ROWSTATUS] (Text,15) Values include "Open" or "Closed". Describes whether a right-of-way is open or closed. If a street is constructed within ROW it is "Open". If a street has not yet been constructed, and there is ROW, it is "Cosed". UPDATE: This feature class only has CL geometries for "Open" rights-of-way. This field should be deleted or re-purposed. </SPAN></P><P><SPAN>[ASBUILT] (Text,200) field used to hyper link as-built documents detailing construction of the CL. Field was added in Dec. 2016. </SPAN></P><P><SPAN>[DateBuilt] (Date) Date field used to record month and year a road was constructed from Asbuilt. Data was collected previously without month information. Data without a known month is entered as "1/1/YYYY". When month and year are known enter as "M/1/YYYY". Month and Year from asbuilt. Added by Engineering/CIP. </SPAN></P><P><SPAN>[ACCEPTED] (Date) Date field used to record the month, day, and year that a roadway was officially accepted by the City of San Marcos. Engineering signs off on acceptance letters and stores these documents. This field was added in May of 2018. Due to a lack of data, the date built field was copied into this field for older roadways. Going forward, all new roadways will have this date. . This field will typically be populated well after a road has been drawn into GIS. Entered by Engineering/CIP. ****In an effort to make summarizing the data more efficient in Operations Dashboard, a generic date of "1/1/1900" was assigned to all COSM owned or maintained roads that had NULL values. These were roads that either have not been accepted yet, or roads that were expcepted a long time ago and their accepted date is not known. </SPAN></P><P><SPAN>[WARRANTY_EXP] (Date) Date field used to record the expiration date of a newly accepted roadway. Typically this is one year from acceptance date, but can be greater. This field was added in May of 2018, so only roadways that have been excepted since and older roadways with valid warranty dates within this time frame have been populated. </SPAN></P><P><SPAN /></P></DIV></DIV></DIV>

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata