100+ datasets found
  1. a

    Parcel Points Shapefile

    • hub.arcgis.com
    • maps.leegov.com
    Updated Aug 15, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Lee County Florida GIS (2022). Parcel Points Shapefile [Dataset]. https://hub.arcgis.com/datasets/f13fddbfe8fb444da730974693ee643b
    Explore at:
    Dataset updated
    Aug 15, 2022
    Dataset authored and provided by
    Lee County Florida GIS
    Description

    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
    
  2. a

    Create Points on a Map

    • hub.arcgis.com
    Updated Jan 17, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    State of Delaware (2019). Create Points on a Map [Dataset]. https://hub.arcgis.com/documents/7d33adf39f8f4e92bcd49ba855247edb
    Explore at:
    Dataset updated
    Jan 17, 2019
    Dataset authored and provided by
    State of Delaware
    Description

    There are many ways to create spatial data. In this tutorial, you'll use an editing tool to draw features on an imagery basemap. The features you create will be saved in a feature class in your project geodatabase.Estimated time: 30 minutesSoftware requirements: ArcGIS Pro

  3. d

    Public Land Survey Corner (Feature Layer)

    • catalog.data.gov
    • agdatacommons.nal.usda.gov
    • +3more
    Updated Apr 21, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Public Land Survey Corner (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/public-land-survey-corner-feature-layer-50cdc
    Explore at:
    Dataset updated
    Apr 21, 2025
    Dataset provided by
    U.S. Forest Service
    Description

    Note: This is a large dataset. To download, go to ArcGIS Open Data Set and click the download button, and under additional resources select the shapefile or geodatabase option. A land survey point from a GCDB LX file, survey plat, or captured from a CFF land net coverage. Includes points generated by calculating an aliquot breakdown of a section.

  4. OpenStreetMap POIs for North America

    • hub.arcgis.com
    Updated Feb 15, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    OpenStreetMap (2022). OpenStreetMap POIs for North America [Dataset]. https://hub.arcgis.com/datasets/8929c22c1fc8418e8531b3d58ffca789
    Explore at:
    Dataset updated
    Feb 15, 2022
    Dataset authored and provided by
    OpenStreetMap//www.openstreetmap.org/
    License

    Open Database License (ODbL) v1.0https://www.opendatacommons.org/licenses/odbl/1.0/
    License information was derived automatically

    Area covered
    Description

    This feature layer provides access to OpenStreetMap (OSM) point of interest (POI) data for North America, which is updated every 1-2 minutes with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM point (node) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. The layer includes POIs with a large number of tags, including amenity, shop, tourism, and several more.Zoom in to large scales (e.g. City level or 1:40k scale) to see the POI features display. You can click on the feature to get the name of the POI. The name of the POI will display by default at very large scales (e.g. Building level of 1:2k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this POI layer displaying just one or two types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. amenity is bar or shop is alcohol), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers that are ready to use, but not for every type of amenity.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.

  5. Charles M. Russell National Wildlife Refuge Fire History GIS Feature Classes...

    • catalog.data.gov
    • datasets.ai
    Updated Feb 22, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Fish and Wildlife Service (2025). Charles M. Russell National Wildlife Refuge Fire History GIS Feature Classes [Dataset]. https://catalog.data.gov/dataset/charles-m-russell-national-wildlife-refuge-fire-history-gis-feature-classes
    Explore at:
    Dataset updated
    Feb 22, 2025
    Dataset provided by
    U.S. Fish and Wildlife Servicehttp://www.fws.gov/
    Description

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

  6. f

    Data from: Detecting common features from point patterns for similarity...

    • figshare.com
    zip
    Updated Jul 21, 2022
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Yifan Zhang (2022). Detecting common features from point patterns for similarity measurement using matrix decomposition [Dataset]. http://doi.org/10.6084/m9.figshare.19470593.v2
    Explore at:
    zipAvailable download formats
    Dataset updated
    Jul 21, 2022
    Dataset provided by
    figshare
    Authors
    Yifan Zhang
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    the dataset of paper "Detecting common features from point patterns for similarity measurement using matrix decomposition" the code is implemented by C# with ArcGIS Engine the data denotes points with X and Y please cite our paper if the dataset can help you with your research

  7. Research Station Facilities (Feature Layer)

    • catalog.data.gov
    • agdatacommons.nal.usda.gov
    • +6more
    Updated Apr 21, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Research Station Facilities (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/research-station-facilities-feature-layer-ce5fc
    Explore at:
    Dataset updated
    Apr 21, 2025
    Dataset provided by
    U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
    Description

    These data are a point feature class that provides the location of Research and Development's offices across the United States.

  8. Recreation Area Activities (Feature Layer)

    • catalog.data.gov
    • datadiscoverystudio.org
    • +7more
    Updated Jun 5, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Recreation Area Activities (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/recreation-area-activities-feature-layer-ce4a3
    Explore at:
    Dataset updated
    Jun 5, 2025
    Dataset provided by
    U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
    Description

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

  9. National USFS Fire Occurrence Point (Feature Layer)

    • catalog.data.gov
    • datasets.ai
    • +4more
    Updated Jul 11, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). National USFS Fire Occurrence Point (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/national-usfs-fire-occurrence-point-feature-layer-d3233
    Explore at:
    Dataset updated
    Jul 11, 2025
    Dataset provided by
    U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
    Description

    The FireOccurrence point layer represents ignition points, or points of origin, from which individual USFS wildland fires started. Data are maintained at the Forest/District level, or their equivalent, to track the occurrence and the origin of individual USFS wildland fires. Forests are working to include historical data, which may be incomplete.National USFS fire occurrence locations where wildland fires have historically occurred on National Forest System Lands and/or where protection is the responsibility of the US Forest Service. Knowing where wildland fire events have happened in the past is critical to land management efforts in the future.This data is utilized by fire & aviation staffs, land managers, land planners, and resource specialists on and around National Forest System Lands. The attributes included within the FireOccurrence point layer are needed to meet the needs of the US Forest Service, for data exchange between interagency data systems, to relate to the FirePerimeter polygon data layer and various fire data systems, and to track the locations of wildland fires.*This data has been updated to match 2021 National GIS Data Dictionary Standards.Metadata and Downloads

  10. m

    MassGIS Master Address Points (Feature Service)

    • gis.data.mass.gov
    • hub.arcgis.com
    Updated Feb 1, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    MassGIS - Bureau of Geographic Information (2024). MassGIS Master Address Points (Feature Service) [Dataset]. https://gis.data.mass.gov/datasets/massgis-master-address-points-feature-service
    Explore at:
    Dataset updated
    Feb 1, 2024
    Dataset authored and provided by
    MassGIS - Bureau of Geographic Information
    Area covered
    Description

    MassGIS is working very closely with the State 911 Department in the state’s Executive Office of Public Safety and Security on the Next Generation 911 Emergency Call System. MassGIS developed and is maintaining the map and address information that are at the heart of this new system. Statewide deployment of this new 9-1-1 call routing system was completed in 2018.Address sources include the Voter Registration List from the Secretary of the Commonwealth, site addresses from municipal departments (primarily assessors), and customer address lists from utilities. Addresses from utilities were “anonymized” to protect customer privacy. The MAD was also validated for completeness using the Emergency Service List (a list of telephone land line addresses) from Verizon.The MAD contains both tabular and spatial data, with addresses being mapped as point features. At present, the MAD contains 3.2 million address records and 2.2 million address points. As the database is very dynamic with changes being made daily, the data available for download will be refreshed weekly.A Statewide Addressing Standard for Municipalities is another useful asset that has been created as part of this ongoing project. It is a best practices guide for the creation and storage of addresses for Massachusetts Municipalities.Points features with each point having an address to the building/floor/unit level, when that information is available. Where more than one address is located at a single location multiple points are included (i.e. "stacked points"). The points for the most part represent building centroids. Other points are located as assessor parcel centroids.Points will display at scales 1:75,000 and closer.MassGIS' service does not contain points for Boston; they may be accessed at https://data.boston.gov/dataset/live-street-address-management-sam-addresses/resource/873a7659-68b6-4ac0-98b7-6d8af762b6f1.More details about the MAD and Master Address Points.Map service also available.

  11. Integrated Resource Restoration (IRR): Point (Feature Layer)

    • catalog.data.gov
    • agdatacommons.nal.usda.gov
    • +5more
    Updated Apr 21, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Integrated Resource Restoration (IRR): Point (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/integrated-resource-restoration-irr-point-feature-layer-5036e
    Explore at:
    Dataset updated
    Apr 21, 2025
    Dataset provided by
    U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
    Description

    Depicts the area of activities funded through the NFRR Budget Line Item and reported through the FACTS database. (The activities fall under number of acres treated annually to sustain or restore watershed function: acres of forestlands treated using timber sales, acres of forestland vegetation improved, acres of forestland vegetation established, acres of rangeland vegetation improved, acres treated for noxious weeds/invasive plants on NFS lands, and acres of hazardous fuels treated outside the wildland/urban interface (WUI) to reduce the risk of catastrophic wildland fire) and are self-reported by Forest Service Units. Metadata

  12. d

    Digital data for the Salinas Valley Geological Framework, California

    • catalog.data.gov
    • data.usgs.gov
    Updated Jul 6, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2024). Digital data for the Salinas Valley Geological Framework, California [Dataset]. https://catalog.data.gov/dataset/digital-data-for-the-salinas-valley-geological-framework-california
    Explore at:
    Dataset updated
    Jul 6, 2024
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Area covered
    California, Salinas Valley, Salinas
    Description

    This digital dataset was created as part of a U.S. Geological Survey study, done in cooperation with the Monterey County Water Resource Agency, to conduct a hydrologic resource assessment and develop an integrated numerical hydrologic model of the hydrologic system of Salinas Valley, CA. As part of this larger study, the USGS developed this digital dataset of geologic data and three-dimensional hydrogeologic framework models, referred to here as the Salinas Valley Geological Framework (SVGF), that define the elevation, thickness, extent, and lithology-based texture variations of nine hydrogeologic units in Salinas Valley, CA. The digital dataset includes a geospatial database that contains two main elements as GIS feature datasets: (1) input data to the 3D framework and textural models, within a feature dataset called “ModelInput”; and (2) interpolated elevation, thicknesses, and textural variability of the hydrogeologic units stored as arrays of polygonal cells, within a feature dataset called “ModelGrids”. The model input data in this data release include stratigraphic and lithologic information from water, monitoring, and oil and gas wells, as well as data from selected published cross sections, point data derived from geologic maps and geophysical data, and data sampled from parts of previous framework models. Input surface and subsurface data have been reduced to points that define the elevation of the top of each hydrogeologic units at x,y locations; these point data, stored in a GIS feature class named “ModelInputData”, serve as digital input to the framework models. The location of wells used a sources of subsurface stratigraphic and lithologic information are stored within the GIS feature class “ModelInputData”, but are also provided as separate point feature classes in the geospatial database. Faults that offset hydrogeologic units are provided as a separate line feature class. Borehole data are also released as a set of tables, each of which may be joined or related to well location through a unique well identifier present in each table. Tables are in Excel and ascii comma-separated value (CSV) format and include separate but related tables for well location, stratigraphic information of the depths to top and base of hydrogeologic units intercepted downhole, downhole lithologic information reported at 10-foot intervals, and information on how lithologic descriptors were classed as sediment texture. Two types of geologic frameworks were constructed and released within a GIS feature dataset called “ModelGrids”: a hydrostratigraphic framework where the elevation, thickness, and spatial extent of the nine hydrogeologic units were defined based on interpolation of the input data, and (2) a textural model for each hydrogeologic unit based on interpolation of classed downhole lithologic data. Each framework is stored as an array of polygonal cells: essentially a “flattened”, two-dimensional representation of a digital 3D geologic framework. The elevation and thickness of the hydrogeologic units are contained within a single polygon feature class SVGF_3DHFM, which contains a mesh of polygons that represent model cells that have multiple attributes including XY location, elevation and thickness of each hydrogeologic unit. Textural information for each hydrogeologic unit are stored in a second array of polygonal cells called SVGF_TextureModel. The spatial data are accompanied by non-spatial tables that describe the sources of geologic information, a glossary of terms, a description of model units that describes the nine hydrogeologic units modeled in this study. A data dictionary defines the structure of the dataset, defines all fields in all spatial data attributer tables and all columns in all nonspatial tables, and duplicates the Entity and Attribute information contained in the metadata file. Spatial data are also presented as shapefiles. Downhole data from boreholes are released as a set of tables related by a unique well identifier, tables are in Excel and ascii comma-separated value (CSV) format.

  13. d

    Western Bark Beetle Strategy: Point (Feature Layer)

    • catalog.data.gov
    • agdatacommons.nal.usda.gov
    • +5more
    Updated Jun 5, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2025). Western Bark Beetle Strategy: Point (Feature Layer) [Dataset]. https://catalog.data.gov/dataset/western-bark-beetle-strategy-point-feature-layer-b22c5
    Explore at:
    Dataset updated
    Jun 5, 2025
    Dataset provided by
    U.S. Forest Service
    Description

    Depicts the area of activities to implement the Western Bark Beetle Strategy. Activities were self-reported by field units, and center around three main objectives: increasing safety to ensure that people and community infrastructure are protected from the hazards of falling bark beetle-killed trees and elevated wildfire potential, facilitating recovery to re-establish forests damaged by bark beetles, and cultivating resiliency to prevent or mitigate future bark beetle impacts. Metadata

  14. Fire Points (CalOES Tracked)

    • wifire-data.sdsc.edu
    csv, esri rest +4
    Updated Jul 31, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    CA Governor's Office of Emergency Services (2019). Fire Points (CalOES Tracked) [Dataset]. https://wifire-data.sdsc.edu/dataset/fire-points-caloes-tracked
    Explore at:
    esri rest, csv, zip, kml, geojson, htmlAvailable download formats
    Dataset updated
    Jul 31, 2019
    Dataset provided by
    California Governor's Office of Emergency Services
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Description

    Feature layer showing all the fires tracked by Cal OES GIS for the year to date.


    Fire information is taken from the National Fire and Aviation Management (FAMWEB) in the form of ICS-209 reports. During normal operations these 209 reports are downloaded once a day at 0630, or soon after. During a SOC activation these 209 reports will be downloaded twice a day at 0630 and 1800. Cal OES GIS considers the FAMWEB ICS-209s as the authoritative fire information source.

    Fire perimeter data is downloaded from the National Interagency Fire Center (NIFC).

    The data for map is updated daily, M-F, by 0800, the map text by 0900, when there are active fires being tracked by Cal OES.

    If the SOC is activated the fire map will be updated daily, Sun-Sat, by 0800, the map text by 0900, until the SOC stands down.

    For a fire to be tracked by Cal OES GIS it needs to be:
    >100 acres in size
    Have an ICS-209 form.

    CalOES GIS indicates a fire as contained when it has reached >=90% containment.

  15. d

    Loudoun Soil Point Features

    • catalog.data.gov
    • data.virginia.gov
    • +8more
    Updated Apr 12, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Loudoun County GIS (2025). Loudoun Soil Point Features [Dataset]. https://catalog.data.gov/dataset/loudoun-soil-point-features-27aa4
    Explore at:
    Dataset updated
    Apr 12, 2025
    Dataset provided by
    Loudoun County GIS
    Area covered
    Loudoun County
    Description

    More MetadataAbstract: The soil spot points, or map symbols layer is a subset of the soils map. Spot points are isolated areas within a symbol that are designated with a symbol because the extent is too small to separate into another mapping unit. These points or symbols include areas such as sinkholes, springs, stony areas, wet spots, etc.Purpose: As a subset of the soils information, the spot points layer should be used in conjunction with the other soils layers. Spot points show specific areas that require special interpretation and/or land use which differs from the surrounding map unit.Supplemental Information: Data are stored in the corporate ArcSDE Geodatabase as a point feature class. The coordinate system is Virginia State Plane (North), Zone 4501, datum NAD83 HARN (vertical datum, if applicable, NAVD88), US Survey foot units.Maintenance and Update Frequency: As neededCompleteness Report: Features may have been eliminated or generalized due to scale and intended use. To assist Loudoun County, Virginia in the maintenance of the data, please provide any information concerning discovered errors, omissions, or other discrepancies found in the data.Soil Point Features: SP = Unknown; BPI = Borrow pit; CLA = Clay spot; GRA = Gravely spot; MDL = Made Land; ROC = Rock; SAN = Sandy spot; SNK = Sink hole; SPR = Spring; SSS = Soil sample spot; STN = Stoney spot; TEC = Terrace capping; WET = Wet spotData Owner: Department of Building and Development

  16. GeoForm (Deprecated)

    • noveladata.com
    • cityofdentongishub-dentontxgis.hub.arcgis.com
    • +1more
    Updated Jul 2, 2014
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    esri_en (2014). GeoForm (Deprecated) [Dataset]. https://www.noveladata.com/items/931653256fd24301a84fc77955914a82
    Explore at:
    Dataset updated
    Jul 2, 2014
    Dataset provided by
    Esrihttp://esri.com/
    Authors
    esri_en
    Description

    Geoform is a configurable app template for form based data editing of a Feature Service. This application allows users to enter data through a form instead of a map's pop-up while leveraging the power of the Web Map and editable Feature Services. This app geo-enables data and workflows by lowering the barrier of entry for completing simple tasks. Use CasesProvides a form-based experience for entering data through a form instead of a map pop-up. This is a good choice for users who find forms a more intuitive format than pop-ups for entering data.Useful to collect new point data from a large audience of non technical staff or members of the community.Configurable OptionsGeoform has an interactive builder used to configure the app in a step-by-step process. Use Geoform to collect new point data and configure it using the following options:Choose a web map and the editable layer(s) to be used for collection.Provide a title, logo image, and form instructions/details.Control and choose what attribute fields will be present in the form. Customize how they appear in the form, the order they appear in, and add hint text.Select from over 15 different layout themes.Choose the display field that will be used for sorting when viewing submitted entries.Enable offline support, social media sharing, default map extent, locate on load, and a basemap toggle button.Choose which locate methods are available in the form, including: current location, search, latitude and longitude, USNG coordinates, MGRS coordinates, and UTM coordinates.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

  17. V

    Loudoun Address Points

    • data.virginia.gov
    • business-loudoungis.opendata.arcgis.com
    • +9more
    Updated Feb 2, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Loudoun County (2024). Loudoun Address Points [Dataset]. https://data.virginia.gov/dataset/loudoun-address-points
    Explore at:
    zip, arcgis geoservices rest api, geojson, csv, kml, htmlAvailable download formats
    Dataset updated
    Feb 2, 2024
    Dataset provided by
    Loudoun County GIS
    Authors
    Loudoun County
    Area covered
    Loudoun County
    Description

    More Metadata


    Data updated daily.


    Address points mark the location of each addressable structure and its access point. The access point is the place where a driveway intersects the road. The building point is where the structure is located. An addressable structure is one where people live, work, or gather. A 1 to 5-digit number designates an address. Purpose: The access point is used to assign an address to the structure. Addresses are also assigned to assist in the provision of emergency services; they can be queried at all Fire and Rescue stations and by E-911 dispatchers. Supplemental Information: Data are stored in the corporate ArcSDE Geodatabase as a feature class. The coordinate system is Virginia State Plane (North), Zone 4501, datum NAD83 HARN. Maintenance and Update Frequency: Daily Completeness Report: Features may have been eliminated or generalized due to scale and intended use. To assist Loudoun County, Virginia in the maintenance of the data, please provide any information concerning discovered errors, omissions, or other discrepancies found in the data.

    Data Owner: Office of Mapping and Geographic Information

  18. n

    IRWIN Data Service User's Guide ( 20190325)

    • prep-response-portal.napsgfoundation.org
    • hub.arcgis.com
    • +2more
    Updated Nov 5, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    NAPSG Foundation (2019). IRWIN Data Service User's Guide ( 20190325) [Dataset]. https://prep-response-portal.napsgfoundation.org/documents/29d7b53aecc1491b9d42fd559368b22f
    Explore at:
    Dataset updated
    Nov 5, 2019
    Dataset authored and provided by
    NAPSG Foundation
    Description

    IntroductionIRWIN ArcGIS Online GeoPlatform Services The Integrated Reporting of Wildland-Fire Information (IRWIN) Production data is replicated every 60 seconds to the ArcGIS Online GeoPlatform organization so that read-only views can be provided for consumers. This replicated view is called the hosted datastore. The “IRWIN Data” group is a set of Feature Layer views based on the replicated IRWIN layers. These feature layers provide a near real-time feed of all valid IRWIN data. All incidents that have been shared through the integration service since May 20, 2014 are available through this service. The incident data provides the location of existing fires, size, conditions and several other attributes that help classify fires. The IRWIN Data service allows users to create a web map, share it with their organization, or pull it into ArcMap or ArcGIS Pro for more in-depth analysis.InstructionsTo allow the emergency management GIS staff to join the IRWIN Data group, they will need to set up an ArcGIS Online account through our account manager. Please send the response to Samantha Gibbes (Samantha.C.Gibbes@saic.com) and Kayloni Ahtong (kayloni_ahtong@ios.doi.gov). Use the below template and fill in each part as best as possible, where the point of contact (POC) is the person responsible for the account.Reply Email Body: The (name of application) application requests the following user account and access to the IRWIN Data group.POC Name: First name Last name and titlePOC Email: Username: <>_irwin (choose a username, something short, followed by _irwin)Business Justification: Once you are set up with the account, I will coordinate a call to go over any questions.

  19. California Overlapping Cities and Counties and Identifiers with Coastal...

    • data.ca.gov
    • gis.data.ca.gov
    • +1more
    Updated Feb 20, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Technology (2025). California Overlapping Cities and Counties and Identifiers with Coastal Buffers [Dataset]. https://data.ca.gov/dataset/california-overlapping-cities-and-counties-and-identifiers-with-coastal-buffers
    Explore at:
    txt, gdb, csv, arcgis geoservices rest api, geojson, html, kml, gpkg, zip, xlsxAvailable download formats
    Dataset updated
    Feb 20, 2025
    Dataset authored and provided by
    California Department of Technologyhttp://cdt.ca.gov/
    Area covered
    California
    Description

    WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

    • Metadata is missing or incomplete for some layers at this time and will be continuously improved.
    • We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.
    This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.

    Purpose

    County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.

    Related Layers

    This dataset is part of a grouping of many datasets:

    1. Cities: Only the city boundaries and attributes, without any unincorporated areas
    2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
    3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
    4. Place Abbreviations
    5. Unincorporated Areas (Coming Soon)
    6. Census Designated Places (Coming Soon)
    7. Cartographic Coastline
    Working with Coastal Buffers
    The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.

    Point of Contact

    California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

    Field and Abbreviation Definitions

    • COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
    • Place Name: CDTFA incorporated (city) or county name
    • County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
    • Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
    • GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
    • GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
    • Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
    • CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
    • Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
    • COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
    • GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

    Accuracy

    CDTFA"s source data notes the following about accuracy:

    City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated

  20. Chinook Abundance - Point Features [ds180]

    • data.ca.gov
    • data.cnra.ca.gov
    • +10more
    Updated Jan 31, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Fish and Wildlife (2020). Chinook Abundance - Point Features [ds180] [Dataset]. https://data.ca.gov/dataset/chinook-abundance-point-features-ds180
    Explore at:
    html, zip, arcgis geoservices rest api, csv, geojson, kmlAvailable download formats
    Dataset updated
    Jan 31, 2020
    Dataset authored and provided by
    California Department of Fish and Wildlifehttps://wildlife.ca.gov/
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    The dataset 'ds180_Chinook_pnts' is a product of the CalFish Adult Salmonid Abundance Database. Data in this shapefile are collected from point features, such as dams and hatcheries. Some escapement monitoring locations, such as spawning stock surveys, are logically represented by linear features. See the companion linear feature shapefile 'ds181_Chinook_ln' for information collected from stream reaches.

    The CalFish Abundance Database contains a comprehensive collection of anadromous fisheries abundance information. Beginning in 1998, the Pacific States Marine Fisheries Commission, the California Department of Fish and Game, and the National Marine Fisheries Service, began a cooperative project aimed at collecting, archiving, and entering into standardized electronic formats, the wealth of information generated by fisheries resource management agencies and tribes throughout California.

    The data format provides for sufficient detail to convey the relative accuracy of each population trend index record yet is simple and straight forward enough to be suited for public use. For those interested in more detail the database offers hyperlinks to digital copies of the original documents used to compile the information. In this way the database serves as an information hub directing the user to additional supporting information. This offers utility to field biologists and others interested in obtaining information for more in-depth analysis. Hyperlinks, built into the spatial data attribute tables used in the BIOS and CalFish I-map viewers, open the detailed index data archived in the on-line CalFish database application. The information can also be queried directly from the database via the CalFish Tabular Data Query. Once the detailed annual trend data are in view, another hyperlink opens a digital copy of the document used to compile each record.

    During 2010, as a part of the Central Valley Chinook Comprehensive Monitoring Plan, the CalFish Salmonid Abundance Database was reorganized and updated. CalFish provides a central location for sharing Central Valley Chinook salmon escapement estimates and annual monitoring reports to all stakeholders, including the public. Annual Chinook salmon in-river escapement indices that were, in many cases, eight to ten years behind are now current though 2009. In some cases, multiple datasets were consolidated into a single, more comprehensive, dataset to more closely reflect how data are reported in the California Department of Fish and Game standard index, Grandtab.

    Extensive data are currently available in the CalFish Abundance Database for California Chinook, coho, and steelhead. Major data categories include adult abundance population estimates, actual fish and/or carcass counts, counts of fish collected at dams, weirs, or traps, and redd counts. Harvest data has also been compiled for many streams.

    This CalFish Abundance Database shapefile was generated from fully routed 1:100,000 hydrography. In a few cases streams had to be added to the hydrography dataset in order to provide a means to create shapefiles to represent abundance data associated with them. Streams added were digitized at no more than 1:24,000 scale based on stream line images portrayed in 1:24,000 Digital Raster Graphics (DRG).

    The features in this layer represent the location for which abundance data records apply. In many cases there are multiple datasets associated with the same location, and so, features may overlap. Please view the associated datasets for detail regarding specific features. In CalFish these are accessed through the "link" field that is visible when performing an identify or query operation. A URL string is provided with each feature in the downloadable data which can also be used to access the underlying datasets.

    The Chinook data that is available from the CalFish website is actually mirrored from the StreamNet website where the CalFish Abundance Database's tabular data is currently stored. Additional information about StreamNet may be downloaded at http://www.streamnet.org" STYLE="text-decoration:underline;">http://www.streamnet.org. Complete documentation for the StreamNet database may be accessed at http://www.streamnet.org/online-data/data_develop.html" STYLE="text-decoration:underline;">http://http://www.streamnet.org/def.html

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Lee County Florida GIS (2022). Parcel Points Shapefile [Dataset]. https://hub.arcgis.com/datasets/f13fddbfe8fb444da730974693ee643b

Parcel Points Shapefile

Explore at:
Dataset updated
Aug 15, 2022
Dataset authored and provided by
Lee County Florida GIS
Description

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
Search
Clear search
Close search
Google apps
Main menu