You have been assigned a new project, which you have researched, and you have identified the data that you need.The next step is to gather, organize, and potentially create the data that you need for your project analysis.In this course, you will learn how to gather and organize data using ArcGIS Pro. You will also create a file geodatabase where you will store the data that you import and create.After completing this course, you will be able to perform the following tasks:Create a geodatabase in ArcGIS Pro.Create feature classes in ArcGIS Pro by exporting and importing data.Create a new, empty feature class in ArcGIS Pro.

In this course, you will learn about some common types of data used for GIS mapping and analysis, and practice adding data to a file geodatabase to support a planned project.Goals Create a file geodatabase. Add data to a file geodatabase. Create an empty geodatabase feature class.

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. For more information on the NHDPlus dataset see the NHDPlus v2 User Guide.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territories not including Alaska.Geographic Extent: The United States not including Alaska, Puerto Rico, Guam, US Virgin Islands, Marshall Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: EPA and USGSUpdate Frequency: There is new new data since this 2019 version, so no updates planned in the futurePublication Date: March 13, 2019Prior to publication, the NHDPlus network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the NHDPlus Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, On or Off Network (flowlines only), Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original NHDPlus dataset. No data values -9999 and -9998 were converted to Null values for many of the flowline fields.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer is limited to scales of approximately 1:1,000,000 or larger but a vector tile layer created from the same data can be used at smaller scales to produce a webmap that displays across the full range of scales. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute. Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map. Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class. Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

Summary This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point location. GPS started being used in 1992 when the technology became available. Records from FMIS (Fire Management Information System) were reviewed and compared to refuge records. Polygon data in FMIS only occurs from 2012 to current and many acreage estimates did not match. This dataset includes ALL fires no matter the size. This feature class documents the fire history on CMR from 1964 - present. This is 1 of 2 feature classes, a polygon and a point. This data has a variety of different origins which leads to differing quality of data. Within the polygon feature class, this contains perimeters that were mapped using a GPS, hand digitized, on-screen digitized, and buffered circles to the estimated acreage. These 2 files should be kept together. Within the point feature class, fires with only a location of latitude/longitude, UTM coordinate, TRS and no estimated acreage were mapped using a point location. GPS started being used in 1992 when the technology became available. Data origins include: Data origins include: 1) GPS Polygon-data (Best), 2) GPS Lat/Long or UTM, 3)TRS QS, 4)TRS Point, 6)Hand digitized from topo map, 7) Circle buffer, 8)Screen digitized, 9) FMIS Lat/Long. Started compiling fire history of CMR in 2007. This has been a 10 year process.FMIS doesn't include fires polygons that are less than 10 acres. This dataset has been sent to FMIS for FMIS records to be updated with correct information. The spreadsheet contains 10-15 records without spatial information and weren't included in either feature class. Fire information from 1964 - 1980 came from records Larry Eichhorn, BLM, provided to CMR staff. Mike Granger, CMR Fire Management Officer, tracked fires on an 11x17 legal pad and all this information was brought into Excel and ArcGIS. Frequently, other information about the fires were missing which made it difficult to back track and fill in missing data. Time was spent verifiying locations that were occasionally recorded incorrectly (DMS vs DD) and converting TRS into Lat/Long and/or UTM. CMR is divided into 2 different UTM zones, zone 12 and zone 13. This occasionally caused errors in projecting. Naming conventions caused confusion. Fires are frequently names by location and there are several "Soda Creek", "Rock Creek", etc fires. Fire numbers were occasionally missing or incorrect. Fires on BLM were included if they were "Assists". Also, fires on satellite refuges and the district were also included. Acreages from GIS were compared to FMIS acres. Please see documentation in ServCat (URL) to see how these were handled.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

This dataset contains the recreation opportunity information that the Forest Service collects through the Recreation Portal and shares with the public on https://www.recreation.gov, the Forest Service World Wide Web pages (https://www.fs.usda.gov/) and the Interactive Visitor Map. This recreation data contains detailed descriptions of recreational sites, areas, activities & facilities. This published dataset consists of one point feature class for recreational areas, one spatial view and three related tables such as activities, facilities & rec area advisories. The purpose of each related table is described belowRECAREAACTIVITIES: This related table contains information about the activities that are associated with the rec area.RECAREAFACILITIES: This related table contains information about the amenities that are associated with the rec area.RECAREAADVISORIES: This table contains events, news, alerts and warnings that are associated with the rec area.RECAREAACTIVITIES_V: This spatial view/feature class is generated by joining the RECAREAACTIVITIES table to the RECREATION OPPORTUNITIES Feature Class. Please note that the RECAREAID is the unique identifier present in point feature class and in the related tables as well. The RECAREAID is used as foreign key to access relate records.This published data is updated nightly from an XML feed maintained by the CIO Rec Portal team. This data is intended for public use and distribution. MetadataThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService OGC WMS CSV Shapefile GeoJSON KML For complete information, please visit https://data.gov.

