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. were derived from the NVC. NatureServe developed a preliminary list of potential vegetation types. These data were combined with existing plot data (Cully 2002) to derive an initial list of potential types. Additional data and information were gleaned from a field visit and incorporated into the final list of map units. Because of the park’s small size and the large amount of field data, the map units are equivalent to existing vegetation associations or local associations/descriptions (e.g., Prairie Dog Colony). In addition to vegetation type, vegetation structures were described using three attributes: height, coverage density, and coverage pattern. In addition to vegetation structure and context, a number of attributes for each polygon were stored in the associated table within the GIS database. Many of these attributes were derived from the photointerpretation; others were calculated or crosswalked from other classifications. Table 2.7.2 shows all of the attributes and their sources. Anderson Level 1 and 2 codes are also included (Anderson et al. 1976). These codes should allow for a more regional perspective on the vegetation types. Look-up tables for the names associated with the codes is included within the geodatabase and in Appendix D. The look-up tables contain all the NVC formation information as well as alliance names, unique IDs, and the ecological system codes (El_Code) for the associations. These El_Codes often represent a one-to-many relationship; that is, one association may be related to more than one ecological system. The NatureServe conservation status is included as a separate item. Finally, slope (degrees), aspect, and elevation were calculated for each polygon label point using a digital elevation model and an ArcView script. The slope figure will vary if one uses a TIN (triangulated irregular network) versus a GRID (grid-referenced information display) for the calculation (Jenness 2005). A grid was used for the slope figure in this dataset. Acres and hectares were calculated using XTools Pro for ArcGIS Desktop.

In order to use the standard color legend for Romanian soil type maps in the ESRI ArcMap-10 electronic format, a dataset consisting a shapefile set (.dbf, .shp, .shx, .sbn, and .sbx files), four different .lyr files, and three different .style files have been prepared (ESRI, 2016). The shapefile set is not a “real” georeferenced layer/coverage; it is designed only to handle all the instants of soil types from the standard legend. This legend contains 67 standard items: 63 proper colors (different color hues, each of them having, generally, 2 - 4 degrees of lightness and/or chroma, four shades of grey, and white color), and four hatching patterns on white background (ESRI, 2016). The “color difference DE*ab” between any two legend colors, calculated with the color perceptually-uniform model CIELAB , is greater than 10 units, thus ensuring acceptably-distinguishable colors in the legend. The 67 standard items are assigned to 60 main soils existing in Romania, four main nonsoils, and three special cases of unsurveyed land. The soils are specified in terms of the current Romanian system of soil taxonomy, SRTS-2012+, and of the international soil classification system WRB-2014. The four different .lyr files presented here are: legend_soilcode_srts_wrb.lyr, legend_soilcode_wrb.lyr, legend_colourcode_srts_wrb.lyr, and legend_colourcode_wrb.lyr. The first two of them are built using as value field the ‘Soil_codes’ field, and as labels (explanation texts) the ‘Soil_name’ field (storing the soil types according to SRTS/WRB classification), respectively, the ‘WRB’ field (the soil type according to WRB classification), while the last two .lyr files are built using as value field the ‘colour_code’ field (storing the color codes) and as labels the soil name in SRTS and WRB, respectively, in WRB classification. In order to exemplify how the legend is displayed, two .jpg files are also presented: legend_soil_srts_wrb.jpg and legend_colour_wrb.jpg. The first displays the legend (symbols and labels) according to the SRTS classification order, the second according to the WRB classification. The three different .style files presented here are: soil_symbols.style, wrb_codes.style, and colour_codes.style. They use as name the soil acronym in SRTS classification, soil acronym in WRB classification, and, respectively, the color code.

This service was last updated September 2016. This map service draws attention to your thematic content by providing a neutral background with minimal colors, labels, and features. Only key information is represented to provide geographic context, allowing your data to come to the foreground. This light gray basemap supports any strong colors and labels for your theme, creating a visually compelling map graphic which helps your reader see the patterns intended. See these blog posts for more information on how to use this map: Esri Canvas Maps Part I: Author Beautiful Web Maps With Our New Artisan Basemap Sandwich and Esri Canvas Maps Part II: Using the Light Gray Canvas Map effectively. The map shows populated places, water, roads, urban areas, parks, building footprints, and administrative boundaries. Alignment of boundaries is a presentation of the feature provided by our data vendors and does not imply endorsement by Esri or any governing authority. This map was compiled by Esri using HERE data, DeLorme basemap layers, MapmyIndia data, and Esri basemap data. The basemap includes boundaries, city labels and outlines, and major roads worldwide from 1:591M scale to 1:72k scale. More detailed nationwide coverage is included in North America, Europe, Africa, South America and Central America, the Middle East, India, Australia, and New Zealand to be fully consistent with the World Street Map and World Topo map down to the 1:9k scale. Data for select areas of Africa and Pacific Island nations from ~1:288k to ~1:9k was sourced from OpenStreetMap contributors. Specific country list and documentation of Esri's process for including OSM data is available to view.In addition, some of the data in the World Light Gray Base map service has been contributed by the GIS community. You can contribute your data to this service and have it served by Esri. For details, see the Community Maps Program. For details on data sources in this map service, view the list of Contributors for the World Light Gray Base map.View the coverage map below to learn more about the levels of detail:World coverage map: Shows the levels of detail throughout the world. The World Light Gray Reference is designed to be drawn on top of this map and provides selected city labels throughout the world. This web map lets you view the Light Gray Base with the Reference service drawn on top. This sample web map contains several examples of thematic content in the light gray canvas basemap with its reference overlay. Note: This map service is not supported in ArcGIS for Desktop 9.3.1 or earlier because it uses the mixed format cache format. Scale Range: 1:591,657,528 down to 1:9,028Coordinate System: Web Mercator Auxiliary Sphere (WKID 102100)Tiling Scheme: Web Mercator Auxiliary SphereMap Service Name: World_Light_Gray_Base

