This is a guide that describes how to interact with pop ups and the attribute tables in web maps where that functionality is available. Not all widgets or functionality is available in every web map.

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

Legacy product - no abstract available

Learn the building blocks of a query expression and how to select features that meet one or more attribute criteria.

This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

A major objective of plant ecology research is to determine the underlying processes responsible for the observed spatial distribution patterns of plant species. Plants can be approximated as points in space for this purpose, and thus, spatial point pattern analysis has become increasingly popular in ecological research. The basic piece of data for point pattern analysis is a point location of an ecological object in some study region. Therefore, point pattern analysis can only be performed if data can be collected. However, due to the lack of a convenient sampling method, a few previous studies have used point pattern analysis to examine the spatial patterns of grassland species. This is unfortunate because being able to explore point patterns in grassland systems has widespread implications for population dynamics, community-level patterns and ecological processes. In this study, we develop a new method to measure individual coordinates of species in grassland communities. This method records plant growing positions via digital picture samples that have been sub-blocked within a geographical information system (GIS). Here, we tested out the new method by measuring the individual coordinates of Stipa grandis in grazed and ungrazed S. grandis communities in a temperate steppe ecosystem in China. Furthermore, we analyzed the pattern of S. grandis by using the pair correlation function g(r) with both a homogeneous Poisson process and a heterogeneous Poisson process. Our results showed that individuals of S. grandis were overdispersed according to the homogeneous Poisson process at 0-0.16 m in the ungrazed community, while they were clustered at 0.19 m according to the homogeneous and heterogeneous Poisson processes in the grazed community. These results suggest that competitive interactions dominated the ungrazed community, while facilitative interactions dominated the grazed community. In sum, we successfully executed a new sampling method, using digital photography and a Geographical Information System, to collect experimental data on the spatial point patterns for the populations in this grassland community.

Methods 1. Data collection using digital photographs and GIS

A flat 5 m x 5 m sampling block was chosen in a study grassland community and divided with bamboo chopsticks into 100 sub-blocks of 50 cm x 50 cm (Fig. 1). A digital camera was then mounted to a telescoping stake and positioned in the center of each sub-block to photograph vegetation within a 0.25 m2 area. Pictures were taken 1.75 m above the ground at an approximate downward angle of 90° (Fig. 2). Automatic camera settings were used for focus, lighting and shutter speed. After photographing the plot as a whole, photographs were taken of each individual plant in each sub-block. In order to identify each individual plant from the digital images, each plant was uniquely marked before the pictures were taken (Fig. 2 B).

Digital images were imported into a computer as JPEG files, and the position of each plant in the pictures was determined using GIS. This involved four steps: 1) A reference frame (Fig. 3) was established using R2V software to designate control points, or the four vertexes of each sub-block (Appendix S1), so that all plants in each sub-block were within the same reference frame. The parallax and optical distortion in the raster images was then geometrically corrected based on these selected control points; 2) Maps, or layers in GIS terminology, were set up for each species as PROJECT files (Appendix S2), and all individuals in each sub-block were digitized using R2V software (Appendix S3). For accuracy, the digitization of plant individual locations was performed manually; 3) Each plant species layer was exported from a PROJECT file to a SHAPE file in R2V software (Appendix S4); 4) Finally each species layer was opened in Arc GIS software in the SHAPE file format, and attribute data from each species layer was exported into Arc GIS to obtain the precise coordinates for each species. This last phase involved four steps of its own, from adding the data (Appendix S5), to opening the attribute table (Appendix S6), to adding new x and y coordinate fields (Appendix S7) and to obtaining the x and y coordinates and filling in the new fields (Appendix S8).

1. Data reliability assessment

To determine the accuracy of our new method, we measured the individual locations of Leymus chinensis, a perennial rhizome grass, in representative community blocks 5 m x 5 m in size in typical steppe habitat in the Inner Mongolia Autonomous Region of China in July 2010 (Fig. 4 A). As our standard for comparison, we used a ruler to measure the individual coordinates of L. chinensis. We tested for significant differences between (1) the coordinates of L. chinensis, as measured with our new method and with the ruler, and (2) the pair correlation function g of L. chinensis, as measured with our new method and with the ruler (see section 3.2 Data Analysis). If (1) the coordinates of L. chinensis, as measured with our new method and with the ruler, and (2) the pair correlation function g of L. chinensis, as measured with our new method and with the ruler, did not differ significantly, then we could conclude that our new method of measuring the coordinates of L. chinensis was reliable.

