Disclaimer of Liability: The user of this application and data assumes all responsibility and risk for the use of both. Under no circumstances, including negligence, shall the Nevada Department of Transportation, or its employees be liable for any DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY or CONSEQUENTIAL DAMAGES, or LOST PROFITS that result from the use, misuse, or inability to use the application and data. Nor shall the Nevada Department of Transportation, or its employees be liable for any damages resulting from or related to reliance, mistakes, omissions, interruptions, deletion of files, computer viruses, errors, defects, or any failure of performance, communications failure, theft, destruction or unauthorized access to the application and data.

Public view of the parcel layer. This view is limited to only the attributes that can be seen by the general public.The data table includes the following fields: Shape Type (Shape), Shape.STArea() (Shape_Area), Shape.STLength() (Shape_Area), Name (APN), Created By Record (CreatedbyR), Retired By Record (RetiredbyR), Stated Area, Stated Area Unit (StatedAr_1), Calculated Area (Calculated), Misclose Ratio (MiscloseRa), Misclose Distance (MiscloseDi), Is Seed (IsSeed), Created By (created_us), Created Date (created_da), Modified By (last_edite), Modified Date (last_edi_1), Validation Status (VALIDATION), APN Dashed (APN_Dashed), Map Page (Map_Page), Municipality (Municipali), FloorOrder, HideThere are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.

Right of Way maintenance check log

This web map created by the Colorado Governor's Office of Information Technology GIS team, serves as a basemap specific to the state of Colorado. The basemap includes general layers such as counties, municipalities, roads, waterbodies, state parks, national forests, national wilderness areas, and trails.Layers:Layer descriptions and sources can be found below. Layers have been modified to only represent features within Colorado and are not up to date. Layers last updated February 23, 2023. Colorado State Extent: Description: “This layer provides generalized boundaries for the 50 States and the District of Columbia.” Notes: This layer was filtered to only include the State of ColoradoSource: Esri Living Atlas USA States Generalized Boundaries Feature LayerState Wildlife Areas:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state wildlife areas layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer hosted in ArcGIS Online Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerMunicipal Boundaries:Description: "Boundaries data from the State Demography Office of Colorado Municipalities provided by the Department of Local Affairs (DOLA)"Source: Colorado Information Marketplace Municipal Boundaries in ColoradoCounties:Description: “This layer presents the USA 2020 Census County (or County Equivalent) boundaries of the United States in the 50 states and the District of Columbia. It is updated annually as County (or County Equivalent) boundaries change. The geography is sources from US Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrology to add a detailed coastline for cartographic purposes. Geography last updated May 2022.” Notes: This layer was filtered to only include counties in the State of ColoradoSource: Esri USA Census Counties Feature LayerInterstates:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: Interstates are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointU.S. Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: U.S. Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointState Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: State Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointMajor Roads:Description: Authoritative data from the Colorado Department of Transportation representing major roads Source: Colorado Department of Transportation Major Roads REST EndpointLocal Roads:Description: Authoritative data from the Colorado Department of Transportation representing local roads Source: Colorado Department of Transportation Local Roads REST EndpointRail Lines:Description: Authoritative data from the Colorado Department of Transportation representing rail lines Source: Colorado Department of Transportation Rail Lines REST EndpointCOTREX Trails:Description: “The Colorado Trail System, now titled the Colorado Trail Explorer (COTREX), endeavors to map every trail in the state of Colorado. Currently their are nearly 40,000 miles of trails mapped. Trails come from a variety of sources (USFS, BLM, local parks & recreation departments, local governments). Responsibility for accuracy of the data rests with the source.These data were last updated on 2/5/2019” Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerNHD Waterbodies:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include waterbodies in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerNHD Flowlines:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include flowline features in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerState Parks:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state parks layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerDenver Parks:Description: "This dataset should be used as a reference to locate parks, golf courses, and recreation centers managed by the Department of Parks and Recreation in the City and County of Denver. Data is based on parcel ownership and does not include other areas maintained by the department such as medians and parkways. The data should be used for planning and design purposes and cartographic purposes only."Source: City and County of Denver Parks REST EndpointNational Wilderness Areas:Description: “A parcel of Forest Service land congressionally designated as wilderness such as National Wilderness Area.”Notes: This layer was filtered to only include National Wilderness Areas in the State of ColoradoSource: United States Department of Agriculture National Wilderness Areas REST EndpointNational Forests: Description: “A depiction of the boundaries encompassing the National Forest System (NFS) lands within the original proclaimed National Forests, along with subsequent Executive Orders, Proclamations, Public Laws, Public Land Orders, Secretary of Agriculture Orders, and Secretary of Interior Orders creating modifications thereto, along with lands added to the NFS which have taken on the status of 'reserved from the public domain' under the General Exchange Act. The following area types are included: National Forest, Experimental Area, Experimental Forest, Experimental Range, Land Utilization Project, National Grassland, Purchase Unit, and Special Management Area.”Notes: This layer was filtered to only include National Forests in the State of ColoradoSource: United States Department of Agriculture Original Proclaimed National Forests REST Endpoint

