The DataGM (Data Governance and Management) extension for CKAN aims to integrate data governance functionalities into the CKAN data portal environment. Based on the available information, it supports CKAN version 2.5 and relies on CKAN's built-in tracking feature to monitor and manage data usage and access. The extension appears to provide a framework for administrating and controlling data assets within the CKAN instance. Key Features: CKAN 2.5 Compatibility: Designed to work with CKAN version 2.5, ensuring compatibility with older CKAN installations. Upgrade to the latest version if the extension does not work on later versions of CKAN. Built-in Tracking Integration: Leverages CKAN's existing tracking capabilities to monitor data usage, access patterns, and other relevant metadata. This allows a view of metrics regarding dataset use. Cron Job Dependency: Requires a cron job setup, indicating scheduled tasks for data governance processes, such as automated data quality checks, metadata updates, or usage reporting. This highlights the automated nature of the DataGM extension. Use Cases: Data Usage Monitoring: Track dataset accesses to understand which data assets are most popular and used, thereby aligning resource allocation and governance efforts. Scheduled Data tasks: Schedule regular data update and archival tasks, making sure datasets do not stay out of date. Metadata Governance: Automatable tasks for validating and improving the metadata quality of datasets and resources. Technical Integration: DataGM uses CKAN's built-in tracking feature. DataGM requires the set up of Cron jobs. The exact integration methodologies that datagm utilizes were not specified in the documentation. Benefits & Impact: Utilizing the datagm extension allows for the monitoring and management of data assets in the CKAN environment.