We compared the results using a t-test (Table 1). We found no significant differences in either (1) the coordinates of L. chinensis or (2) the pair correlation function g of L. chinensis. Further, we compared the pattern characteristics of L. chinensis when measured by our new method against the ruler measurements using a null model. We found that the two pattern characteristics of L. chinensis did not differ significantly based on the homogenous Poisson process or complete spatial randomness (Fig. 4 B). Thus, we concluded that the data obtained using our new method was reliable enough to perform point pattern analysis with a null model in grassland communities.

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. An ArcInfo (copyright ESRI) GIS database was designed for THRO using the National Park GIS Database Design, Layout, and Procedures created by RSGIG. This was created through Arc Macro Language (AML) scripts that helped automate the transfer process and ensure that all spatial and attribute data was consistent and stored properly. Actual transfer of information from the interpreted aerial photographs to a digital, geo-referenced format involved two techniques, scanning (for the vegetation classes) and on-screen digitizing (for the land-use classes). Transferred information used to create vegetation polygon coverages and linear coverages in ArcInfo were based on quarter-quad borders. Attribute information including vegetation map unit, location, and aerial photo number was subsequently entered for all polygons. In addition, the spatial database has an FGDC-compliant metadata file.

Parcels and property data maintained and provided by Lee County Property Appraiser are converted to points. Property attribute data joined to parcel GIS layer by Lee County Government GIS. This dataset is generally used in spatial analysis.Process description: Parcel polygons, condominium points and property data provided by the Lee County Property Appraiser are processed by Lee County's GIS Department using the following steps:Join property data to parcel polygons Join property data to condo pointsConvert parcel polygons to points using ESRI's ArcGIS tool "Feature to Point" and designate the "Source" field "P".Load Condominium points into this layer and designate the "Source" field "C". Add X/Y coordinates in Florida State Plane West, NAD 83, feet using the "Add X/Y" tool.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue. See https://leepa.org/Docs/Codes/DOR_Code_List.pdf


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13

