43 datasets found
  1. r

    Add GTFS to a Network Dataset

    • opendata.rcmrd.org
    Updated Jun 27, 2013
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    ArcGIS for Transportation Analytics (2013). Add GTFS to a Network Dataset [Dataset]. https://opendata.rcmrd.org/content/0fa52a75d9ba4abcad6b88bb6285fae1
    Explore at:
    Dataset updated
    Jun 27, 2013
    Dataset authored and provided by
    ArcGIS for Transportation Analytics
    Description

    Deprecation notice: This tool is deprecated because this functionality is now available with out-of-the-box tools in ArcGIS Pro. The tool author will no longer be making further enhancements or fixing major bugs.Use Add GTFS to a Network Dataset to incorporate transit data into a network dataset so you can perform schedule-aware analyses using the Network Analyst tools in ArcMap.After creating your network dataset, you can use the ArcGIS Network Analyst tools, like Service Area and OD Cost Matrix, to perform transit/pedestrian accessibility analyses, make decisions about where to locate new facilities, find populations underserved by transit or particular types of facilities, or visualize the areas reachable from your business at different times of day. You can also publish services in ArcGIS Server that use your network dataset.The Add GTFS to a Network Dataset tool suite consists of a toolbox to pre-process the GTFS data to prepare it for use in the network dataset and a custom GTFS transit evaluator you must install that helps the network dataset read the GTFS schedules. A user's guide is included to help you set up your network dataset and run analyses.Instructions:Download the tool. It will be a zip file.Unzip the file and put it in a permanent location on your machine where you won't lose it. Do not save the unzipped tool folder on a network drive, the Desktop, or any other special reserved Windows folders (like C:\Program Files) because this could cause problems later.The unzipped file contains an installer, AddGTFStoaNetworkDataset_Installer.exe. Double-click this to run it. The installation should proceed quickly, and it should say "Completed" when finished.Read the User's Guide for instructions on creating and using your network dataset.System requirements:ArcMap 10.1 or higher with a Desktop Standard (ArcEditor) license. (You can still use it if you have a Desktop Basic license, but you will have to find an alternate method for one of the pre-processing tools.) ArcMap 10.6 or higher is recommended because you will be able to construct your network dataset much more easily using a template rather than having to do it manually step by step. This tool does not work in ArcGIS Pro. See the User's Guide for more information.Network Analyst extensionThe necessary permissions to install something on your computer.Data requirements:Street data for the area covered by your transit system, preferably data including pedestrian attributes. If you need help preparing high-quality street data for your network, please review this tutorial.A valid GTFS dataset. If your GTFS dataset has blank values for arrival_time and departure_time in stop_times.txt, you will not be able to run this tool. You can download and use the Interpolate Blank Stop Times tool to estimate blank arrival_time and departure_time values for your dataset if you still want to use it.Help forum

  2. a

    City Points

    • hub.arcgis.com
    • azgeo-open-data-agic.hub.arcgis.com
    Updated May 4, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    AZGeo ArcGIS Online (AGO) (2020). City Points [Dataset]. https://hub.arcgis.com/maps/azgeo::city-points
    Explore at:
    Dataset updated
    May 4, 2020
    Dataset authored and provided by
    AZGeo ArcGIS Online (AGO)
    Area covered
    Description

    This dataset represents point locations of cities and towns in Arizona. The data contains point locations for incorporated cities, Census Designated Places and populated places. Several data sets were used as inputs to construct this data set. A subset of the Geographic Names Information System (GNIS) national dataset for the state of Arizona was used for the base location of most of the points. Polygon files of the Census Designated Places (CDP), from the U.S. Census Bureau and an incorporated city boundary database developed and maintained by the Arizona State Land Department were also used for reference during development. Every incorporated city is represented by a point, originally derived from GNIS. Some of these points were moved based on local knowledge of the GIS Analyst constructing the data set. Some of the CDP points were also moved and while most CDP's of the Census Bureau have one point location in this data set, some inconsistencies were allowed in order to facilitate the use of the data for mapping purposes. Population estimates were derived from data collected during the 2010 Census. During development, an additional attribute field was added to provide additional functionality to the users of this data. This field, named 'DEF_CAT', implies definition category, and will allow users to easily view, and create custom layers or datasets from this file. For example, new layers may created to include only incorporated cities (DEF_CAT = Incorporated), Census designated places (DEF_CAT = Incorporated OR DEF_CAT = CDP), or all cities that are neither CDP's or incorporated (DEF_CAT= Other). This data is current as of February 2012. At this time, there is no planned maintenance or update process for this dataset.This data is created to serve as base information for use in GIS systems for a variety of planning, reference, and analysis purposes. This data does not represent a legal record.

  3. a

    Job Destination Walk Access

    • datahub-dc-dcgis.hub.arcgis.com
    • opendata.dc.gov
    • +3more
    Updated Jul 5, 2022
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Washington, DC (2022). Job Destination Walk Access [Dataset]. https://datahub-dc-dcgis.hub.arcgis.com/datasets/job-destination-walk-access/about
    Explore at:
    Dataset updated
    Jul 5, 2022
    Dataset authored and provided by
    City of Washington, DC
    License

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

    Area covered
    Description

    This layer considers jobs and destinations to be accessible by walking if the destinations are reachable within 20 minutes. Access to jobs and destinations within a fixed time is measured using the actual networks and not a straight line distance. Destinations include grocery stores, hospitals, community services, education centers, and other significant community areas. Jobs across the region (not just within the District) were used to provide a full picture of employment access.

  4. d

    5.02 New Jobs Created (summary)

    • catalog.data.gov
    • hub.arcgis.com
    • +1more
    Updated Oct 4, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Tempe (2025). 5.02 New Jobs Created (summary) [Dataset]. https://catalog.data.gov/dataset/5-02-new-jobs-created-summary-3cc9b
    Explore at:
    Dataset updated
    Oct 4, 2025
    Dataset provided by
    City of Tempe
    Description

    Tempe is among Arizona's most educated cities, lending to a creative, smart atmosphere. With more than a dozen colleges, trade schools, and universities, about 40 percent of our residents over the age of 25 have Bachelor's degrees or higher. Having such an educated and accessible workforce is a driving factor in attracting and growing jobs for residents in the region.The City of Tempe is a member of the Greater Phoenix Economic Council (GPEC), and with the membership, staff tracks collaborative efforts to recruit business prospects and locations. The Greater Phoenix Economic Council (GPEC) is a performance-driven, public-private partnership. GPEC partners with the City of Tempe, Maricopa County, 22 other communities, and more than 170 private-sector investors to promote the region’s competitive position and attract quality jobs that enable strategic economic growth and provide increased tax revenue for Tempe. This dataset provides the target and actual job creation numbers for the City of Tempe and the Greater Phoenix Economic Council (GPEC). The job creation target for Tempe is calculated by multiplying GPEC's target by twice Tempe's proportion of the population. This page provides data for the New Jobs Created performance measure.The performance measure dashboard is available at 5.02 New Jobs Created. Additional Information Source: Extracted from GPEC monthly and annual reports and proprietary excel filesContact: Madalaine McConvilleContact Phone: 480-350-2927Data Source Type: Excel filesPreparation Method: Extracted from GPEC monthly and annual reports and proprietary Excel filesPublish Frequency: AnnuallyPublish Method: ManualData Dictionary

  5. a

    Employment Services Program Data by Local Boards

    • hub.arcgis.com
    Updated Jan 23, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    EO_Analytics (2017). Employment Services Program Data by Local Boards [Dataset]. https://hub.arcgis.com/maps/a1a2149aa4eb453bbcaaa8436feb117c
    Explore at:
    Dataset updated
    Jan 23, 2017
    Dataset authored and provided by
    EO_Analytics
    Area covered
    Description

    This map presents the full data available on the MLTSD GeoHub, and maps several of the key variables reflected by the Employment Services Program of ETD.Employment Services are a suite of services delivered to the public to help Ontarians find sustainable employment. The services are delivered by third-party service providers at service delivery sites (SDS) across Ontario on behalf of the Ministry of Labour, Training and Skills Development (MLTSD). The services are tailored to meet the individual needs of each client and can be provided one-on-one or in a group format. Employment Services fall into two broad categories: unassisted and assisted services.

    Unassisted services include the following components:resources and information on all aspects of employment including detailed facts on the local labour marketresources on how to conduct a job search.assistance in registering for additional schoolinghelp with career planningreference to other Employment and government programs.

    Unassisted services are available to all Ontarians without reference to eligibility criteria. These unassisted services can be delivered through structured orientation or information sessions (on or off site), e-learning sessions, or one-to-one sessions up to two days in duration. Employers can also use unassisted services to access information on post-employment opportunities and supports available for recruitment and workplace training.

    The second category is assisted services, and it includes the following components:assistance with the job search (including individualized assistance in career goal setting, skills assessment, and interview preparation) job matching, placement and incentives (which match client skills and interested with employment opportunities, and include placement into employment, on-the-job training opportunities, and incentives to employers to hire ES clients), and job training/retention (which supports longer-term attachment to or advancement in the labour market or completion of training)For every assisted services client a service plan is maintained by the service provider, which gives details on the types of assisted services the client has accessed. To be eligible for assisted services, clients must be unemployed (defined as working less than twenty hours a week) and not participating in full-time education or training. Clients are also assessed on a number of suitability indicators covering economic, social and other barriers to employment, and service providers are to prioritize serving those clients with multiple suitability indicators.

    About This Dataset

    This dataset contains data on ES clients for each of the twenty-six Local Board (LB) areas in Ontario for the 2015/16 fiscal year, based on data provided to Local Boards and Local Employment Planning Councils (LEPC) in June 2016 (see below for details on Local Boards). This includes all assisted services clients whose service plan was closed in the 2015/16 fiscal year and all unassisted services clients who accessed unassisted services in the 2015/16 fiscal year. These clients have been distributed across Local Board areas based on the address of each client’s service delivery site, not the client’s home address. Note that clients who had multiple service plans close in the 2015/16 fiscal year (i.e. more than one distinct period during which the client was accessing assisted services) will be counted multiple times in this dataset (once for each closed service plan). Assisted services clients who also accessed unassisted services either before or after accessing assisted services would also be included in the count of unassisted clients (in addition to their assisted services data).

    Demographic data on ES assisted services clients, including a client’s suitability indicators and barriers to employment, are collected by the service provider when a client registers for ES (i.e. at intake). Outcomes data on ES assisted services clients is collected through surveys at exit (i.e. when the client has completed accessing ES services and the client’s service plan is closed) and at three, six, and twelve months after exit. As demographic and outcomes data is only collected for assisted services clients, all fields in this dataset contain data only on assisted services clients except for the ‘Number of Clients – Unassisted R&I Clients’ field.

    Note that ES is the gateway for other Employment Ontario programs and services; the majority of Second Career (SC) clients, some apprentices, and some Literacy and Basic Skills (LBS) clients have also accessed ES. It is standard procedure for SC, LBS and apprenticeship client and outcome data to be entered as ES data if the program is part of ES service plan. However, for this dataset, SC client and outcomes data has been separated from ES, which as a result lowers the client and outcome counts for ES.

    About Local Boards

    Local Boards are independent not-for-profit corporations sponsored by the Ministry of Labour, Training and Skills Development to improve the condition of the labour market in their specified region. These organizations are led by business and labour representatives, and include representation from constituencies including educators, trainers, women, Francophones, persons with disabilities, visible minorities, youth, Indigenous community members, and others. For the 2015/16 fiscal year there were twenty-six Local Boards, which collectively covered all of the province of Ontario.

    The primary role of Local Boards is to help improve the conditions of their local labour market by:engaging communities in a locally-driven process to identify and respond to the key trends, opportunities and priorities that prevail in their local labour markets;facilitating a local planning process where community organizations and institutions agree to initiate and/or implement joint actions to address local labour market issues of common interest; creating opportunities for partnership development activities and projects that respond to more complex and/or pressing local labour market challenges; and organizing events and undertaking activities that promote the importance of education, training and skills upgrading to youth, parents, employers, employed and unemployed workers, and the public in general.

    In December 2015, the government of Ontario launched an eighteen-month Local Employment Planning Council pilot program, which established LEPCs in eight regions in the province formerly covered by Local Boards. LEPCs expand on the activities of existing Local Boards, leveraging additional resources and a stronger, more integrated approach to local planning and workforce development to fund community-based projects that support innovative approaches to local labour market issues, provide more accurate and detailed labour market information, and develop detailed knowledge of local service delivery beyond Employment Ontario (EO).

    Eight existing Local Boards were awarded LEPC contracts that were effective as of January 1st, 2016. As such, from January 1st, 2016 to March 31st, 2016, these eight Local Boards were simultaneously Local Employment Planning Councils. The eight Local Boards awarded contracts were:Durham Workforce Authority Peel-Halton Workforce Development GroupWorkforce Development Board - Peterborough, Kawartha Lakes, Northumberland, HaliburtonOttawa Integrated Local Labour Market PlanningFar Northeast Training BoardNorth Superior Workforce Planning Board Elgin Middlesex Oxford Workforce Planning & Development BoardWorkforce Windsor-Essex

    MLTSD has provided Local Boards and LEPCs with demographic and outcome data for clients of Employment Ontario (EO) programs delivered by service providers across the province on an annual basis since June 2013. This was done to assist Local Boards in understanding local labour market conditions. These datasets may be used to facilitate and inform evidence-based discussions about local service issues – gaps, overlaps and under-served populations - with EO service providers and other organizations as appropriate to the local context.

    Data on the following EO programs for the 2015/16 fiscal year was made available to Local Boards and LEPCs in June 2016:Employment Services (ES)Literacy and Basic Skills (LBS) Second Career (SC) Apprenticeship

    This dataset contains the 2015/16 ES data that was sent to Local Boards and LEPCs. Datasets covering past fiscal years will be released in the future.

    Notes and Definitions

    NAICS – The North American Industry Classification System (NAICS) is an industry classification system developed by the statistical agencies of Canada, the United States, and Mexico against the backdrop of the North American Free Trade Agreement. It is a comprehensive system that encompasses all economic activities in a hierarchical structure. At the highest level, it divides economic activity into twenty sectors, each of which has a unique two-digit identifier. These sectors are further divided into subsectors (three-digit codes), industry groups (four-digit codes), and industries (five-digit codes). This dataset uses two-digit NAICS codes from the 2007 edition to identify the sector of the economy an Employment Services client is employed in prior to and after participation in ES.

    NOC – The National Organizational Classification (NOC) is an occupational classification system developed by Statistics Canada and Human Resources and Skills Development Canada to provide a standard lexicon to describe and group occupations in Canada primarily on the basis of the work being performed in the occupation. It is a comprehensive system that encompasses all occupations in Canada in a hierarchical structure. At the highest level are ten broad occupational categories, each of which has a unique one-digit identifier. These broad occupational categories are further divided into forty major groups (two-digit codes), 140 minor groups

  6. A

    ‘AE/VCE Unconfirmed Vernal Pools’ analyzed by Analyst-2

    • analyst-2.ai
    Updated Nov 21, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com) (2021). ‘AE/VCE Unconfirmed Vernal Pools’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/data-gov-ae-vce-unconfirmed-vernal-pools-dbca/2b6cb4d8/?iid=008-640&v=presentation
    Explore at:
    Dataset updated
    Nov 21, 2021
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

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

    Description

    Analysis of ‘AE/VCE Unconfirmed Vernal Pools’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/a0caaa0d-2ee7-4ed1-a82d-45ee37ac66c9 on 20 November 2021.

    --- Dataset description provided by original source is as follows ---

    This dataset is derived from a project by the Vermont Center for Ecostudies(VCE) and Arrowwood Environmental(AE) to map vernal pools throughout the state of Vermont. AE and VCE are mapping locations of potential vernal pools throughout Vermont, and recruiting a corps of volunteers to field-verify the presence of these potential pools. In the process, we will develop a GIS layer of potential and known vernal pools, as well as a database populated with biological and physical attributes of each verified pool. With partial funding from the Vermont State Wildlife Grants Program, potential vernal pools will be identified using color infrared aerial photographs.

    Data was collected remotely using color infrared aerial photo interpretation. "Potential" vernal pools were mapped and available for the purpose of confirming whether vernal pool habitat was present through site visits. This dataset represents only those sites which have not yet been field-visited or verified as vernal pools. This statewide dataset was collected in 2009-2011.

    --- Original source retains full ownership of the source dataset ---

  7. d

    Job Destination Bike Access

    • catalog.data.gov
    • datasets.ai
    • +4more
    Updated Feb 4, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Washington, DC (2025). Job Destination Bike Access [Dataset]. https://catalog.data.gov/dataset/job-destination-bike-access
    Explore at:
    Dataset updated
    Feb 4, 2025
    Dataset provided by
    City of Washington, DC
    Description

    This layer considers jobs and destinations to be accessible by bike if the destinations are reachable within 30 minutes. Access to jobs and destinations within a fixed time is measured using the actual networks and not a straight line distance. Destinations include grocery stores, hospitals, community services, education centers, and other significant community areas. Jobs across the region (not just within the District) were used to provide a full picture of employment access.

  8. a

    RTB Mapping application

    • hub.arcgis.com
    • data.amerigeoss.org
    • +2more
    Updated Aug 12, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    ArcGIS StoryMaps (2015). RTB Mapping application [Dataset]. https://hub.arcgis.com/datasets/81ea77e8b5274b879b9d71010d8743aa
    Explore at:
    Dataset updated
    Aug 12, 2015
    Dataset authored and provided by
    ArcGIS StoryMaps
    Description

    RTB Maps is a cloud-based electronic Atlas. We used ArGIS 10 for Desktop with Spatial Analysis Extension, ArcGIS 10 for Server on-premise, ArcGIS API for Javascript, IIS web services based on .NET, and ArcGIS Online combining data on the cloud with data and applications on our local server to develop an Atlas that brings together many of the map themes related to development of roots, tubers and banana crops. The Atlas is structured to allow our participating scientists to understand the distribution of the crops and observe the spatial distribution of many of the obstacles to production of these crops. The Atlas also includes an application to allow our partners to evaluate the importance of different factors when setting priorities for research and development. The application uses weighted overlay analysis within a multi-criteria decision analysis framework to rate the importance of factors when establishing geographic priorities for research and development.Datasets of crop distribution maps, agroecology maps, biotic and abiotic constraints to crop production, poverty maps and other demographic indicators are used as a key inputs to multi-objective criteria analysis.Further metadata/references can be found here: http://gisweb.ciat.cgiar.org/RTBmaps/DataAvailability_RTBMaps.htmlDISCLAIMER, ACKNOWLEDGMENTS AND PERMISSIONS:This service is provided by Roots, Tubers and Bananas CGIAR Research Program as a public service. Use of this service to retrieve information constitutes your awareness and agreement to the following conditions of use.This online resource displays GIS data and query tools subject to continuous updates and adjustments. The GIS data has been taken from various, mostly public, sources and is supplied in good faith.RTBMaps GIS Data Disclaimer• The data used to show the Base Maps is supplied by ESRI.• The data used to show the photos over the map is supplied by Flickr.• The data used to show the videos over the map is supplied by Youtube.• The population map is supplied to us by CIESIN, Columbia University and CIAT.• The Accessibility map is provided by Global Environment Monitoring Unit - Joint Research Centre of the European Commission. Accessibility maps are made for a specific purpose and they cannot be used as a generic dataset to represent "the accessibility" for a given study area.• Harvested area and yield for banana, cassava, potato, sweet potato and yam for the year 200, is provided by EarthSat (University of Minnesota’s Institute on the Environment-Global Landscapes initiative and McGill University’s Land Use and the Global Environment lab). Dataset from Monfreda C., Ramankutty N., and Foley J.A. 2008.• Agroecology dataset: global edapho-climatic zones for cassava based on mean growing season, temperature, number of dry season months, daily temperature range and seasonality. Dataset from CIAT (Carter et al. 1992)• Demography indicators: Total and Rural Population from Center for International Earth Science Information Network (CIESIN) and CIAT 2004.• The FGGD prevalence of stunting map is a global raster datalayer with a resolution of 5 arc-minutes. The percentage of stunted children under five years old is reported according to the lowest available sub-national administrative units: all pixels within the unit boundaries will have the same value. Data have been compiled by FAO from different sources: Demographic and Health Surveys (DHS), UNICEF MICS, WHO Global Database on Child Growth and Malnutrition, and national surveys. Data provided by FAO – GIS Unit 2007.• Poverty dataset: Global poverty headcount and absolute number of poor. Number of people living on less than $1.25 or $2.00 per day. Dataset from IFPRI and CIATTHE RTBMAPS GROUP MAKES NO WARRANTIES OR GUARANTEES, EITHER EXPRESSED OR IMPLIED AS TO THE COMPLETENESS, ACCURACY, OR CORRECTNESS OF THE DATA PORTRAYED IN THIS PRODUCT NOR ACCEPTS ANY LIABILITY, ARISING FROM ANY INCORRECT, INCOMPLETE OR MISLEADING INFORMATION CONTAINED THEREIN. ALL INFORMATION, DATA AND DATABASES ARE PROVIDED "AS IS" WITH NO WARRANTY, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, FITNESS FOR A PARTICULAR PURPOSE. By accessing this website and/or data contained within the databases, you hereby release the RTB group and CGCenters, its employees, agents, contractors, sponsors and suppliers from any and all responsibility and liability associated with its use. In no event shall the RTB Group or its officers or employees be liable for any damages arising in any way out of the use of the website, or use of the information contained in the databases herein including, but not limited to the RTBMaps online Atlas product.APPLICATION DEVELOPMENT:• Desktop and web development - Ernesto Giron E. (GeoSpatial Consultant) e.giron.e@gmail.com• GIS Analyst - Elizabeth Barona. (Independent Consultant) barona.elizabeth@gmail.comCollaborators:Glenn Hyman, Bernardo Creamer, Jesus David Hoyos, Diana Carolina Giraldo Soroush Parsa, Jagath Shanthalal, Herlin Rodolfo Espinosa, Carlos Navarro, Jorge Cardona and Beatriz Vanessa Herrera at CIAT, Tunrayo Alabi and Joseph Rusike from IITA, Guy Hareau, Reinhard Simon, Henry Juarez, Ulrich Kleinwechter, Greg Forbes, Adam Sparks from CIP, and David Brown and Charles Staver from Bioversity International.Please note these services may be unavailable at times due to maintenance work.Please feel free to contact us with any questions or problems you may be having with RTBMaps.

  9. f

    Data from: Semantic typing of linked geoprocessing workflows

    • tandf.figshare.com
    • datasetcatalog.nlm.nih.gov
    pdf
    Updated May 31, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Simon Scheider; Andrea Ballatore (2023). Semantic typing of linked geoprocessing workflows [Dataset]. http://doi.org/10.6084/m9.figshare.4814827
    Explore at:
    pdfAvailable download formats
    Dataset updated
    May 31, 2023
    Dataset provided by
    Taylor & Francis
    Authors
    Simon Scheider; Andrea Ballatore
    License

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

    Description

    In Geographic Information Systems (GIS), geoprocessing workflows allow analysts to organize their methods on spatial data in complex chains. We propose a method for expressing workflows as linked data, and for semi-automatically enriching them with semantics on the level of their operations and datasets. Linked workflows can be easily published on the Web and queried for types of inputs, results, or tools. Thus, GIS analysts can reuse their workflows in a modular way, selecting, adapting, and recommending resources based on compatible semantic types. Our typing approach starts from minimal annotations of workflow operations with classes of GIS tools, and then propagates data types and implicit semantic structures through the workflow using an OWL typing scheme and SPARQL rules by backtracking over GIS operations. The method is implemented in Python and is evaluated on two real-world geoprocessing workflows, generated with Esri's ArcGIS. To illustrate the potential applications of our typing method, we formulate and execute competency questions over these workflows.

  10. w

    Current Job Postings

    • data.wu.ac.at
    • data.wakegov.com
    • +4more
    Updated Apr 25, 2018
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Wake County (2018). Current Job Postings [Dataset]. https://data.wu.ac.at/schema/data_gov/NGNhZTY5YzUtMjIwNS00ZDk4LTk0MGMtZWU3YTA3YmVlMGUx
    Explore at:
    csv, application/vnd.geo+json, json, htmlAvailable download formats
    Dataset updated
    Apr 25, 2018
    Dataset provided by
    Wake County
    Area covered
    459242fe6edffa6237cfd0c23b973d289b08aa2a
    Description

    Dataset featuring the full-time, part-time and seasonal jobs, as well as internships posted on the City's job portal @ https://www.raleighnc.gov/jobs This dataset is updated weekdays by 9am and does not contain past (non-active) postings.

  11. w

    Visible Surface Water

    • geo.wa.gov
    • data-wdfw.opendata.arcgis.com
    • +3more
    Updated May 19, 2021
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    WA Dept of Fish and Wildlife (2021). Visible Surface Water [Dataset]. https://geo.wa.gov/datasets/wdfw::visible-surface-water/about
    Explore at:
    Dataset updated
    May 19, 2021
    Dataset provided by
    Washington Department of Fish and Wildlifehttps://wdfw.wa.gov/
    Authors
    WA Dept of Fish and Wildlife
    Area covered
    Description

    Mapping of Visible Surface Water (VSW), or water features not concealed by other objects (i.e., tree canopy, bridges, etc.), is an important component of landcover models. VSW is not intended to represent a full hydrography or show connectivity, like other available water datasets – like NHD – whose boundaries may include other landcover types (i.e., shrubs, trees, etc.). Each feature has been visually verified and given attributes by an analyst. This dataset is also unique in that it reflects surface water for a single year - 2017. A variety of funding sources acquired between 2019 and 2023 aided the completion of the dataset for the entire state of Washington. More information on the dataset, current data coverage, and applications can be found on our website: https://hrcd-wdfw.hub.arcgis.com/.

    Tip: Try using the filter options on the data tab to limit your download to a single County or WRIA. The filtered download can take a substantial amount of time to initiate, so it may be necessary to download the full dataset if the filter option does not work.

  12. n

    National IA Frequency Zones (Federal) - Dataset - CKAN

    • nationaldataplatform.org
    Updated Feb 28, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). National IA Frequency Zones (Federal) - Dataset - CKAN [Dataset]. https://nationaldataplatform.org/catalog/dataset/national-ia-frequency-zones-federal1
    Explore at:
    Dataset updated
    Feb 28, 2024
    Description

    Initial attack frequency zones are used by pilots and dispatchers for purposes of response to incidents such as wildland fires. Initial attack frequency zones are agreed upon annually by the Communications Duty Officer at the National Interagency Fire Center (NIFC), other frequency managers, and the FAA, and can't be changed during the year without required approval from the CDO at NIFC. Each zone has assigned to it FAA-issued frequencies that are to be used only within the zone boundary. The initial attack frequency zones are delineated to help ensure that frequencies used do not "bleed" over into other incident areas and causing issues for incident communications. The data contains no actual frequencies, but does contain the zones in which they are used. 01/12/2023 - Tabular changes only. Oregon Initial Attack Frequency Zones renumbered per Kim Albracht, Communications Duty Officer, with input from other Northwest personnel. Edits by JKuenzi, USFS. Changes are as follows:OR09 changed to OR02OR02 changed to OR03OR03 changed to OR04OR04 changed to OR05OR05 changed to OR07OR07 changed to OR08OR08 changed to OR09OR01 and OR06 remained unchanged.01/10/2023 - Geospatial and tabular changes made. Two islands on west side of OR05 absorbed into OR03. Change made to both Initial Attack Frequency Zones-Federal and to Dispatch Boundaries per Kaleigh Johnson (Asst Ctr Mgr), Jada Altman (Dispatch Ctr Mgr), and Jerry Messinger (Air Tactical Group Supervisor). Edits by JKuenzi, USFS. 01/09/2023 - Geospatial and tabular changes to align Federal Frequency Zones to Dispatch Area boundaries in Northwest GACC. No alignments made to USWACAC, USWAYAC, or USORWSC. Changes approved by Ted Pierce (NW Deputy Coordination Ctr Mgr), Kaleigh Johnson (Assistant Ctr Mgr), and Kim Albracht (Communications Duty Officer). Edits by JKuenzi, USFS. Specific changes include: WA02 changed to WA04. New WA02 carved out of WA01 and OR01. OR09 carved out of OR01 and OR02. Boundary adjustments between OR07, OR05, and OR03.11/8/2022 - Geospatial and tabular changes. Boundary modified between Big Horn and Rosebud Counties of MT07 and MT08 per KSorenson and KPluhar. Edits by JKuenzi, USFS. 09/06/2022-09/26/2022 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southern California and Great Basin in the state of Nevada. Boundary modified between CA03 and NV03, specifically between Queen Valley and Mono Valley. The team making the changes is made up of Southern Calif (JTomaselli) and Great Basin (GDingman) GACCs, with input from Ian Mills and Lance Rosen (BLM). Changes proposed will be put into effect for the 2023 calendar year, and will also impact alignments of GACC boundaries and Dispatch boundaries in the area described. Initial edits provided by Ian Mills and Daniel Yarborough. Final edits by JKuenzi, USFS. A description of the change is as follows: The northwest end of changes start approximately 1 mile west of Mt Olsen and approximately 0.5 mile south of the Virginia Lakes area.Head northwest passing on the northeast side of Red Lake and the south side of Big Virginia Lake to follow HWY 395 North east to CA 270.East through Bodie to the CA/NV state line.Follows the CA/NV State Line south to HWY CA 167/NV 359.East on NV359 to where the HWY intersects the corner of FS/BLM land.Follows the FS/BLM boundary to the east and then south where it ties into the current GACC boundary. 09/07/2022 - 09/08/2022 - Tabular and geospatial changes. Multiple boundaries modified in Northern Rockies GACC to bring Dispatch Boundaries and Initial Attack Frequency Zone lines closer in accordance with State boundaries. Information provided by Don Copple, State Fire Planning & Intelligence Program Manager for Montana Dept of Natural Resources & Conservation (DNRC), Kathy Pipkin, Northern Rockies GACC Center Manager, and Kat Sorenson, R1 Asst Aircraft Coordinator. Edits by JKuenzi, USFS. The following changes were made:Initial Attack Frequency Zone changes made to the following: Dillon Interagency Dispatch Ctr (USMTDDC) (MT03), Helena Interagency Dispatch Ctr (USMTHDC) (MT04), Lewistown Interagency Dispatch Ctr (USMTLEC) (MT06), and Missoula Interagency Dispatch Ctr (USMTMDC) (MT02).Talk was also directed to removing the Initial Attack Frequency Zone line between MT05 and MT07, but that currently remains unchanged until Telecommunications (Kimberly Albracht) can get approval from the Frequency Managers and the FAA.10/15/2021 - Geospatial and tabular changes. Boundary alignments for the Duck Valley Reservation in southern Idaho along the Nevada border. Changes impacting ID02 and NV01. The Duck Valley Reservation remains within NV01. The only change was to the alignment of the physical boundary surrounding the Reservation in accordance with the boundary shown on the 7.5 minute quadrangle maps and data supplied by CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Center Manager. Edits by JKuenzi, USFS. 9/30/2021 - Geospatial and tabular changes. Boundary alignments for Idaho on Hwy 95 NE of Weiser between Boise Dispatch Center and Payette Interagency Dispatch Center - per CClay/JLeguineche/Gina Dingman-USFS Great Basin Coordination Center (GBCC) Center Manager. Edits by JKuenzi, USFS. Boundary changes at: Weiser (T11N R5W Sec 32), (T11N, R5W, Sec 3), (T12N R5W, Sec 25), and Midvale.9/21/2021 - Geospatial and tabular changes in accordance with proposed GACC boundary re-alignments between Southwestern and Southern GACCs where a portion of Texas, formerly under Southwestern GACC direction was moved to the Southern GACC. Changes to Federal Initial Attack Frequency Zones by Kim Albracht, Communications Duty Officer (CDO) include the following: State designation TXS06 changed to federal TX06.State designation TXS05 changed to federal TX05.State designation TXS04 changed to federal TX04.State designation TXS03 changed to federal TX03.State designation TXS02 changed to federal TX02.State designation TXS01 changed to federal TX01.The Oklahoma Panhandle, formerly TXS01 changed to OK04.All changes proposed for implementation starting in January 2022. Edits by JKuenzi, USFS. See also data sets for Geographic Area Coordination Centers (GACC), and Dispatch Boundary for related changes.8/17/2021 - Tabular changes only. As part of GACC realignment for 2022, area changed from state designation TXS01 to federal TX01 per Kim Albracht, Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC). Edits by JKuenzi, USFS. 2/19/2021 - Geospatial and tabular changes. Boundary changes for Idaho originally submitted in 2016 but never completed in entirety. Changes between Initial Attack Zones ID01 and ID02 and with Dispatch Boundaries - per Chris Clay-BLM Boise, DeniseTolness-DOI/BLM ID State Office GIS Specialist, and Gina Dingman-USFS Great Basin Coordination Center (GBCC) Center Manager. Edits by JKuenzi, USFS. Boundary changes at: (T13N R3E Sec 25), (T15N R3E Sec 31), (T16N R3E Sec 18-20, and 30), and (T16N R2E Sec 13) all from ID02 to ID01. (T10N R4E Sec 4-9,17-18, 20) and (T11N R4E Sec15-16, 21-22, 27-29, 34-31) from ID01 to ID02. 11/10/2020 - Michigan split from MI01 only, to MI01(Upper Penninsula) and MI02 in the south, per Kim Albracht, Communications Duty Officer. No change made to Dispatch Zone Boundary. Edits by JKuenzi. 11/4/2020 - Oregon OR07 divided into OR07 and OR08 per Kim Albracht, Communications Duty Officer. Edits by JKuenzi.10/26/2020 - Multiple boundary changes made to Federal Initial Attack Zones, but without any change to Dispatch Zone Boundaries: Raft River District of Sawtooth National Forest changed from UT01 to ID04; land east of Black Pine District of Sawtooth National Forest changed from ID05 to ID04. Direction from Denise Tolness, DOI/BLM GIS Specialist, and Gina Dingman, Great Basin Coordination Center Manager. Parts of Craters of the Moon National Monument changed from ID04 to ID05; Sheep Mountain (Red Rocks) area changed from MT03 to ID05, per Denise Tolness, Gina Dingman, and Kathryn "Kat" Sorenson, R1 Assistant Aircraft Coordinator. Edits for all changes made by JKuenzi.4/2/2020 - State owned land added and a portion of the boundary modified between MT01 and MT02 per Mike J Gibbons, Flathead Dispatch Center Mgr, and Kathryn "Kat" Sorenson, R1 Assistant Aircraft Coordinator. Edits by JKuenzi.2/21/2020 - Existing boundaries are updated, where possible, to a uniform base layer using the August 2019 Census State & County boundaries, along with Geographic Area Command Center boundaries, Dispatch Zone Boundaries, and Initial Attack State Zones. Edits by JKuenzi.2019-2020 - Initial Attack Frequency Zone data was provided by Kim Albracht, Acting and Permanent Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC), and maintained by Jill Kuenzi, USFS Fire & Aviation Mgt Geospatial Coordinator, NIFC, Boise, ID. Efforts made to tie changes with the Initial Attack Frequency Zones to other closely related datasets such as Geospatial Area Command Centers (GACCs),and Dispatch Areas, Major work completed to bring all the datasets up to date on consistent base data (8/2019 Census data), into alignment where possible, and to establish a scheduled update cycle for the nation. 2017-2019 - Initial Attack Frequency Zone data was provided by Gary Stewart, Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC), and maintained by Jill Kuenzi, USFS Fire & Aviation Mgt Geospatial Coordinator, NIFC, Boise, ID.2015-2016 - Initial Attack Frequency Zone data was provided by Gary Stewart, Communications Duty Officer (CDO) at National Interagency Fire Center (NIFC), and maintained by Dianna Sampson, BLM Geospatial Data Analyst, NIFC, Boise, ID.

  13. s

    Public Safety Answering Points

    • gis.shelbycounty911.org
    • hub.arcgis.com
    Updated Sep 21, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Shelby County 911 (2017). Public Safety Answering Points [Dataset]. https://gis.shelbycounty911.org/datasets/62ca043d54b4407fbecfa9e90ad66921
    Explore at:
    Dataset updated
    Sep 21, 2017
    Dataset authored and provided by
    Shelby County 911
    License

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

    Area covered
    Description

    This dataset maps Public Safety Answering Points (PSAPs) throughout the Mid South Region. A PSAP is a dedicated call center that receives 9-1-1 calls for police, fire, or emergency medical services. These facilities operate continuously — 24 hours a day, 7 days a week — ensuring uninterrupted emergency coverage.How It WorksWhen a 9-1-1 call is placed, trained telecommunicators at the PSAP either:Dispatch appropriate emergency responders directly, orTransfer the call to another public or private safety agency when specialized response is needed. Dataset ContentsThe feature layer includes:PSAP name and facility informationAgency affiliation and service jurisdictionAttributes supporting coverage analysis and interoperability Use CasesThis dataset supports:Operational awareness – visualizing where PSAPs are located and how jurisdictions are servedInteragency coordination – enabling effective response during large-scale incidents and disastersNext Generation 9-1-1 (NG9-1-1) – preparing for accurate, location-based routing of callsStrategic planning – identifying service overlaps, coverage gaps, and opportunities for system improvement Why It MattersPSAPs are the backbone of emergency communications. By centralizing and mapping this data, public safety leaders, GIS analysts, and emergency planners can strengthen regional readiness, improve response times, and ensure reliable access to life-saving services across the Mid South.This integrates the i3 Forest Guide principles:Forest canopy (overview) → What is this dataset about?Tree trunks (orientation) → How does it work?Branches (details) → What’s in it?Undergrowth (purpose) → Why does it matter?

  14. d

    Contour Dataset of the Potentiometric Surface of Groundwater-Level Altitudes...

    • catalog.data.gov
    • data.usgs.gov
    • +2more
    Updated Oct 8, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2025). Contour Dataset of the Potentiometric Surface of Groundwater-Level Altitudes Near the Planned Highway 270 Bypass, East of Hot Springs, Arkansas, July-August 2017 [Dataset]. https://catalog.data.gov/dataset/contour-dataset-of-the-potentiometric-surface-of-groundwater-level-altitudes-near-the-plan
    Explore at:
    Dataset updated
    Oct 8, 2025
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Area covered
    Arkansas, Hot Springs
    Description

    This dataset contains 50-ft contours for the Hot Springs shallowest unit of the Ouachita Mountains aquifer system potentiometric-surface map. The potentiometric-surface shows altitude at which the water level would have risen in tightly-cased wells and represents synoptic conditions during the summer of 2017. Contours were constructed from 59 water-level measurements measured in selected wells (locations in the well point dataset). Major streams and creeks were selected in the study area from the USGS National Hydrography Dataset (U.S. Geological Survey, 2017), and the spring point dataset with 18 spring altitudes calculated from 10-meter digital elevation model (DEM) data (U.S. Geological Survey, 2015; U.S. Geological Survey, 2016). After collecting, processing, and plotting the data, a potentiometric surface was generated using the interpolation method Topo to Raster in ArcMap 10.5 (Esri, 2017a). This tool is specifically designed for the creation of digital elevation models and imposes constraints that ensure a connected drainage structure and a correct representation of the surface from the provided contour data (Esri, 2017a). Once the raster surface was created, 50-ft contour interval were generated using Contour (Spatial Analyst), a spatial analyst tool (available through ArcGIS 3D Analyst toolbox) that creates a line-feature class of contours (isolines) from the raster surface (Esri, 2017b). The Topo to Raster and contouring done by ArcMap 10.5 is a rapid way to interpolate data, but computer programs do not account for hydrologic connections between groundwater and surface water. For this reason, some contours were manually adjusted based on topographical influence, a comparison with the potentiometric surface of Kresse and Hays (2009), and data-point water-level altitudes to more accurately represent the potentiometric surface. Select References: Esri, 2017a, How Topo to Raster works—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/how-topo-to-raster-works.htm. Esri, 2017b, Contour—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro Raster Surface toolset at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/contour.htm. Kresse, T.M., and Hays, P.D., 2009, Geochemistry, Comparative Analysis, and Physical and Chemical Characteristics of the Thermal Waters East of Hot Springs National Park, Arkansas, 2006-09: U.S. Geological Survey 2009–5263, 48 p., accessed November 28, 2017, at https://pubs.usgs.gov/sir/2009/5263/. U.S. Geological Survey, 2015, USGS NED 1 arc-second n35w094 1 x 1 degree ArcGrid 2015, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html. U.S. Geological Survey, 2016, USGS NED 1 arc-second n35w093 1 x 1 degree ArcGrid 2016, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html.

  15. BLM Natl WesternUS GRSG Biologically Significant Units October 2017 Update

    • catalog.data.gov
    • s.cnmilf.com
    Updated Sep 29, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bureau of Land Management (2025). BLM Natl WesternUS GRSG Biologically Significant Units October 2017 Update [Dataset]. https://catalog.data.gov/dataset/blm-natl-westernus-grsg-biologically-significant-units-october-2017-update-969a9
    Explore at:
    Dataset updated
    Sep 29, 2025
    Dataset provided by
    Bureau of Land Managementhttp://www.blm.gov/
    Description

    The Sheeprocks (UT) was revised to resync with the UT habitat change as reflected in the Oct 2017 habitat data, creating the most up-to-date version of this dataset. Data submitted by Wyoming in February 2018 and by Montana and Oregon in May 2016 were used to update earlier versions of this feature class. The biologically significant unit (BSU) is a geographical/spatial area within Greater Sage-Grouse habitat that contains relevant and important habitats which is used as the basis for comparative calculations to support evaluation of changes to habitat. This BSU unit, or subset of this unit is used in the calculation of the anthropogenic disturbance threshold and in the adaptive management habitat trigger. BSU feature classes were submitted by individual states/EISs and consolidated by the Wildlife Spatial Analysis Lab. They are sometimes referred to as core areas/core habitat areas in the explanations below, which were consolidated from metadata submitted with BSU feature classes. These data provide a biological tool for planning in the event of human development in sage-grouse habitats. The intended use of all data in the BLM's GIS library is to support diverse activities including planning, management, maintenance, research, and interpretation. While the BSU defines the geographic extent and scale of these two measures, how they are calculated differs based on the specific measures to reflect appropriate assessment and evaluation as supported by scientific literature.There are 10 BSUs for the Idaho and Southwestern Montana GRSG EIS sub-region. For the Idaho and Southwestern Montana Greater Sage-Grouse Plan Amendment FEIS the biologically significant unit is defined as: a geographical/spatial area within greater sage-grouse habitat that contains relevant and important habitats which is used as the basis for comparative calculations to support evaluation of changes to habitat. Idaho: BSUs include all of the Idaho Fish and Game modeled nesting and delineated winter habitat, based on 2011 inventories within Priority and/or Important Habitat Management Area (Alternative G) within a Conservation Area. There are eight BSUs for Idaho identified by Conservation Area and Habitat Management Area: Idaho Desert Conservation Area - Priority, Idaho Desert Conservation Area - Important, Idaho Mountain Valleys Conservation Area - Priority, Idaho Mountain Valleys Conservation Area - Important, Idaho Southern Conservation Area - Priority, Idaho Southern Conservation Area - Important, Idaho West Owyhee Conservation Area - Priority, and Idaho West Owyhee Conservation Area - Important. Raft River : Utah portion of the Sawtooth National Forest, 1 BSU. All of this areas was defined as Priority habitat in Alternative G. Raft River - Priority. Montana: All of the Priority Habitat Management Area. 1 BSU. SW Montana Conservation Area - Priority. Montana BSUs were revised in May 2016 by the MT State Office. They are grouped together and named by the Population in which they are located: Northern Montana, Powder River Basin, Wyoming Basin, and Yellowstone Watershed. North and South Dakota BSUs have been grouped together also. California and Nevada's BSUs were developed by Nevada Department of Wildlife's Greater Sage-Grouse Wildlife Staff Specialist and Sagebrush Ecosystem Technical Team Representative in January 2015. Nevada's Biologically Significant Units (BSUs) were delineated by merging associated PMUs to provide a broader scale management option that reflects sage grouse populations at a higher scale. PMU boundarys were then modified to incorporate Core Management Areas (August 2014; Coates et al. 2014) for management purposes. (Does not include Bi-State DPS.) Within Colorado, a Greater Sage-Grouse GIS data set identifying Preliminary Priority Habitat (PPH) and Preliminary General Habitat (PGH) was developed by Colorado Parks and Wildlife. This data is a combination of mapped grouse occupied range, production areas, and modeled habitat (summer, winter, and breeding). PPH is defined as areas of high probability of use (summer or winter, or breeding models) within a 4 mile buffer around leks that have been active within the last 10 years. Isolated areas with low activity were designated as general habitat. PGH is defined as Greater sage-grouse Occupied Range outside of PPH. Datasets used to create PPH and PGH: Summer, winter, and breeding habitat models. Rice, M. B., T. D. Apa, B. L. Walker, M. L. Phillips, J. H. Gammonly, B. Petch, and K. Eichhoff. 2012. Analysis of regional species distribution models based on combined radio-telemetry datasets from multiple small-scale studies. Journal of Applied Ecology in review. Production Areas are defined as 4 mile buffers around leks which have been active within the last 10 years (leks active between 2002-2011). Occupied range was created by mapping efforts of the Colorado Division of Wildlife (now Colorado Parks and Wildlife –CPW) biologists and district officers during the spring of 2004, and further refined in early 2012. Occupied Habitat is defined as areas of suitable habitat known to be used by sage-grouse within the last 10 years from the date of mapping. Areas of suitable habitat contiguous with areas of known use, which do not have effective barriers to sage-grouse movement from known use areas, are mapped as occupied habitat unless specific information exists that documents the lack of sage-grouse use. Mapped from any combination of telemetry locations, sightings of sage grouse or sage grouse sign, local biological expertise, GIS analysis, or other data sources. This information was derived from field personnel. A variety of data capture techniques were used including the SmartBoard Interactive Whiteboard using stand-up, real-time digitizing atvarious scales (Cowardin, M., M. Flenner. March 2003. Maximizing Mapping Resources. GeoWorld 16(3):32-35). Update August 2012: This dataset was modified by the Bureau of Land Management as requested by CPW GIS Specialist, Karin Eichhoff. Eichhoff requested that this dataset, along with the GrSG managment zones (population range zones) dataset, be snapped to county boundaries along the UT-CO border and WY-CO border. The county boundaries dataset was provided by Karin Eichhoff. In addition, a few minor topology errors were corrected where PPH and PGH were overlapping. Update October 10, 2012: NHD water bodies greater than 100 acres were removed from GrSG habitat, as requested by Jim Cagney, BLM CO Northwest District Manager. 6 water bodies in total were removed (Hog Lake, South Delaney, Williams Fork Reservoir, North Delaney, Wolford Mountain Reservoir (2 polygons)). There were two “SwampMarsh” polygons that resulted when selecting polygons greater than 100 acres; these polygons were not included. Only polygons with the attribute “LakePond” were removed from GrSG habitat. Colorado Greater Sage Grouse managment zones based on CDOW GrSG_PopRangeZones20120609.shp. Modified and renumbered by BLM 06/09/2012. The zones were modified again by the BLM in August 2012. The BLM discovered areas where PPH and PGH were not included within the zones. Several discrepancies between the zones and PPH and PGH dataset were discovered, and were corrected by the BLM. Zones 18-21 are linkages added as zones by the BLM. In addition to these changes, the zones were adjusted along the UT-CO boundary and WY-CO boundary to be coincident with the county boundaries dataset. This was requested by Karin Eichhoff, GIS Specialist at the CPW. She provided the county boundaries dataset to the BLM. Greater sage grouse GIS data set identifying occupied, potential and vacant/unknown habitats in Colorado. The data set was created by mapping efforts of the Colorado Division of Wildlife biologist and district officers during the spring of 2004, and further refined in the winter of 2005. Occupied Habitat: Areas of suitable habitat known to be used by sage-grouse within the last 10 years from the date of mapping. Areas of suitable habitat contiguous with areas of known use, which do not have effective barriers to sage-grouse movement from known use areas, are mapped as occupied habitat unless specific information exists that documents the lack of sage-grouse use. Mapped from any combination of telemetry locations, sightings of sage grouse or sage grouse sign, local biological expertise, GIS analysis, or other data sources. Vacant or Unknown Habitat: Suitable habitat for sage-grouse that is separated (not contiguous) from occupied habitats that either: 1) Has not been adequately inventoried, or 2) Has not had documentation of grouse presence in the past 10 years Potentially Suitable Habitat: Unoccupied habitats that could be suitable for occupation of sage-grouse if practical restoration were applied. Soils or other historic information (photos, maps, reports, etc.) indicate sagebrush communities occupied these areas. As examples, these sites could include areas overtaken by pinyon-juniper invasions or converted rangelandsUpdate October 10, 2012: NHD water bodies greater than 100 acres were removed from GrSG habitat and management zones, as requested by Jim Cagney, BLM CO Northwest District Manager. 6 water bodies in total were removed (Hog Lake, South Delaney, Williams Fork Reservoir, North Delaney, Wolford Mountain Reservoir (2 polygons)). There were two “SwampMarsh” polygons that resulted when selecting polygons greater than 100 acres; these polygons were not included. Only polygons with the attribute “LakePond” were removed from GrSG habitat. Oregon submitted updated BSU boundaries in May 2016 and again in October 2016, which were incorporated into this latest version. In Oregon, the Core Area maps and data were developed as one component of the Conservation Strategy for sage-grouse. Specifically, these data provide a tool in planning and identifying appropriate mitigation in the event of human development in sage-grouse habitats. These maps will assist in making

  16. Namoi bore analysis rasters

    • researchdata.edu.au
    • data.gov.au
    Updated Dec 10, 2018
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bioregional Assessment Program (2018). Namoi bore analysis rasters [Dataset]. https://researchdata.edu.au/namoi-bore-analysis-rasters/2991466
    Explore at:
    Dataset updated
    Dec 10, 2018
    Dataset provided by
    Data.govhttps://data.gov/
    Authors
    Bioregional Assessment Program
    License

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

    Area covered
    Namoi River
    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 resource contains raster datasets created using ArcGIS to analyse groundwater levels in the Namoi subregion.

    Purpose

    These data layers were created in ArcGIS as part of the analysis to investigate surface water - groundwater connectivity in the Namoi subregion. The data layers provide several of the figures presented in the Namoi 2.1.5\tSurface water - groundwater interactions report.

    Dataset History

    Extracted points inside Namoi subregion boundary. Converted bore and pipe values to Hydrocode format, changed heading of 'Value' column to 'Waterlevel' and removed unnecessary columns then joined to Updated_NSW_GroundWaterLevel_data_analysis_v01\NGIS_NSW_Bore_Join_Hydmeas_unique_bores.shp clipped to only include those bores within the Namoi subregion.

    Selected only those bores with sample dates between >=26/4/2012 and <31/7/2012. Then removed 4 gauges due to anomalous ref_pt_height values or WaterElev values higher than Land_Elev values.

    Then added new columns of calculations:

    WaterElev = TsRefElev - Water_Leve

    DepthWater = WaterElev - Ref_pt_height

    Ref_pt_height = TsRefElev - LandElev

    Alternatively - Selected only those bores with sample dates between >=1/5/2006 and <1/7/2006

    2012_Wat_Elev - This raster was created by interpolating Water_Elev field points from HydmeasJune2012_only.shp, using Spatial Analyst - Topo to Raster tool. And using the alluvium boundary (NAM_113_Aquifer1_NamoiAlluviums.shp) as a boundary input source.

    12_dw_olp_enf - Select out only those bores that are in both source files.

    Then using depthwater in Topo to Raster, with alluvium as the boundary, ENFORCE field chosen, and using only those bores present in 2012 and 2006 dataset.

    2012dw1km_alu - Clipped the 'watercourselines' layer to the Namoi Subregion, then selected 'Major' water courses only. Then used the Geoprocessing 'Buffer' tool to create a polygon delineating an area 1km around all the major streams in the Namoi subregion.

    selected points from HydmeasJune2012_only.shp that were within 1km of features the WatercourseLines then used the selected points and the 1km buffer around the major water courses and the Topo to Raster tool in Spatial analyst to create the raster.

    Then used the alluvium boundary to truncate the raster, to limit to the area of interest.

    12_minus_06 - Select out bores from the 2006 dataset that are also in the 2012 dataset. Then create a raster using depth_water in topo to raster, with ENFORCE field chosen to remove sinks, and alluvium as boundary. Then, using Map Algebra - Raster Calculator, subtract the raster just created from 12_dw_olp_enf

    Dataset Citation

    Bioregional Assessment Programme (2017) Namoi bore analysis rasters. Bioregional Assessment Derived Dataset. Viewed 10 December 2018, http://data.bioregionalassessments.gov.au/dataset/7604087e-859c-4a92-8548-0aa274e8a226.

    Dataset Ancestors

  17. d

    Geospatial data for object-based high-resolution classification of conifers...

    • catalog.data.gov
    • data.usgs.gov
    • +1more
    Updated Oct 8, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey (2025). Geospatial data for object-based high-resolution classification of conifers within greater sage-grouse habitat across Nevada and a portion of northeastern California (ver. 2.0 July 2018) [Dataset]. https://catalog.data.gov/dataset/geospatial-data-for-object-based-high-resolution-classification-of-conifers-within-greater
    Explore at:
    Dataset updated
    Oct 8, 2025
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Description

    These products were developed to provide scientific and correspondingly spatially explicit information regarding the distribution and abundance of conifers (namely, singleleaf pinyon (Pinus monophylla), Utah juniper (Juniperus osteosperma), and western juniper (Juniperus occidentalis)) in Nevada and portions of northeastern California. Encroachment of these trees into sagebrush ecosystems of the Great Basin can present a threat to populations of greater sage-grouse (Centrocercus urophasianus). These data provide land managers and other interested parties with a high-resolution representation of conifers across the range of sage-grouse habitat in Nevada and northeastern California that can be used for a variety of management and research applications. We mapped conifer trees at 1 x 1 meter resolution across the extent of all Nevada Department of Wildlife Sage-grouse Population Management Units plus a 10 km buffer. Using 2010 and 2013 National Agriculture Imagery Program digital orthophoto quads (DOQQs) as our reference imagery, we applied object-based image analysis with Feature Analyst software (Overwatch, 2013) to classify conifer features across our study extent. This method relies on machine learning algorithms that extract features from imagery based on their spectral and spatial signatures. Conifers in 6230 DOQQs were classified and outputs were then tested for errors of omission and commission using stratified random sampling. Results of the random sampling were used to populate a confusion matrix and calculate the overall map accuracy of 84.3 percent. We provide 5 sets of products for this mapping process across the entire mapping extent: (1) a shapefile representing accuracy results linked to our mapping subunits; (2) binary rasters representing conifer presence or absence at a 1 x 1 meter resolution; (3) a 30 x 30 meter resolution raster representing percentage of conifer canopy cover within each cell from 0 to 100; (4) 1 x 1 meter resolution canopy cover classification rasters derived from a 50 meter radius moving window analysis; and (5) a raster prioritizing pinyon-juniper management for sage-grouse habitat restoration efforts. The latter three products can be reclassified into user-specified bins to meet different management or study objectives, which include approximations for phases of encroachment. These products complement, and in some cases improve upon, existing conifer maps in the western United States, and will help facilitate sage-grouse habitat management and sagebrush ecosystem restoration. These data support the following publication: Coates, P.S., Gustafson, K.B., Roth, C.L., Chenaille, M.P., Ricca, M.A., Mauch, Kimberly, Sanchez-Chopitea, Erika, Kroger, T.J., Perry, W.M., and Casazza, M.L., 2017, Using object-based image analysis to conduct high-resolution conifer extraction at regional spatial scales: U.S. Geological Survey Open-File Report 2017-1093, 40 p., https://doi.org/10.3133/ofr20171093. References: ESRI, 2013, ArcGIS Desktop: Release 10.2: Environmental Systems Research Institute. Overwatch, 2013, Feature Analyst Version 5.1.2.0 for ArcGIS: Overwatch Systems Ltd.

  18. e

    Water network

    • data.europa.eu
    wms
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    WMS - Saxon Water Network (Flowing and Standing Waters) - Working status [Dataset]. https://data.europa.eu/data/datasets/59ec271c-1c9f-4185-8386-eb74d3905e03?locale=en
    Explore at:
    wmsAvailable download formats
    Description

    The water network was attributed with the area code according to the catchment area boundaries in Saxony. Waters with a catchment area size greater than 10 km² are fully attributed with the water code.

  19. c

    Graphics Code Variances

    • opendata.columbus.gov
    • columbus.hub.arcgis.com
    • +2more
    Updated Jul 3, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Columbus Maps & Apps (2017). Graphics Code Variances [Dataset]. https://opendata.columbus.gov/datasets/graphics-code-variances
    Explore at:
    Dataset updated
    Jul 3, 2017
    Dataset authored and provided by
    City of Columbus Maps & Apps
    License

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

    Area covered
    Description

    This map layer shows Graphics Code variances approved by the Graphics Commission. The Graphics Code, as described in Columbus Code Chapters 3375 to 3383 regulates private graphics within the city. A graphic is defined as any communication designed to be seen from any public place utilizing letters, words, numbers, symbols, pictures, color, illumination, geometric, or nongeometric shapes or planes, in whole or part, including all structural components. This map layer includes variances from approximately 2005 to current. Graphics commission actions are added to the map based on parcel and address location provided on the application. Data is maintained by the GIS Analyst at the Department of Building and Zoning Services.

  20. Wellington Region High Detailed Streams

    • opendata.gw.govt.nz
    • hub.arcgis.com
    • +1more
    Updated Feb 20, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Greater Wellington Regional Council (2017). Wellington Region High Detailed Streams [Dataset]. https://opendata.gw.govt.nz/maps/wellington-region-high-detailed-streams/about
    Explore at:
    Dataset updated
    Feb 20, 2017
    Dataset authored and provided by
    Greater Wellington Regional Councilhttps://www.gw.govt.nz/
    License

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

    Area covered
    Description

    This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