Water supply lakes are the primary source of water for many communities in northern and western Missouri. Therefore, accurate and up-to-date estimates of lake capacity are important for managing and predicting adequate water supply. Many of the water supply lakes in Missouri were previously surveyed by the U.S. Geological Survey (USGS) in the early 2000s (Richards, 2013) and in 2013 (Huizinga, 2014); however, years of potential sedimentation may have resulted in reduced water storage capacity. Periodic bathymetric surveys are useful to update the area/capacity table and to determine changes in the bathymetric surface. In April and May 2022, the USGS, in cooperation with the Missouri Department of Natural Resources (MoDNR) and in collaboration with the cities of Cameron, Springfield, and Unionville, Missouri, completed bathymetric surveys of seven (7) lakes using a marine-based mobile mapping unit, which consists of a multibeam echosounder (MBES) and an inertial navigation system (INS) mounted on a marine survey vessel. Bathymetric data were collected as the vessel traversed longitudinal transects to provide nearly complete coverage of the lake. The MBES was electronically tilted in some areas to improve data collection along the shoreline, in coves, and in areas that are shallower than about 2.0 meters deep (the practical limit of reasonable and safe data collection with the MBES). At some lakes, supplemental data were collected in shallow areas using an acoustic Doppler current profiler (ADCP) mounted on a remote-controlled vessel equipped with a differential global positioning system (DGPS). Bathymetric quality-assurance data also were collected at each lake to evaluate the vertical accuracy of the gridded bathymetric point data from the MBES. As part of the survey at each of these lakes, one or more reference marks or temporary bench marks were established to provide a point of known _location and elevation from which the water surface could be measured or another survey could be referenced at a later date. In addition, the elevation of a primary spillway or intake was surveyed, when present. These points were surveyed using a real-time kinematic (RTK) Global Navigation Satellite System (GNSS) receiver connected to the Missouri Department of Transportation real-time network (RTN), which provided real-time survey-grade horizontal and vertical positioning, using field procedures as described in Rydlund and Densmore (2012) for a Level II real-time positioning survey. The MBES data can be combined with light detection and ranging (lidar) data to prepare a bathymetric map and a surface area and capacity table for each lake. These data also can be used to compare the current bathymetric surface with any previous bathymetric surface. Data from each of the surveys are provided in ESRI Shapefile format (ESRI, 2023). Each of the seven lakes surveyed in 2022 has a child page containing the metadata and two zip files, one for the bathymetric data, and the other for the bathymetric quality-assurance data. The zip files follow the format of "####2022_bathy_pts.zip" or ####2022_QA_raw.zip," where "####" is the lake name. Each of these zip files contains a shapefile with an attribute table. Attribute/column labels of each table are described in the "Entity and attribute" section of the metadata file. The various reference marks and additional points from all the lake surveys are provided in ESRI Shapefile format (ESRI, 2023) with an attribute table on the main landing page. Attribute/column labels of this table are described in the "Entity and attribute" section of the metadata file. References Cited: Environmental Systems Research Institute, 2023, ArcGIS: accessed July 12, 2023, at https://www.esri.com/en-us/arcgis/about-arcgis/overview Huizinga, R.J., 2014, Bathymetric surveys and area/capacity tables of water-supply reservoirs for the city of Cameron, Missouri, July 2013: U.S. Geological Survey Open-File Report 2014–1005, 15 p., https://doi.org/10.3133/ofr20141005. Richards, J.M., 2013, Bathymetric surveys of selected lakes in Missouri—2000–2008: U.S. Geological Survey Open-File Report 2013–1101, 9 p. with appendix, https://doi.org/10.3133/ofr20131101. Rydlund, P.H., Jr., and Densmore, B.K., 2012, Methods of practice and guidelines for using survey-grade global navigation satellite systems (GNSS) to establish vertical datum in the United States Geological Survey: U.S. Geological Survey Techniques and Methods, book 11, chap. D1, 102 p. with appendixes, https://doi.org/10.3133/tm11D1. First posted November 29, 2023 Revised July 31, 2024, ver. 1.1

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.

Instrumental to the photo interpretive effort was the use of the GPS located vegetation plots collected by the field crew. These plots provided an idea of what the signatures of the individual map units should look like. In addition to the tablular data associated with each vegetation plot were five photographs collected at each plot. These photographs helped not only in identifying the immediate area but also provided us with a “look” at the areas surrounding the vegetation plot which might be a different map unit. These photographs may be “hyperlinked” within ArcMap to the salient vegetation observation point for a better concept of on the ground conditions.All interpreted mylar layers were scanned at 300 dpi. Each scanned mylar was then rectified to the NAIP base layer using recognizable ground features as registration points. The resulting scan produced a raster image that was subsequently vectorized. Each vectorized output was then extensively edited to produce clean digital vector lines. From the digitized vectors we created polygons by building topology in the GIS program. Finally, we created labels for each polygon and used these to add the attribute information. Attribution for all the polygons at CHIC included information pertaining to map units, NVC associations, Anderson land-use classes, and other relevant data. Attribute data were taken directly from the interpreted photos or were added later using the orthophotos as a guide.