Parcels and property data maintained and provided by Lee County Property Appraiser. This dataset includes condominium units. Property attribute data joined to parcel GIS layer by Lee County Government GIS.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983

 Name
 Type
 Length
 Description


 STRAP
 String
 25
 17-digit Property ID (Section, Township, Range, Area, Block, Lot)


 BLOCK
 String
 10
 5-digit portion of STRAP (positions 9-13)


 LOT
 String
 8
 Last 4-digits of STRAP


 FOLIOID
 Double
 8
 Unique Property ID


 MAINTDATE
 Date
 8
 Date LeePA staff updated record


 MAINTWHO
 String
 20
 LeePA staff who updated record


 UPDATED
 Date
 8
 Data compilation date


 HIDE_STRAP
 String
 1
 Confidential parcel ownership


 TRSPARCEL
 String
 17
 Parcel ID sorted by Township, Range & Section


 DORCODE
 String
 2
 Department of Revenue property classification code


 CONDOTYPE
 String
 1
 Type of condominium: C (commercial) or R (residential)


 UNITOFMEAS
 String
 2
 Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)


 NUMUNITS
 Double
 8
 Number of Land Units (units defined in UNITOFMEAS)


 FRONTAGE
 Integer
 4
 Road Frontage in Feet


 DEPTH
 Integer
 4
 Property Depth in Feet


 GISACRES
 Double
 8
 Total Computed Acres from GIS


 TAXINGDIST
 String
 3
 Taxing District of Property


 TAXDISTDES
 String
 60
 Taxing District Description


 FIREDIST
 String
 3
 Fire District of Property


 FIREDISTDE
 String
 60
 Fire District Description


 ZONING
 String
 10
 Zoning of Property


 ZONINGAREA
 String
 3
 Governing Area for Zoning


 LANDUSECOD
 SmallInteger
 2
 Land Use Code


 LANDUSEDES
 String
 60
 Land Use Description


 LANDISON
 String
 5
 BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF


 SITEADDR
 String
 55
 Lee County Addressing/E911


 SITENUMBER
 String
 10
 Property Location - Street Number


 SITESTREET
 String
 40
 Street Name


 SITEUNIT
 String
 5
 Unit Number


 SITECITY
 String
 20
 City


 SITEZIP
 String
 5
 Zip Code


 JUST
 Double
 8
 Market Value


 ASSESSED
 Double
 8
 Building Value + Land Value


 TAXABLE
 Double
 8
 Taxable Value


 LAND
 Double
 8
 Land Value


 BUILDING
 Double
 8
 Building Value


 LXFV
 Double
 8
 Land Extra Feature Value


 BXFV
 Double
 8
 Building Extra Feature value


 NEWBUILT
 Double
 8
 New Construction Value


 AGAMOUNT
 Double
 8
 Agriculture Exemption Value


 DISAMOUNT
 Double
 8
 Disability Exemption Value


 HISTAMOUNT
 Double
 8
 Historical Exemption Value


 HSTDAMOUNT
 Double
 8
 Homestead Exemption Value


 SNRAMOUNT
 Double
 8
 Senior Exemption Value


 WHLYAMOUNT
 Double
 8
 Wholly Exemption Value


 WIDAMOUNT
 Double
 8
 Widow Exemption Value


 WIDRAMOUNT
 Double
 8
 Widower Exemption Value


 BLDGCOUNT
 SmallInteger
 2
 Total Number of Buildings on Parcel


 MINBUILTY
 SmallInteger
 2
 Oldest Building Built


 MAXBUILTY
 SmallInteger
 2
 Newest Building Built


 TOTALAREA
 Double
 8
 Total Building Area


 HEATEDAREA
 Double
 8
 Total Heated Area


 MAXSTORIES
 Double
 8
 Tallest Building on Parcel


 BEDROOMS
 Integer
 4
 Total Number of Bedrooms


 BATHROOMS
 Double
 8
 Total Number of Bathrooms / Not For Comm


 GARAGE
 String
 1
 Garage on Property 'Y'


 CARPORT
 String
 1
 Carport on Property 'Y'


 POOL
 String
 1
 Pool on Property 'Y'


 BOATDOCK
 String
 1
 Boat Dock on Property 'Y'


 SEAWALL
 String
 1
 Sea Wall on Property 'Y'


 NBLDGCOUNT
 SmallInteger
 2
 Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel


 NMINBUILTY
 SmallInteger
 2
 Oldest New Building Built


 NMAXBUILTY
 SmallInteger
 2
 Newest New Building Built


 NTOTALAREA
 Double
 8
 Total New Building Area


 NHEATEDARE
 Double
 8
 Total New Heated Area


 NMAXSTORIE
 Double
 8
 Tallest New Building on Parcel


 NBEDROOMS
 Integer
 4
 Total Number of New Bedrooms


 NBATHROOMS
 Double
 8
 Total Number of New Bathrooms/Not For Comm


 NGARAGE
 String
 1
 New Garage on Property 'Y'


 NCARPORT
 String
 1
 New Carport on Property 'Y'


 NPOOL
 String
 1
 New Pool on Property 'Y'


 NBOATDOCK
 String
 1
 New Boat Dock on Property 'Y'


 NSEAWALL
 String
 1
 New Sea Wall on Property 'Y'


 O_NAME
 String
 30
 Owner Name


 O_OTHERS
 String
 120
 Other Owners


 O_CAREOF
 String
 30
 In Care Of Line


 O_ADDR1
 String
 30
 Owner Mailing Address Line 1


 O_ADDR2
 String
 30
 Owner Mailing Address Line 2


 O_CITY
 String
 30
 Owner Mailing City


 O_STATE
 String
 2
 Owner Mailing State


 O_ZIP
 String
 9
 Owner Mailing Zip


 O_COUNTRY
 String
 30
 Owner Mailing Country


 S_1DATE
 Date
 8
 Most Current Sale Date > $100.00


 S_1AMOUNT
 Double
 8
 Sale Amount


 S_1VI
 String
 1
 Sale Vacant or Improved


 S_1TC
 String
 2
 Sale Transaction Code


 S_1TOC
 String
 2
 Sale Transaction Override Code


 S_1OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_2DATE
 Date
 8
 Previous Sale Date > $100.00


 S_2AMOUNT
 Double
 8
 Sale Amount


 S_2VI
 String
 1
 Sale Vacant or Improved


 S_2TC
 String
 2
 Sale Transaction Code


 S_2TOC
 String
 2
 Sale Transaction Override Code


 S_2OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_3DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_3AMOUNT
 Double
 8
 Sale Amount


 S_3VI
 String
 1
 Sale Vacant or Improved


 S_3TC
 String
 2
 Sale Transaction Code


 S_3TOC
 String
 2
 Sale Transaction Override Code


 S_3OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 S_4DATE
 Date
 8
 Next Previous Sale Date > $100.00


 S_4AMOUNT
 Double
 8
 Sale Amount


 S_4VI
 String
 1
 Sale Vacant or Improved


 S_4TC
 String
 2
 Sale Transaction Code


 S_4TOC
 String
 2
 Sale Transaction Override Code


 S_4OR_NUM
 String
 13
 Original Record (Lee County Clerk)


 LEGAL
 String
 255
 Full Legal Description (On Deed)


 GARBDIST
 String
 3
 County Garbage Hauling Area


 GARBTYPE
 String
 1
 County Garbage Pick-up Type


 GARBCOMCAT
 String
 1
 County Garbage Commercial Category


 GARBHEADER
 String
 1
 Garbage Header Code


 GARBUNITS
 Double
 8
 Number of Garbage Units


 CREATEYEAR