ArcGIS for Transportation Analytics (2013). Add GTFS to a Network Dataset [Dataset]. https://opendata.rcmrd.org/content/0fa52a75d9ba4abcad6b88bb6285fae1

Add GTFS to a Network Dataset

Explore at:
63 scholarly articles cite this dataset (View in Google Scholar)
Dataset updated
Jun 27, 2013
Dataset authored and provided by
ArcGIS for Transportation Analytics
Description

Deprecation notice: This tool is deprecated because this functionality is now available with out-of-the-box tools in ArcGIS Pro. The tool author will no longer be making further enhancements or fixing major bugs.Use Add GTFS to a Network Dataset to incorporate transit data into a network dataset so you can perform schedule-aware analyses using the Network Analyst tools in ArcMap.After creating your network dataset, you can use the ArcGIS Network Analyst tools, like Service Area and OD Cost Matrix, to perform transit/pedestrian accessibility analyses, make decisions about where to locate new facilities, find populations underserved by transit or particular types of facilities, or visualize the areas reachable from your business at different times of day. You can also publish services in ArcGIS Server that use your network dataset.The Add GTFS to a Network Dataset tool suite consists of a toolbox to pre-process the GTFS data to prepare it for use in the network dataset and a custom GTFS transit evaluator you must install that helps the network dataset read the GTFS schedules. A user's guide is included to help you set up your network dataset and run analyses.Instructions:Download the tool. It will be a zip file.Unzip the file and put it in a permanent location on your machine where you won't lose it. Do not save the unzipped tool folder on a network drive, the Desktop, or any other special reserved Windows folders (like C:\Program Files) because this could cause problems later.The unzipped file contains an installer, AddGTFStoaNetworkDataset_Installer.exe. Double-click this to run it. The installation should proceed quickly, and it should say "Completed" when finished.Read the User's Guide for instructions on creating and using your network dataset.System requirements:ArcMap 10.1 or higher with a Desktop Standard (ArcEditor) license. (You can still use it if you have a Desktop Basic license, but you will have to find an alternate method for one of the pre-processing tools.) ArcMap 10.6 or higher is recommended because you will be able to construct your network dataset much more easily using a template rather than having to do it manually step by step. This tool does not work in ArcGIS Pro. See the User's Guide for more information.Network Analyst extensionThe necessary permissions to install something on your computer.Data requirements:Street data for the area covered by your transit system, preferably data including pedestrian attributes. If you need help preparing high-quality street data for your network, please review this tutorial.A valid GTFS dataset. If your GTFS dataset has blank values for arrival_time and departure_time in stop_times.txt, you will not be able to run this tool. You can download and use the Interpolate Blank Stop Times tool to estimate blank arrival_time and departure_time values for your dataset if you still want to use it.Help forum

Search
Clear search
Close search
Google apps
Main menu