WSDOT template for Esri file geodatabase polygon feature class. Template has pre-defined attribute schema to help users create data that is more consistent or compliant with agency standards. Metadata has been created using the FGDC metadata style but stored in the ArcGIS format. Content presentation will change upon export to FGDC format.This service is maintained by the WSDOT Transportation Data, GIS & Modeling Office. If you are having trouble viewing the service, please contact Online Map Support at onlinemapsupport@wsdot.wa.gov.

The National Hydrography Dataset Plus High Resolution (NHDplus High Resolution) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US Geological Survey, NHDPlus High Resolution provides mean annual flow and velocity estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.For more information on the NHDPlus High Resolution dataset see the User’s Guide for the National Hydrography Dataset Plus (NHDPlus) High Resolution.Dataset SummaryPhenomenon Mapped: Surface waters and related features of the United States and associated territoriesGeographic Extent: The Contiguous United States, Hawaii, portions of Alaska, Puerto Rico, Guam, US Virgin Islands, Northern Marianas Islands, and American SamoaProjection: Web Mercator Auxiliary Sphere Visible Scale: Visible at all scales but layer draws best at scales larger than 1:1,000,000Source: USGSUpdate Frequency: AnnualPublication Date: July 2022This layer was symbolized in the ArcGIS Map Viewer and while the features will draw in the Classic Map Viewer the advanced symbology will not. Prior to publication, the network and non-network flowline feature classes were combined into a single flowline layer. Similarly, the Area and Waterbody feature classes were merged under a single schema.Attribute fields were added to the flowline and waterbody layers to simplify symbology and enhance the layer's pop-ups. Fields added include Pop-up Title, Pop-up Subtitle, Esri Symbology (waterbodies only), and Feature Code Description. All other attributes are from the original dataset. No data values -9999 and -9998 were converted to Null values.What can you do with this layer?Feature layers work throughout the ArcGIS system. Generally your work flow with feature layers will begin in ArcGIS Online or ArcGIS Pro. Below are just a few of the things you can do with a feature service in Online and Pro.ArcGIS OnlineAdd this layer to a map in the map viewer. The layer or a map containing it can be used in an application. Change the layer’s transparency and set its visibility rangeOpen the layer’s attribute table and make selections. Selections made in the map or table are reflected in the other. Center on selection allows you to zoom to features selected in the map or table and show selected records allows you to view the selected records in the table.Apply filters. For example you can set a filter to show larger streams and rivers using the mean annual flow attribute or the stream order attribute.Change the layer’s style and symbologyAdd labels and set their propertiesCustomize the pop-upUse as an input to the ArcGIS Online analysis tools. This layer works well as a reference layer with the trace downstream and watershed tools. The buffer tool can be used to draw protective boundaries around streams and the extract data tool can be used to create copies of portions of the data.ArcGIS ProAdd this layer to a 2d or 3d map.Use as an input to geoprocessing. For example, copy features allows you to select then export portions of the data to a new feature class.Change the symbology and the attribute field used to symbolize the dataOpen table and make interactive selections with the mapModify the pop-upsApply Definition Queries to create sub-sets of the layerThis layer is part of the ArcGIS Living Atlas of the World that provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

This Quarter Section feature class depicts PLSS Second Divisions . PLSS townships are subdivided in a spatial hierarchy of first, second, and third division. These divisions are typically aliquot parts ranging in size from 640 acres to 160 to 40 acres, and subsequently all the way down to 2.5 acres. The data in this feature class was translated from the PLSSSecondDiv feature class in the original production data model, which defined the second division for a specific parcel of land. Metadata

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