The Geospatial Analytics Market size was valued at USD 79.06 USD billion in 2023 and is projected to reach USD 202.74 USD billion by 2032, exhibiting a CAGR of 14.4 % during the forecast period. The growing adoption of location-based technologies and the increasing need for data-driven decision-making in various industries are key factors driving market growth. Geospatial analytics captures, produces and displays GIS (geographic information system)-maps and pictures that may be weather maps, GPS or satellite photos. The geospatial analysis as a tool works with state of art technology in every formats namely; the GPS, sensors that locates, social media, mobile devices, multi of the satellite imagery to produce data visualizations that are facilitating trend-finding in complex relations between people and places as well are the situations' understanding. Visualizations are depicted through the use of maps, graphs, figures, and cartograms that illustrate the entire historical picture as well as a current changing trend. This is why the forecast becomes more confident and the situation is anticipated better. Recent developments include: February 2024: Placer.ai and Esri, a Geographic Information System (GIS) technology provider, partnered to empower customers with enhanced analytics capabilities, integrating consumer behavior analysis. Additionally, the agreement will foster collaborations to unlock further features by synergizing our respective product offerings., December 2023: CKS and Esri India Technologies Pvt Ltd teamed up to introduce the 'MMGEIS' program, focusing on students from 8th grade to undergraduates, to position India as a global leader in geospatial technology through skill development and innovation., December 2023: In collaboration with Bayanat, the UAE Space Agency revealed the initiation of the operational phase of the Geospatial Analytics Platform during its participation in organizing the Space at COP28 initiatives., November 2023: USAID unveiled its inaugural Geospatial Strategy, designed to harness geospatial data and technology for more targeted international program delivery. The strategy foresees a future where geographic methods enhance the effectiveness of USAID's efforts by pinpointing development needs, monitoring program implementation, and evaluating outcomes based on location., May 2023: TomTom International BV, a geolocation technology specialist, expanded its partnership with Alteryx, Inc. Through this partnership, Alteryx will use TomTom’s Maps APIs and location data to integrate spatial data into Alteryx’s products and location insights packages, such as Alteryx Designer., May 2023: Oracle Corporation announced the launch of Oracle Spatial Studio 23.1, available in the Oracle Cloud Infrastructure (OCI) marketplace and for on-premises deployment. Users can browse, explore, and analyze geographic data stored in and managed by Oracle using a no-code mapping tool., May 2023: CAPE Analytics, a property intelligence company, announced an enhanced insurance offering by leveraging Google geospatial data. Google’s geospatial data can help CAPE create appropriate solutions for insurance carriers., February 2023: HERE Global B.V. announced a collaboration with Cognizant, an information technology, services, and consulting company, to offer digital customer experience using location data. In this partnership, Cognizant will utilize the HERE location platform’s real-time traffic data, weather, and road attribute data to develop spatial intelligent solutions for its customers., July 2022: Athenium Analytics, a climate risk analytics company, launched a comprehensive tornado data set on the Esri ArcGIS Marketplace. This offering, which included the last 25 years of tornado insights from Athenium Analytics, would extend its Bronze partner relationship with Esri. . Key drivers for this market are: Advancements in Technologies to Fuel Market Growth. Potential restraints include: Lack of Standardization Coupled with Shortage of Skilled Workforce to Limit Market Growth. Notable trends are: Rise of Web-based GIS Platforms Will Transform Market.

The Lake County Data Extract provides parcel characteristics and tax information for all properties located in Lake County, Illinois. Casual users can find the standalone Tax Parcel Boundary Data above and Parcel Attribute Data here. The information contained in the extract is "as is", and Lake County does not in any way guarantee the correctness or accuracy of the information contained therein.

Download In State Plane Projection Here The 2024 Parcel Fabric Data is a copy of the Lake County Chief Assessor's Office spatial dataset, consisting of separate layers which represent the boundaries for Tax Parcels, Lots, Units, Subs, Condos, Rights of Way, and Encumbrance parcels, along with points, lines, and PLSS townships for reference, which have all been captured for the 2024 Tax Year.This data is spatial in nature and does not include extensive fields of attributes to which each layer may be associated. This data is provided for use to individuals or entities with an understanding of Esri's ArcGIS Pro (specifically the Parcel Fabric), and those with access to ArcGIS Pro, which is necessary to view or manipulate the data.Casual users can find the standalone Tax Parcel Boundary Data here and Parcel Attribute Data here. Update Frequency: This dataset is updated on a yearly basis.

