67 datasets found
  1. a

    311 Issues Non Spatial

    • v3-api-demo-dcdev.opendata.arcgis.com
    • hub.arcgis.com
    Updated Aug 30, 2016
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Cape Coral GIS (2016). 311 Issues Non Spatial [Dataset]. https://v3-api-demo-dcdev.opendata.arcgis.com/datasets/CapeGIS::311-issues-non-spatial
    Explore at:
    Dataset updated
    Aug 30, 2016
    Dataset authored and provided by
    Cape Coral GIS
    Area covered
    Description

    This data was developed to represent city of cape coral citizen action center issues and their associated attributes for the purpose of mapping, analysis, and planning. The accuracy of this data varies and should not be used for precise measurements or calculations.

  2. 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
    Salinas, Salinas Valley, California
    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.

  3. W

    Asset database for the Central West subregion on 29 April 2015

    • cloud.csiss.gmu.edu
    • researchdata.edu.au
    • +3more
    Updated Dec 13, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Australia (2019). Asset database for the Central West subregion on 29 April 2015 [Dataset]. https://cloud.csiss.gmu.edu/uddi/dataset/5c3f9a56-7a48-4c26-a617-a186c2de5bf7
    Explore at:
    Dataset updated
    Dec 13, 2019
    Dataset provided by
    Australia
    Description

    Abstract

    The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

    This database is an initial Asset database for the Central West subregion on 29 April 2015. This dataset contains the spatial and non-spatial (attribute) components of the Central West subregion Asset List as one .mdb files, which is readable as an MS Access database and a personal geodatabase. Under the BA program, a spatial assets database is developed for each defined bioregional assessment project. The spatial elements that underpin the identification of water dependent assets are identified in the first instance by regional NRM organisations (via the WAIT tool) and supplemented with additional elements from national and state/territory government datasets. All reports received associated with the WAIT process for Central West are included in the zip file as part of this dataset. Elements are initially included in the preliminary assets database if they are partly or wholly within the subregion's preliminary assessment extent (Materiality Test 1, M1). Elements are then grouped into assets which are evaluated by project teams to determine whether they meet the second Materiality Test (M2). Assets meeting both Materiality Tests comprise the water dependent asset list. Descriptions of the assets identified in the Central West subregion are found in the "AssetList" table of the database. In this version of the database only M1 has been assessed. Assets are the spatial features used by project teams to model scenarios under the BA program. Detailed attribution does not exist at the asset level. Asset attribution includes only the core set of BA-derived attributes reflecting the BA classification hierarchy, as described in Appendix A of "CEN_asset_database_doc_20150429.doc ", located in the zip file as part of this dataset. The "Element_to_Asset" table contains the relationships and identifies the elements that were grouped to create each asset. Detailed information describing the database structure and content can be found in the document "CEN_asset_database_doc_20150429.doc" located in the zip file. Some of the source data used in the compilation of this dataset is restricted.

    Dataset History

    This is initial asset database.

    The Bioregional Assessments methodology (Barrett et al., 2013) defines a water-dependent asset as a spatially distinct, geo-referenced entity contained within a bioregion with characteristics having a defined cultural indigenous, economic or environmental value, and that can be linked directly or indirectly to a dependency on water quantity and/or quality.

    Under the BA program, a spatial assets database is developed for each defined bioregional assessment project. The spatial elements that underpin the identification of water dependent assets are identified in the first instance by regional NRM organisations (via the WAIT tool) and supplemented with additional elements from national and state/territory government datasets. Elements are initially included in database if they are partly or wholly within the subregion's preliminary assessment extent (Materiality Test 1, M1). Elements are then grouped into assets which are evaluated by project teams to determine whether they meet materiality test 2 (M2) - assets considered to be water dependent.

    Elements may be represented by a single, discrete spatial unit (polygon, line or point), or a number of spatial units occurring at more than one location (multipart polygons/lines or multipoints). Spatial features representing elements are not clipped to the preliminary assessment extent - features that extend beyond the boundary of the assessment extent have been included in full. To assist with an assessment of the relative importance of elements, area statements have been included as an attribute of the spatial data. Detailed attribute tables contain descriptions of the geographic features at the element level. Tables are organised by data source and can be joined to the spatial data on the "ElementID" field

    Elements are grouped into Assets, which are the objects used by project teams to model scenarios under the BA program. Detailed attribution does not exist at the asset level. Asset attribution includes only the core set of BA-derived attributes reflecting the BA classification hierarchy.

    The "Element_to_asset" table contains the relationships and identifies the elements that were grouped to create each asset.

    Following delivery of the first pass asset list, project teams make a determination as to whether an asset (comprised of one or more elements) is water dependent, as assessed against the materiality tests detailed in the BA Methodology. These decisions are provided to ERIN by the project team leader and incorporated into the Assetlist table in the Asset database. The Asset database is then re-registered into the BA repository.

    The Asset database dataset (which is registered to the BA repository) contains separate spatial and non-spatial databases.

    Non-spatial (tabular data) is provided in an ESRI personal geodatabase (.mdb - doubling as a MS Access database) to store, query, and manage non-spatial data. This database can be accessed using either MS Access or ESRI GIS products. Non-spatial data has been provided in the Access database to simplify the querying process for BA project teams. Source datasets are highly variable and have different attributes, so separate tables are maintained in the Access database to enable the querying of thematic source layers.

    Spatial data is provided as an ESRI file geodatabase (.gdb), and can only be used in an ESRI GIS environment. Spatial data is represented as a series of spatial feature classes (point, line and polygon layers). Non-spatial attribution can be joined from the Access database using the AID and ElementID fields, which are common to both the spatial and non-spatial datasets. Spatial layers containing all the point, line and polygon - derived elements and assets have been created to simplify management of the Elementlist and Assetlist tables, which list all the elements and assets, regardless of the spatial data geometry type. i.e. the total number of features in the combined spatial layers (points, lines, polygons) for assets (and elements) is equal to the total number of non-spatial records of all the individual data sources.

    Dataset Citation

    Department of the Environment (2013) Asset database for the Central West subregion on 29 April 2015. Bioregional Assessment Derived Dataset. Viewed 08 February 2017, http://data.bioregionalassessments.gov.au/dataset/5c3f9a56-7a48-4c26-a617-a186c2de5bf7.

    Dataset Ancestors

  4. Great Smoky Mountains National Park Maintained Landscapes

    • catalog.data.gov
    Updated Jun 4, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Park Service (2024). Great Smoky Mountains National Park Maintained Landscapes [Dataset]. https://catalog.data.gov/dataset/great-smoky-mountains-national-park-maintained-landscapes
    Explore at:
    Dataset updated
    Jun 4, 2024
    Dataset provided by
    National Park Servicehttp://www.nps.gov/
    Area covered
    Great Smoky Mountains
    Description

    Geospatial data can provide valuable visualization and analytical abilities to Facility and Resource Managers in regards to maintained landscapes throughout the NPS. Maintained landscapes are records in the Facility Management Software System (FMSS) and can include battlefields, ornamental gardens, picnic areas, and other types. To map a maintained area and the features within it at the enterprise level, a geospatial data service is needed to ensure consistency, accuracy, and thorough documentation of data lineage. The Maintained Landscape Spatial Data Service will structure maintained landscape data into a common format that will enable GIS data to be easily integrated, traced, analyzed and shared across the park. Such a structure will increase users’ ability to discern the quality and accuracy of the data enabling the user to make better data driven decisions. This schema is designed to match the structure and hierarchy of FMSS so that should this system become spatially enabled this data could be utilized. Within the FMSS database, features are organized in locations records and assets records. A location record could be thought of as a bin, within which component assets records are stored. Park Facilities Management Division(PFMD) Employees of the National Park Service are tasked with managing facilities such as roads, trails, buildings, and landscapes. To properly manage these assets PFMD must make management decisions based on spatial and non-spatial data. This service allows the accurate geographic representation of maintained landscapes in a common service-wide schema. Furthermore, the establishment of a maintained landscapes spatial data service will allow for the integration of several NPS managed databases. These include (but are not limited to) the Facilities Management Software System (FMSS), the Cultural Resources Enterprise Geographic Information System (CRGIS), the Cultural Landscapes Inventory (CLI), and the List of Classified Structures (LCS). The Cultural Resource Enterprise GIS dataset contains the cultural landscapes inventory spatial data, list of classified structures spatial data, National Register spatial data and links to all of these databases, as well as other partner programs

  5. a

    Budget Capital Projects 2019

    • opendata-cityofgp.hub.arcgis.com
    Updated Jul 16, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    The City of Grande Prairie (2019). Budget Capital Projects 2019 [Dataset]. https://opendata-cityofgp.hub.arcgis.com/datasets/6b4fe3337da8488d84c9284e1c4c4a82
    Explore at:
    Dataset updated
    Jul 16, 2019
    Dataset authored and provided by
    The City of Grande Prairie
    Area covered
    Description

    This layer shows a hosted table detailing information relating to the City of Grande Prairie's Capital Projects budget for 2019, including categories such as funding amount and project description. This information was downloaded from the city's open data portal for use in visualizing spatial and non-spatial data using GIS tools. It is used in an associated map and dashboard. All data is maintained by the City of Grande Prairie GIS department.

  6. a

    Infrastructure RoadsMaintenance

    • akscf-msb.opendata.arcgis.com
    • data.matsugov.us
    • +2more
    Updated Mar 6, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Matanuska-Susitna Borough (2019). Infrastructure RoadsMaintenance [Dataset]. https://akscf-msb.opendata.arcgis.com/items/8a2523dfc6d14509812f6732ba58c01b
    Explore at:
    Dataset updated
    Mar 6, 2019
    Dataset authored and provided by
    Matanuska-Susitna Borough
    Area covered
    Description

    Road centerlines with road names and generalized classifications is a snapshot from our spatial roads (addressing) dataset. Maintenance data was pulled from the Borough asset management software, Cartegraph, which is non-spatial. The non-spatial maintenance data was then tied to the spatial roads data through a series of joins and analyses.Roads with multiple maintenance groups listed have shared maintenance responsibilities; for example 1/2 the road may be maintained by the Borough and the other 1/2 maintained by a city. More detailed information regarding the distances each maintenance group is responsible for can be looked up in the Cartegraph database. This more detailed information can not currently be mapped due to differences in design between the spatial roads (911 addressing) dataset and the Cartegraph database.This dataset does not have a scheduled update cycle and should be viewed as just a snapshot in time. It was last updated in Sept 2017.

  7. a

    BeneficialUses

    • hub.arcgis.com
    Updated Aug 23, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Water Boards (2023). BeneficialUses [Dataset]. https://hub.arcgis.com/maps/waterboards::beneficialuses
    Explore at:
    Dataset updated
    Aug 23, 2023
    Dataset authored and provided by
    California Water Boards
    Area covered
    Description

    The California State Water Resources Control Board is currently in the process of improving the functionality and accessibility of information residing in their Water Quality Control Plans (aka Basin Plans). In order to achieve this, the data (i.e. statewide water quality objectives, beneficial uses, applicable TMDLs, etc.), are being transferred to a standardized digital format and linked to applicable surface water features. This dataset is limited to the beneficial uses data, while the water quality objectives, applicable TMDLs, etc. will be released at a later date. Data formats will include GIS data layers and numerous nonspatial data tables. The GIS layers contain hydrography features derived from a 2012 snapshot of the high-resolution (1:24000 scale) National Hydrography Dataset with added attribution. Nonspatial tables will contain various textual and numeric data from the Regional Basin and State Plans. The extent of the dataset covers the state of California and the non-spatial tables reflect the information and elements from the various plans used up to 2020. The GIS layers and associated attribution will enable the future integration of the various elements of the Basin Plans to ensure that all applicable Basin Plan requirements for a particular waterbody can be determined in a quick and precise manner across different modern mediums. The data are being managed and the project implemented by State and Regional Water Board staff using ESRI's ArcGIS Server and ArcSDE technology.The statewide layer is only provided as a map image layer service. The data is available as feature layer services by Regional Board extract. To view all regional board feature layer extracts go to the Basin Plan GIS Data Library Group here.

  8. Z

    Determination of areas with release potential of snow avalanche in Sharr...

    • data.niaid.nih.gov
    Updated Jul 17, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Idrizi, Bashkim (2024). Determination of areas with release potential of snow avalanche in Sharr Mountains in the Republic of Kosovo [Dataset]. https://data.niaid.nih.gov/resources?id=ZENODO_5841907
    Explore at:
    Dataset updated
    Jul 17, 2024
    Dataset provided by
    Bucaj, Besian
    Idrizi, Bashkim
    License

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

    Area covered
    Šar Mountains, Kosovo
    Description

    Avalanches represent a very high risk in residential areas, road infrastructure, environment, and economy, and can have fatal consequences if the human factors do not take any action. Advances in geospatial technology and access to spatial data have enabled spatial analysis to assist in decision-making regarding spatial planning in avalanche-prone locations. Determining locations with snow avalanche discharge potential is a crucial step in the avalanche zoning process.

    This research deals with areas with snow avalanche potential disjunction, based mainly on topographic factors followed by meteorological ones. Topographic factors were mainly determined according to morphometric techniques, which are achieved through geographic information systems (GIS), as well as meteorological ones from statistical data and various processing of spatial and non-spatial data. Spatial analysis are also supported by geostatistical methods Fuzzy Logic and AHP, which in interaction with GIS have enabled the achievement of the purpose of this paper. The results from the spatial analysis have been verified based on comparison methods, such as the ROC method which was used during this final phase, in which the analysis has shown that the methods used in this research have given satisfactory results. As the main result, we obtained maps of areas with snow avalanche potential discharge in the study area relating to two geostatistical methods.

  9. a

    GRSM MAINTAINED LANDSCAPES

    • hub.arcgis.com
    • mapdirect-fdep.opendata.arcgis.com
    Updated Mar 14, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Park Service (2025). GRSM MAINTAINED LANDSCAPES [Dataset]. https://hub.arcgis.com/maps/nps::grsm-maintained-landscapes
    Explore at:
    Dataset updated
    Mar 14, 2025
    Dataset authored and provided by
    National Park Service
    Area covered
    Description

    Geospatial data can provide valuable visualization and analytical abilities to Facility and Resource Managers in regards to maintained landscapes throughout the NPS. Maintained landscapes are records in the Facility Management Software System (FMSS) and can include battlefields, ornamental gardens, picnic areas, and other types. To map a maintained area and the features within it at the enterprise level, a geospatial data service is needed to ensure consistency, accuracy, and thorough documentation of data lineage. The Maintained Landscape Spatial Data Service will structure maintained landscape data into a common format that will enable GIS data to be easily integrated, traced, analyzed and shared across the park. Such a structure will increase users’ ability to discern the quality and accuracy of the data enabling the user to make better data driven decisions. This schema is designed to match the structure and hierarchy of FMSS so that should this system become spatially enabled this data could be utilized. Within the FMSS database, features are organized in locations records and assets records. A location record could be thought of as a bin, within which component assets records are stored. Park Facilities Management Division (PFMD) Employees of the National Park Service are tasked with managing facilities such as roads, trails, buildings, and landscapes. To properly manage these assets PFMD must make management decisions based on spatial and non-spatial data. This service allows the accurate geographic representation of maintained landscapes in a common service-wide schema. Furthermore, the establishment of a maintained landscapes spatial data service will allow for the integration of several NPS managed databases. These include (but are not limited to) the Facilities Management Software System (FMSS).The corresponding Integration of Resource Management Applications (IRMA) NPS Data Store reference is Great Smoky Mountains National Park Maintained Landscapes.

  10. California Basin Plan Beneficial Uses

    • gis.data.ca.gov
    • hub.arcgis.com
    Updated Aug 23, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Water Boards (2023). California Basin Plan Beneficial Uses [Dataset]. https://gis.data.ca.gov/maps/1b9f4712278e4b35ab77dc20e451b979
    Explore at:
    Dataset updated
    Aug 23, 2023
    Dataset provided by
    California State Water Resources Control Board
    Authors
    California Water Boards
    Area covered
    Description

    The California State Water Resources Control Board is currently in the process of improving the functionality and accessibility of information residing in their Water Quality Control Plans (aka Basin Plans). In order to achieve this, the data (i.e. statewide water quality objectives, beneficial uses, applicable TMDLs, etc.), are being transferred to a standardized digital format and linked to applicable surface water features. This dataset is limited to the beneficial uses data, while the water quality objectives, applicable TMDLs, etc. will be released at a later date. Data formats will include GIS data layers and numerous nonspatial data tables. The GIS layers contain hydrography features derived from a 2012 snapshot of the high-resolution (1:24000 scale) National Hydrography Dataset with added attribution. Nonspatial tables will contain various textual and numeric data from the Regional Basin and State Plans. The extent of the dataset covers the state of California and the non-spatial tables reflect the information and elements from the various plans used up to 2020. The GIS layers and associated attribution will enable the future integration of the various elements of the Basin Plans to ensure that all applicable Basin Plan requirements for a particular waterbody can be determined in a quick and precise manner across different modern mediums. The data are being managed and the project implemented by State and Regional Water Board staff using ESRI's ArcGIS Server and ArcSDE technology.The statewide layer is only provided as a map image layer service. The data is available as feature layer services by Regional Board extract. To view all regional board feature layer extracts go to the Basin Plan GIS Data Library Group here.

  11. d

    Great Smoky Mountains National Park Water Quality Monitoring Locations

    • datasets.ai
    • data.amerigeoss.org
    2, 55
    Updated Jul 20, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Department of the Interior (2015). Great Smoky Mountains National Park Water Quality Monitoring Locations [Dataset]. https://datasets.ai/datasets/great-smoky-mountains-national-park-water-quality-monitoring-locations
    Explore at:
    2, 55Available download formats
    Dataset updated
    Jul 20, 2015
    Dataset authored and provided by
    Department of the Interior
    Area covered
    Great Smoky Mountains
    Description

    A feature class depicting geographic locations where permanent water quality monitoring locations have been established in Great Smoky Mountains National Park. This includes monitoring location sites establised by the National Park Service and other state and federal agencies responsible for water quality monitoring and reporting. Agencies responsible for a monitoring location are listed in the attributes ORGANIZATIONIDENTIFIER and ORGANIZATIONFORMALNAME. For the display, query, and analysis of legacy and current hydrology spatial and tabular data; Consolidate and centralize a very diverse range and quantity of monitoring location site data from numerous programs and protocols; Mitigate the duplication of monitoring location data across shared systems; Allow for single-source identification and management of monitoring location sites that are "co-located"; Provide a single point of data entry, management, query, analysis, and display of water quality data from numerous sources, including STORET which are sourced from an accurate monitoring location database; Enable spatial relationship of water quality monitoring data to High-Resolution USGS NHD Reaches through the use of modern GIS, database, and statistics software; Support USGS and EPA standards for spatial and non-spatial hydrology and water quality data exchange and sharing. Very important details are included in the attached metadata document and should be read thouroughly before these data are used.

  12. f

    Data from: A Health GIS Based Approach to Portray the Influence of Ambient...

    • figshare.com
    pdf
    Updated Jan 20, 2016
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Mihir Bhatta; Debasish Das; Probal Ranjan Ghosh (2016). A Health GIS Based Approach to Portray the Influence of Ambient Temperature on Goat Health in Two Different Agro-Climatic Zones in West Bengal, India [Dataset]. http://doi.org/10.6084/m9.figshare.1507463.v1
    Explore at:
    pdfAvailable download formats
    Dataset updated
    Jan 20, 2016
    Dataset provided by
    figshare
    Authors
    Mihir Bhatta; Debasish Das; Probal Ranjan Ghosh
    License

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

    Area covered
    West Bengal, India
    Description

    AbstractThe spatial and temporal distribution patterns of the livestock health status in the developing countrieslike India are complex. In this regards, the application of Geographical Information System (GIS) isvaluable as it has many features that make it an ideal tool for use in animal health surveillance, monitoring,prediction and its management strategy. The goal of the present study is to find out the effect of ambienttemperature on goat health in two different agro-climatic zones in West Bengal, India with the additionalhelp of GIS technology. The highest mean value of temperature (42.6 ± 1.5 ºC) has been reported duringthe month of April or May in the season of pre-monsoon in Purulia. Survey of India (SOI) topographicalsheets (73 I/3 and 79 B/5) are used to map the study areas. Top sheets are scanned, geo-referenced andthen digitized with the help of GIS software. The biochemical and meteorological data are entered to thenewly prepared digitized map as the non-spatial data or attributes. Moreover, the present work aims toconfer an indication of the potential applications and usages of a GIS in the field of animal health foradvancing the knowledge about this innovative approach of goat heath surveillance and monitoring.Keywords: Goats; GIS; Pre-Monsoon; Post-Monsoon; Purulia; Nadia.

  13. l

    All Community Health Profiles Data Download

    • data.lacounty.gov
    • geohub.lacity.org
    • +3more
    Updated Apr 17, 2024
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    County of Los Angeles (2024). All Community Health Profiles Data Download [Dataset]. https://data.lacounty.gov/datasets/b2d4d3c03f114440af6e3088ee612328
    Explore at:
    Dataset updated
    Apr 17, 2024
    Dataset authored and provided by
    County of Los Angeles
    Description

    Use this layer to join non-spatial data: https://ph-lacounty.hub.arcgis.com/datasets/3e38574c3d31477d908c8028fb864ca4/aboutFor more information about the Community Health Profiles data initiative, please see the initiative homepage.

  14. Newark Area Road Network

    • data-newgin.opendata.arcgis.com
    Updated Sep 2, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    erwinn_NewGIN (2020). Newark Area Road Network [Dataset]. https://data-newgin.opendata.arcgis.com/items/f7071d11532647c8a2cfe3f15b394135
    Explore at:
    Dataset updated
    Sep 2, 2020
    Dataset provided by
    NewGinhttp://www.newgin.co.jp/
    Authors
    erwinn_NewGIN
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    The New Jersey Office of Information Technology (OIT), Office of GIS (OGIS) has enhanced the previously published NJ Department of Transportation (DOT) Roadway Network GIS data set to create a fully segmented Road Centerlines of New Jersey feature class. This dataset includes fully parsed address information and additional roadway characteristics. It provides the geometric framework for display and query of relevant non-spatial data published as separate tables that can be joined to the feature class. The enhancement process included integration of multiple data sets, primarily those developed and maintained by county agencies in New Jersey and the US Census Bureau.At the present time, there are known issues with the linear referencing systems contained within this data. The most prevalent issues appear to be with the Parent linear referencing system. It is strongly recommended that users utilize the NJDOT Roadway Network data for linear referencing at this time. The NJ Office of GIS is currently working to correct the linear referencing issues.

  15. d

    Asset database for the Cooper subregion on 27 August 2015

    • data.gov.au
    • researchdata.edu.au
    • +1more
    Updated Aug 9, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bioregional Assessment Program (2023). Asset database for the Cooper subregion on 27 August 2015 [Dataset]. https://data.gov.au/data/dataset/0b122b2b-e5fe-4166-93d1-3b94fc440c82
    Explore at:
    Dataset updated
    Aug 9, 2023
    Dataset authored and provided by
    Bioregional Assessment Program
    Description

    Abstract

    The public version of this Asset database can be accessed via the following dataset:

    Asset database for the Cooper subregion on 27 August 2015 Public (526707e0-9d32-47de-a198-9c8f35761a7e)

    The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

    The asset database for Cooper subregion (v3) supersedes previous version (v2) of the Cooper Asset database (Asset database for the Cooper subregion on 14 August 2015, 5c3697e6-8077-4de7-b674-e0dfc33b570c). The M2_Reason in the Assetlist table and DecisionBrief in the AssetDecisions table have been updated with short descriptions (<255 characters) provided by project team 21/8, and the draft "water-dependent asset register and asset list" (BA-LEB-COO-130-WaterDependentAssetRegister-AssetList-V20150827) also updated accordingly. This change was made to avoid truncation in the brief reasons fields of the database and asset register. There have been no changes to assets or asset numbers.

    This dataset contains a combination of spatial and non-spatial (attribute) components of the Cooper subregion Asset List - an mdb file (readable as an MS Access database or as an ESRI personal geodatabase) holds the non-spatial tabular attribute data, and an ESRI file geodatabase contains the spatial data layers, which are attributed only with unique identifiers ("AID" for assets, and "ElementID" for elements). The dataset also contains an update of the draft "Water-dependent asset register and asset list" spreadsheet (BA-NIC-COO-130-WaterDependentAssetRegister-AssetList-V20150827.xlsx).

    The tabular attribute data can be joined in a GIS to the "Assetlist" table in the mdb database using the "AID" field to view asset attributes (BA attribution). To view the more detailed attribution at the element-level, the intermediate table "Element_to_asset" can be joined to the assets spatial datasets using AID, and then joining the individual attribute tables from the Access database using the common "ElementID" fields. Alternatively, the spatial feature layers representing elements can be linked directly to the individual attribute tables in the Access database using "ElementID", but this arrangement will not provide the asset-level groupings.

    Further information is provided in the accompanying document, "COO_asset_database_doc20150827.doc" located within this dataset.

    Dataset History

    Version ID Date Notes

    1.0 27/03/2015 Initial database

    2.0 14/08/2015 "(1) Updated the database for M2 test results provided from COO assessment team and created the draft BA-LEB-COO-130-WaterDependentAssetRegister-AssetList-V20150814.xlsx

    (2) updated the group, subgroup, class and depth for (up to) 2 NRM WAIT assets to cooperate the feedback to OWS from relevant SA NRM regional office (whose staff missed the asset workshop). The AIDs and names of those assets are listed in table LUT_changed_asset_class_20150814 in COO_asset_database_20150814.mdb

    (3) As a result of (2), added one new asset separated from one existing asset. This asset and its parent are listed in table LUT_ADD_1_asste_20150814 in COO_asset_database_20150814.mdb. The M2 test result for this asset is inherited from its parent in this version

    (5) Added Appendix C in COO_asset_database_doc_201500814.doc is about total elements/assets in current Group and subgroup

    (6)Added Four SQL queries (Find_All_Used_Assets, Find_All_WD_Assets, Find_Amount_Asset_in_Class and Find_Amount_Elements_in_Class) in COO_asset_database_20150814.mdb.mdb for total assets and total numbers

    (7)The databases, especially spatial database (COO_asset_database_20150814Only.gdb), were changed such as duplicated attribute fields in spatial data were removed and only ID field is kept. The user needs to join the Table Assetlist or Elementlist to the relevant spatial data"

    3.0 27/08/2015 M2_Reason in the Assetlist table and DecisionBrief in the AssetDecisions table have been updated with short descriptions (<255 characters) provided by project team 21/8, and the draft "water-dependent asset register and asset list" (BA-LEB-COO-130-WaterDependentAssetRegister-AssetList-V20150827) also updated accordingly. No changes to asset numbers.

    Dataset Citation

    Bioregional Assessment Programme (2014) Asset database for the Cooper subregion on 27 August 2015. Bioregional Assessment Derived Dataset. Viewed 27 November 2017, http://data.bioregionalassessments.gov.au/dataset/0b122b2b-e5fe-4166-93d1-3b94fc440c82.

    Dataset Ancestors

  16. BLM OR Northern Spotted Owl Sites Publication Point Hub

    • catalog.data.gov
    • gbp-blm-egis.hub.arcgis.com
    Updated May 18, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bureau of Land Management (2025). BLM OR Northern Spotted Owl Sites Publication Point Hub [Dataset]. https://catalog.data.gov/dataset/blm-or-northern-spotted-owl-sites-publication-point-hub
    Explore at:
    Dataset updated
    May 18, 2025
    Dataset provided by
    Bureau of Land Managementhttp://www.blm.gov/
    Description

    NSO_SITE_PUB_PT: The Northern Spotted Owl (NSO) data standard documents how spatial location and information about inventory and monitoring activities for Northern Spotted Owls is stored. This dataset is a replacement of the former Northern Spotted Owl database. BLM wildlife biologists and GIS specialists enter and query data that was collected by district staff or contractors. The dataset includes four spatial feature classes and four non-spatial tables to support the following data collection: This data is only updated annually after the data entry has been completed for the previous years' field season.

  17. W

    Asset database for the Central West subregion on 21 August 2015

    • cloud.csiss.gmu.edu
    • researchdata.edu.au
    • +2more
    Updated Dec 13, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Australia (2019). Asset database for the Central West subregion on 21 August 2015 [Dataset]. https://cloud.csiss.gmu.edu/uddi/dataset/5e90d2ee-a551-48c5-ba48-83e3a907fcf9
    Explore at:
    Dataset updated
    Dec 13, 2019
    Dataset provided by
    Australia
    Description

    Abstract

    The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

    This database is an update (v2) of the initial asset database for the Central West subregion (titled "Asset database for the Central West subregion on 29 April 2015", ID 5c3f9a56-7a48-4c26-a617-a186c2de5bf7).

    This dataset contains a combination of spatial and non-spatial (attribute) components of the Central West subregion Asset List - an mdb file (readable as an MS Access database or as an ESRI personal geodatabase) holds the non-spatial tabular attribute data, and an ESRI file geodatabase contains the spatial data layers, which are attributed only with unique identifiers ("AID" for assets, and "ElementID" for elements). The dataset also contains a draft "Water-dependent asset register and asset list" spreadsheet (BA-NIC-CEN-130-WaterDependentAssetRegister-AssetList-V20150814.xlsx).

    The tabular attribute data can be joined in a GIS to the "Assetlist" table in the mdb database using the "AID" field to view asset attributes (BA attribution). To view the more detailed attribution at the element-level, the intermediate table "Element_to_asset" can be joined to the assets spatial datasets using AID, and then joining the individual attribute tables from the Access database using the common "ElementID" fields. Alternatively, the spatial feature layers representing elements can be linked directly to the individual attribute tables in the Access database using "ElementID", but this arrangement will not provide the asset-level groupings.

    Dataset History

    VersionID Date Notes

    1.0 29/04/2015 Initial database

    2.0 21/08/2015 v2 - additions as follows:

    (1) At the request of NSW OEH, data identifying species and ecological communities listed under NSW legislation has been included in two additional attribute tables "NSW_TS" and "NSW_TEC" (a total of 149 new elements and assets, AIDs 70001-70149). However, given the extremely course catchment-scale resolution of the data as compared to the relatively fine-scale of the PAE, it is essentially a non-spatial list of species and communities which may or may not occur within the PAE. As the data was unable to be meaningfully used as a spatial dataset it was subsequently "turned off" at decision M0 (not fit for purpose), with the decision reflected in the "Assetlist"and "AssetDecisions" tables.

    (2) The database has been updated to include M2 (water dependency) test results from the CEN project team, and a draft "Water-dependent asset register and asset list" spreadsheet (BA-NIC-CEN-130-WaterDependentAssetRegister-AssetList-V20150814.xlsx) has been created and is included in this dataset.

    (3) Four queries have been added to the non-spatial database (mdb) (Find_All_Used_Assets, Find_All_WD_Assets, Find_Amount_Asset_in_Class and Find_Amount_Elements_in_Class) to assist project teams to identify and calculate figures to be published.

    Dataset Citation

    Bioregional Assessment Programme (2013) Asset database for the Central West subregion on 21 August 2015. Bioregional Assessment Derived Dataset. Viewed 08 February 2017, http://data.bioregionalassessments.gov.au/dataset/5e90d2ee-a551-48c5-ba48-83e3a907fcf9.

    Dataset Ancestors

  18. a

    2019 Revenue Expense Categories

    • opendata-cityofgp.hub.arcgis.com
    • openbudget-cityofgp.hub.arcgis.com
    Updated Jul 17, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    The City of Grande Prairie (2019). 2019 Revenue Expense Categories [Dataset]. https://opendata-cityofgp.hub.arcgis.com/items/49f363f33b314698ab50a8b0ed5b902f
    Explore at:
    Dataset updated
    Jul 17, 2019
    Dataset authored and provided by
    The City of Grande Prairie
    Description

    This CSV is a table detailing information relating to the City of Grande Prairie's revenue expense categories for 2019. This information was downloaded from the city's open data portal for use in visualizing spatial and non-spatial data using GIS tools. It is used in an associated map and dashboard. All data is maintained by the City of Grande Prairie GIS department.

  19. d

    Asset database for the Pedirka subregion on 27 August 2015

    • data.gov.au
    • researchdata.edu.au
    • +2more
    Updated Aug 9, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bioregional Assessment Program (2023). Asset database for the Pedirka subregion on 27 August 2015 [Dataset]. https://data.gov.au/data/dataset/62dc178f-65ae-4e6a-b5d4-12895b37d04c
    Explore at:
    Dataset updated
    Aug 9, 2023
    Dataset authored and provided by
    Bioregional Assessment Program
    Area covered
    Pedirka Desert
    Description

    Abstract

    The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement.

    The asset database for the Pedirka subregion (v3) supersedes previous version (v2) of the Pedirka Asset database (Asset database for the Arckaringa subregion on 07 August 2015, 3c976085-ff75-44c7-a3b1-9608f6a6a994). The M2_Reason in the Assetlist table and DecisionBrief in the AssetDecisions table have been updated with short descriptions (<255 characters) provided by project team 21/8, and the draft "water-dependent asset register and asset list" (BA-LEB-PED-130-WaterDependentAssetRegister-AssetList-V20150827) also updated accordingly. This change was made to avoid truncation in the brief reasons fields of the database and asset register. There have been no changes to assets or asset numbers.

    This dataset contains a combination of spatial and non-spatial (attribute) components of the Pedirka subregion Asset List - an mdb file (readable as an MS Access database or as an ESRI personal geodatabase) holds the non-spatial tabular attribute data, and an ESRI file geodatabase contains the spatial data layers, which are attributed only with unique identifiers ("AID" for assets, and "ElementID" for elements). The dataset also contains an update of the draft "Water-dependent asset register and asset list" spreadsheet (BA-NIC-PED-130-WaterDependentAssetRegister-AssetList-V20150827.xlsx).

    The tabular attribute data can be joined in a GIS to the "Assetlist" table in the mdb database using the "AID" field to view asset attributes (BA attribution). To view the more detailed attribution at the element-level, the intermediate table "Element_to_asset" can be joined to the assets spatial datasets using AID, and then joining the individual attribute tables from the Access database using the common "ElementID" fields. Alternatively, the spatial feature layers representing elements can be linked directly to the individual attribute tables in the Access database using "ElementID", but this arrangement will not provide the asset-level groupings.

    Further information is provided in the accompanying document, "PED_asset_database_doc20150827.doc" located within this dataset.

    Dataset History

    VersionID Date Notes

    1.0 13/03/2015 Initial database

    1.1 19/03/2015 Add SA point Eco data (2 assets and 28 Elements) and fixed Note field value in table AssetDecisions

    2 7/08/2015 "(1) Updated the database for M2 test results provided from PED assessment team and created the draft BA-LEB-PED-130-WaterDependentAssetRegister-AssetList-V20150807.xlsx

    (2) Updated the group, subgroup, class and depth for (up to) 67 NRM WAIT assets to cooperate the feedback to OWS from relevant SA NRM office (whose staff missed the asset workshop). The AIDs and names of those assets are listed in table LUT_changed_asset_class_20150807 in PED_asset_database_20150807.mdb

    (3) Appendix C in PED_asset_database_doc_201500807.doc is about total elements/assets in current Group and subgroup

    (4) Four SQL queries (Find_All_Used_Assets, Find_All_WD_Assets, Find_Amount_Asset_in_Class and Find_Amount_Elements_in_Class) in PED_asset_database_20150807.mdb can be used for total assets and total numbers

    (5)There are 1 asset (in PED subregion), which is same as 1 asset in MBC subregion. Its AID, Asset Name, Group, SubGroup, Depth, Source and ListDate is using values from MBC asset. This asset is listed in table LUT_DUP_PED_MBC in PED_asset_database_20150807.mdb

    (6)The databases, especially spatial database (PED_asset_database_20150807Only.gdb), were changed such as duplicated attribute fields in spatial data were removed and only ID field is kept. The user needs to join the Table Assetlist or Elementlist to the relevant spatial data."

    1. 27/08/2015 M2_Reason in the Assetlist table and DecisionBrief in the AssetDecisions table have been updated with short descriptions (<255 characters) provided by project team 21/8, and the draft "water-dependent asset register and asset list" (BA-LEB-PED-130-WaterDependentAssetRegister-AssetList-V20150827) also updated accordingly. No changes to asset numbers.

    Dataset Citation

    Bioregional Assessment Programme (2014) Asset database for the Pedirka subregion on 27 August 2015. Bioregional Assessment Derived Dataset. Viewed 05 July 2017, http://data.bioregionalassessments.gov.au/dataset/62dc178f-65ae-4e6a-b5d4-12895b37d04c.

    Dataset Ancestors

  20. m

    Asset database for the Gwydir subregion on 24 August 2015

    • demo.dev.magda.io
    • researchdata.edu.au
    • +1more
    Updated Aug 8, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bioregional Assessment Program (2023). Asset database for the Gwydir subregion on 24 August 2015 [Dataset]. https://demo.dev.magda.io/dataset/ds-dga-72fdde7c-99d0-4326-8645-c4623b86172e
    Explore at:
    Dataset updated
    Aug 8, 2023
    Dataset provided by
    Bioregional Assessment Program
    Description

    Abstract The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The …Show full descriptionAbstract The dataset was derived by the Bioregional Assessment Programme from multiple source datasets. The source datasets are identified in the Lineage field in this metadata statement. The processes undertaken to produce this derived dataset are described in the History field in this metadata statement. This database is an update (v2) of the initial asset database for the Gwydir subregion (titled "Asset database for the Gwydir subregion on 8 May 2015", ID 429a2721-6fc1-4f3b-96d1-3eaeaa98a993). This dataset contains a combination of spatial and non-spatial (attribute) components of the Gwydir subregion Asset List - an mdb file (readable as an MS Access database or as an ESRI personal geodatabase) holds the non-spatial tabular attribute data, and an ESRI file geodatabase contains the spatial data layers, which are attributed only with unique identifiers ("AID" for assets, and "ElementID" for elements). The dataset also contains a draft "Water-dependent asset register and asset list" spreadsheet (BA-NIC-GWY-130-WaterDependentAssetRegister-AssetList-V20150824.xlsx). The tabular attribute data can be joined in a GIS to the "Assetlist" table in the mdb database using the "AID" field to view asset attributes (BA attribution). To view the more detailed attribution at the element-level, the intermediate table "Element_to_asset" can be joined to the assets spatial datasets using AID, and then joining the individual attribute tables from the Access database using the common "ElementID" fields. Alternatively, the spatial feature layers representing elements can be linked directly to the individual attribute tables in the Access database using "ElementID", but this arrangement will not provide the asset-level groupings. Further information is provided in the accompanying document, "GWY_asset_database_doc20150824.doc" located within this dataset. Dataset History VersionID Date Notes 1.0 8/05/2015 Initial database 2.0 24/08/2015 v2 - additions as follows: (1) At the request of NSW OEH, data identifying species and ecological communities listed under NSW legislation has been included in two additional attribute tables "NSW_TS" and "NSW_TEC" (a total of 110 elements and assets, AIDs 70150-70259). However, given the extremely course catchment-scale resolution of the data as compared to the relatively fine-scale of the PAE, it is essentially a non-spatial list of species and communities which may or may not occur within the PAE. As the data was unable to be meaningfully used as a spatial dataset it was subsequently "turned off" at decision M0 (not fit for purpose), with the decision reflected in the "Assetlist"and "AssetDecisions" tables. Although they are included in the asset database, these new assets are not included in the asset count for GWY. (2) The database has been updated to include M2 (water dependency) test results from the GWY project team, and a draft "Water-dependent asset register and asset list" spreadsheet (BA-NIC-GWY-130-WaterDependentAssetRegister-AssetList-V20150824.xlsx) has been created and is included in this dataset. (3) Four queries have been added to the non-spatial database (mdb) (Find_All_Used_Assets, Find_All_WD_Assets, Find_Amount_Asset_in_Class and Find_Amount_Elements_in_Class) to assist project teams to identify and calculate figures to be published. Further information is contained in the associate document "GWY_asset_database_doc_20150824.doc". Dataset Citation Bioregional Assessment Programme (2013) Asset database for the Gwydir subregion on 24 August 2015. Bioregional Assessment Derived Dataset. Viewed 08 February 2017, http://data.bioregionalassessments.gov.au/dataset/7350df87-5103-40f5-b82c-42b0fc59a6a5. Dataset Ancestors Derived From NSW Office of Water GW licence extract linked to spatial locations NIC v2 (28 February 2014) Derived From NSW Office of Water Surface Water Entitlements Locations v1_Oct2013 Derived From Travelling Stock Route Conservation Values Derived From NSW Wetlands Derived From Communities of National Environmental Significance Database - RESTRICTED - Metadata only Derived From Climate Change Corridors for Nandewar and New England Tablelands Derived From NSW Office of Water Surface Water Licences in NIC linked to locations v1 (22 April 2014) Derived From Birds Australia - Important Bird Areas (IBA) 2009 Derived From Spatial Threatened Species and Communities (TESC) NSW 20131129 Derived From Environmental Asset Database - Commonwealth Environmental Water Office Derived From Ecological assets of the Gwydir wetlands and floodplain 2008 VIS_ID 3923 Derived From National Groundwater Dependent Ecosystems (GDE) Atlas (including WA) Derived From Species Profile and Threats Database (SPRAT) - Australia - Species of National Environmental Significance Database (BA subset - RESTRICTED - Metadata only) Derived From Ramsar Wetlands of Australia Derived From Native Vegetation Management (NVM) - Manage Benefits Derived From Key Environmental Assets - KEA - of the Murray Darling Basin Derived From Asset database for the Gwydir subregion on 8 May 2015 Derived From National Heritage List Spatial Database (NHL) (v2.1) Derived From Great Artesian Basin and Laura Basin groundwater recharge areas Derived From NSW Office of Water combined geodatabase of regulated rivers and water sharing plan regions Derived From New South Wales NSW Regional CMA Water Asset Information WAIT tool databases, RESTRICTED Includes ALL Reports Derived From New South Wales NSW - Regional - CMA - Water Asset Information Tool - WAIT - databases Derived From Collaborative Australian Protected Areas Database (CAPAD) 2010 (Not current release) Derived From Australia - Species of National Environmental Significance Database Derived From NSW Office of Water Surface Water Offtakes - NIC v1 20131024 Derived From NSW Office of Water Groundwater Licence Extract NIC- Oct 2013 Derived From Australia, Register of the National Estate (RNE) - Spatial Database (RNESDB) Internal Derived From NSW Office of Water Groundwater Entitlements Spatial Locations Derived From National Groundwater Dependent Ecosystems (GDE) Atlas Derived From Directory of Important Wetlands in Australia (DIWA) Spatial Database (Public) Derived From NSW Office of Water Groundwater licences extract linked to spatial locations NIC v3 (13 March 2014)

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Cape Coral GIS (2016). 311 Issues Non Spatial [Dataset]. https://v3-api-demo-dcdev.opendata.arcgis.com/datasets/CapeGIS::311-issues-non-spatial

311 Issues Non Spatial

Explore at:
Dataset updated
Aug 30, 2016
Dataset authored and provided by
Cape Coral GIS
Area covered
Description

This data was developed to represent city of cape coral citizen action center issues and their associated attributes for the purpose of mapping, analysis, and planning. The accuracy of this data varies and should not be used for precise measurements or calculations.

Search
Clear search
Close search
Google apps
Main menu