The ckanext-dadosgovbr extension is designed to customize CKAN for use as the Open Data Portal of the Brazilian Federal Government (Portal de Dados Abertos do Governo Federal). It provides specific theming and functionality tailored to the needs of this portal. The extension supports CKAN versions 2.5.x and 2.6.x, and integrates with ckanext-scheming to enable custom dataset types. Key Features: Portal Theme: Implements a specific theme to align the CKAN instance with the visual identity of the Brazilian Federal Government's Open Data Portal. This provides a consistent and recognizable user experience. Featured Datasets: Requires a group with the name "dados-em-destaque" to highlight featured datasets, allowing for curated content presentation on the portal. Custom Dataset Types (via ckanext-scheming): Supports custom dataset types like "Inventário" (Inventory), "Concurso" (Contest), and "Aplicativo" (Application) by integrating with the ckanext-scheming and ckanext-dadosgovbrschema extensions. WordPress Integration: Enables integration with WordPress (version 4.7 or higher) via the WP-API/rest-filter plugin, to allow external content to be pulled, displayed or managed. ckanext-dadosgovbrschema Integration: Requires ckanext-dadosgovbrschema to support new packages types. Technical Integration: The extension integrates with CKAN through plugins that are added to the CKAN configuration file (development.ini). Configuration requires enabling the plugin, installing dependencies, and potentially configuring WordPress integration by adding specific lines to the development.ini file. To take advantage of custom dataset types, using ckanext-scheming is important to allow for dataset types created by dados.gov.br. Note that ckanext-dadosgovbrschema required to apply the schema. Benefits & Impact: Implementing the ckanext-dadosgovbr extension ensures that a CKAN instance can be used effectively as the Brazilian Federal Government's Open Data Portal. Through a branded theme, support for featured datasets, and custom dataset types, the extension caters to the specific needs of the portal. By supporting datasets like "concurso" and "aplicativo," for instance, the extension also broadens the data available in the portal to a wider diversity of areas.

Services that support students’ capacity to pursue educational and training programs, including academic counselling, tutoring, bridging programs, and financial support. Taxonomoy-based search of 211Toronto's database. For additional information and for the latest version of this data, please contact Findhelp/211 at info@findhelp.ca.

The combination of probability theory and scenario planning with multi-attribute utility theory, with adaptations and extensions of these theories, to capture societal objectives and improve their application for supporting environmental decision making applied to river management.

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

The ckanext-asc-csa extension for CKAN is designed to implement a Government of Canada theme, transforming a standard CKAN instance into a bilingual and accessible data portal. This improves the user experience and facilitates governmental data publication according to specific accessibility and presentation guidelines. The extension enriches CKAN's core functionalities by catering to the specific needs for Canadian governmental data dissemination. Key Features: Government of Canada Theme Implementation: Applies a visual theme consistent with the Government of Canada's branding guidelines, providing a familiar and trusted interface for users. Bilingual Support: Enables a fully bilingual (English/French) interface, catering to Canada's official languages and supporting broader accessibility for Canadian users. Enhanced Accessibility: Improves accessibility features within the CKAN instance, ensuring compliance with accessibility standards and guidelines. This likely includes improvements to ARIA attributes, keyboard navigation, and contrast ratios. In-Browser Data Visualization: Provides tools or integrations for visualizing data directly within the web browser, potentially through integration with charting libraries or data visualization plugins. Technical Integration: The extension builds upon CKAN's plugin architecture, modifying the user interface and potentially adding new functionalities through plugins. Crucially, it requires the companion extensions ckanext-asc-csa-scheming and ckanext-fluent. ckanext-asc-csa-scheming likely deals with dataset schema customizations to align with governmental standards, and ckanext-fluent probably manages the bilingual aspects of the portal. The extension is explicitly intended for CKAN 2.9, ensuring compatibility and leveraging the features of that version. Earlier versions (0.1-0.4) supported CKAN 2.8, indicating a history of updates to maintain compatibility. Benefits & Impact: By implementing the ckanext-asc-csa extension, organizations can rapidly deploy a CKAN instance that meets the Government of Canada's specific requirements for data publication. The bilingual and accessible theme promotes inclusivity and user satisfaction, while the in-browser data visualization capabilities empower users to explore and understand data more easily. The required use of ckanext-asc-csa-scheming ensures that published datasets adhere to prescribed schemas and metadata standards, facilitating data interoperability and reusability across the Canadian governmental data ecosystem.

