Description of data fields in the Boston street segment data

City of Boston street segments data from the Street Address Management (SAM) system. Updated nightly.

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)**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. ** The column Speed Limit was updated in November 2014 by the Transportation Intern and is believed to be accurate** The column One Way was updated in November of 2014 by core GIS and is believed to be accurate.[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. STREET NAMING IS BROKEN INTO THREE FIELDS FOR GEOCODING:PREFIX This field is attributed if a street name has a prefix such as W, N, E, or S.NAME Domain with all street names. The name of the street without prefix or suffix.ROAD_TYPE (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. LEFT_LOW 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.LEFT_HIGH 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.LOW 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.HIGHThe 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.ALIAS Alternative names for roads if known. This field is useful for geocode re-matching. CLASSThe functional classification of the centerline. For example, Minor (Minor Arterial), Major (Major Arterial). THIS FIELD IS NOT CONSISTENTLY FILLED OUT, NEEDS AN AUDIT. FULLSTREET The full name of the street concatenating the [PREFIX], [NAME], and [SUFFIX] fields. For example, "W San Antonio St."ROWWIDTH Width of right-of-way along the CL segment. Data entry from Plat by Planning GIS Or from Engineering PICPs/ CIPs.NUMLANES Number of striped vehicular driving lanes, including turn lanes if present along majority of segment. Does not inlcude bicycle lanes. LANEMILES 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.SPEEDLIMIT 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.[YRBUILT] replaced by [DateBuilt] See below. Will be deleted. 4/21/2017LASTYRRECON (Text,10) Is the last four-digit year a major reconstruction occurred. Most streets have not been reconstructed since orignal construction, and will have values. The Transportation GIS Specialist will update this field. OWNER 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.ST_FROM 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. ST_TO 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. PAV_WID 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 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. ONEWAY 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". ROADLEVEL 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 ))ROWSTATUS 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. ASBUILT field used to hyper link as-built documents detailing construction of the CL. Field was added in Dec. 2016. DateBuilt 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. ACCEPTED 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. WARRANTY_EXP 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.

GisGeoDbPres.MAPBASE.RoadSegmentDetails

This dataset shows polygon locations of the road segments inventoried by the City of Perth. The road segment data was collected from as constructed drawings and old survey maps. At least 95% of the locational data for the road segment is accurate to within a few meters. Some errors and/or duplicate data may exist. Show full description

Field Name DescriptionObjectIDFor internal use.FacilityIDThe tracking number for each street segment.InstallDateInstallation date for the street segment.LifeCycleStatusFor internal use.LocationDescriptionLocation of street segment, from cross street to cross street.CommentsComment field for location.EAM_PARENTFor internal use.EAM_PARENTORGFor internal use.GISOBJIDInfor object ID field.EAM_UOMFor internal use.EAM_UOMREFFor internal use.EAM_PRECISIONFor internal use.StreetClassType of street, such as Residential, Minor arterial, Collector, etc.SubZoneFor internal use.LaneMilesLength of segment, in miles.GlobalIDFor internal use.PCIQuality of road condition, as a percent.WidthWidth of street segment, in feet.ShapeFor internal use.created_userFor internal use.created_dateFor internal use.last_edited_userFor internal use.last_edited_dateFor internal use.StreetSaverFor internal use.UPDATE_COUNTFor internal use.StreetSaverIDID value for StreetSaver.LanesNumber of lanes within street segment.Shape.STLength()For internal use.

A list of street segments and intersections sorted by street name and ascending address number. This data set is based on the City's GIS basemap and contains CNN id numbers for each record.

If you are looking for a geometric field for each street, please refer to Streets - Active and Retired (https://data.sfgov.org/Geographic-Locations-and-Boundaries/Streets-Active-and-Retired/3psu-pn9h)

City of Cincinnati street center line data, broken out by street segment. Pavement Condition Index (PCI) rating for each street segment is also included. Pavement Condition is assessed annually by the Department of Transportation & Engineering (DOTE).

This data is maintained by the Department of Transportation & Engineering, and is refreshed daily.

Analysis of ‘Speed Limits per Street Segment’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/a6392832-6f6d-4d4b-b8f8-87c0c2956e5e on 11 February 2022.

--- Dataset description provided by original source is as follows ---

A. SUMMARY Maximum speed limits per street segment for the City of San Francisco. Speed limits are indicated primarily for streets that have speeds greater than 25 MPH, unless the speed limit has been changed from a higher speed or a speed survey has been conducted to enforce the de facto speed limit of 25 MPH. 25 MPH is the de fact speed limit for most residential and commercial streets, and apply to streets on this map denoted by a 0 MPH label. Alleys narrower than 25 feet can have de facto speed limits of 15 MPH.

B. METHODOLOGY Speed limit legislation information is taken from MTAB legislation and in some cases directives from engineers in the 5212 classification. Speed limit implementation information is taken from SSD Shops Reports and then parsed via python code. Implementation for speed limits will specify when signs are put in stating the new speed limits, and the work order that the sign installation was spec'd in.

C. UPDATE FREQUENCY Updated quarterly or on an as need basis by request

--- Original source retains full ownership of the source dataset ---

Street Segments

Street segments of the road network.attributes:ID - Unique identifierToponymy - Full street nameNorte - Road numberCivic NumberOriginLeft - Civic number that originated the segment on the left side according to the direction of digitalizationNumberCivicOriginRight - Civic number that originated the segment on the right side according to the direction of digitalizationCivic NumberDestinationLeft - Civic number destined for segment on the left side according to the direction of digitalizationCivic NumberDestinationRight - Civic number to the segment on the right side according to the direction of DigitalNameGeneric - Short name of the streetType - Street typeStreet typeStreet typeSegmentStreet - Hierarchical class of the segment in the networkSpeed - Speed limit displayTypesUnique - Indication relating to the presence of a one-way wayMunicipal - Municipal code - Municipal codeHeavy traffic - Indication relating to heavy traffic**This third party metadata element was translated using an automated translation tool (Amazon Translate).**

This dataset contains each parking zone and the street segment that it is linked to. The parking zone can go across multiple street segments and also one street segment can have multiple parking zones.

This data can be linked to both the sign plate parking zone dataset.

The dataset(s) can be joined on parking zone.

To create a spatial dataset the street segment can be joined with the road corridor dataset on the street segment id.

Street segments of the road network.attributes:ID - Unique identifierToponymy - Full street nameNorte - Road numberCivic NumberOriginLeft - Civic number that originated the segment on the left side according to the direction of digitalizationNumberCivicOriginRight - Civic number that originated the segment on the right side according to the direction of digitalizationCivic NumberDestinationLeft - Civic number destined for segment on the left side according to the direction of digitalizationCivic NumberDestinationRight - Civic number to the segment on the right side according to the direction of DigitalNameGeneric - Short name of the streetType - Street typeStreet typeStreet typeSegmentStreet - Hierarchical class of the segment in the networkSpeed - Speed limit displayTypesUnique - Indication relating to the presence of a one-way wayMunicipal - Municipal code - Municipal codeHeavy traffic - Indication relating to heavy trafficThis third party metadata element was translated using an automated translation tool (Amazon Translate).

Street segment in the City of Repentigny.This third party metadata element was translated using an automated translation tool (Amazon Translate).

Overview

This dataset contains all DOMI Street Closure Permit data in the Computronix (CX) system from the date of its adoption (in May 2020) until the present. The data in each record can be used to determine when street closures are occurring, who is requesting these closures, why the closure is being requested, and for mapping the closures themselves. It is updated hourly (as of March 2024).

Preprocessing/Formatting

It is important to distinguish between a permit, a permit's street closure(s), and the roadway segments that are referenced to that closure(s).

• The CX system identifies a street in segments of roadway. (As an example, the CX system could divide Maple Street into multiple segments.)

• A single street closure may span multiple segments of a street.

• The street closure permit refers to all the component line segments.

• A permit may have multiple streets which are closed. Street closure permits often reference many segments of roadway.

The roadway_id field is a unique GIS line segment representing the aforementioned segments of road. The roadway_id values are assigned internally by the CX system and are unlikely to be known by the permit applicant. A section of roadway may have multiple permits issued over its lifespan. Therefore, a given roadway_id value may appear in multiple permits.

The field closure_id represents a unique ID for each closure, and permit_id uniquely identifies each permit. This is in contrast to the aforementioned roadway_id field which, again, is a unique ID only for the roadway segments.

City teams that use this data requested that each segment of each street closure permit be represented as a unique row in the dataset. Thus, a street closure permit that refers to three segments of roadway would be represented as three rows in the table. Aside from the roadway_id field, most other data from that permit pertains equally to those three rows. Thus, the values in most fields of the three records are identical.

Each row has the fields segment_num and total_segments which detail the relationship of each record, and its corresponding permit, according to street segment. The above example produced three records for a single permit. In this case, total_segments would equal 3 for each record. Each of those records would have a unique value between 1 and 3.

The geometry field consists of string values of lat/long coordinates, which can be used to map the street segments.

All string text (most fields) were converted to UPPERCASE data. Most of the data are manually entered and often contain non-uniform formatting. While several solutions for cleaning the data exist, text were transformed to UPPERCASE to provide some degree of regularization. Beyond that, it is recommended that the user carefully think through cleaning any unstructured data, as there are many nuances to consider. Future improvements to this ETL pipeline may approach this problem with a more sophisticated technique.

Known Uses

These data are used by DOMI to track the status of street closures (and associated permits).

Further Documentation and Resources

An archived dataset containing historical street closure records (from before May of 2020) for the City of Pittsburgh may be found here: https://data.wprdc.org/dataset/right-of-way-permits

The City of Bend road centerline data plays a key role in many business processes. This line feature class represents the current road centerline network. Road centerlines are updated as needed based on private and public development. For more details regarding the City of Bend authority on road names and standards please see the Bend Code Chapter 3.90. Bend Code Chapter 3.90.Field Name DescriptionOBJECTIDFor internal useCENTERLINEIDFor internal useFROMLEFTFrom value for the address range on the left side of the street segment, relative to the digitized direction of the segmentTOLEFTTo value for the address range on the left side of the street segment, relative to the digitized direction of the segmentFROMRIGHTFrom value for the address range on the right side of the street segment, relative to the digitized direction of the segmentTORIGHTTo value for the address range on the right side of the street segment, relative to the digitized direction of the segmentFULLNAMEFull road name. FEDROUTEFederal route type codeFEDRTETYPEFederal route type descriptionAFEDRTEAlternative federal route type codeAFEDRTETYPEAlternative federal route type descriptionSTROUTEState route type codeSTRTETYPEFederal route type descriptionASTRTEAlternative state route type codeASTRTETYPEAlternative state route type description. CTYROUTECounty route type descriptionONEWAYDIROne way indicatorROADCLASSFunctional road class as determined by the current Transportation System PanMTFCCCensus MTFCC CodeMUNILEFTMunicipality for the left side of the street segment, relative to the digitized direction of the segmentMUNIRIGHTMunicipality for the right side of the street segment, relative to the digitized direction of the segmentSTATELEFTState for the left side of the street segment, relative to the digitized direction of the segmentSTATERIGHTState for the right side of the street segment, relative to the digitized direction of the segmentZIPLEFTFive-digit postal zip code for the left side of the street segment, relative to the digitized direction of the segmentZIPRIGHTFive-digit postal zip code for the right side of the street segment, relative to the digitized direction of the segmentMSAGLEFTMaster street address guide for the left side of the street segment, relative to the digitized direction of the segmentMSAGRIGHTMaster street address guide for the right side of the street segment, relative to the digitized direction of the segmentESNLEFTEmergency service number for the left side of the street segment, relative to the digitized direction of the segmentESNRIGHTEmergency service number for the right side of the street segment, relative to the digitized direction of the segmentCOUNTYIDFor internal useSTATUSCurrent road status descriptionOWNERRoad ownership descriptionBLOCKIDFor internal useSHAPEFor internal usecreated_userFor internal usecreated_dateFor internal uselast_edited_userFor internal uselast_edited_dateFor internal useGlobalIDFor internal useSHAPE.STLength()For internal useData updated nightly.

This dataset refers to a deprecated parking management solution.

It contains each Pay Stay zone and the street segment that it is linked to. The Pay Stay zone can go across multiple street segments and also one street segment can have multiple Pay Stay zones.

This data can be linked to both the sign plate Pay Stay zone dataset.
https://data.melbourne.vic.gov.au/explore/dataset/sign-plates-located-in-each-pay-stay-zone/information/
and also the Pay Stay parking restrictions dataset
https://data.melbourne.vic.gov.au/explore/dataset/pay-stay-parking-restrictions/information/
The datasets can be joined on Pay Stay zone.

To create a spatial dataset the street segment can be joined with the road corridor dataset on the street segment id.
https://data.melbourne.vic.gov.au/explore/dataset/road-corridors/information/

For further information on Pay Stay https://www.paystay.com.au/

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

The Los Angeles Clean Streets Index, the first-of-its-kind, is a grading system of every street in Los Angeles. The Bureau of Sanitation drove and scored over 9,000 miles of streets and alleys - each segment received a "cleanliness score" from 1-3. Each street score is based on four factors: litter, weeds, bulky items and illegal dumping. This assessment will be repeated every quarter. Los Angeles is leading the way as the only big city in the US conducting a regular cleanliness assessment of every City street.

List of streets by block (street segment) accepted for maintenance