The ckanext-intro extension is designed as a hands-on tutorial for developers new to creating CKAN extensions. It offers an interactive learning experience, guiding users through the fundamental steps of extension development within the CKAN framework, as showcased during the OKCon 2013 workshop. This extension acts as a practical starting point, directing users towards more detailed official CKAN extension development tutorials for comprehensive learning. Key Features: Step-by-Step Learning: The extension presents a structured, commit-based approach, where each step of the extension-building process is contained within a distinct Git commit. Interactive Exploration: Developers can move between different development stages using Git commands, allowing them to easily review the changes and understand the incremental progress. Practical Introduction: Serves as a quick-start guide to CKAN extension development, enabling new developers to familiarize themselves with the core concepts efficiently. GitHub Integration: Enables users to browse each step of the extension's development directly on GitHub, facilitating easy code review and understanding. Technical Integration: The extension's installation involves the standard process for CKAN extensions, utilizing pip within the activated virtual environment. To activate the fully-built extension, the plugin needs to be added to the CKAN configuration file following the completion of interactive exercises. The Git-based structure provides a clear view on the structural changes required at each development step. Benefits & Impact: The primary benefit of using ckanext-intro is its role in onboarding new developers to the CKAN ecosystem. By providing a guided, hands-on experience, it reduces the initial learning curve associated with extension development. This approach ensures that developers gain practical knowledge and a solid foundation before diving into more complex and comprehensive documentation.

The Development Pipeline bulletin examines how and where the City has been growing over the past five years and how it may continue to develop in the near future. It summarizes information from the City of Toronto’s Land Use Information System II, providing an overview of all projects with any development activity between January 1, 2015 and December 31, 2019. This development pipeline data is supplemented by other data sources such as CMHC, Statistics Canada and the Toronto Employment Survey. For further information refer to the bulletin.

This dataset lists all currently active (open) and inactive (closed) Community Planning applications and Committee of Adjustment applications received by the City between January 1st 2008 till present. For more info, see: Application Information Centre Development Applications - Development Projects

CEGA is a hub for research on global development. Headquartered at the University of California, Berkeley, our large, interdisciplinary network–including a growing number of scholars from low and middle-income countries–identifies and tests innovations designed to reduce poverty and promote development. NLT specializes in providing integrated consulting services, to help organizations achieve and exceed their mission critical objectives. Our broad IT and scientific expertise and partnerships enable us to incorporate best in class technologies and methodologies from across the industry into our solutions for our customers. 3ie funds, produces, quality assures and synthesises rigorous evidence on development effectiveness. We support evaluations and reviews that examine what works, for whom, why and at what cost in low-and middle-income countries. Contribute by proposing a new project or supporting our work.

The Peel River 'without development' model is a hydrological model of the Peel River system that does not represent river system infrastructure, extractions or water management rules. Note: Source software (available from ewater.org.au) is required to view and run the model(s) within. ----------------------------------- Note: If you would like to ask a question, make any suggestions, or tell us how you are using this dataset, please vis

The ckanext-developerpage extension appears to be a CKAN extension designed to provide developers with a dedicated page or set of features within the CKAN platform. Based on the limited information, it likely aims to assist developers in understanding the CKAN environment, potentially offering functionalities like API documentation, code examples, or debugging tools. While specific features are not detailed in the README, the presence of installation and development instructions suggests its purpose involves enhancing the developer experience within CKAN. Key Features (Inferred): Enhanced Developer Environment: Provides a specific area within CKAN tailored for developers, possibly offering resources such as API documentation, code snippets, or debugging tools. Development Installation Support: Simplifies the process of setting up a development environment for CKAN extension or core development. Testing Framework: Provides tools and instructions for running tests related to the extension or CKAN core functionality. Technical Integration: Based on the installation steps, the extension likely integrates with CKAN as a plugin. Activating the virtual environment and adding the plugin name to the ckan.plugins setting in the CKAN configuration file implies a standard CKAN extension integration. Restarting CKAN after these steps suggests that the plugin hooks into CKAN's request handling or templating systems to provide its functionalities. Benefits & Impact (Inferred): Improved Developer Productivity: By providing a centralized location for developer-related resources, the extension can potentially improve developer onboarding and overall productivity when working with CKAN. Simplified Development Workflow: The presence of development installation and testing instructions suggests the extension might include features that streamline the development workflow, making it easier for developers to contribute to or customize CKAN.