The dataset represents Emergency Medical Services (EMS) locations in the United States and its territories. EMS Stations are part of the Fire Stations / EMS Stations HSIP Freedom sub-layer, which in turn is part of the Emergency Services and Continuity of Government Sector, which is itself a part of the Critical Infrastructure Category. The EMS stations dataset consists of any location where emergency medical service (EMS) personnel are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Ambulance services are included even if they only provide transportation services, but not if they are located at, and operated by, a hospital. If an independent ambulance service or EMS provider happens to be collocated with a hospital, it will be included in this dataset. The dataset includes both private and governmental entities. A concerted effort was made to include all emergency medical service locations in the United States and its territories. This dataset is comprised completely of license free data. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based upon this field, the oldest record dates from 12/29/2004 and the newest record dates from 01/11/2010.This dataset represents the EMS stations of any location where emergency medical service (EMS) personnel are stationed or based out of, or where equipment that such personnel use in carrying out their jobs is stored for ready use. Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1. An assessment of whether or not the total emergency medical services capability in a given area is adequate. 2. A list of resources to draw upon by surrounding areas when local resources have temporarily been overwhelmed by a disaster - route analysis can determine those entities that are able to respond the quickest. 3. A resource for Emergency Management planning purposes. 4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster. 5. A resource for situational awareness planning and response for Federal Government events.

Programs and resources to assist youth in accessing or upholding their rights, including services for youth involved with the justice system. Includes general information, advocacy, diversion, reintegration, and mental health and justice services. Taxonomoy-based search of 211Toronto's database. For additional information and for the latest version of this data, please contact Findhelp/211 at info@findhelp.ca.

Welcome to the NHS Business Services Authority’s (NHSBSA) Open Data Portal, the home of all our open data. All of our data is released under the Open Government License and is free for use and re-use. We want to put users at the heart of what we do. You can see what we’re working on at the minute on our Open Data Roadmap that is hosted on our GitHub. You can help shape what we do next by giving us feedback on our roadmap and making suggestions for what data sets you would like see published or expanded on. The Open Data Portal is powered by CKAN - an open source data management system. You can see the code that has been created to help support this implementation of CKAN in a series of public GitHub repositories:

A current list of all FamilySource Centers within the City of Los Angeles. FamilySource Centers (FSC) are a one-stop shop in your neighborhood for social, educational, work, and family support services. With 19 locations established in the City of Los Angeles, we can help you find the resources to increase your family income, establish financial security, and build academic success.

Other community services offering legal/paralegal support and advocacy. Taxonomoy-based search of 211Toronto's database. For additional information and for the latest version of this data, please contact Findhelp/211 at info@findhelp.ca.

To address Toronto's 2012 budget gap of $774 million, City Council launched a review of all of its services and implemented a multi-year financial planning process. This data set contains the responses to the open-ended questions on the Services Review Public Consultation Feedback Form from members of the public. Approximately 13,000 responses were received (full and partial). The consultation was held between May 11 and June 17, 2011. As a public consultation, respondents chose to participate, and chose which questions to answer. This produced a self-selected sample of respondents. The majority of the responses were from City of Toronto residents. There were some responses from GTA residents. City staff reviewed the data and removed personal information and input violating city policies (for example, contravenes the City's current anti-discrimination policy or confidentiality policy).

Spesifikaatio määrittelee useita eri näkökulmia, joiden pitäisi olla yhteisiä useille tai kaikille OGC:n määrittelemille verkkopalveluille. This document specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Standards. The common Implementation Specification aspects specified by this document currently include: a) Operation request and response contents, most partial b) Parameters and data structures included in operation requests and responses c) XML and KVP encoding of operation requests and responses (07.03.2013)

The datitrentinoit extension for CKAN provides customizations tailored specifically for the dati.trentino.it platform. This extension aims to enhance the CKAN installation with region-specific features and functionalities. While the provided documentation is limited, it suggests the extension focuses on adapting CKAN to the unique requirements and context of the dati.trentino.it open data portal. Key Features: Customizations for dati.trentino.it: The primary function is providing alterations and adjustments to the core CKAN system to align with the specific needs of the dati.trentino.it platform. Translation Support: Implements or enhances translation capabilities within the datitrentinoit CKAN installation, enabling localized support via babel and jinja. Translation Management: Includes the ability to extract messages, initialize catalogs, update catalogs, and compile catalogs, which are standard tasks in internationalizing software projects. Technical Integration: The extension is installed as a standard CKAN plugin by including datitrentinoit in the CKAN plugins configuration. This integration point allows the extension to modify CKAN's behavior and appearance to match the dati.trentino.it requirements. It likely involves changes to templates, controllers, or models within CKAN. The readme mentions the project has solved issues with translations, suggesting a deep integration within CKAN’s translation system. Benefits & Impact: The datitrentinoit extension provides a more tailored and user-friendly experience for users of the dati.trentino.it portal. By customizing CKAN, it ensures that the open data platform meets the specific requirements of the Trentino region. Furthermore enhanced translation support also improves accessibility by catering to a multilingual audience.

