The Right of Way Map Footprint is a GIS data set created to represent the outer footprint or extent of a right of way map (including footprints for both Vector (CAD) and Raster Images). The purpose is to aid the user in more rapidly identifying the desired map for a specific area of interest relative to other maps, roads, landmarks, etc. This data set is developed and maintained on a statewide basis. It does not include geo-referenced representations of right of way maps themselves.

An area depicting a privilege to pass over the land of another in some particular path; usually an easement over the land of another; a strip of land used in this way for railroad and highway purposes, for pipelines or pole lines and for private and public passage. Metadata

This line layer contains centerlines of all paved and unpaved roads, ramps, and bridges in the City of Cambridge. Each centerline segment contains attributes including street name, street type, address ranges, and one-way designations.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription ID type: Stringwidth: 40precision: 0 Unique identifier for each street segment

ROADWAYS type: Stringwidth: 1precision: 0 Divided street designation

ValueDescription TDivided FNot divided

Street type: Stringwidth: 40precision: 0 Full street name with street type

Street_Name type: Stringwidth: 30precision: 0 Street name only

Street_Type type: Stringwidth: 10precision: 0 Street type

Street_ID type: Doublewidth: 8precision: 38 Street ID number from master address database

Alias type: Stringwidth: 50precision: 0 Alternate street name

L_From type: Integerwidth: 4precision: 10 Left side address range 'from'

L_To type: Integerwidth: 4precision: 10 Left side address range 'to'

R_From type: Integerwidth: 4precision: 10 Right side address range 'from'

R_To type: Integerwidth: 4precision: 10 Right side address range 'to

FromNode type: Doublewidth: 8precision: 38 New 'from node' number

ToNode type: Doublewidth: 8precision: 38 New 'to node' number

Direction type: Stringwidth: 5precision: 0 One-way designation

ValueDescription 0Two-way street segment 1One-way street in same direction as street segment -1One-way street in opposite direction of street segment

Restriction type: Stringwidth: 1precision: 0 Truck restriction designation

Label type: Stringwidth: 50precision: 0 Street name field for labels when mapping

MajorRoad type: SmallIntegerwidth: 2precision: 5 Major road designation

ZIP_Left type: Stringwidth: 8precision: 0 Left side zip code

ZIP_Right type: Stringwidth: 8precision: 0 Right side zip code

EditDate type: Stringwidth: 4precision: 0 Date of last edit

Potential_L_From type: Integerwidth: 4precision: 10 Potential left side address range 'from'

Potential_L_To type: Integerwidth: 4precision: 10 Potential left side address range 'to'

Potential_R_From type: Integerwidth: 4precision: 10 Potential right side address range 'from'

Potential_R_To type: Integerwidth: 4precision: 10 Potential right side address range 'to'

Potentail_Range_Done type: SmallIntegerwidth: 2precision: 5 Potential range researched and populated

created_date type: Datewidth: 8precision: 0

last_edited_date type: Datewidth: 8precision: 0

The City of Mercer Island GIS base map data for public download (base map, map grid, address, building, property line, parcel line, docks, right-of-way, trails, parks, street, road edge, city boundary)

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

This is a publicly available map image service with limited GIS attributes. A downloadable version of this data is now available through the MDOT GIS Open Data Portal: Download MDOT SHA Right-of-Way Polygons (Open Data Portal) The following related versions of this data are available here:MDOT SHA Right-of-Way (Secured)Line dataFull attribute tableAccessible to only MDOT employees and contractors upon requestMDOT SHA Right-of-Way (Map Image Service)Read-only map serviceLine dataLimited attributes (quality level)Accessible to publicMDOT SHA Right-of-Way data is a composite layer of PSD field-collected survey sources, PSD in-house computations, traced PSD hardcopy materials, and historical Maryland Department of Planning (MDP) parcel boundaries.This data product was intended to replace MDOT SHA Planning Level Right-of-Way (Tax Map Legacy), which is an increasingly obsolete legacy product for MDOT SHA Right-of-Way information that in some areas remains the most comprehensive. For continuity, many MDP parcel boundaries found in MDOT SHA Planning Level Right-of-Way (Tax Map Legacy) have been incorporated into MDOT SHA Right-of-Way data with an "Estimated" quality level. Please see below for a description of the primary attribute.-----------------------------------------------------The polygons in this layer are divided into 318 arbitrary grid zones across the State of Maryland. Updates to the parent ROW boundary line data set [MDOT SHA Right-of-Way (Secured)] are made by grid and reflected in this polygon layer.For more information or to report errors in this data, please contact MDOT SHA OIT Enterprise Information Services:Email: GIS@mdot.maryland.gov

