ArcGIS REST Services Directory Login
JSON

ItemInfo

Item Information

snippet: The data are created to serve as base information for use in GIS systems for a variety of planning and analysis purposes.
summary: The data are created to serve as base information for use in GIS systems for a variety of planning and analysis purposes.
accessInformation: Maricopa Association of Governments (MAG) and the MAG member agencies
thumbnail:
maxScale: NaN
typeKeywords: []
description: Non-Motorized Network Bike Lanes & Paved ShoulderDigitizing & Labeling MethodologyName – Derived from the street name with “bike lanes” at the endFrom location –Street name at the northern section(if a north-south segment) or eastern section(if east-west segment)To location – Street name at the southern section (if a north-south segment) or western section (if east-west segment)Location type – trail only Category – trail onlyMonth & year added– source used was LIS aerials. In instances where the aerials were taken over a period of months, the latter date and year was recorded (for example, Flown Dec 2001-Jan 2002, would record January 2002 as the month and year added). In rare cases, a secondary source was Historical Aerial Photography from Maricopa County GIS Portal: https://gis.maricopa.gov/GIO/HistoricalAerial/index.htmlLanes were segmented / grouped by 1-mile segments, change in road name, or date of striping Non-Motorized Network Unpaved Trails, Shared Use Path, & Walking PathsDigitizing & Labeling Methodology*Name – Derived from the street name, subdivision or park with “trail,” “shared use path,” or “walking path” at the endFrom location –Street name at the northern section(if a north-south segment) or eastern section(if east-west segment)To location – Street name at the southern section (if a north-south segment) or western section (if east-west segment)*Note on location type – Shared Use Paths are 8’ or wider, Walking Paths are usually found in neighborhoodsLocation type Description of where trail is found based on DS&PM (relevant to trails only)Category - Trail hierarchy based on DS&PM (relevant to trails only)Month & year added– source used was LIS aerials. In instances where the aerials were taken over a period of months, the latter date and year was recorded (for example, Flown Dec 2001-Jan 2002, would record January 2002 as the month and year added). A secondary source was Historical Aerial Photography from Maricopa County GIS Portal: https://gis.maricopa.gov/GIO/HistoricalAerial/index.htmlIn cases where there is glare or tree coverage or another obstacle blocking segment from view, the date is listed as when the adjoining subdivision was built. In cases of natural washes, the date was listed as April 1976, the furthest the Maricopa County GIS Portal had aerial coverage. Network was segmented / grouped arbitrarily based on subdivision or continuous road coverage.
licenseInfo: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Data may be used only by the licensee and only for the non-commercial purposes stated in such licensee's request. Data is provided on an "as is" basis, with no warranties, express or implied, including, but not limited to, any warranties of accuracy, merchantability or fitness for a particular purpose. The licensee shall be solely responsible, and MAG shall have no liability, for the accuracy, selection, installation, use, efficiency and suitability of any data or documentation provided to licensee by MAG. In no event shall MAG be liable to the licensee for any damages arising from or related to any use or loss of the data. The licensee is advised to use the data with caution and to independently verify accuracy. For information regarding commercial use of the data, see Arizona Revised Statutes section 39-121.03.</SPAN></P></DIV>
catalogPath:
title: COS_active_transportation_system_existing
type:
url:
tags: ["transportation"]
culture: en-US
portalUrl:
name:
guid:
minScale: NaN
spatialReference: