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.

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.

This dataset depicts Right of Ways for private developments in the Town of Mammoth Lakes, CA

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

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

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. This dataset is not complete.

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

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

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.

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.

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 dataset contains data about the City of Bellevue public right-of-way. This data is updated as needed to support city operations.

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.

Table containing an object describing the right-of-way and the useful characteristics of the flood-risk territory. Spatial data set produced by the GIS High Flood Risk Land Flood Directive (TRI) of... and mapped for reporting purposes for the European Flood Directive. European Directive 2007/60/EC of 23 October 2007 on the assessment and management of flood risks (OJ L 288, 06-11-2007, p. 27) influences the flood prevention strategy in Europe. It requires the production of flood risk management plans to reduce the negative consequences of flooding on human health, the environment, cultural heritage and economic activity. The objectives and implementation requirements are set out in the Law of 12 July 2010 on the National Commitment for the Environment (LENE) and the Decree of 2 March 2011. In this context, the primary objective of flood and flood risk mapping for IRRs is to contribute, by homogenising and objectivating knowledge of flood exposure, to the development of flood risk management plans (WRMs). This dataset is used to produce flood surface maps and flood risk maps that represent flood hazards and issues at an appropriate scale, respectively. Their objective is to provide quantitative evidence to further assess the vulnerability of a territory for the three levels of probability of flooding (high, medium, low).

The geo-spatial data was primarily created from the conversion land surveying records and data. The data was created for internal use during the acquisition of additional Right of Way parcels and to aide in the location of the Right of Way during construction and maintenance. It was also created for the Public to be more completely informed how a project may impact their property or the area they live in. The descriptive or status data information for each parcel or tract of land is from the TxDOT Right of Way Information System database (ROWIS) and is updated daily at Midnight). Additions to the geo-spatial data are made on an ongoing basis and become available after one of the two daily updates.

Landsat Path Row Map

Freebase is amongst the largest public cross-domain knowledge graphs. It possesses three main data modeling idiosyncrasies. It has a strong type system; its properties are purposefully represented in reverse pairs; and it uses mediator objects to represent multiary relationships. These design choices are important in modeling the real-world. But they also pose nontrivial challenges in research of embedding models for knowledge graph completion, especially when models are developed and evaluated agnostically of these idiosyncrasies. We make available several variants of the Freebase dataset by inclusion and exclusion of these data modeling idiosyncrasies. This is the first-ever publicly available full-scale Freebase dataset that has gone through proper preparation.

Dataset Details The dataset consists of the four variants of Freebase dataset as well as related mapping/support files. For each variant, we made three kinds of files available:

Subject matter triples file

fb+/-CVT+/-REV One folder for each variant. In each folder there are 5 files: train.txt, valid.txt, test.txt, entity2id.txt, relation2id.txt Subject matter triples are the triples belong to subject matters domains—domains describing real-world facts.

Example of a row in train.txt, valid.txt, and test.txt:

2, 192, 0 Example of a row in entity2id.txt:

/g/112yfy2xr, 2 Example of a row in relation2id.txt:

/music/album/release_type, 192 Explaination

"/g/112yfy2xr" and "/m/02lx2r" are the MID of the subject entity and object entity, respectively. "/music/album/release_type" is the realtionship between the two entities. 2, 192, and 0 are the IDs assigned by the authors to the objects. Type system file

freebase_endtypes: Each row maps an edge type to its required subject type and object type.

Example

92, 47178872, 90 Explanation

"92" and "90" are the type id of the subject and object which has the relationship id "47178872". Metadata files

object_types: Each row maps the MID of a Freebase object to a type it belongs to.

Example

/g/11b41c22g, /type/object/type, /people/person Explanation

The entity with MID "/g/11b41c22g" has a type "/people/person" object_names: Each row maps the MID of a Freebase object to its textual label.

Example

/g/11b78qtr5m, /type/object/name, "Viroliano Tries Jazz"@en Explanation

The entity with MID "/g/11b78qtr5m" has name "Viroliano Tries Jazz" in English. object_ids: Each row maps the MID of a Freebase object to its user-friendly identifier.

Example

/m/05v3y9r, /type/object/id, "/music/live_album/concert" Explanation

The entity with MID "/m/05v3y9r" can be interpreted by human as a music concert live album. domains_id_label: Each row maps the MID of a Freebase domain to its label.

Example

/m/05v4pmy, geology, 77 Explanation

The object with MID "/m/05v4pmy" in Freebase is the domain "geology", and has id "77" in our dataset. types_id_label: Each row maps the MID of a Freebase type to its label.

Example

/m/01xljxh, /government/political_party, 147 Explanation

The object with MID "/m/01xljxh" in Freebase is the type "/government/political_party", and has id "147" in our dataset. entities_id_label: Each row maps the MID of a Freebase entity to its label.

Example

/g/11b78qtr5m, Viroliano Tries Jazz, 2234 Explanation

The entity with MID "/g/11b78qtr5m" in Freebase is "Viroliano Tries Jazz", and has id "2234" in our dataset. properties_id_label: Each row maps the MID of a Freebase property to its label.

Example

/m/010h8tp2, /comedy/comedy_group/members, 47178867 Explanation

The object with MID "/m/010h8tp2" in Freebase is a property(relation/edge), it has label "/comedy/comedy_group/members" and has id "47178867" in our dataset. uri_original2simplified and uri_simplified2original: The mapping between original URI and simplified URI and the mapping between simplified URI and original URI repectively.

Example

uri_original2simplified

"http://rdf.freebase.com/ns/type.property.unique": "/type/property/unique" uri_simplified2original

"/type/property/unique": "http://rdf.freebase.com/ns/type.property.unique" Explanation

The URI "http://rdf.freebase.com/ns/type.property.unique" in the original Freebase RDF dataset is simplified into "/type/property/unique" in our dataset. The identifier "/type/property/unique" in our dataset has URI http://rdf.freebase.com/ns/type.property.unique in the original Freebase RDF dataset.

ADMMR map collection: Plat Showing Right-of-Way Required by Mascot & Western Railroad Company Over Property of Roy Klump; 1 in. to 400 feet; 17 x 15 in.