A dataset of well information and geospatial data was developed for 426 U.S. Geological Survey (USGS) observation wells in Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island, and Vermont. An extensive list of attributes is included about each well, its location, and water-level history to provide the public and water-resources community with comprehensive information on the USGS well network in New England and data available from these sites. These data may be useful for evaluating groundwater conditions and variability across the region. The well list and site attributes, which were extracted from USGS National Water Information System (NWIS), represent all of the active wells in the New England network up to the end of 2017, and an additional 45 wells that were inactive (discontinued or replaced by a nearby well) at that time. Inactive wells were included in the database because they (1) contain periods of water-level record that may be useful for groundwater assessments, (2) may become active again at some point, or (3) are being monitored by another agency (most discontinued New Hampshire wells are still being monitored and the data are available in the National Groundwater Monitoring Network (https://cida.usgs.gov/ngwmn/index.jsp). The wells in this database have been sites of water-level data collection (periodic levels and/or continuous levels) for an average of 31 years. Water-level records go back to 1913. The groundwater-level statistics included in the dataset represent hydrologic conditions for the period of record for inactive wells, or through the end of water year 2017 (September 30, 2017) for active wells. Geographic Information Systems (GIS) data layers were compiled from various sources and dates ranging from 2003 to 2018. These GIS data were used to calculate attributes related to topographic setting, climate, land cover, soil, and geology giving hydrologic and environmental context to each well. In total, the data include 90 attributes for each well. In addition to site number and station name, attributes were developed for site information (15 attributes); groundwater-level statistics through water year 2017 (16 attributes); well-construction information (9 attributes); topographic setting (11 attributes); climate (2 attributes); land use and cover (17 attributes); soils (4 attributes); and geology (14 attributes). Basic well and site information includes well location, period of record, well-construction details, continuous versus intermittent data collection, and ground altitudes. Attributes that may influence groundwater levels include: well depth, location of open or screened interval, aquifer type, surficial and bedrock geology, topographic position, flow distance to surface water, land use and cover near the well, soil texture and drainage, precipitation, and air temperature.

The multiple attribute mapping process provides a vector based inventory of the landscape in\r terms of slope, terrain, landuse, vegetation, presence of tree regrowth, tree and shrub canopy\r density, presence of understorey, soil erosion condition, and rockiness. Mass movement and\r soil conservation measures are mapped where they exist, as is a selected range of weed\r species. These characteristics of the land are part of the larger set of characteristics that can\r be mapped using the NSW Dept. of Land and Water Conservation's full set of attribute codes.\r This set of codes are termed the Standard Classification for Attributes of Land (SCALD). The\r value of the attribute mapping is that the data objectively characterises the land and can be\r used for a range of land uses and land management purposes. This system of mapping\r maximises the efficiency of GIS operation by describing a number of attributes into one\r polygon, avoiding problems caused by overlaying of different data sets.\r Mapping is carried out at 1:25000 scale using base maps from the NSW Land Information\r Centre medium scale topographic series. Outputs are most useful at the sub-catchment or\r regional scale but not at property level. The data are extremely valuable at the river basin scale\r for integrated catchment planning programmes The information can, however, be useful as a\r first level of information in property planning exercises.

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. An ArcInfo(tm) (ESRI) GIS database was designed for WICA using the National Park GIS Database Design, Layout, and Procedures created by the BOR. This was created through Arc Macro Language (AML) scripts that helped automate the transfer process and ensure that all spatial and attribute data was consistent and stored properly. Actual transfer of information from the interpreted aerial photographs to a digital, geo-referenced format involved two techniques, scanning (for the vegetation classes) and on-screen digitizing (for the land-use classes). Both techniques required the use of 14 digital black-and-white orthophoto quarter quadrangles (DOQQ's) covering the study area. Transferred information was used to create vegetation polygon coverages and ancillary linear coverages in ArcInfo(tm) for each WICA DOQQ. Attribute information including vegetation map unit, location, and aerial photo number was subsequently entered for all polygons.

Crime data assembled by census block group for the MSA from the Applied Geographic Solutions' (AGS) 1999 and 2005 'CrimeRisk' databases distributed by the Tetrad Computer Applications Inc. CrimeRisk is the result of an extensive analysis of FBI crime statistics. Based on detailed modeling of the relationships between crime and demographics, CrimeRisk provides an accurate view of the relative risk of specific crime types at the block group level. Data from 1990 - 1996,1999, and 2004-2005 were used to compute the attributes, please refer to the 'Supplemental Information' section of the metadata for more details. Attributes are available for two categories of crimes, personal crimes and property crimes, along with total and personal crime indices. Attributes for personal crimes include murder, rape, robbery, and assault. Attributes for property crimes include burglary, larceny, and mother vehicle theft. 12 block groups have no attribute information. CrimeRisk is a block group and higher level geographic database consisting of a series of standardized indexes for a range of serious crimes against both persons and property. It is derived from an extensive analysis of several years of crime reports from the vast majority of law enforcement jurisdictions nationwide. The crimes included in the database are the "Part I" crimes and include murder, rape, robbery, assault, burglary, theft, and motor vehicle theft. These categories are the primary reporting categories used by the FBI in its Uniform Crime Report (UCR), with the exception of Arson, for which data is very inconsistently reported at the jurisdictional level. Part II crimes are not reported in the detail databases and are generally available only for selected areas or at high levels of geography. In accordance with the reporting procedures using in the UCR reports, aggregate indexes have been prepared for personal and property crimes separately, as well as a total index. While this provides a useful measure of the relative "overall" crime rate in an area, it must be recognized that these are unweighted indexes, in that a murder is weighted no more heavily than a purse snatching in the computation. For this reason, caution is advised when using any of the aggregate index values. The block group boundaries used in the dataset come from TeleAtlas's (formerly GDT) Dynamap data, and are consistent with all other block group boundaries in the BES geodatabase.

   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.


   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Tags

   survey, environmental behaviors, lifestyle, status, PRIZM, Baltimore Ecosystem Study, LTER, BES




   Summary


   BES Research, Applications, and Education


   Description


   Geocoded for Baltimore County. The BES Household Survey 2003 is a telephone survey of metropolitan Baltimore residents consisting of 29 questions. The survey research firm, Hollander, Cohen, and McBride conducted the survey, asking respondents questions about their outdoor recreation activities, watershed knowledge, environmental behavior, neighborhood characteristics and quality of life, lawn maintenance, satisfaction with life, neighborhood, and the environment, and demographic information. The data from each respondent is also associated with a PRIZM� classification, census block group, and latitude-longitude. PRIZM� classifications categorize the American population using Census data, market research surveys, public opinion polls, and point-of-purchase receipts. The PRIZM� classification is spatially explicit allowing the survey data to be viewed and analyzed spatially and allowing specific neighborhood types to be identified and compared based on the survey data. The census block group and latitude-longitude data also allow us additional methods of presenting and analyzing the data spatially. 


   The household survey is part of the core data collection of the Baltimore Ecosystem Study to classify and characterize social and ecological dimensions of neighborhoods (patches) over time and across space. This survey is linked to other core data including US Census data, remotely-sensed data, and field data collection, including the BES DemSoc Field Observation Survey. 



   The BES 2003 telephone survey was conducted by Hollander, Cohen, and McBride from September 1-30, 2003. The sample was obtained from the professional sampling firm Claritas, in order that their "PRIZM" encoding would be appended to each piece of sample (telephone number) supplied. Mailing addresses were also obtained so that a postcard could be sent in advance of interviewers calling. The postcard briefly informed potential respondents about the survey, who was conducting it, and that they might receive a phone call in the next few weeks. A stratified sampling method was used to obtain between 50 - 150 respondents in each of the 15 main PRIZM classifications. This allows direct comparison of PRIZM classifications. Analysis of the data for the general metropolitan Baltimore area must be weighted to match the population proportions normally found in the region. They obtained a total of 9000 telephone numbers in the sample. All 9,000 numbers were dialed but contact was only made on 4,880. 1508 completed an interview, 2524 refused immediately, 147 broke off/incomplete, 84 respondents had moved and were no longer in the correct location, and a qualified respondent was not available on 617 calls. This resulted in a response rate of 36.1% compared with a response rate of 28.2% in 2000. The CATI software (Computer Assisted Terminal Interviewing) randomized the random sample supplied, and was programmed for at least 3 attempted callbacks per number, with emphasis on pulling available callback sample prior to accessing uncalled numbers. Calling was conducted only during evening and weekend hours, when most head of households are home. The use of CATI facilitated stratified sampling on PRIZM classifications, centralized data collection, standardized interviewer training, and reduced the overall cost of primary data collection. Additionally, to reduce respondent burden, the questionnaire was revised to be concise, easy to understand, minimize the use of open-ended responses, and require an average of 15 minutes to complete. 


   The household survey is part of the core data collection of the Baltimore Ecosystem Study to classify and characterize social and ecological dimensions of neighborhoods (patches) over time and across space. This survey is linked to other core data, including US Census data, remotely-sensed data, and field data collection, including the BES DemSoc Field Observation Survey. 


   Additional documentation of this database is attached to this metadata and includes 4 documents, 1) the telephone survey, 2) documentation of the telephone survey, 3) metadata for the telephone survey, and 4) a description of the attribute data in the BES survey 2003 survey.


   This database was created by joining the GDT geographic database of US Census Block Group geographies for the Baltimore Metropolitan Statisticsal Area (MSA), with the Claritas PRIZM database, 2003, of unique classifications of each Census Block Group, and the unique PRIZM code for each respondent from the BES Household Telephone Survey, 2003. The GDT database is preferred and used because

