Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Right of Way Scan. Right of Way Distribution Maps, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Scans provided by DDOT identified rights of way locations which were best fit to road planimetrics.
Street right of way polygons are public spaces along the DC managed street segments. A database provided by DDOT identified ROW locations from authoritative source documentation including DDOT surface maps, ROW distribution cards, Subdivision Books in the DC Surveyor's Office, Survey Books, King Plats, Record Books, Street Extension Maps, County Maps, AT Map Books, Wall Books and Wall Reports.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A line feature class of Right Of Way (ROW) lines within Miami-Dade County. This data was derived from the ROW polygon 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
This data is intended as a reference material of street and alley vacations, but not designed for survey, accurate positioning, or legal documents. It is created as polygon feature class, vacation information based on field measurements, types of Right of Way, and citations of Journal of the Common Council (J.C.C.) and the plat Liber and Page is listed under the column titled 'Sub_Plat'. The paper maps of the Street and Alley Vacation, the raster layer version of those maps (Linen Map Markup Mosaic), and the Detroit parcel layer are used as base maps to create this data.
The street and alley vacations were recorded from 1831 to 2022 throughout the whole city, and it will be updated weekly. The existed and/or active street and alley vacations are ready to view, the authors are working on pending and historical records.
Spatial Reference: WGS 1984 Web Mercator Auxiliary Sphere
Attribution-ShareAlike 4.0 (CC BY-SA 4.0)https://creativecommons.org/licenses/by-sa/4.0/
License information was derived automatically
This dataset depicts Right of Ways for private developments in the Town of Mammoth Lakes, CA
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
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This polyline feature class contains the Inventory of Right of Way for Hillsborough County excluding Cities and Platted Areas.The drawings that make up the Hillsborough County Right of Way Inventory Program show platting, recording, mapping or other sources of right of way information where available. In areas where the maintained right of way limits were spotted and field data collected, the drawings provide that line work in the layer (Sv-rdrw-mant-lin, the "orange" layer) as located, in NAD 83 Adjustment of 1990 SPC grid. The field location documentation for the limits of maintained right of way layer is referenced in a separate XLS file with information as to when and by whom the limits of maintenance were spotted. The limits of maintained right of way are required to be used in the preparation of plats made to be recorded in Hillsborough County. In the case of right of way that is depicted in “modern plats” the State Plane Co-ordinate data shown on plats was used to incorporate these plats into the Hillsborough County Right of Way Inventory drawings.Definitions of Right of Way as used in the Hillsborough County Right of Way Inventory:1.) Right of Way by Deed - Right of Way Owned by Hillsborough County by a recorded deed specifically to Hillsborough County.2.) Right of Way by Plat - Right of Way that has been dedicated by a recorded subdivision plat.3.) Right of Way by Deed Exception - Right of Way whereby specific footage has been explicitly exempted from a deed.4.) Right of Way by Property Line - Right of Way whereby the property line defined by a deed follows the same line as the right of way so that both lines are co-incident.5.) Limits of Maintenance – The physical limits of the maintenance of a road as delineated by the Road and Street maintenance division of the Public Works Department, where no other right of way dedication exists or where the maintenance limits exceed the described property lines in a significant manner.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Map provides access to right-of-ways plats and corner recordation. Sections of land that have DOT right-of-way plats tied to them are highlighted in green. Townships that have the corner recordation information tied to them and are highlighted in pink. Use the identify button and "selection toggle" to view the plats and recordations contained in the system.
Constraints:
Not to be used for navigation, for informational purposes only. See full disclaimer for more information
This dataset represents the cadastral maps created by the Geomatics branch in support of real property acquisitions within the Department of Water Resources. The geographic extent of each map frame was created after using all the spatial attributes available in each map to appropriately georeference it and create the extents from the outer frame of the map. The maps were digitally scanned from the original paper format that were archived after moving to the new resources building. As new maps are created by the branch for real property acquisition services, they will be georeference, attributed and updated into this dataset. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.6, dated September 27, 2023. DWR makes no warranties or guarantees either expressed or implied as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Original internal source projection for this dataset was Teale Albers/NAD83. For copies of data in the original projection, please contact DWR. Comments, problems, improvements, updates, or suggestions should be forwarded to gis@water.ca.gov as available and appropriate.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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).
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.
These data are used by DOMI to track the status of street closures (and associated permits).
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
Drainage data is provided by Miami Dade County to FDOT District 6. The data (structures and pipes) is clipped to 100 foot buffer of the state road center line. Attribute data is collected by Miami Dade County. Updates are made on a quarterly basis.
A right of way is a legal right to travel over land belonging to someone else. Right of ways are used in the planning, construction, and other major phases of road development. Because right of way plays an integral role in road development, the Nebraska Department of Transportation maintains a database of rights of way in the State of Nebraska. The right of way feature contains both lines and polygons representing rights of way in Nebraska, as well as containing useful information about the property, road project, and location. The right of way application can make finding rights of way easier with built in tools for finding road projects, section quadrangles, mile markers, communities, and districts.
This dataset seeks to encapsulate right of way parcel information for the Los Angeles County Flood Control District(LACFCD). It contains polygons representing each parcel and attribute information information that lists the basic identification information of those parcels. There is also information on the underlying right-of-way map that the parcel polygon and attributes are based on--with a link to that map in the Land Records Information Website.This data is maintained by the Right of Way Section of the Survey/Mapping and Property Management Division of the Department of Public Works. It is drawn to be coincident with the county's landbase linework and thus may not be a true representation of a parcel's boundary. It is intended to be used as a general information tool and is not survey quality.Field ListFacilityThe primary name of the facility this parcel belongs to. Typically the name of the river, stream, or drainage project it is a part of.Parcel_NoThe identification number for a particular parcel within a facility. The parcel number is not necessarilly unique.EstateThe type of estate that the LACFCD holds over a particular parcel. This field will list the following attributes:Fee: The LACFCD owns the parcel outright.Easement: The LACFCD holds an easement over this parcel. The type of easement is not listed in this data. It can usually be found in the linked right of way map or by contacting Right of Way Engineering.Quitclaim: This is a parcel which the LACFCD owned or had an easement over at some point but has now sold, released its claim, or transferred its right of way to another party.Other: This is a catch-all attribute for any sort of relationship that does not fit in the other estate types. One example of this is a permit that grants temporary rights to the LACFCD. Map_NoThe primary right of way map that shows a parcel and that served as the basis for the information shown in the dataset. These maps are maintained and are considered to take precedence over the data in this dataset.MapLinkThis is a link to a a scan of the map, if one exists, listed in the "Map_No" field. These are color scans found in the LA County's Land Records Information Website. Update Schedule: QuarterlyContact Info:Diego Veradvera@dpw.lacounty.gov(626) 458-7368Right of Way SectionSurvey/Mapping and Property Management DivisionDepartment of Public Works
Open in: [Superset)] [ArcGIS] or [Request format]Open in: [Superset)] or [Request format]The Act51 Map Layer represents the road network that the City of Detroit reports to the Michigan Department of Transportation on a annual basis. The Act51 Map Layer identifies road jurisdictions for permitting and planning.Public Act 51 of 1951 created the Michigan Transportation Fund (MTF), and it is the main road funding source for most cities and villages. This Act defines the formula by which Michigan distributes money for road maintenance to cities, villages, and counties.Under Act 51, county roads can be classified as either primary or local roads. City and village streets can be classified as either major or local streets. Primary roads and major streets are selected by the counties, cities and villages on the basis of the greatest general importance to each respective local agency.
Right-of-Way (General) displays the general extent of rights-of-way for the City and County of Denver.
A spatial representation of a subset of parcel features that contain special use characteristics. This polygon feature class is maintained in a geodatabase using topology with the TaxParcel feature class. The key attribute is AccessType, which describes the type of access (Prescriptive, Dedicated, or Private) on the feature.
© Oakland County, MI
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset represents the cadastral maps created by the Geomatics branch in support of real property acquisitions within the Department of Water Resources. The geographic extent of each map frame was created after using all the spatial attributes available in each map to appropriately georeference it and create the extents from the outer frame of the map. The maps were digitally scanned from the original paper format that were archived after moving to the new resources building. As new maps are created by the branch for real property acquisition services, they will be georeference, attributed and updated into this dataset. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.6, dated September 27, 2023. DWR makes no warranties or guarantees either expressed or implied as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Original internal source projection for this dataset was Teale Albers/NAD83. For copies of data in the original projection, please contact DWR. Comments, problems, improvements, updates, or suggestions should be forwarded to gis@water.ca.gov as available and appropriate.
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.
© 2017, County of Santa Clara
This layer is a component of SCCMap1.
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
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Right of Way Scan. Right of Way Distribution Maps, created as part of the DC Geographic Information System (DC GIS) for the D.C. Office of the Chief Technology Officer (OCTO) and participating D.C. government agencies. Scans provided by DDOT identified rights of way locations which were best fit to road planimetrics.