This data table provides the detailed data quality assessment scores for the Long Term Development Statement dataset. The quality assessment was carried out on 31st March. At SPEN, we are dedicated to sharing high-quality data with our stakeholders and being transparent about its' quality. This is why we openly share the results of our data quality assessments. We collaborate closely with Data Owners to address any identified issues and enhance our overall data quality; to demonstrate our progress we conduct annual assessments of our data quality in line with the dataset refresh rate. To learn more about our approach to how we assess data quality, visit Data Quality - SP Energy Networks. We welcome feedback and questions from our stakeholders regarding this process. Our Open Data Team is available to answer any enquiries or receive feedback on the assessments. You can contact them via our Open Data mailbox at opendata@spenergynetworks.co.uk.The first phase of our comprehensive data quality assessment measures the quality of our datasets across three dimensions. Please refer to the data table schema for the definitions of these dimensions. We are now in the process of expanding our quality assessments to include additional dimensions to provide a more comprehensive evaluation and will update the data tables with the results when available.

Feature layer showing all the fire perimeters tracked by Cal OES GIS for year to date.Fire information is taken from the National Fire and Aviation Management (FAMWEB) in the form of ICS-209 reports. During normal operations these 209 reports are downloaded once a day at 0630, or soon after. During a SOC activation these 209 reports will be downloaded twice a day at 0630 and 1800. Cal OES GIS considers the FAMWEB ICS-209s as the authoritative fire information source.Fire perimeter data is downloaded from the National Interagency Fire Center (NIFC). The data for map is updated daily, M-F, by 0800, the map text by 0900, when there are active fires being tracked by Cal OES.If the SOC is activated the fire map will be updated daily, Sun-Sat, by 0800, the map text by 0900, until the SOC stands down.For a fire to be tracked by Cal OES GIS it needs to be:>100 acres in sizeHave an ICS-209 form.CalOES GIS indicates a fire as contained when it has reached >=90% containment.

This data table provides the detailed data quality assessment scores for the Network Development Plan dataset. The quality assessment was carried out on 31st March. At SPEN, we are dedicated to sharing high-quality data with our stakeholders and being transparent about its' quality. This is why we openly share the results of our data quality assessments. We collaborate closely with Data Owners to address any identified issues and enhance our overall data quality; to demonstrate our progress we conduct annual assessments of our data quality in line with the dataset refresh rate. To learn more about our approach to how we assess data quality, visit Data Quality - SP Energy Networks. We welcome feedback and questions from our stakeholders regarding this process. Our Open Data Team is available to answer any enquiries or receive feedback on the assessments. You can contact them via our Open Data mailbox at opendata@spenergynetworks.co.uk.The first phase of our comprehensive data quality assessment measures the quality of our datasets across three dimensions. Please refer to the data table schema for the definitions of these dimensions. We are now in the process of expanding our quality assessments to include additional dimensions to provide a more comprehensive evaluation and will update the data tables with the results when available.

A recreation site is a discrete area on a National Forest that provides recreation opportunities, receives recreational use, and requires a management investment to operate and/or maintain to standard under the direction of an administrative unit in the National Forest system. Recreation sites range in development from relatively undeveloped areas, with little to no improvements (Development Scale 0 and 1), to concentrations of facilities and services evidencing a range of amenities and investment (Development Scale 2 through 5). Recreation opportunities are point locations of recreational site activities available to visitors and populates the Forest Service websites and the interactive visitor map. See Metadata

The Rural-Urban Continuum Codes (RUCC), developed by the U.S. Department of Agriculture's Economic Research Service (ERS), classify U.S. counties by their level of urbanization and proximity to metropolitan areas. Counties are categorized as metropolitan or nonmetropolitan, with further divisions based on population size, urbanization level, and adjacency to metro regions. The RUCC provides a detailed framework that supports research and policy analysis in areas such as public health, sociology, regional planning, and economic development. It is widely used for identifying rural-urban disparities and integrates Census data, aligning with Office of Management and Budget (OMB) metro delineations for consistent updates. Its nuanced stratification is particularly valuable in studies like the Alzheimer's Disease Neuroimaging Initiative (ADNI), which explore the social determinants of health.

Lidar was captured of the Westport area by Aerial Surveys in 2020. The dataset was generated by Aerial Surveys and their subcontractors. The survey area includes Westport and the surrounding area and is part of the all-of-West Coast regional lidar survey. Data management and distribution is by Toitu Te Whenua Land Information New Zealand. Co-funding was provided by the Ministry of Business, Innovation and Employment Provincial Development Unit. Prepared DEM and DSM files are available through the LINZ Data Service: Westport, West Coast, New Zealand 2020 Digital Elevation Model Westport, West Coast, New Zealand 2020 Digital Surface Model