This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

This layer contains the boundaries and IDs of the Maryland tax maps produced by Maryland Department of Planning. Tax maps, also known as assessment maps, property maps or parcel maps, are a graphic representation of real property showing and defining individual property boundaries in relationship to contiguous real property.This is a MD iMAP hosted service layer. Find more information at https://imap.maryland.gov.Feature Service Layer Link:https://geodata.md.gov/imap/rest/services/PlanningCadastre/MD_PropertyData/MapServer/2

[Metadata] Description: Streets for the island of Oahu only as of August 2024.Source: Hawaii Statewide GIS staff downloaded from Honolulu Land Information System (HOLIS), C&C of Honolulu, September 26, 2024.For additional information, please refer to complete metadata at https://files.hawaii.gov/dbedt/op/gis/data/streets_oah.pdf or contact Hawaii Statewide GIS Program, Office of Planning and Sustainable Development, State of Hawaii; PO Box 2359, Honolulu, HI 96804; (808) 587-2846; email: gis@hawaii.gov; Website: https://planning.hawaii.gov/gis.NOTE: This layer is maintained by the C&C of Honolulu HOLIS. It is provided on the State of Hawaii GIS ArcGIS Online and downloading sites as a service to the public. Data is downloaded from the C&C website periodically. To obtain the latest version of the Oahu Street Centerline layer, users should visit the HOLIS Open Geospatial Data Portal at https://honolulu-cchnl.opendata.arcgis.com/.

This line feature class shows road centerlines in Deschutes County.

This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

All roads in Grey County. Intersection-to-intersection segments are continuously updated monthly to maintain accurate addressing. Captured at various scales from 1:5000 - 1:20,000 depending on location and jurisdiction. Original source data derived from Ontario Ministry of Natural Resources and Forestry Ontario Road Network (ORN).
Field Name Alias Data Type Description

OBJECTID OBJECTID Object ID GIS Unique identifier

ROAD_NAME ROAD NAME Text Full official road name composed of individual street name components where present, including street name body, street type suffix and directional suffix.

ROAD_NAME_ABBR ROAD NAME ABBREVIATED Text Abbreviated version of road name (E.g. 10th Ave E instead of 10th Avenue East)

ALT_NAME ALTERNATE NAME Text Full alternate road name. This is typically county or provincial highways when a local municipality street name is provided as the official road name. Should be null if no alternate name exists

STREET_NAM STREET_NAM Text Street name body only, the identifying named component of a street name

STREET_TYP STREET_TYP Text Street type (non-abbreviated)

STREET_TYP_SHORT STREET TYPE SHORT Text Street type (abbreviated)

STREET_DIR STREET_DIR Text Street direction (non-abbreviated)

STREET_DIR_SHORT STREET DIRECTION SHORT Text Street direction (abbreviated)

STREET_CLA STREET_CLA Short Street class used to facilitate mapping. Values can be Highways (1), County roads (2), Municipal roads (3), Unmaintained roads (4) and Roads under construction (5)

L_F_ADD L_F_ADD Long Left - From address range

L_T_ADD L_T_ADD Long Left - To address range