The Wildland Fire Interagency Geospatial Services (WFIGS) Group provides authoritative geospatial data products under the interagency Wildland Fire Data Program. Hosted in the National Interagency Fire Center ArcGIS Online Organization (The NIFC Org), WFIGS provides both internal and public facing data, accessible in a variety of formats.This service contains all wildland fire incidents from the IRWIN (Integrated Reporting of Wildland Fire Information) integration service that meet the following criteria:Categorized in IRWIN as a Wildfire (WF), Prescribed Fire (RX), or Incident Complex (CX) recordHas not been declared contained, controlled, nor outHas not had fire report record completed (certified)Is Valid and not "quarantined" in IRWIN due to potential conflicts with other records"Fall-off" rules are used to ensure that stale records are not retained. Records are removed from this service under the following conditions:Fire size is less than 10 acres (Size Class A or B), and fire information has not been updated in more than 3 daysFire size is between 10 and 100 acres (Size Class C), and fire information hasn't been updated in more than 8 daysFire size is larger than 100 acres (Size Class D-L), but fire information hasn't been updated in more than 14 days.Fire size used in the fall off rules is from the IncidentSize field.Criteria were determined by an NWCG Geospatial Subcommittee task group. Data are refreshed from IRWIN every 5 minutes.Fall-off rules are enforced hourly.Attributes:SourceOIDThe OBJECTID value of the source record in the source dataset providing the attribution.ABCDMiscA FireCode used by USDA FS to track and compile cost information for emergency IA fire suppression on A, B, C & D size class fires on FS lands.ADSPermissionStateIndicates the permission hierarchy that is currently being applied when a system utilizes the UpdateIncident operation.ContainmentDateTimeThe date and time a wildfire was declared contained.ControlDateTimeThe date and time a wildfire was declared under control.CreatedBySystemArcGIS Server Username of system that created the IRWIN Incident record.IncidentSizeReported for a fire. The minimum size is 0.1.DiscoveryAcresAn estimate of acres burning when the fire is first reported by the first person to call in the fire. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.DispatchCenterIDA unique identifier for a dispatch center responsible for supporting the incident.EstimatedCostToDateThe total estimated cost of the incident to date.FinalAcresReported final acreage of incident.FinalFireReportApprovedByTitleThe title of the person that approved the final fire report for the incident.FinalFireReportApprovedByUnitNWCG Unit ID associated with the individual who approved the final report for the incident.FinalFireReportApprovedDateThe date that the final fire report was approved for the incident.FireBehaviorGeneralA general category describing how the fire is currently reacting to the influences of fuel, weather, and topography.FireBehaviorGeneral1A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography).FireBehaviorGeneral2A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography). FireBehaviorGeneral3A more specific category further describing the general fire behavior (how the fire is currently reacting to the influences of fuel, weather, and topography).FireCauseBroad classification of the reason the fire occurred identified as human, natural or unknown. FireCauseGeneralAgency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. For statistical purposes, fire causes are further broken into specific causes. FireCauseSpecificA further categorization of each General Fire Cause to indicate more specifically the agency or circumstance which started a fire or set the stage for its occurrence; source of a fire's ignition. FireCodeA code used within the interagency wildland fire community to track and compile cost information for emergency fire suppression expenditures for the incident. FireDepartmentIDThe U.S. Fire Administration (USFA) has created a national database of Fire Departments. Most Fire Departments do not have an NWCG Unit ID and so it is the intent of the IRWIN team to create a new field that includes this data element to assist the National Association of State Foresters (NASF) with data collection.FireDiscoveryDateTimeThe date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.FireMgmtComplexityThe highest management level utilized to manage a wildland fire event. FireOutDateTimeThe date and time when a fire is declared out. FireStrategyConfinePercentIndicates the percentage of the incident area where the fire suppression strategy of "Confine" is being implemented.FireStrategyFullSuppPercentIndicates the percentage of the incident area where the fire suppression strategy of "Full Suppression" is being implemented.FireStrategyMonitorPercentIndicates the percentage of the incident area where the fire suppression strategy of "Monitor" is being implemented.FireStrategyPointZonePercentIndicates the percentage of the incident area where the fire suppression strategy of "Point Zone Protection" is being implemented.FSJobCodeSpecific to the Forest Service, code use to indicate the FS job accounting code for the incident. Usually displayed as 2 char prefix on FireCode.FSOverrideCodeSpecific to the Forest Service, code used to indicate the FS override code for the incident. Usually displayed as a 4 char suffix on FireCode. For example, if the FS is assisting DOI, an override of 1502 will be used.GACC"A code that identifies the wildland fire geographic area coordination center (GACC) at the point of origin for the incident. A GACC is a facility used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic area."ICS209ReportDateTimeThe date and time of the latest approved ICS-209 report.ICS209ReportForTimePeriodFromThe date and time of the beginning of the time period for the current ICS-209 submission.ICS209ReportForTimePeriodToThe date and time of the end of the time period for the current ICS-209 submission. ICS209ReportStatusThe version of the ICS-209 report (initial, update, or final). There should never be more than one initial report, but there can be numerous updates and multiple finals (as determined by business rules).IncidentManagementOrganizationThe incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.IncidentNameThe name assigned to an incident.IncidentShortDescriptionGeneral descriptive location of the incident such as the number of miles from an identifiable town. IncidentTypeCategoryThe Event Category is a sub-group of the Event Kind code and description. The Event Category breaks down the Event Kind into more specific event categories.IncidentTypeKindA general, high-level code and description of the types of incidents and planned events to which the interagency wildland fire community responds.InitialLatitudeThe latitude of the initial reported point of origin specified in decimal degrees.InitialLongitudeThe longitude of the initial reported point of origin specified in decimal degrees.InitialResponseAcresAn estimate of acres burning at the time of initial response (when the IC arrives and performs initial size up) The minimum size must be 0.1. The estimate should include number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.InitialResponseDateTimeThe date/time of the initial response to the incident (when the IC arrives and performs initial size up)IrwinIDUnique identifier assigned to each incident record in IRWIN.IsFireCauseInvestigatedIndicates if an investigation is underway or was completed to determine the cause of a fire.IsFSAssistedIndicates if the Forest Service provided assistance on an incident outside their jurisdiction.IsMultiJurisdictionalIndicates if the incident covers multiple jurisdictions.IsReimbursableIndicates the cost of an incident may be another agency’s responsibility.IsTrespassIndicates if the incident is a trespass claim or if a bill will be pursued.IsUnifiedCommandIndicates whether the incident is being managed under Unified Command. Unified Command is an application of the ICS used when there is more than one agency with incident jurisdiction or when incidents cross political jurisdictions. Under Unified Command, agencies work together through their designated IC at a single incident command post to establish common objectives and issue a single Incident Action Plan.LocalIncidentIdentifierA number or code that uniquely identifies an incident for a particular local fire management organization within a particular calendar year.ModifiedBySystemArcGIS Server username of system that last modified the IRWIN Incident record.PercentContainedIndicates the percent of incident area that is no longer active. Reference definition in fire line handbook when developing standard.PercentPerimeterToBeContainedIndicates the percent of perimeter left to be completed. This entry is appropriate for full suppression, point/zone protection, and confine fires, or any combination of these strategies. This entry is not used for wildfires managed entirely under a monitor strategy. (Note: Value is not currently being passed by ICS-209)POOCityThe closest city to the incident point of origin.POOCountyThe County Name