This mapping tool provides a representation of the general watershed boundaries for stream systems declared fully appropriated by the State Water Board. The boundaries were created by Division of Water Rights staff by delineating FASS critical reaches and consolidating HUC 12 sub-watersheds to form FASS Watershed boundaries. As such, the boundaries are in most cases conservative with respect to the associated stream system. However, users should check neighboring FASS Watersheds to ensure the stream system of interest is not restricted by other FASS listings. For more information regarding the Declaration of Fully Appropriated Stream Systems, visit the Division of Water Rights’ Fully Appropriated Streams webpage. How to Use the Interactive Mapping Tool: If it is your first time viewing the map, you will need to click the “OK” box on the splash screen and agree to the disclaimer before continuing. Navigate to your point of interest by either using the search bar or by zooming in on the map. You may enter a stream name, street address, or watershed ID in the search bar. Click on the map to identify the location of interest and one or more pop-up boxes may appear with information about the fully appropriated stream systems within the general watershed boundaries of the identified location. The information provided in the pop-up box may include: (a) stream name, (b) tributary, (c) season declared fully appropriated, (d) Board Decisions/Water Right Orders, and/or (e) court references/adjudications. You may toggle the FAS Streams reference layer on and off to find representative critical reaches associated with the FASS Watershed layer. Please note that this layer is for general reference purposes only and ultimately the critical reach listed in Appendix A of Water Rights Order 98-08 and Appendix A together with any associated footnotes controls. Note: A separate FAS Watershed boundary layer was created for the Bay-Delta Watershed. The Bay-Delta Watershed layer should be toggled on to check if the area of interest is fully appropriated under State Water Board Decision 1594.

A polygon feature class of Right Of Way (ROW) boundaries within Miami-Dade County. This data was derived from the Lot layer and is maintain in the Esri Parcel Fabric (PF) data model.Updated: Not Planned The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A visual representation of street right-of-way boundaries within Santa Clara County. THE GIS DATA IS PROVIDED "AS IS". THE COUNTY MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OR MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE ACCURACY, COMPLETENESS, VALUE, QUALITY, VALIDITY, MERCHANTABILITY, SUITABILITY, AND CONDITION, OF THE GIS DATA. USER'S OF COUNTY'S GIS DATA ARE HEREBY NOTIFIED THAT CURRENT PUBLIC PRIMARY INFORMATION SOURCES SHOULD BE CONSULTED FOR VERIFICATION OF THE DATA AND INFORMATION CONTAINED HEREIN. SINCE THE GIS DATA IS DYNAMIC, IT WILL BY ITS NATURE BE INCONSISTENT WITH THE OFFICIAL COUNTY DATA. ANY USE OF COUNTY'S GIS DATA WITHOUT CONSULTING OFFICIAL PUBLIC RECORDS FOR VERIFICATION IS DONE EXCLUSIVELY AT THE RISK OF THE PARTY MAKING SUCH USE.

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.

Existing ROW layer was created by contacting county assessor's offices and based off of parcel data received from them. Each county has different levels of accuracy. If a county did not have a GIS parcel dataset, ERMS was utilized. Strip maps were pulled from ERMS, georectified, and traced over to created the boundary.