This dataset contains the recreation opportunity information that the Forest Service collects through the Recreation Portal and shares with the public on https://www.recreation.gov, the Forest Service World Wide Web pages (https://www.fs.usda.gov/) and the Interactive Visitor Map. This recreation data contains detailed descriptions of recreational sites, areas, activities & facilities. This published dataset consists of one point feature class for recreational areas, one spatial view and three related tables such as activities, facilities & rec area advisories. The purpose of each related table is described below RECAREAACTIVITIES: This related table contains information about the activities that are associated with the rec area.RECAREAFACILITIES: This related table contains information about the amenities that are associated with the rec area. RECAREAADVISORIES: This table contains events, news, alerts and warnings that are associated with the rec area.RECAREAACTIVITIES_V: This spatial view/feature class is generated by joining the RECAREAACTIVITIES table to the RECREATION OPPORTUNITIES Feature Class. Please note that the RECAREAID is the unique identifier present in point feature class and in the related tables as well. The RECAREAID is used as foreign key to access relate records.This published data is updated nightly from an XML feed maintained by the CIO Rec Portal team. This data is intended for public use and distribution. Metadata

This dataset represents cellular tower locations as recorded by the Federal Communications Commission This feature class serves as base information for use in GIS systems for general planning, analytical, and research purposes. It is not intended for engineering work or to legally define FCC licensee data or FCC market boundaries. The material in these data and text files are provided as-is. The FCC disclaims all warranties with regard to the contents of these files, including their fitness. In no event shall the FCC be liable for any special, indirect, or consequential damages whatsoever resulting from loss or use, data or profits, whether in connection with the use or performance of the contents of these files, action of contract, negligence, or other action arising out of, or in connection with the use of the contents of these files. It is known that there are some errors in the licensing information - Latitude, Longitude and Ground Elevation data as well as frequency assignment data from which these MapInfo files were generated.

The feature class indicates the specific types of motorized vehicles allowed on the designated routes and their seasons of use. The feature class is designed to be consistent with the MVUM (Motor Vehicle Use Map). It is compiled from the GIS Data Dictionary data and Infra tabular data that the administrative units have prepared for the creation of their MVUMs. Only trails with the symbol value of 5-12, 16, 17 are Forest Service System trails and contain data concerning their availability for motorized use. This data is published and refreshed on a unit by unit basis as needed. Individual unit's data must be verified and proved consistent with the published MVUMs prior to publication in the EDW. Click this link for full metadata description: Metadata _

The State Lands Commission has prepared the Significant Lands Inventory (report) for the California Legislature as a general identification and classification of those unconveyed State school lands and tide and submerged lands which possess significant environmental values. The publication incorporates evaluated and pertinent comments received on the initial draft report which was circulated statewide in February 1975.The absence of a particular digitized waterway in the dataset does not mean that the State does not claim ownership of that parcel or waterway, or that such specific parcel or waterway has no significant environmental values. This dataset is not intended to establish ownership, only to identify those parcels which possess significant environmental values. Staff was unable to physically inventory all of the considered lands; instead, the advice and participation of those with known environmental expertise was utilized as additional to staff survey.Tide and submerged lands are digitized in the WaterBody and WaterLine feature classes; WaterLines for coastal areas, WaterBody for inland areas. Tide and submerged lands under the jurisdiction of the State Lands Commission are those sovereign lands received from the Federal Government by virtue of California's admission to the Union on an equal footing with the original States. Such lands, and State interest therein, are generally the lands waterward of the ordinary high water mark of the Pacific Ocean (seaward to a three-mile limit); tidal bays, sloughs, estuaries; and, navigable lakes and streams within the State.School Lands are digitized in the SchoolLand feature class. State school lands under the jurisdiction of the Commission are largely composed of the 16th and 36th sections of each township. The Federal Government transferred these lands to the State in 1853, in order to establish a financial foundation for a public school system. In cases where the 16th and 36th sections were mineral in character, incomplete as to acreage total, or already claimed or granted by the Federal Government, the State was permitted to select other lands "in lieu" of the specific sections.The public trust of commerce, navigation and fisheries which the State retains on patented sovereign lands should also be considered included in this inventory. Wherever a waterway, or body of water, is listed or mapped, the common trust state interest in patented sovereign lands, if any, is also included.The State Lands Commission emphasized when it adopted this report at its December 1, 1975 meeting that all tide and submerged lands are significant by the nature of their public ownership. Only because of the methodology used for this report are all of these waterways not specifically listed in this inventory.It is the intent of the State Lands Commission that the Significant Lands Inventory be periodically updated. This dataset should be considered informational, to assist the Legislature, the Commission, and the public in considering the environmental aspects of a proposed project and the significant values to be protected therein.