R_F_ADD R_F_ADD Long Right - From address range

R_T_ADD R_T_ADD Long Right - To address range

VERIFY VERIFY Short Unchanged (0), or Changed/updated (1). Values of 1 have underwent a modification since data inception, and should have a change log description in the VERIFY_COM field

VERIFY_COM VERIFY_COM Text Logged comments to describe changes to road data during verification

DATE_ADD DATE_ADD Date Date road created in geodatabase. Initialize date was 1/1/2004

HWY_NUM HWY_NUM Text MTO Highway Number

GREYRD_NUM GREYRD_NUM Text Grey Road Number

EDITOR EDITOR Text Last user who edited data

CLOSE_DETR CLOSURE DETOURS Text Roads that are suitable or not suitable for public traffic detours, completed in NOV2013, only those not suitable for detours have been captured. One record marked partial - not Minto-Normanby townline is not passable from Sideroad 25 to Ski Road (Wellington Co.)

EDIT_DATE EDIT_DATE Date Last time data was edited

JURIS_L LEFT JURISDICTION Text Road owner and authority having jurisdiction, who issues permits for the road left segment. May be governed by MTO connecting link or boundary agreement

JURIS_R RIGHT JURISDICTION Text Road owner and authority having jurisdiction, who issues permits for the road right segment. May be governed by MTO connecting link or boundary agreement

MUNICIPAL_L LEFT MUNICIPALITY Text Lower Tier Municipality, determined by the traversal from the "L_F_ADD" to the "L_T_ADD"

MUNICIPAL_R RIGHT MUNICIPALITY Text Lower Tier Municipality, determined by the traversal from the "R_F_ADD" to the "R_T_ADD"

MUN911_L LEFT 911 MUN SHORT Text 3 character municipal name used for 911 CAD, abbreviated version of MUNICIPAL_L.

MUN911_R RIGHT 911 MUN SHORT Text 3 character municipal name used for 911 CAD, abbreviated version of MUNICIPAL_R.

PARITY_L LEFT PARITY Text The even or odd property of the address number range on the Left side of the road segment relative to the FROM address: O=Odd; E=Even; B=Both

PARITY_R RIGHT PARITY Text The even or odd property of the address number range on the Right side of the road segment relative to the FROM address: O=Odd; E=Even; B=Both

ORN_ROAD_CLASS ORN ROAD CLASS Short Road classification per ORN

PAVED_STATUS PAVED STATUS Short Paved (1), Unpaved (2)

DIR_OF_TRAFFIC_FLOW DIR OF TRAFFIC FLOW Short The direction(s) of vehicular or motor traffic flow. Both (1), Positive (2), Negative (3)

MAINT_SUMMER MAINTENANCE SUMMER Text Jurisdiction responsible for summer maintenance

MAINT_WINTER MAINTENANCE WINTER Text Jurisdiction responsible for winter maintenance

MAINT_AGREEMENT MAINTENANCE AGREEMENT Text The agreement record that outlines seasonal maintenance responsibilities (Alfresco/sharepoint url)

BOUNDARY_ROAD BOUNDARY ROAD Text Indicates if a road segment runs along a municipal or county boundary (Yes/No)

ROAD_LENGT ROAD LENGTH (m) Double Length of Road Segment in meters. Geometry of line segment calculated in GIS with UTM NAD83 Zone 17N coordinate system

LANE_COUNT LANE COUNT Short Number of Lanes

SPEED_LIMI SPEED LIMIT Short Speed limit in km/h

Shape Shape Geometry Auto generated line geometry in GIS

Shape.STLength() Shape.STLength() Double Auto generated pseudo length in GIS. Due to the web coordinate system used, this is not the true length.

This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

This data was developed in response to citizens’ road maintenance requests from across the state as to whom to contact as the official maintenance authority - be it MDOT State Highway Administration, MDOT Transportation Authority, a county, or a municipality.MDOT SHA Website