Dataset description-br /- This dataset is a recalculation of the Copernicus 2015 high resolution layer (HRL) of imperviousness density data (IMD) at different spatial/territorial scales for the case studies of Barcelona and Milan. The selected spatial/territorial scales are the following: * a) Barcelona city boundaries * b) Barcelona metropolitan area, Àrea Metropolitana de Barcelona (AMB) * c) Barcelona greater city (Urban Atlas) * d) Barcelona functional urban area (Urban Atlas) * e) Milan city boundaries * f) Milan metropolitan area, Piano Intercomunale Milanese (PIM) * g) Milan greater city (Urban Atlas) * h) Milan functional urban area (Urban Atlas)-br /- In each of the spatial/territorial scales listed above, the number of 20x20mt cells corresponding to each of the 101 values of imperviousness (0-100% soil sealing: 0% means fully non-sealed area; 100% means fully sealed area) is provided, as well as the converted measure into squared kilometres (km2). -br /- -br /- -br /- Dataset composition-br /- The dataset is provided in .csv format and is composed of: -br /- _IMD15_BCN_MI_Sources.csv_: Information on data sources -br /- _IMD15_BCN.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Barcelona: * a) Barcelona city boundaries (label: bcn_city) * b) Barcelona metropolitan area, Àrea metropolitana de Barcelona (AMB) (label: bcn_amb) * c) Barcelona greater city (Urban Atlas) (label: bcn_grc) * d) Barcelona functional urban area (Urban Atlas) (label: bcn_fua)-br /- _IMD15_MI.csv_: This file refers to the 2015 high resolution layer of imperviousness density (IMD) for the selected territorial/spatial scales in Milan: * e) Milan city boundaries (label: mi_city) * f) Milan metropolitan area, Piano intercomunale milanese (PIM) (label: mi_pim) * g) Milan greater city (Urban Atlas) (label: mi_grc) * h) Milan functional urban area (Urban Atlas) (label: mi_fua)-br /- _IMD15_BCN_MI.mpk_: the shareable project in Esri ArcGIS format including the HRL IMD data in raster format for each of the territorial boundaries as specified in letter a)-h). -br /- Regarding the territorial scale as per letter f), the list of municipalities included in the Milan metropolitan area in 2016 was provided to me in 2016 from a person working at the PIM. -br /- In the IMD15_BCN.csv and IMD15_MI.csv, the following columns are included: * Level: the territorial level as defined above (a)-d) for Barcelona and e)-h) for Milan); * Value: the 101 values of imperviousness density expressed as a percentage of soil sealing (0-100%: 0% means fully non-sealed area; 100% means fully sealed area); * Count: the number of 20x20mt cells corresponding to a certain percentage of soil sealing or imperviousness; * Km2: the conversion of the 20x20mt cells into squared kilometres (km2) to facilitate the use of the dataset.-br /- -br /- -br /- Further information on the Dataset-br /- This dataset is the result of a combination between different databases of different types and that have been downloaded from different sources. Below, I describe the main steps in data management that resulted in the production of the dataset in an Esri ArcGIS (ArcMap, Version 10.7) project.-br /- 1. The high resolution layer (HRL) of the imperviousness density data (IMD) for 2015 has been downloaded from the official website of Copernicus. At the time of producing the dataset (April/May 2021), the 2018 version of the IMD HRL database was not yet validated, so the 2015 version was chosen instead. The type of this dataset is raster. 2. For both Barcelona and Milan, shapefiles of their administrative boundaries have been downloaded from official sources, i.e. the ISTAT (Italian National Statistical Institute) and the ICGC (Catalan Institute for Cartography and Geology). These files have been reprojected to match the IMD HRL projection, i.e. ETRS 1989 LAEA. 3. Urban Atlas (UA) boundaries for the Greater Cities (GRC) and Functional Urban Areas (FUA) of Barcelona and Milan have been checked and reconstructed in Esri ArcGIS from the administrative boundaries files by using a Eurostat correspondence table. This is because at the time of the dataset creation (April/May 2021), the 2018 Urban Atlas shapefiles for these two cities were not fully updated or validated on the Copernicus Urban Atlas website. Therefore, I had to re-create the GRC and FUA boundaries by using the Eurostat correspondence table as an alternative (but still official) data source. The use of the Eurostat correspondence table with the codes and names of municipalities was also useful to detect discrepancies, basically stemming from changes in municipality names and codes and that created inconsistent spatial features. When detected, these discrepancies have been checked with the ISTAT and ICGC offices in charge of producing Urban Atlas data before the final GRC and FUA boundaries were defined.-br /- Steps 2) and 3) were the most time consuming, because they required other tools to be used in Esri ArcGIS, like spatial joins and geoprocessing tools for shapefiles (in particular dissolve and area re-calculator in editing sessions) for each of the spatial/territorial scales as indicated in letters a)-h). -br /- Once the databases for both Barcelona and Milan as described in points 2) and 3) were ready (uploaded in Esri ArcGIS, reprojected and their correctness checked), they have been ‘crossed’ (i.e. clipped) with the IMD HRL as described in point 1) and a specific raster for each territorial level has been calculated. The procedure in Esri ArcGIS was the following: * Clipping: Arctoolbox - Data management tools - Raster - Raster Processing - Clip. The ‘input’ file is the HRL IMD raster file as described in point 1) and the ‘output’ file is each of the spatial/territorial files. The option "Use Input Features for Clipping Geometry (optional)” was selected for each of the clipping. * Delete and create raster attribute table: Once the clipping has been done, the raster has to be recalculated first through Arctoolbox - Data management tools - Raster - Raster properties - Delete Raster Attribute Table and then through Arctoolbox - Data management tools - Raster - Raster properties - Build Raster Attribute Table; the "overwrite" option has been selected. -br /- -br /- Other tools used for the raster files in Esri ArcGIS have been the spatial analyst tools (in particular, Zonal - Zonal Statistics). As an additional check, the colour scheme of each of the newly created raster for each of the spatial/territorial attributes as per letters a)-h) above has been changed to check the consistency of its overlay with the original HRL IMD file. However, a perfect match between the shapefiles as per letters a)-h) and the raster files could not be achieved since the raster files are composed of 20x20mt cells.-br /- The newly created attribute tables of each of the raster files have been exported and saved as .txt files. These .txt files have then been copied in the excel corresponding to the final published dataset.

Link to the ScienceBase Item Summary page for the item described by this metadata record. Service Protocol: Link to the ScienceBase Item Summary page for the item described by this metadata record. Application Profile: Web Browser. Link Function: information

Precinct (voting district) polygon boundaries for 2022 collected by the Maryland Department of Planning (Planning) from counties (including Baltimore City) or digitized by Planning in coordination with counties, with precinct numbers reformatted as necessary for statewide consistency (see VTD field specifications below). All data are reprojected to WGS 1984 Web Mercator (auxiliary sphere) consistent with MD iMap standards, but precincts are otherwise delineated as received from counties. Planning may complete minor future adjustments to ensure precincts are edge matched with Census block boundaries.Fields include: JURSCODE (Jurisdiction Code) – MdProperty View jurisdiction code (four-letter county or Baltimore City code) COUNTY (County) – The US Census Bureau’s five-digit geographic identifier for each county in Maryland (including Baltimore City), which is includes the Maryland state code (24) followed by a three-digit county code. COUNTYNAME (County Name) – County name in text format VTD (Voting District Identifier) – Voting district identifier comprised of a five-digit county code (see “COUNTY” field) followed by a six-digit precinct identifier. The six-digit precinct identifier contains a two-digit election district number followed by a dash followed by a three-digit precinct number. This field is NULL for precinct names that could not be formatted according to these specifications. LABEL (Precinct Label) – Includes either the final six digits of the VTD field (precinct identifier) or the precinct name as provided by the county if a six-digit precinct identifier could not be derived from the source data. May be blank or NULL. Precinct labels are not unique across counties. NAME (Full Precinct Name) - Full precinct name, including the County Name and Precinct Label AGG_SRC (Aggregator Source) - Includes the aggregator organization credited with data aggregation, feature class name, and vintage date DATE_AGGREGATED (Date Aggregated) – Date the data were aggregated (YYMMDD) GIS_SRC (GIS Source) – The original source of the GIS spatial and attribute information the aggregator obtained, typically formatted as a shapefile or feature class name SRC_DATE (GIS Source Date) - The date (YYYYMMDD) the GIS data were obtained by the data aggregator. If the month or day is unknown, the date is YYYY0000This dataset includes historical precinct data from 2022. For the latest precinct information, please contact the Local Board of Elections: https://elections.maryland.gov/about/county_boards.html.This is a MD iMAP hosted service. Find more information at https://imap.maryland.gov.Feature Service Link:https://mdgeodata.md.gov/imap/rest/services/Boundaries/MD_ElectionBoundaries/FeatureServer/2