In this course, you will learn to work within the free and open-source R environment with a specific focus on working with and analyzing geospatial data. We will cover a wide variety of data and spatial data analytics topics, and you will learn how to code in R along the way. The Introduction module provides more background info about the course and course set up. This course is designed for someone with some prior GIS knowledge. For example, you should know the basics of working with maps, map projections, and vector and raster data. You should be able to perform common spatial analysis tasks and make map layouts. If you do not have a GIS background, we would recommend checking out the West Virginia View GIScience class. We do not assume that you have any prior experience with R or with coding. So, don't worry if you haven't developed these skill sets yet. That is a major goal in this course. Background material will be provided using code examples, videos, and presentations. We have provided assignments to offer hands-on learning opportunities. Data links for the lecture modules are provided within each module while data for the assignments are linked to the assignment buttons below. Please see the sequencing document for our suggested order in which to work through the material. After completing this course you will be able to: prepare, manipulate, query, and generally work with data in R. perform data summarization, comparisons, and statistical tests. create quality graphs, map layouts, and interactive web maps to visualize data and findings. present your research, methods, results, and code as web pages to foster reproducible research. work with spatial data in R. analyze vector and raster geospatial data to answer a question with a spatial component. make spatial models and predictions using regression and machine learning. code in the R language at an intermediate level.

The Express Loader (ckanext-xloader) extension enhances CKAN's data loading capabilities by providing a faster and more robust alternative to the DataPusher for importing tabular data into the CKAN DataStore. It optimizes the data loading process, particularly for CSV and similar formats, prioritizing speed and preventing common errors encountered with type conversions. Sponsored by OpenGov Inc., this extension aims to improve open data infrastructure globally. Key Features: High-Speed Data Loading: Utilizes PostgreSQL's COPY command to directly pipe CSV files into the database, resulting in significantly faster loading speeds (reportedly 10x faster in tests) compared to DataPusher. Robust Data Handling: Loads all data initially as text, preventing errors associated with premature type guessing and allowing administrators to convert columns to appropriate types using CKAN's Data Dictionary feature (CKAN 2.7+). Simplified Job Queue: Employs RQ (Redis Queue) for job management, offering a simpler and more debuggable queueing system compared to the bespoke ckan-service-provider used by DataPusher. RQ is backed by Redis and allows access to the CKAN model. Integrated Worker Process: Runs the data loading job within the same application as CKAN, eliminating the need for a separate web server and reducing complexity related to inter-service communication and configuration. Job results are stored in their own db which the intent is to move into the CKAN db. Format Flexibility: Supports loading data from CSV and other formats like XLS. The accepted formats are configurable via the ckanext.xloader.formats setting. Configuration Options: Provides several configuration options: maximum file size, job timeout, ignoring file hash and specifying whether to load a data excerpt if the file size exceeds the maximum allowed. Technical Integration: The extension integrates directly into CKAN as a plugin. It requires enabling the xloader plugin in the CKAN configuration file (production.ini). It overrides the default DataPusher (if enabled) by handling data loading requests itself. It also has dependencies such as RQ for the job queue system. It adds background worker processes that need to be managed separately, ideally through a process supervision tool such as Supervisor. Benefits & Impact: By replacing DataPusher with Express Loader, CKAN instances can experience significantly improved performance when loading tabular data. The extension's robust data handling mitigates errors related to automatic type conversion, while the simplified job queue and integrated worker process reduce the complexity of deployment and maintenance. These improvements contribute to more efficient open data infrastructure and a better user experience.

Work-health balance is a questionnaire that assesses the influence of work on the participant's health and the influence of their health on their work.

Geological sections noted in the field were to be added to a database for ease of access and for incorporation into GIS and modelling. The final database has never been approved and a data manager never identified. Currently only test data is held.

Table to show all people in work in the UK by their place of residence and place of work (main job). The data helps to show commuting patterns since 2004. Matrix shows where workers commute from (residence) and to (workplace). Commuting data from the Annual Population Survey 2010 has been presented here using Prezi software. How does London get to work? Commuting in London on Prezi.

This data primarily pertains to City-owned trees located on road allowances across Toronto. The intent of the database is to provide an inventory of City owned-trees on the road allowance for inspection and maintenance. Urban Forestry has had requests to determine ownership of trees within the road allowance, and where this has confirmed private ownership, these trees may be in the database as well for future reference. The dataset is limited to the City of Toronto boundaries and is best utilized when overlaid with the City's Street Centreline file. This shape file should not be used for ownership verification. The positioning shown is not accurate as the tree data has been geographically coded to the parcel address, and this will incorrectly indicate the tree location within the private parcel. The Toronto Street Tree data is compiled by Urban Forestry staff during their inspections or tree maintenance work on trees located on City owned street allowances. The database is large covering over 530,000 records and annually Urban Forestry can only update the volume that is worked on. Some data may be several years old and have not been updated recently, so there may be inaccuracies with the data as a result. Note: We are currently updating and improving street tree location information. This is an ongoing process; therefore, some trees may still appear mapped to the address point, whereas others will be mapped in their physical location along the street. For more information please contact Urban Forestry. Downloading This is a fairly large data set. If you have any issues (like a timeout) using the dynamic file downloader (the first link in the "Download Data" section) feel free to use the Alternate Files.