This Zoning feature class is an element of the Oregon GIS Framework statewide, Zoning spatial data. This version is authorized for public use. Attributes include zoning districts that have been generalized to state classes. As of June 30, 2023, this feature class contains zoning data from 229 local jurisdictions. DLCD plans to continue adding to and updating this statewide zoning dataset as they receive zoning information from the local jurisdictions. Jurisdictions included in the latest version of the statewide zoning geodatabase:

Cities: Adams, Adrian, Albany, Amity, Antelope, Ashland, Astoria, Athena, Aurora, Banks, Barlow, Bay City, Beaverton, Bend, Boardman, Bonanza, Brookings, Brownsville, Burns, Butte Falls, Canby, Cannon Beach, Carlton, Cascade Locks, Cave Junction, Central Point, Chiloquin, Coburg, Columbia City, Coos Bay, Cornelius, Corvallis, Cottage Grove, Creswell, Culver, Dayton, Detroit, Donald, Drain, Dufur, Dundee, Dunes City, Durham, Eagle Point, Echo, Enterprise, Estacada, Eugene, Fairview, Falls City, Florence, Forest Grove, Fossil, Garibaldi, Gaston, Gates, Gearhart, Gervais, Gladstone, Gold Beach, Gold Hill, Grants Pass, Grass Valley, Gresham, Halsey, Happy Valley, Harrisburg, Helix, Hermiston, Hillsboro, Hines, Hood River, Hubbard, Idanha, Independence, Jacksonville, Jefferson, Johnson City, Jordan Valley, Junction City, Keizer, King City, Klamath Falls, La Grande, La Pine, Lafayette, Lake Oswego, Lebanon, Lincoln City, Lowell, Lyons, Madras, Malin, Manzanita, Maupin, Maywood Park, McMinnville, Medford, Merrill, Metolius, Mill City, Millersburg, Milton-Freewater, Milwaukie, Mitchell, Molalla, Monmouth, Moro, Mosier, Mount Angel, Myrtle Creek, Myrtle Point, Nehalem, Newberg, Newport, North Bend, North Plains, Nyssa, Oakridge, Ontario, Oregon City, Pendleton, Philomath, Phoenix, Pilot Rock, Port Orford, Portland, Prescott, Prineville, Rainier, Redmond, Reedsport, Rivergrove, Rockaway Beach, Rogue River, Roseburg, Rufus, Saint Helens, Salem, Sandy, Scappoose, Scio, Scotts Mills, Seaside, Shady Cove, Shaniko, Sheridan, Sherwood, Silverton, Sisters, Sodaville, Spray, Springfield, Stanfield, Stayton, Sublimity, Sutherlin, Sweet Home, Talent, Tangent, The Dalles, Tigard, Tillamook, Toledo, Troutdale, Tualatin, Turner, Ukiah, Umatilla, Vale, Veneta, Vernonia, Warrenton, Wasco, Waterloo, West Linn, Westfir, Weston, Wheeler, Willamina, Wilsonville, Winston, Wood Village, Woodburn, Yamhill.

Counties: Baker County, Benton County, Clackamas County, Clatsop County, Columbia County, Coos County, Crook County, Curry County, Deschutes County, Douglas County, Harney County, Hood River County, Jackson County, Jefferson County, Josephine County, Klamath County, Lane County, Lincoln County, Linn County, Malheur County, Marion County, Multnomah County, Polk County, Sherman County, Tillamook County, Umatilla County, Union County, Wasco County, Washington County, Wheeler County, Yamhill County.

R emaining jurisdictions either chose not to share data to incorporate into the public, statewide dataset or did not respond to DLCD’s request for data. These jurisdictions’ attributes are designated “not shared” in the orZDesc field and “NS” in the orZCode field.

The Current Invasive Plants (InvasivePlantCurrent) feature class contains only the most recent or latest invasive Plant Infestation polygons collected by the National Invasive Plant Inventory Protocol. Includes most recent and excludes historic observations. Includes Site ID, Plant code, status etc. for the infesting species, date, area and other basic data. Metadata

Public Open Space Geographic Information System data collection for Perth and Peel Metropolitan Areas

The public open space (POS) dataset contains polygon boundaries of areas defined as publicly available and open. This geographic information system (GIS) dataset was collected in 2011/2012 using ArcGIS software and aerial photography dated from 2010-2011. The data was collected across the Perth Metro and Peel Region.

POS refer to all land reserved for the provision of green space and natural environments (e.g. parks, reserves, bushland) that is freely accessible and intended for use for recreation purposes (active or passive) by the general public. Four types of “green and natural public open spaces” are distinguished: (1) Park; (2) Natural or Conservation Area; (3) School Grounds; and (4) Residual. Areas where the public are not permitted except on payment or which are available to limited and selected numbers by membership (e.g. golf courses and sports centre facilities) or setbacks and buffers required by legislation are not included.