Overview:This document describes the 2021 accessibility data released by the Accessibility Observatory at the University of Minnesota. The data are included in the National Accessibility Evaluation Project for 2021, and this information can be accessed for each state in the U.S. at https://access.umn.edu/research/america. The following sections describe the format, naming, and content of the data files.Data Formats: The data files are provided in a Geopackage format. Geopackage (.gpkg) files are an open-source, geospatial filetype that can contain multiple layers of data in a single file, and can be opened with most GIS software, including both ArcGIS and QGIS.Within this zipfile, there are six geopackage files (.gpkg) structured as follows. Each of them contains the blocks shapes layer, results at the block level for all LEHD variables (jobs and workers), with a layer of results for each travel time (5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60 minutes). {MPO ID}_tr_2021_0700-0859-avg.gpkg = Average Transit Access Departing Every Minute 7am-9am{MPO ID}_au_2021_08.gpkg = Average Auto Access Departing 8am{MPO ID}_bi_2021_1200_lts1.gpkg = Average Bike Access on LTS1 Network{MPO ID}_bi_2021_1200_lts2.gpkg = Average Bike Access on LTS2 Network{MPO ID}_bi_2021_1200_lts3.gpkg = Average Bike Access on LTS3 Network{MPO ID}_bi_2021_1200_lts4.gpkg = Average Bike Access on LTS4 NetworkFor mapping and geospatial analysis, the blocks shape layer within each geopackage can be joined to the blockid of the access attribute data. Opening and Using Geopackages in ArcGIS:Unzip the zip archiveUse the "Add Data" function in Arc to select the .gpkg fileSelect which layer(s) are needed — always select "main.blocks" as this layer contains the Census block shapes; select any other attribute data layers as well.There are three types of layers in the geopackage file — the "main.blocks" layer is the spatial features layer, and all other layers are either numerical attribute data tables, or the "fieldname_descriptions" metadata layer. The numerical attribute layers are named with the following format:[mode]_[threshold]_minutes[mode] is a two-character code indicating the transport mode used[threshold] is an integer indicating the travel time threshold used for this data layerTo use the data spatially, perform a join between the "main.blocks" layer and the desired numerical data layer, using either the numerical "id" fields, or 15-digit "blockid" fields as join fields.