The CYI Survey invites employees to voluntarily disclose how they self-identify based on questions related to Indigenous identity, Black identity, gender, race/ethnicity, sexual orientation and if they identify as a person with a disability. The data displays the diversity within the workforce at the City of Toronto. The goal of the survey is to track progress towards realizing the City's Motto "Diversity Our Strength", and to continuously monitor and socialize diversity data across the City, in order to help inform decision-making and address gaps in representation across all levels at the City. About the Datasets The following datasets were collected through the City's CYI Workforce survey between 2013 and 2024. The data has been reported in aggregate formats that do not allow for the identification of individual employees. First Nations, Inuit, and Metis Data The City is working with an external working group of First Nations, Inuit, and Métis (FNIM) advisors to develop a framework for the collection and use of FNIM data. While this framework is in development, Indigenous data from CYI surveys conducted in 2022, 2023, and 2024 will not be made available until Ownership, Control, Access, and Possession (OCAP) and United Nations Declaration on the Rights of Indigenous Peoples (UNDRIP) principles have been applied. However, Indigenous data from 2018, 2019, 2020 and 2021 is still available. For questions related to the implications or considerations of the framework’s development, please contact dataequity@toronto.ca

The Get Started document provides an overview of Energydata.info's interface and features. ENERGYDATA.INFO is an open data platform providing access to datasets and data analytics that are relevant to the energy sector. ENERGYDATA.INFO has been developed as a public good available to governments, development organizations, private sector, non-governmental organizations, academia, civil society and individuals to share data and analytics that can help achieving the United Nations’ Sustainable Development Goal 7 of ensuring access to affordable, reliable, sustainable and modern energy for all. The World Bank and the International Finance Corporation, collectively the World Bank Group (WBG) strives to enhance public access to and use of data that can support development impact. ENERGYDATA.INFO is designed according to open data and open source standards and principles. Access to data and information available on ENERGYDATA.INFO is free, subject to the terms of this agreement. The World Bank Group welcomes the opportunity to collaborate further with data providers and users in making more data, visualizations and tools publicly available. Please contact our team at energydata@worldbankgroup.org if you are interested in collaborating further with ENERGYDATA.INFO. ENERGYDATA.INFO is powered by the open-source data portal platform CKAN, and it is developed publicly on GitHub. More information on CKAN and GitHub can be accessed at https://ckan.org/ and https://github.com/ Map disclaimer The boundaries, colors, denominations and any other information shown on maps presented on ENERGYDATA.INFO do not imply, on the part of The World Bank Group, any judgment on the legal status of any territory, or any endorsement or acceptance of such boundaries. Terms of Use You are encouraged to use the content in ENERGYDATA.INFO to benefit yourself and others in creative ways. The majority of content in ENERGYDATA.INFO is licensed under the Creative Commons Attribution license (CC BY 4.0). Works in ENERGYDATA.INFO that are not subject to the CC BY license are clearly labeled with the specific license terms under which those works may be used. By using ENERGYDATA.INFO, you agree to be bound by these Terms of Use for ENERGYDATA.INFO. Please read the terms before using any content in ENERGYDATA.INFO. The boundaries, colors, denominations and any other information shown on maps presented on ENERGYDATA.INFO do not imply, on the part of The World Bank Group, any judgment on the legal status of any territory, or any endorsement or acceptance of such boundaries. You are encouraged to use the content in ENERGYDATA.INFO to benefit yourself and others in creative ways. The majority of content in ENERGYDATA.INFO is licensed under the Creative Commons Attribution license (CC BY 4.0). Works in ENERGYDATA.INFO that are not subject to the CC BY license are clearly labeled with the specific license terms under which those works may be used. By using ENERGYDATA.INFO, you agree to be bound by these Terms of Use for ENERGYDATA.INFO. Please read the terms before using any content in ENERGYDATA.INFO.

[Retrieved Data from the Wetscapes 1 project. Everything here is from the original author and not form me]