Initially, potential POSs were identified from a combination of existing geographic information system (GIS) spatial data layers to create a generalized representation of ‘green space’ throughout the Perth metropolitan and Peel regions. Base data layers include: cadastral polygons, metropolitan and regional planning scheme polygons, school point locations, and reserve vesting polygons. The ‘green’ space layer was then visually updated and edited to represent the true boundaries of each POS using 2010-2011 aerial photography within the ArcGIS software environment. Each resulting ’green’ polygon was then classified using a decision tree into one of four possible categories: park, natural or conservation area, school grounds, or residual green space.

Following the classification process, amenity and other information about each POS was collected for polygons classified as “Park” following a protocol developed at the Centre for the Built Environment and Health (CBEH) called POSDAT (Public Open Space Desktop Auditing Tool). The parks were audited using aerial photography visualized using ArcGIS software. . The presence or absence of amenities such as sporting facilities (e.g. tennis courts, soccer fields, skate parks etc) were audited as well as information on the environmental quality (i.e. presence of water, adjacency to bushland, shade along paths, etc), recreational amenities (e.g. presence of BBQ’, café or kiosks, public access toilets) and information on selected features related to personal safety.

The data is stored in an ArcGIS File Geodatabase Feature Class (size 4MB) and has restricted access.

Data creation methodology, data definitions, and links to publications based on this data, accompany the dataset.

The Trails Layer is designed to provide information about National Forest System trail locations and characteristics to the public. When fully realized, it will describe trail locations, basic characteristics of the trail, and where and when various trail uses are prohibited, allowed and encouraged. Because the data readiness varies between Forests, each Forest will approve which level of attribute subset are published for that forest. Forests can provide no information or one of three attribute subsets describing trails. The attribute subsets include TrailNFS_Centerline which includes the location and trail name and number; TrailNFS_Basic which adds information about basic trail characteristics; and TrailNFS_Mgmt which adds information about where and when users are prohibited, allowed, and encouraged. When a Forest chooses to provide the highest attribute subset, TrailNFS_Mgmt, these attributes must be consistent with the Forest's published Motorized Vehicle Use Map (MVUM). Metadata for the individual Forest feature classes used to compile this feature class are available at data.fs.usda.gov/geodata/edw/dir_trails.php. Metadata

The feature class indicates the specific types of motorized vehicles allowed on the designated routes and their seasons of use. The feature class is designed to be consistent with the MVUM (Motor Vehicle Use Map). It is compiled from the GIS Data Dictionary data and NRM Infra tabular data that the administrative units have prepared for the creation of their MVUMs. Only roads with a SYMBOL attribute value of 1, 2, 3, 4, 11, and 12 are Forest Service System roads and contain data concerning their availability for OHV (Off Highway Vehicle) use. This data is published and refreshed on a unit by unit basis as needed. Data for each individual unit must be verified and proved consistent with the published MVUMs prior to publication.The Forest Service's Natural Resource Manager (NRM) Infrastructure (Infra) is the agency standard for managing and reporting information about inventory of constructed features and land units as well as the permits sold to the general public and to partners. MetadataThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService OGC WMS CSV Shapefile GeoJSON KML https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_MVUM_01/MapServer/1 Metadata For complete information, please visit https://data.gov.

The FDOT GIS Interstates feature class provides spatial information on Florida Interstate highways. The interstate and US route numbers are assigned by the Federal American Association of State Highway and Transportation Officials (AASHTO) usually following recommendations by the each state department. Both interstate and US routes are coded under the USROUTE characteristic. Interstate numbers are assigned with even numbers for west to east routes and odd numbers for routes going south to north, starting with the lowest number in the lowest part of the nation and progressing higher nationwide. US route numbers are assigned with odd numbers for north and south routes with the low number beginning in the east and progressing higher toward the west. This numbering practice is used across all states for all interstates and US routes for the public traveling purposes. This information is required for roadways functionally classified as principal, minor arterials that have US route designations, and all Active Exclusive roads that are associated with Interstate and the US route. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 11/08/2025.For more details please review the FDOT RCI Handbook Download Data: Enter Guest as Username to download the source shapefile from here: https://ftp.fdot.gov/file/d/FTP/FDOT/co/planning/transtat/gis/shapefiles/interstates.zip