The approximate representation of real property areas in Lake County, Minnesota.

Converted from paper to digital in 2000. Parcel boundaries have been updated by the Taxmap Department. Auditors Department updates the property data for each parcel. A scripted nightly update is ran by the GIS Department to bring the parcel layer up to date with the Auditor and Taxmap changes.

Visit the USGS National Wetlands Inventory surface water and wetlands map.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under Basic Parcels."Database containing parcel boundary, parcel identifier, parcel address, owner type, and county recorder contact information" - HB113. The intent of the bill was to not include any attributes that the counties rely on for data sales. If you want other attributes associated with the parcels you need to contact the county recorder.Users should be aware the owner type field 'OWN_TYPE' in the parcel polygons is a very generalized ownership type (Federal, Private, State, Tribal). It is populated with the value of the 'OWNER' field where the parcel's centroid intersects the CADASTRE.LandOwnership polygon layer.This dataset is a snapshot in time and may not be the most current. For the most current data contact the county recorder.

The Digital Geologic-GIS Map of Alibates Flint Quarries National Monument and Lake Meredith National Recreational Area and Vicinity, Texas is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (aflm_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (aflm_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (alfl_lamr_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (aflm_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (aflm_geology_metadata_faq.pdf). Please read the alfl_lamr_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Texas Water Development Board and Texas Bureau of Economic Geology, University of Texas at Austin. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (aflm_geology_metadata.txt or aflm_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:250,000 and United States National Map Accuracy Standards features are within (horizontally) 127 meters or 416.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The Colorado Trail System, now titled the Colorado Trail Explorer (COTREX), endeavors to map every trail in the state of Colorado. Currently there 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 9/11/2019

Airport Protection Overlay District

Features in this dataset represent segments of public highways that are maintained by and under the jurisdiction of the Colorado Department of Transportation. These highways consist of Interstates, US Highways, and State Highways. Features are represented by polyline (linear) geographic shapes.

Download .zipThese files contain the lake boundary data used by the Ohio Division of Wildlife for the construction of lake maps. Lake boundary data was derived by digitizing Ohio Statewide Imagery Program (OSIP-1) data. Additional details on the digitizing process are available on request.

Lake boundary: http://ogrip.oit.ohio.gov/ProjectsInitiatives/StatewideImagery.aspxContact Information:GIS Support, ODNR GIS ServicesOhio Department of Natural ResourcesDivision of Wildlife2045 Morse Rd, Bldg G-2Columbus, OH, 43229Telephone: 614-265-6462Email: gis.support@dnr.ohio.gov Data Update Frequency: As Needed

REQUIRED: A brief narrative summary of the data set.

Features in this dataset represent public roads under local jurisdiction that are functionally classified as local. Features are represented by polyline (linear) geographic shapes.

This package contains National, Statewide, and Palm Beach County elements. Links are provided where available but do note that staff geoprocess files to create a more personalized MPO-purposed basemap.MPO Basemap PackageLayer/Groups*Additional InformationCounty BoundaryThis layer utilizes staff defined Definition Queries depending on the scenario (i.e. only PBC vs the Region).API: https://services1.arcgis.com/T0NPfOCJr9tmBN93/arcgis/rest/services/Florida_Counties/FeatureServerRoadway Labels*This following group contains several FDOT maintained layers bulleted below. Additional these roadway layers utilize specialized icon labels along with staff defined Definition Queries (DQs) to help manipulate them based on the current need.InterstatesAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/Interstates_TDA/FeatureServerUS HighwaysAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/US_Routes_TDA/FeatureServerToll RoadsAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/Toll_Roads_TDA/FeatureServerThis layer's labels utilized two classes each incorporating SQL queries to separate Toll symbologies from the main Turnpike one.State RoadsAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/State_Roads_TDA/FeatureServerCounty RoadwaysAPI: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/County_Roads_TDA/FeatureServerMajor RoadwaysThis FDOT Functional Classification layer utilizes staff defined Definition Queries for Major Roadway symbolization.API: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/Functional_Classification_TDA/FeatureServerRailroadsThis ESRI layer utilizes staff defined Definition Queries for general Railroad symbolization.API: https://services.arcgis.com/xOi1kZaI0eWDREZv/arcgis/rest/services/NTAD_North_American_Rail_Network_Lines/FeatureServerstate_fl_uabThis geoprocessed layer is clip to the state_fl_basemap for a cleaner version of the FDOT Smoothed Urban Boundaries layer along coastlines; linked below for reference.API: https://services1.arcgis.com/O1JpcwDW8sjYuddV/arcgis/rest/services/FDOT_FHWA_Smoothed_Urban_Boundaries_TDA/FeatureServercounty_pal*This following group contains several Palm Beach County and MPO maintained layers bulleted below. Additional staff defined Definition Queries (DQ) and noted below:county_pal_roadways (County)API: https://maps.co.palm-beach.fl.us/arcgis/rest/services/OpenData/Transportation_Open_Data/MapServerPBC localized road network. If not using DQs note that is may lag on older/slower systems to render.county_pal_water (County)API: https://maps.co.palm-beach.fl.us/arcgis/rest/services/OpenData/Environment_Open_Data/MapServerDQ: Detailed and Not Detailed (automatically enabled) versions of PBC water features. Detailed may lag somewhat.county_pal_municipal (MPO)API: https://services5.arcgis.com/79IoFXBn9ZeqmVlC/arcgis/rest/services/Test_File/FeatureServerDQ: Automatically enabled the “geo” attribute to “Municipality” to render only PBC municipalities. This MPO file also contains commissioner districts, special districts, community redevelopment agency (CRA) districts, the Port of Palm Beach, and a County outline if needed.natural_areas*This following group contains State and MPO maintained layers bulleted below. These layers and their symbologies are used to help match the ESRI Topographic Basemap.all_natural_areas (State)API: https://services.arcgis.com/9Jk4Zl9KofTtvg3x/ArcGIS/rest/services/FL_Conservation_Lands_web/FeatureServerUtilizes the marsh style symbology.static_county_natural_areas (MPO)API: Geoprocessed in file.A clipped version of the api layer below. This was to make geometry along coastlines cleaner.api_county_natural_areas (State)API: https://services.arcgis.com/9Jk4Zl9KofTtvg3x/ArcGIS/rest/services/FL_Conservation_Lands_web/FeatureServerDQ: To match the ESRI Topographic Basemap, a staff defined Definition Query was developed to highlight certain areas. The OBJECTID's included are: 105,109,755,823,1260,1359,1410,1723,1724,2426,2539,2713,2046,2045,1297,2654,826,592,2643,1404,204,900,832,2200,2803,233,53,2680,2056,747,1302,1397state_fl_basemapThis staff created layer was developed to consolidate the previous many separate county, Lake Okeechobee, and coastline geometries for easier use.API: Geoprocessed in file.State Boundary's API used as a base: https://geodata.myfwc.com/datasets/myfwc::florida-state-waters-and-land-boundary/explore?location=25.629877%2C-81.683769%2C6.98state_fl_waterThis staff created layer was developed to consolidate the previous many separate water layers by county for easier use.API: Geoprocessed in file.Lake Okeechobee water used as a base: https://services.arcgis.com/V4Rx2DXlIHdEvTZA/arcgis/rest/services/Okeechobee_lake/FeatureServer