This dataset displays the Open Data intake queue in its raw form. Data here contains attributes relating to how the Toronto Open Data team manages its various requests for updating old and publishing new datasets the Toronto Open Data Portal. Records here are direct from an internal ticket management system, so they match exactly what Open Data staff are working with. Each record is a period of time in which a ticket was in a particular status. The creation of this data is to support council motion 2023.EX10.18 and shared with the hopes that it will inform the public what Open Data is working on, and what datasets Open Data is updating or publishing.

This dataset serves as base information for use in GIS systems for general planning, analytical, and research purposes. It is not intended for engineering work or to legally define FCC licensee data or FCC market boundaries. The material in these data and text files are provided as-is. The FCC disclaims all warranties with regard to the contents of these files, including their fitness. In no event shall the FCC be liable for any special, indirect, or consequential damages whatsoever resulting from loss or use, data or profits, whether in connection with the use or performance of the contents of these files, action of contract, negligence, or other action arising out of, or in connection with the use of the contents of these files. It is know that there are some errors in the licensing information - Latitude, Longitude and Ground Elevation data as well as frequency assignment data from which these files were generated.Caution should be exercised by the user of this feature class. This feature class does not contain fields of attribution for MEDS attributes of ZIP, ZIP+4, TELEPHONE (non-PII general switchboard phone number), and COUNTY FIPS. The following fields are only partially populated with actual values beyond “NOT AVAILABLE” (or blank): QZONE: 1% (this is likely a correct population of the value, but this cannot be adequately determined on the lack of adequate explanation in the metadata), TOWREG: 20%, STRUCTYPE: 84%, NEPA: 61%. LOCADD information is largely directional or locational, rather than an actual address. This layer also includes 11 records that appear to have erroneous locations in the Atlantic Ocean and Pacific Ocean.

The HDX repository, where data providers can upload their raw data spreadsheets for others to find and use. HDX analytics, a database of high-value data that can be compared across countries and crises, with tools for analysis and visualisation. Standards to help share humanitarian data through the use of a consensus Humanitarian Exchange Language. We are designing the HDX system with the following principles in mind: HDX will aggregate data that already exists. We are not working on primary data collection or the creation of new indicators. HDX will provide technical support for (a) sharing any data, and (b) allowing data providers to decide not to share some data for privacy, security or ethical reasons. Read our Terms of Service. As selected high-value data moves from the dataset repository into the curated analytic database, we will take it through a quality-review process to ensure that it is sourced, trusted, and can be combined and compared with data from other sources. HDX will use open-source, open content, and open data as often as possible to reduce costs and in the spirit of transparency. We are using an open-source software called CKAN for the dataset repository. We partner with ScraperWiki for data transformation and operations support. You can find all of our code on GitHub. The plan for 2014 is to create a place where users can easily find humanitarian data and understand the data's source, collection methodology, and license for reuse. We will be working with three countries - Colombia, Kenya(for Eastern Africa) and Yemen - to introduce the platform to partners and to integrate local systems. Our initial public beta will allow users to find and share data through the HDX repository. We will continue to build on this foundation into 2015, eventually adding functionality for data visualization and custom analytics. The HDX project is ambitious, but it presents an excellent opportunity to change the way humanitarians share, access and use data, with positive implications for those who need assistance. We want to ensure that users are at the centre of our design process, so please join the conversation on our blog, follow us on twitter and send us feedback.

% of residents that think CYC/partners are working well to make communities safer *This indicator is discontinued

SELECTED ECONOMIC CHARACTERISTICS OCCUPATION - DP03 Universe - Civilian employed population 16 Year and over Survey-Program - American Community Survey 5-year estimates Years - 2020;2021 Occupation data describe the kind of work the person does on the job. These data are derived from responses to write-in questions that are autocoded and clerically coded by Census Bureau staff, using the Census Occupation Code List developed for Census Bureau household surveys.

% of panel who disagree that to continue working in York will have to retrain

% of panel who agree the council and its partners are helping to create jobs in the city

This data set is no longer maintained. You will find the new data here. See "Total General Job Applications Submitted Online Readme" File Statistics relating to the number of job applications submitted online for on-going recruitment as posted on the web per quarter. The City of Toronto tracks its number of general job applications received and updates this information every quarter on Toronto's Progress Portal. A CSV file can be exported directly through Toronto's Progress Portal.

This data set is no longer maintained. You will find the new data here. See "External Job Postings and Applications Readme" File Statistics relating to the number of external job opportunities published on the City's Internet site and number of applications received from the public. The City of Toronto tracks its number of external job postings and job applications received and updated this information quarterly through Toronto's Progress Portal. A CSV file can be exported directly through Toronto's Progress Portal. The calculation for "Number of Job Applications Received per External Job Posting" is done by dividing the number of external job postings in a month by the number of applications received in that same month.