The Massachusetts Department of Transportation Highway Division Road Inventory contains the spatial linework for all the public and a good portion of the private roadways in Massachusetts, along with roadway attributes covering the roadway classification, ownership, physical conditions, traffic volumes, pavement conditions, highway performance monitoring information, and more. This version has been processed by CTPS to eliminate overlaps among features in the original distributed by MassDOT and to add pavement data, which is no longer attached by MassDOT.

description: Parcels and Land Ownership dataset current as of unknown. This data set consists of digital map files containing parcel-level cadastral information obtained from property descriptions. Cadastral features contained in the data set include real property boundary lines, rights-of-way boundaries, property dimensions.; abstract: Parcels and Land Ownership dataset current as of unknown. This data set consists of digital map files containing parcel-level cadastral information obtained from property descriptions. Cadastral features contained in the data set include real property boundary lines, rights-of-way boundaries, property dimensions.

(Link to Metadata)(User Guide)(Symbology layer files: aotclass_only.lyr aotclass_surfacetyp.lyr)The Vermont Road Centerline data layer (TransRoad_RDS) contains all town and state highways, as well as many private roads. The centerlines were originally developed under contract by Greenhorne and O'Mara under the guidance of VCGI (1992). VCGI was the original steward of the road centerline data between 1992 and 2004. The Vermont Agency of Transportation (VTrans) is now considered the steward of this data layer. Updates have been performed over the years by VCGI, RPCs, and VTrans. The VT Agency of Transportation has taken over the update and maintenance of the road centerline data layer and has revised the layer to match "Official" highway mileage. NOTE: TransRoad_RDS meets the requirements articulated in the VGIS Road Centerline Data Standard (https://vcgi.vermont.gov/resources/standards).This layer is the most reliable source for official VTrans road class (AOTCLASS) information. However, this layer may not include every private road, and the road name information is not may not match perfectly with the EmergencyE911_RDS data layer. The EmergencyE911_RDS road centerline layer maintained by VT's E911 Board as the most up-to-date roadname information. It was originally based on TransRoad_RDS, and is therefore very similar. However, it includes all private roads and generally more reliable road name and address range information. There was a significant change in the schema in the June 2013 release as part of the effort between VTrans and E911 to merge their two datasets. The data layer includes the field structure agreed to by both entities, but most of the fields that are E911's have not been populated in this release.Stewards: Information Technology, Data Owner: Mapping Unit

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.

This data is not for tax collection purposes. It is used to expedite Road Maintenance operations. This data is typically updated to coincide with city annexations.

This feature class consists of approximately 195,000 features representing over 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS). Geometry and Attribution: The Linear Referencing System (LRS) data contained within this feature class provides dissolved route segmentation (i.e. routes are not segmented when they intersect other routes), thus rendering one table record per route. Multi-part geometry is created where routes are noncontiguous (e.g. a valid physical gap exists because another route is the master). The feature class only depicts master routes, those are routes built in the prime direction and on divided roadways where the non-prime direction is the master. Each road centerline record has a master route record assigned. Measures: The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions). Purpose: This linear referenced data layer represents roadways that are maintained by the Virginia Department of Transportation and provides the underlying spatially enabled geometric network to which all "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, etc...) can be located. Note: The overlap and non-prime measures are for reference only and have not been fully validated for accuracy or completeness.

This dataset is designed to represent and identify the property boundaries in Lexington-Fayette County. The original dataset was created in late 1990's by a third party that converted existing paper maps to digital GIS files. The data has since been updated by georeferencing recorded plats for corrections and new additions. In cases where the plats do not appear accurate, aerial photos are utilized in attempt to properly locate the property lines. The only except for this process are changes to highway right-of-way in which calls are run from deeds. The geometry of this data is not of survey quality and should not be used for survey purposes. The data is intended for general reference purposes only.As part of the basemap data layers, the parcel boundary map layer is an integral part of the Lexington Fayette-Urban County Government Geographic Information System. Basemap data layers are accessed by personnel in most LFUCG divisions for basic applications such as viewing, querying, and map output production. More advanced user applications may focus on thematic mapping, summarization of data by geography, or planning purposes (including defining boundaries, managing assets and facilities, integrating attribute databases with geographic features, spatial analysis, and presentation output).