This dataset is a compilation of county parcel data from Minnesota counties that have opted-in for their parcel data to be included in this dataset.

It includes the following 55 counties that have opted-in as of the publication date of this dataset: Aitkin, Anoka, Becker, Benton, Big Stone, Carlton, Carver, Cass, Chippewa, Chisago, Clay, Clearwater, Cook, Crow Wing, Dakota, Douglas, Fillmore, Grant, Hennepin, Houston, Isanti, Itasca, Jackson, Koochiching, Lac qui Parle, Lake, Lyon, Marshall, McLeod, Mille Lacs, Morrison, Mower, Murray, Norman, Olmsted, Otter Tail, Pennington, Pipestone, Polk, Pope, Ramsey, Renville, Rice, Saint Louis, Scott, Sherburne, Stearns, Stevens, Traverse, Waseca, Washington, Wilkin, Winona, Wright, and Yellow Medicine.

If you represent a county not included in this dataset and would like to opt-in, please contact Heather Albrecht (Heather.Albrecht@hennepin.us), co-chair of the Minnesota Geospatial Advisory Council (GAC)’s Parcels and Land Records Committee's Open Data Subcommittee. County parcel data does not need to be in the GAC parcel data standard to be included. MnGeo will map the county fields to the GAC standard.

County parcel data records have been assembled into a single dataset with a common coordinate system (UTM Zone 15) and common attribute schema. The county parcel data attributes have been mapped to the GAC parcel data standard for Minnesota: https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