This dataset is a series of digital map-posters accompanying the AdaptNRM Guide: Helping Biodiversity Adapt: supporting climate adaptation planning using a community-level modelling approach.

These represent supporting materials and information about the community-level biodiversity models applied to climate change. Map posters are organised by four biological groups (vascular plants, mammals, reptiles and amphibians), two climate change scenario (1990-2050 MIROC5 and CanESM2 for RCP8.5), and five measures of change in biodiversity.

The map-posters present the nationally consistent data at locally relevant resolutions in eight parts – representing broad groupings of NRM regions based on the cluster boundaries used for climate adaptation planning (http://www.environment.gov.au/climate-change/adaptation) and also Nationally.

Map-posters are provided in PNG image format at moderate resolution (300dpi) to suit A0 printing. The posters were designed to meet A0 print size and digital viewing resolution of map detail. An additional set in PDF image format has been created for ease of download for initial exploration and printing on A3 paper. Some text elements and map features may be fuzzy at this resolution.

Each map-poster contains four dataset images coloured using standard legends encompassing the potential range of the measure, even if that range is not represented in the dataset itself or across the map extent.

Most map series are provided in two parts: part 1 shows the two climate scenarios for vascular plants and mammals and part 2 shows reptiles and amphibians. Eight cluster maps for each series have a different colour theme and map extent. A national series is also provided. Annotation briefly outlines the topics presented in the Guide so that each poster stands alone for quick reference.

An additional 77 National maps presenting the probability distributions of each of 77 vegetation types – NVIS 4.1 major vegetation subgroups (NVIS subgroups) - are currently in preparation.

Example citations:

Williams KJ, Raisbeck-Brown N, Prober S, Harwood T (2015) Generalised projected distribution of vegetation types – NVIS 4.1 major vegetation subgroups (1990 and 2050), A0 map-poster 8.1 - East Coast NRM regions. CSIRO Land and Water Flagship, Canberra. Available online at www.AdaptNRM.org and https://data.csiro.au/dap/.

Williams KJ, Raisbeck-Brown N, Harwood T, Prober S (2015) Revegetation benefit (cleared natural areas) for vascular plants and mammals (1990-2050), A0 map-poster 9.1 - East Coast NRM regions. CSIRO Land and Water Flagship, Canberra. Available online at www.AdaptNRM.org and https://data.csiro.au/dap/.

This dataset has been delivered incrementally. Please check that you are accessing the latest version of the dataset. Lineage: The map posters show case the scientific data. The data layers have been developed at approximately 250m resolution (9 second) across the Australian continent to incorporate the interaction between climate and topography, and are best viewed using a geographic information system (GIS). Each data layers is 1Gb, and inaccessible to non-GIS users. The map posters provide easy access to the scientific data, enabling the outputs to be viewed at high resolution with geographical context information provided.

Maps were generated using layout and drawing tools in ArcGIS 10.2.2

A check list of map posters and datasets is provided with the collection.

Map Series: 7.(1-77) National probability distribution of vegetation type – NVIS 4.1 major vegetation subgroup pre-1750 #0x

8.1 Generalised projected distribution of vegetation types (NVIS subgroups) (1990 and 2050)

9.1 Revegetation benefit (cleared natural areas) for plants and mammals (1990-2050)

9.2 Revegetation benefit (cleared natural areas) for reptiles and amphibians (1990-2050)

10.1 Need for assisted dispersal for vascular plants and mammals (1990-2050)

10.2 Need for assisted dispersal for reptiles and amphibians (1990-2050)

11.1 Refugial potential for vascular plants and mammals (1990-2050)

11.1 Refugial potential for reptiles and amphibians (1990-2050)

12.1 Climate-driven future revegetation benefit for vascular plants and mammals (1990-2050)

12.2 Climate-driven future revegetation benefit for vascular reptiles and amphibians (1990-2050)

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. Final WUPA map classes used for interpreting the aerial photographs were derived (1) from plant associations and alliances described by CPRS, (2) from the Anderson (1976) Level II land use classification system, (3) from land cover classes, and (4) from unique stands specific to WUPA. A draft hard copy vegetation map at the 1:12,000 scale was printed and checked against the interpreted aerial photographs. As a final internal accuracy check, RSGIG applied photointerpretation observations and classification relevés over the vegetation map to determine if the polygon labels matched the field data. Map validation occurred prior to the accuracy assessment. Because of the difficulties in interpreting the vegetation directly from the aerial photographs, we eventually mapped and/or validated much of the project area in the field. Metadata are required for all spatial data produced by the federal government. RSGIG used SIMMS™ software to create the three FGDC-compliant metadata files attached to the spatial databases and to this report. The metadata files explain the vegetation coverage and ancillary coverages created by RSGIG, the plot data coverage created by CPRS, and the accuracy assessment data created by CPRS.

FEMA provides access to the National Flood Hazards Layer (NFHL) through web mapping services. The maps depict effective flood hazard information and supporting data. The primary flood hazard classification is indicated in the Flood Hazard Zones layer.The NFHL layers include:Flood hazard zones and labelsRiver Miles MarkersCross-sections and coastal transects and their labelsLetter of Map Revision (LOMR) boundaries and case numbersFlood Insurance Rate Map (FIRM) boundaries, labels and effective datesCoastal Barrier Resources System (CBRS) and Otherwise Protected Area (OPA) unitsCommunity boundaries and namesLeveesHydraulic and flood control structuresProfile and coastal transect baselinesLimit of Moderate Wave Action(LiMWA)Not all effective Flood Insurance Rate Maps (FIRM) have GIS data available. To view a list of available county and single-jurisdiction flood study data in GIS format and check the status of the NFHL GIS services, please visit the NFHL Status Page.Preliminary & Pending National Flood Hazard LayersThe Preliminary and Pending NFHL dataset represents the current pre-effective flood data for the country. These layers are updated as new preliminary and pending data becomes available, and data is removed from these layers as it becomes effective.For more information, please visit FEMA's website.To download map panels or GIS Data, go to: NFHL on FEMA GeoPlatform.Preliminary & Pending DataPreliminary data are for review and guidance purposes only. By viewing preliminary data and maps, the user acknowledges that the information provided is preliminary and subject to change. Preliminary data are not final and are presented in this national layer as the best information available at this time. Additionally, preliminary data cannot be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove preliminary data once pending data are available.Pending data are for early awareness of upcoming changes to regulatory flood map information. Until the data becomes effective, when it will appear in FEMA's National Flood Hazard Layer (NFHL), the data should not be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove pending data once effective data are available.To better understand Preliminary data please see the View Your Community's Preliminary Flood Hazard Data webpage.FEMA GeoPlatformFEMA's GIS flood map services are available through FEMAs GeoPlatform, an ArcGIS Online portal containing a variety of FEMA-related data.To view the NFHL on the FEMA GeoPlatform go to NFHL on FEMA GeoPlatform.To view the Preliminary and Pending national layers on the FEMA Geoplatform go to FEMA's Preliminary & Pending National Flood Hazard Layer.Technical InformationFlood hazard and supporting data are developed using specifications for horizontal control consistent with 1:12,000–scale mapping. If you plan to display maps from the NFHL with other map data for official purposes, ensure that the other information meets FEMA’s standards for map accuracy.The minimum horizontal positional accuracy for base map hydrographic and transportation features used with the NFHL is the NSSDA radial accuracy of 38 feet. United States Geological Survey (USGS) imagery and map services that meet this standard can be found by visiting the Knowledge Sharing Site (KSS) for Base Map Standards (420). Other base map standards can be found at https://riskmapportal.msc.fema.gov/kss/MapChanges/default.aspx. You will need a username and password to access this information.The NFHL data are from FEMA’s FIRM databases. New data are added continually. The NFHL also contains map changes to FIRM data made by LOMRs.The NFHL is stored in North American Datum of 1983, Geodetic Reference System 80 coordinate system, though many of the NFHL GIS web services support the Web Mercator Sphere projection commonly used in web mapping applications.Organization & DisplayThe NFHL is organized into many data layers. The layers display information at map scales appropriate for the data. A layer indicating the availability of NFHL data is displayed at map scales smaller than 1:250,000, regional overviews at map scales between 1:250,000 and 1:50,000, and detailed flood hazard maps at map scales of 1:50,000 and larger. The "Scalehint" item in the Capabilities file for the Web Map Service encodes the scale range for a layer.In addition, there are non-NFHL datasets provided in the GIS web services, such as information about the availability of flood data and maps, the national map panel scheme, and point locations for LOMA and LOMR-Fs. The LOMA are positioned less accurately than are the NFHL data.Layers in the public NFHL GIS services:Use the numbers shown below when referencing layers by number.0. NFHL Availability1. LOMRs2. LOMAs3. FIRM Panels4. Base Index5. PLSS6. Toplogical Low Confidence Areas7. River Mile Markers8. Datum Conversion Points9. Coastal Gages10. Gages11. Nodes12. High Water Marks13. Station Start Points14. Cross-Sections15. Coastal Transects16. Base Flood Elevations17. Profile Baselines18. Transect Baselines19. Limit of Moderate Wave Action20. Water Lines21. Coastal Barrier Resources System Area22. Political Jurisdictions23. Levees24. General Structures25. Primary Frontal Dunes26. Hydrologic Reaches27. Flood Hazard Boundaries28. Flood Hazard Zones29. Submittal Information30. Alluvial Fans31. Subbasins32. Water Areas

FEMA provides access to the National Flood Hazards Layer (NFHL) through web mapping services. The maps depict effective flood hazard information and supporting data. The primary flood hazard classification is indicated in the Flood Hazard Zones layer.The NFHL layers include:Flood hazard zones and labelsRiver Miles MarkersCross-sections and coastal transects and their labelsLetter of Map Revision (LOMR) boundaries and case numbersFlood Insurance Rate Map (FIRM) boundaries, labels and effective datesCoastal Barrier Resources System (CBRS) and Otherwise Protected Area (OPA) unitsCommunity boundaries and namesLeveesHydraulic and flood control structuresProfile and coastal transect baselinesLimit of Moderate Wave Action(LiMWA)Not all effective Flood Insurance Rate Maps (FIRM) have GIS data available. To view a list of available county and single-jurisdiction flood study data in GIS format and check the status of the NFHL GIS services, please visit the NFHL Status Page.Preliminary & Pending National Flood Hazard LayersThe Preliminary and Pending NFHL dataset represents the current pre-effective flood data for the country. These layers are updated as new preliminary and pending data becomes available, and data is removed from these layers as it becomes effective.For more information, please visit FEMA's website.To download map panels or GIS Data, go to: NFHL on FEMA GeoPlatform.Preliminary & Pending DataPreliminary data are for review and guidance purposes only. By viewing preliminary data and maps, the user acknowledges that the information provided is preliminary and subject to change. Preliminary data are not final and are presented in this national layer as the best information available at this time. Additionally, preliminary data cannot be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove preliminary data once pending data are available.Pending data are for early awareness of upcoming changes to regulatory flood map information. Until the data becomes effective, when it will appear in FEMA's National Flood Hazard Layer (NFHL), the data should not be used to rate flood insurance policies or enforce the Federal mandatory purchase requirement. FEMA will remove pending data once effective data are available.To better understand Preliminary data please see the View Your Community's Preliminary Flood Hazard Data webpage.FEMA GeoPlatformFEMA's GIS flood map services are available through FEMAs GeoPlatform, an ArcGIS Online portal containing a variety of FEMA-related data.To view the NFHL on the FEMA GeoPlatform go to NFHL on FEMA GeoPlatform.To view the Preliminary and Pending national layers on the FEMA Geoplatform go to FEMA's Preliminary & Pending National Flood Hazard Layer.Technical InformationFlood hazard and supporting data are developed using specifications for horizontal control consistent with 1:12,000–scale mapping. If you plan to display maps from the NFHL with other map data for official purposes, ensure that the other information meets FEMA’s standards for map accuracy.The minimum horizontal positional accuracy for base map hydrographic and transportation features used with the NFHL is the NSSDA radial accuracy of 38 feet. United States Geological Survey (USGS) imagery and map services that meet this standard can be found by visiting the Knowledge Sharing Site (KSS) for Base Map Standards (420). Other base map standards can be found at https://riskmapportal.msc.fema.gov/kss/MapChanges/default.aspx. You will need a username and password to access this information.The NFHL data are from FEMA’s FIRM databases. New data are added continually. The NFHL also contains map changes to FIRM data made by LOMRs.The NFHL is stored in North American Datum of 1983, Geodetic Reference System 80 coordinate system, though many of the NFHL GIS web services support the Web Mercator Sphere projection commonly used in web mapping applications.Organization & DisplayThe NFHL is organized into many data layers. The layers display information at map scales appropriate for the data. A layer indicating the availability of NFHL data is displayed at map scales smaller than 1:250,000, regional overviews at map scales between 1:250,000 and 1:50,000, and detailed flood hazard maps at map scales of 1:50,000 and larger. The "Scalehint" item in the Capabilities file for the Web Map Service encodes the scale range for a layer.In addition, there are non-NFHL datasets provided in the GIS web services, such as information about the availability of flood data and maps, the national map panel scheme, and point locations for LOMA and LOMR-Fs. The LOMA are positioned less accurately than are the NFHL data.Layers in the public NFHL GIS services:Use the numbers shown below when referencing layers by number.0. NFHL Availability1. LOMRs2. LOMAs3. FIRM Panels4. Base Index5. PLSS6. Toplogical Low Confidence Areas7. River Mile Markers8. Datum Conversion Points9. Coastal Gages10. Gages11. Nodes12. High Water Marks13. Station Start Points14. Cross-Sections15. Coastal Transects16. Base Flood Elevations17. Profile Baselines18. Transect Baselines19. Limit of Moderate Wave Action20. Water Lines21. Coastal Barrier Resources System Area22. Political Jurisdictions23. Levees24. General Structures25. Primary Frontal Dunes26. Hydrologic Reaches27. Flood Hazard Boundaries28. Flood Hazard Zones29. Submittal Information30. Alluvial Fans31. Subbasins32. Water Areas

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. Spatial data from field observation points and quantitative plots were used to edit the formation-level maps of Colonial National Historical Park to better reflect vegetation classes. Using ArcView 3.3, polygon boundaries were revised onscreen over leaf-off photography. Units used to label polygons on the map (i.e. map classes) are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson (Anderson et al. 1976) Level II classification system. Each polygon on the Colonial National Historical Park map was assigned to one of forty map classes based on plot data, field observations, aerial photography signatures, and topographic maps. The mapping boundary was based on park boundary data obtained Colonial National Historical Park in May 2003. The mapping boundary includes lands under a scenic easement at Swanns Point and it excludes the Cheatham Annex, an area that returned to US Navy ownership in February 2004. The vegetation map was clipped at the park boundary because areas outside the park were not surveyed or included in the accuracy assessment.

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. A draft hard copy vegetation map at the 1:12,000 scale was printed and checked against the interpreted aerial photographs. As a final internal accuracy check, we applied photointerpretative observations and classification relevés over the vegetation map to determine if the polygon labels matched the field data. Finally, map validation occurred prior to the accuracy assessment. Staff from RSGIG conducted a field trip in conjunction with other meetings in Flagstaff, AZ in January 2001 to refine and assess the initial mapping effort. On this trip we collected additional photointerpretative observations and ground-truthed aerial photograph signatures using landmarks and GPS waypoints. Map classes were lumped or split to account for inadequacies in the final photointerpretation. Metadata are required for all spatial data produced by the federal government. RSGIG used SIMMS™ software and CPRS used ArcCatalogue software to create the FGDC-compliant metadata files attached to the spatial databases and to this report (see Appendix A). The metadata files explain the vegetation coverage and ancillary coverages created by RSGIG, the classification relevé data coverage created by CPRS, and the accuracy assessment observation data created by CPRS.

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. Spatial data from observation points and quantitative plots were used to edit the formation-level maps of George Washington Birthplace National Monument to better reflect homogeneous vegetation classes. Using Arcview 3.3, polygon boundaries were revised onscreen over leaf-off photography. Units used to label polygons on the map (i.e. map classes) are equivalent to one or more vegetation classes from the regional vegetation classification, or to a land-use class from the Anderson Level II classification system. Each polygon on the George Washington Birthplace National Monument map was assigned to one of 19 map classes based on plot data, field observations, aerial photography signatures, and topographic maps.

Contains:World HillshadeWorld Street Map (with Relief) - Base LayerLarge Scale International Boundaries (v11.3)World Street Map (with Relief) - LabelsDoS Country Labels DoS Country LabelsCountry (admin 0) labels that have been vetted for compliance with foreign policy and legal requirements. These labels are part of the US Federal Government Basemap, which contains the borders and place names that have been vetted for compliance with foreign policy and legal requirements.Source: DoS Country Labels - Overview (arcgis.com)Large Scale International BoundariesVersion 11.3Release Date: December 19, 2023DownloadFor more information on the LSIB click here: https://geodata.state.gov/ A direct link to the data is available here: https://data.geodata.state.gov/LSIB.zipAn ISO-compliant version of the LSIB metadata (in ISO 19139 format) is here: https://geodata.state.gov/geonetwork/srv/eng/catalog.search#/metadata/3bdb81a0-c1b9-439a-a0b1-85dac30c59b2 Direct inquiries to internationalboundaries@state.govOverviewThe Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.3 (published 19 December 2023). The 11.3 release contains updates to boundary lines and data refinements enabling reuse of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control.National Geospatial Data AssetThis dataset is a National Geospatial Data Asset managed by the Department of State on behalf of the Federal Geographic Data Committee's International Boundaries Theme.DetailsSources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process involves analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground.Attribute StructureThe dataset uses thefollowing attributes:Attribute NameCC1COUNTRY1CC2COUNTRY2RANKSTATUSLABELNOTES These attributes are logically linked:Linked AttributesCC1COUNTRY1CC2COUNTRY2RANKSTATUS These attributes have external sources:Attribute NameExternal Data SourceCC1GENCCOUNTRY1DoS ListsCC2GENCCOUNTRY2DoS ListsThe eight attributes listed above describe the boundary lines contained within the LSIB dataset in both a human and machine-readable fashion. Other attributes in the release include "FID", "Shape", and "Shape_Leng" are components of the shapefile format and do not form an intrinsic part of the LSIB."CC1" and "CC2" fields are machine readable fields which contain political entity codes. These codes are derived from the Geopolitical Entities, Names, and Codes Standard (GENC) Edition 3 Update 18. The dataset uses the GENC two-character codes. The code ‘Q2’, which is not in GENC, denotes a line in the LSIB representing a boundary associated with an area not contained within the GENC standard.The "COUNTRY1" and "COUNTRY2" fields contain human-readable text corresponding to the name of the political entity. These names are names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the list of Independent States in the World and the list of Dependencies and Areas of Special Sovereignty maintained by the Department of State. To ensure the greatest compatibility, names are presented without diacritics and certain names are rendered using commonly accepted cartographic abbreviations. Names for lines associated with the code ‘Q2’ are descriptive and are not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS are names of independent states. Other names are those associated with dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user.The following fields are an intrinsic part of the LSIB dataset and do not rely on external sources:Attribute NameMandatoryContains NullsRANKYesNoSTATUSYesNoLABELNoYesNOTESNoYesNeither the "RANK" nor "STATUS" field contains null values; the "LABEL" and "NOTES" fields do.The "RANK" field is a numeric, machine-readable expression of the "STATUS" field. Collectively, these fields encode the views of the United States Government on the political status of the boundary line.Attribute NameValueRANK123STATUSInternational BoundaryOther Line of International Separation Special Line A value of "1" in the "RANK" field corresponds to an "International Boundary" value in the "STATUS" field. Values of "2" and "3" correspond to "Other Line of International Separation" and "Special Line", respectively.The "LABEL" field contains required text necessarily to describe the line segment. The "LABEL" field is used when the line segment is displayed on maps or other forms of cartographic visualizations. This includes most interactive products. The requirement to incorporate the contents of the "LABEL" field on these products is scale dependent. If a label is legible at the scale of a given static product a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field is not a line labeling field but does contain the preferred description for the three LSIB line types when lines are incorporated into a map legend. Using the "CC1", "CC2", or "RANK" fields for labeling purposes is prohibited.The "NOTES" field contains an explanation of any applicable special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, any limitations regarding the purpose of the lines, or the original source of the line. Use of the "NOTES" field for labeling purposes is prohibited.External Data SourcesGeopolitical Entities, Names, and Codes Registry: https://nsgreg.nga.mil/GENC-overview.jspU.S. Department of State List of Independent States in the World: https://www.state.gov/independent-states-in-the-world/U.S. Department of State List of Dependencies and Areas of Special Sovereignty: https://www.state.gov/dependencies-and-areas-of-special-sovereignty/The source for the U.S.—Canada international boundary (NGDAID97) is the International Boundary Commission: https://www.internationalboundarycommission.org/en/maps-coordinates/coordinates.phpThe source for the “International Boundary between the United States of America and the United States of Mexico” (NGDAID82) is the International Boundary and Water Commission: https://catalog.data.gov/dataset?q=usibwcCartographic UsageCartographic usage of the LSIB requires a visual differentiation between the three categories of boundaries. Specifically, this differentiation must be between:- International Boundaries (Rank 1);- Other Lines of International Separation (Rank 2); and- Special Lines (Rank 3).Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary.Additional cartographic information can be found in Guidance Bulletins (https://hiu.state.gov/data/cartographic_guidance_bulletins/) published by the Office of the Geographer and Global Issues.ContactDirect inquiries to internationalboundaries@state.gov.CreditsThe lines in the LSIB dataset are the product of decades of collaboration between geographers at the Department of State and the National Geospatial-Intelligence Agency with contributions from the Central Intelligence Agency and the UK Defence Geographic Centre.Attribution is welcome: U.S. Department of State, Office of the Geographer and Global Issues.Changes from Prior ReleaseThe 11.3 release is the third update in the version 11 series.This version of the LSIB contains changes and accuracy refinements for the following line segments. These changes reflect improvements in spatial accuracy derived from newly available source materials, an ongoing review process, or the publication of new treaties or agreements. Notable changes to lines include:• AFGHANISTAN / IRAN• ALBANIA / GREECE• ALBANIA / KOSOVO• ALBANIA/MONTENEGRO• ALBANIA / NORTH MACEDONIA• ALGERIA / MOROCCO• ARGENTINA / BOLIVIA• ARGENTINA / CHILE• BELARUS / POLAND• BOLIVIA / PARAGUAY• BRAZIL / GUYANA• BRAZIL / VENEZUELA• BRAZIL / French Guiana (FR.)• BRAZIL / SURINAME• CAMBODIA / LAOS• CAMBODIA / VIETNAM• CAMEROON / CHAD• CAMEROON / NIGERIA• CHINA / INDIA• CHINA / NORTH KOREA• CHINA / Aksai Chin• COLOMBIA / VENEZUELA• CONGO, DEM. REP. OF THE / UGANDA• CZECHIA / GERMANY• EGYPT / LIBYA• ESTONIA / RUSSIA• French Guiana (FR.) / SURINAME• GREECE / NORTH MACEDONIA• GUYANA / VENEZUELA• INDIA / Aksai Chin• KAZAKHSTAN / RUSSIA• KOSOVO / MONTENEGRO• KOSOVO / SERBIA• LAOS / VIETNAM• LATVIA / LITHUANIA• MEXICO / UNITED STATES• MONTENEGRO / SERBIA• MOROCCO / SPAIN• POLAND / RUSSIA• ROMANIA / UKRAINEVersions 11.0 and 11.1 were updates to boundary lines. Like this version, they also contained topology fixes, land boundary terminus refinements, and tripoint adjustments. Version 11.2 corrected a few errors in the attribute data and ensured that CC1 and CC2 attributes are in alignment with an updated version of the Geopolitical Entities, Names, and Codes (GENC) Standard, specifically Edition 3 Update 17.LayersLarge_Scale_International_BoundariesTerms of

Natural Earth is a public domain map dataset available at 1:10m, 1:50m, and 1:110 million scales. Featuring tightly integrated vector and raster data, with Natural Earth you can make a variety of visually pleasing, well-crafted maps with cartography or GIS software.

Natural Earth was built through a collaboration of many volunteers and is supported by NACIS (North American Cartographic Information Society).

Natural Earth Vector comes in ESRI shapefile format, the de facto standard for vector geodata. Character encoding is Windows-1252.

Natural Earth Vector includes features corresponding to the following:

Cultural Vector Data Thremes:

• Countries: matched boundary lines and polygons with names attributes for countries and sovereign states. Includes dependencies (French Polynesia), map units (U.S. Pacific Island Territories) and sub-national map subunits (Corsica versus mainland Metropolitan France).
• Disputed areas and breakaway regions - From Kashmir to the Elemi Triangle, Northern Cyprus to Western Sahara.
• First order admin (provinces, departments, states, etc.): internal boundaries and polygons for all but a few tiny island nations. Includes names attributes and some statistical groupings of the same for smaller countries.
• Populated places: point symbols with name attributes. Includes capitals, major cities and towns, plus significant smaller towns in sparsely inhabited regions. We favor regional significance over population census in determining rankings.
• Urban polygons: derived from 2002-2003 MODIS satellite data.
• Parks and protected areas: US National Park Service units.
• Pacific nation groupings: boxes for keeping these far-flung islands tidy.
• Water boundary indicators: partial selection of key 200-mile nautical limits, plus some disputed, treaty, and median lines.

Physical Vector Data Themes:

• Coastline: ocean coastline, including major islands. Coastline is matched to land and water polygons.
• Land: Land polygons including major islands
• Ocean: Ocean polygon split into contiguous pieces.
• Minor Islands: additional small ocean islands ranked to two levels of relative importance.
• Reefs: major coral reefs from WDB2.
• Physical region features: polygon and point labels of major physical features.
• Rivers and Lake Centerlines: ranked by relative importance. Includes name and line width attributes. Don’t want minor lakes? Turn on their centerlines to avoid unseemly data gaps.
• Lakes: ranked by relative importance, coordinating with river ranking. Includes name attributes.
• Glaciated areas: polygons derived from DCW, except for Antarctica derived from MOA. Includes name attributes for major polar glaciers.
• Antarctic ice shelves: derived from 2003-2004 MOA. Reflects recent ice shelf collapses.
• Bathymetry: nested polygons at 0, -200, -1,000, -2,000, -3,000, -4,000, -5,000, -6,000, -7,000, -8,000, -9,000,and -10,000 meters. Created from SRTM Plus.
• Geographic lines: Polar circles, tropical circles, equator, and International Date Line.
• Graticules: 1-, 5-, 10-, 15-, 20-, and 30-degree increments. Includes WGS84 bounding box.

City of Austin Open Data Terms of Use https://data.austintexas.gov/stories/s/ranj-cccq This dataset was created to depict approximate tree canopy cover for all land within the City of Austin's "full watershed regulation area." Intended for planning purposes and measuring citywide percent canopy. Definition: Tree canopy is defined as the layer of leaves, branches, and stems of trees that cover the ground when viewed from above. Methods: The 2022 tree canopy layer was derived from satellite imagery (Maxar) and aerial imagery (NAIP). Images were used to extract tree canopy into GIS vector features. First, a “visual recognition engine” generated the vector features. The engine used machine learning algorithms to detect and label image pixels as tree canopy. Then using prior knowledge of feature geometries, more modeling algorithms were used to predict and transform probability maps of labeled pixels into finished vector polygons depicting tree canopy. The resulting features were reviewed and edited through manual interpretation by GIS professionals. When appropriate, NAIP 2022 aerial imagery supplemented satellite images that had cloud cover, and a manual editing process made sure tree canopy represented 2022 conditions. Finally, an independent accuracy assessment was performed by the City of Austin and the Texas A&M Forest Service for quality assurance. GIS professionals assessed agreement between the tree canopy data and its source satellite imagery. An overall accuracy of 98% was found. Only 23 errors were found out of a total 1,000 locations reviewed. These were mostly omission errors (e.g. not including canopy in this dataset when canopy is shown in the satellite or aerial image). Best efforts were made to ensure ground-truth locations contained a tree on the ground. To ensure this, location data were used from City of Austin and Texas A&M Forest Service databases. Analysis: The City of Austin measures tree canopy using the calculation: acres of tree canopy divided by acres of land. The area of interest for the land acres is evaluated at the City of Austin's jurisdiction including Full Purpose, Limited Purpose, and Extraterritorial jurisdictions as of May 2023. New data show, in 2022, tree canopy covered 41% of the total land area within Austin's city limits (using city limit boundaries May 2023 and included in the download as layer name "city_of_austin_2023"). 160,046.50 canopy acres (2022) / 395,037.53 land acres = 40.51% ~41%. This compares to 36% last measured in 2018, and a historical average that’s also hovered around 36%. The time period between 2018 and 2022 saw a 5 percentage point change resulting in over 19K acres of canopy gained (estimated). Data Disclaimer: It's possible changes in percent canopy over the years is due to annexation and improved data methods (e.g. higher resolution imagery, AI, software used, etc.) in addition to actual in changes in tree canopy cover on the ground. For planning purposes only. Dataset does not account for individual trees, tree species nor any metric for tree canopy height. Tree canopy data is provided in vector GIS format housed in a Geodatabase. Download and unzip the folder to get started. Please note, errors may exist in this dataset due to the variation in species composition and land use found across the study area. This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries. This product has been produced by the City of Austin for the sole purpose of geographic reference. No warranty is made by the City of Austin regarding specific accuracy or completeness. Data Provider: Ecopia AI Tech Corporation and PlanIT Geo, Inc. Data derived from Maxar Technologies, Inc. and USDA NAIP imagery

Polygon feature GIS layer of all public park boundaries in Wyandotte County, KS. These boundaries are based primarily on public recreational land use extents interpreted from high resolution aerial imagery. A tax parcel GIS layer was the secondary information source (for land ownership). Additionally, this park layer's development started with a pre-existing park boundary GIS layer that used tax parcels as a basis. Published as an ESRI shapefile format, polygon vector layer, in US feet units in Kansas North State Plane coordinate system, NAD 83 datum Companion public parks datasets are available : 1) park_bldg_py for building footprints (polygons) 2) park facilities points layer (park_facility_pt), 3) plan line features like driveways, fences, etc (park_plan_ln), 4) plan point features like poles, light posts (park_plan_pt), 5) recreational facility polygons, e.g. tennis courts and ball diamonds (park_facility_py), 6) park trails (park_trail_ln) 6) GIS annotation labels are available to complement this park_py layer. Contact GSS for more information.By using this dataset you acknowledge the following:Kansas Open Records Act StatementThe Kansas Open Records Act provides in K.S.A. 45-230 that "no person shall knowingly sell, give or receive, for the purpose of selling or offering for sale, any property or service to persons listed therein, any list of names and addresses contained in, or derived from public records..." Violation of this law may subject the violator to a civil penalty of $500.00 for each violation. Violators will be reported for prosecution.By accessing this site, the user makes the following certification pursuant to K.S.A. 45-220(c)(2): "The requester does not intend to, and will not: (A) Use any list of names or addresses contained in or derived from the records or information for the purpose of selling or offering for sale any property or service to any person listed or to any person who resides at any address listed; or (B) sell, give or otherwise make available to any person any list of names or addresses contained in or derived from the records or information for the purpose of allowing that person to sell or offer for sale any property or service to any person listed or to any person who resides at any address listed."

This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.