The main objective of the project is to make viable the agriculture, the preservation and promotion of the environment and the agricultural areas of Vouga. / O principal objectivo do projecto é viabilizar a agricultura, a preservação e promoção do ambiente e das áreas agrícolas do Vouga.

This dataset provides pertinent information on the delineation of water system pressure districts. The data is updated on a continual daily basis. The data is intended to support development and growth by facilitating pre-application discussions and preparation of servicing reports by Developers (and their teams).

Secondary Plans are more detailed local development policies to guide growth and change in a defined area of the City.

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 2012, the CPUC ordered the development of a statewide map that is designed specifically for the purpose of identifying areas where there is an increased risk for utility associated wildfires. The development of the CPUC -sponsored fire-threat map, herein "CPUC Fire-Threat Map," started in R.08-11-005 and continued in R.15-05-006. A multistep process was used to develop the statewide CPUC Fire-Threat Map. The first step was to develop Fire Map 1 (FM 1), an agnostic map which depicts areas of California where there is an elevated hazard for the ignition and rapid spread of powerline fires due to strong winds, abundant dry vegetation, and other environmental conditions. These are the environmental conditions associated with the catastrophic powerline fires that burned 334 square miles of Southern California in October 2007. FM 1 was developed by CAL FIRE and adopted by the CPUC in Decision 16-05-036.FM 1 served as the foundation for the development of the final CPUC Fire-Threat Map. The CPUC Fire-Threat Map delineates, in part, the boundaries of a new High Fire-Threat District (HFTD) where utility infrastructure and operations will be subject to stricter fire‑safety regulations. Importantly, the CPUC Fire-Threat Map (1) incorporates the fire hazards associated with historical powerline wildfires besides the October 2007 fires in Southern California (e.g., the Butte Fire that burned 71,000 acres in Amador and Calaveras Counties in September 2015), and (2) ranks fire-threat areas based on the risks that utility-associated wildfires pose to people and property. Primary responsibility for the development of the CPUC Fire-Threat Map was delegated to a group of utility mapping experts known as the Peer Development Panel (PDP), with oversight from a team of independent experts known as the Independent Review Team (IRT). The members of the IRT were selected by CAL FIRE and CAL FIRE served as the Chair of the IRT. The development of CPUC Fire-Threat Map includes input from many stakeholders, including investor-owned and publicly owned electric utilities, communications infrastructure providers, public interest groups, and local public safety agencies. The PDP served a draft statewide CPUC Fire-Threat Map on July 31, 2017, which was subsequently reviewed by the IRT. On October 2 and October 5, 2017, the PDP filed an Initial CPUC Fire-Threat Map that reflected the results of the IRT's review through September 25, 2017. The final IRT-approved CPUC Fire-Threat Map was filed on November 17, 2017. On November 21, 2017, SED filed on behalf of the IRT a summary report detailing the production of the CPUC Fire-Threat Map(referenced at the time as Fire Map 2). Interested parties were provided opportunity to submit alternate maps, written comments on the IRT-approved map and alternate maps (if any), and motions for Evidentiary Hearings. No motions for Evidentiary Hearings or alternate map proposals were received. As such, on January 19, 2018 the CPUC adopted, via Safety and Enforcement Division's (SED) disposition of a Tier 1 Advice Letter, the final CPUC Fire-Threat Map.Additional information can be found here.

The dataset comprises a set of images that includes different man-made objects considered critical in underwater operations. Anchors, buoy, chain, flutuation module, 3D marker, mine and pipeline were selected to represent some common objects that are presented in water scenarios. The data were acquired with a monocular camera in diverse conditions of the luminosity and perspectives of the objects. Moreover, the objects were captured in pure and turbid water and with white and coral reef background, to simulate real environments. Nowadays, the online available datasets are incomplete for this type scenarios and so, datasets as the UWObjects@CRAS are important to validate new perspectives and to answer to challenges, because to allow the development and validation of systems able to object identification, manipulation and obstacle avoidance, for example.

Data from a number of sources is used for the development and ongoing maintenance of the MajorRoads feature class. Source data includes SanGIS Roads_All, Caltrans State Highway Centerlines, and street centerline data from the County of Imperial. Regional aerial imagery (1'/pixel resolution or better) is generally used as a guide for delineating roadway alignments, primarily using heads up digitizing methods, using ArcGIS desktop software.

This dataset contains data relating to the Human Development Index, and articles written around this topic by the Africa Data Hub Team.