This compiled parcel dataset was created using Python code developed by Minnesota state agency GIS professionals, and represents a best effort to map individual county source file attributes into the common attribute schema of the GAC parcel data standard. The attributes from counties are mapped to the most appropriate destination column. In some cases, the county source files included attributes that were not mapped to the GAC standard. Additionally, some county attribute fields were parsed and mapped to multiple GAC standard fields, such as a single line address. Each quarter, MnGeo provides a text file to counties that shows how county fields are mapped to the GAC standard. Additionally, this text file shows the fields that are not mapped to the standard and those that are parsed. If a county shares changes to how their data should be mapped, MnGeo updates the compilation. If you represent a county and would like to update how MnGeo is mapping your county attribute fields to this compiled dataset, please contact us.

This dataset is a snapshot of parcel data, and the source date of the county data may vary. Users should consult County websites to see the most up-to-date and complete parcel data.

There have been recent changes in date/time fields, and their processing, introduced by our software vendor. In some cases, this has resulted in date fields being empty. We are aware of the issue and are working to correct it for future parcel data releases.

The State of Minnesota makes no representation or warranties, express or implied, with respect to the use or reuse of data provided herewith, regardless of its format or the means of its transmission. THE DATA IS PROVIDED “AS IS” WITH NO GUARANTEE OR REPRESENTATION ABOUT THE ACCURACY, CURRENCY, SUITABILITY, PERFORMANCE, MECHANTABILITY, RELIABILITY OR FITINESS OF THIS DATA FOR ANY PARTICULAR PURPOSE. This dataset is NOT suitable for accurate boundary determination. Contact a licensed land surveyor if you have questions about boundary determinations.

DOWNLOAD NOTES: This dataset is only provided in Esri File Geodatabase and OGC GeoPackage formats. A shapefile is not available because the size of the dataset exceeds the limit for that format. The distribution version of the fgdb is compressed to help reduce the data footprint. QGIS users should consider using the Geopackage format for better results.

This dataset includes all 7 metro counties that have made their parcel data freely available without a license or fees.

This dataset is a compilation of tax parcel polygon and point layers assembled into a common coordinate system from Twin Cities, Minnesota metropolitan area counties. No attempt has been made to edgematch or rubbersheet between counties. A standard set of attribute fields is included for each county. The attributes are the same for the polygon and points layers. Not all attributes are populated for all counties.

NOTICE: The standard set of attributes changed to the MN Parcel Data Transfer Standard on 1/1/2019.
https://www.mngeo.state.mn.us/committee/standards/parcel_attrib/parcel_attrib.html

See section 5 of the metadata for an attribute summary.

Detailed information about the attributes can be found in the Metro Regional Parcel Attributes document.

The polygon layer contains one record for each real estate/tax parcel polygon within each county's parcel dataset. Some counties have polygons for each individual condominium, and others do not. (See Completeness in Section 2 of the metadata for more information.) The points layer includes the same attribute fields as the polygon dataset. The points are intended to provide information in situations where multiple tax parcels are represented by a single polygon. One primary example of this is the condominium, though some counties stacked polygons for condos. Condominiums, by definition, are legally owned as individual, taxed real estate units. Records for condominiums may not show up in the polygon dataset. The points for the point dataset often will be randomly placed or stacked within the parcel polygon with which they are associated.

The polygon layer is broken into individual county shape files. The points layer is provided as both individual county files and as one file for the entire metro area.

In many places a one-to-one relationship does not exist between these parcel polygons or points and the actual buildings or occupancy units that lie within them. There may be many buildings on one parcel and there may be many occupancy units (e.g. apartments, stores or offices) within each building. Additionally, no information exists within this dataset about residents of parcels. Parcel owner and taxpayer information exists for many, but not all counties.

This is a MetroGIS Regionally Endorsed dataset.

Additional information may be available from each county at the links listed below. Also, any questions or comments about suspected errors or omissions in this dataset can be addressed to the contact person at each individual county.

Anoka = http://www.anokacounty.us/315/GIS
Caver = http://www.co.carver.mn.us/GIS
Dakota = http://www.co.dakota.mn.us/homeproperty/propertymaps/pages/default.aspx
Hennepin = https://gis-hennepin.hub.arcgis.com/pages/open-data
Ramsey = https://www.ramseycounty.us/your-government/open-government/research-data
Scott = http://opendata.gis.co.scott.mn.us/
Washington: http://www.co.washington.mn.us/index.aspx?NID=1606