The EarthScope Consortium streams three-dimensional GNSS high rate (1Hz) position time series from nearly a thousand GNSS stations to study earthquakes, volcanos, tsunamis, hydrologic loads, and glaciers. The data is made available via the National Data Platform pilot project.

This data set is retired. A new data set replaces at: 311 Service Requests - Customer Initiated

The EarthScope Consortium streams three-dimensional GNSS high rate (1Hz) position time series from nearly a thousand GNSS stations to study earthquakes, volcanos, tsunamis, hydrologic loads, and glaciers. The data is made available via the National Data Platform pilot project.

The dataset is an .xls file that combines the bibliographic information selected to Identify global studies on DMP support in different institutions and understand how institutions provide, implement, and organize DMP support for researchers. The search was conducted on 14 May 2022 in the Scopus Database, and the dataset contains DMP related bibliography, collected with the following criteria: Application of inclusion; Application of exclusion; Addition of other sources, Application of exclusion criteria to other sources, Dimensions of analysis. This dataset is one of the outputs of the PhD thesis "Research data description in multiple domains: supporting researchers with Data Management Plans", financed by National Funds through the Portuguese funding agency, FCT (Fundação para a Ciência e a Tecnologia) - SFRH/BD/136332/2018, defended by Karimova Yulia on the X of X, 2023, published on X, and cited as: Karimova, Y. "Research data description in multiple domains: supporting researchers with Data Management Plans", PhD thesis, URL: XX. Namely, this dataset includes data related to the systematic review described in Chapter 4 of the thesis.

Picture of macroalgae on hard support (stones of the dam from Sarichioi) in Lake Razim (Razelm) (Danube Delta Biosphere Reserve, Romania).

This tool is designed to assist decision-makers in understanding the benefits of ponds for biodiversity and climate change adaptation/mitigation, helping them to understand the benefits of increasing the presence of ponds in their regions. Developed as part of the EU Horizon 2020 project, PONDERFUL, (2020-2024) the tool explores the role of ponds and pond landscapes (pondscapes) as Nature-Based Solutions (NBS) for adressing societal challenges linked to climate changes. It enables decision-makers to evaluate selected NBS strategies (pond creation and water quality management), assessing their impacts on a set of Nature's Contributions to People (NCP) indicators (aquatic biodiversity (amphibians, plants, macroinvertebrates), emissions of GHG, water quantity, water quality). Additionally, the tool allows for scenario analysis, evaluating outcomes under different climate change and land use projections for 2050.

HSIP Local Emergency Operations Centers in the United States "The physical location at which the coordination of information and resources to support domestic incident management activities normally takes place. An Emergency Operations Center may be a temporary facility or may be located in a more central or permanently established facility, perhaps at a higher level of organization within a jurisdiction. Emergency Operations Centers may be organized by major functional disciplines (e.g., fire, law enforcement, and medical services), by jurisdiction (e.g., Federal, State, regional, county, city, tribal), or some combination thereof." (Excerpted from the National Incident Management System) The GFI source for this layer contains State and Federal Emergency Operations Centers in addition to local Emergency Operations Centers. This dataset contains these features as well. In cases where an Emergency Operations Center has a mobile unit, TechniGraphics captured the location of the mobile unit as a separate record. This record represents where the mobile unit is stored. If this location could not be verified, a point was placed in the approximate center of the Emergency Operations Centers service area. Effort was made by TechniGraphics to verify whether or not each Emergency Operations Center has a generator on-site and whether or not the Emergency Operations Center is located in a basement. This information is indicated by the values in the [GENERATOR] and [BASEMENT] fields respectively. In cases where more than one record existed for a geographical area (e.g., county, city), TechniGraphics verified whether or not one of the records represented an alternate location. This was indicated by appending "-ALTERNATE" to the value in the [NAME] field. Some Emergency Operations Centers are located at private residences. The [TYPE] field was manually evaluated during the delivery process to compare the records in which the [NAME] field contained "-ALTERNATE". In cases where these values contradicted information that was verified by TechniGraphics (e.g. [NAME] contained "-ALTERNATE" and [TYPE] = "PRIMARY"), the value in the [TYPE] field was changed to match the type indicated by the [NAME] of the verified record. TechniGraphics did not change values in this field if the type was not verified. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard HSIP fields that TechniGraphics populated. Double spaces were replaced by single spaces in these same fields. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, all diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based upon this attribute, the oldest record dates from 08/28/2009 and the newest record dates from 11/18/2009.Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1. A resource for preparing, mitigating, responding to and recovering from an emergency. 2. A list of resources to draw upon by surrounding areas when local resources have temporarily been overwhelmed by a disaster. 3. A resource for Emergency Management planning purposes. 4. A resource for catastrophe response to aid in the retrieval of equipment by outside responders in order to deal with the disaster. 5. A resource for situational awareness planning and response for Federal Government events.