This dataset provides pertinent information on the general location of sewer system maintenance holes and the classification by flow medium in the connected sewer. 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).

The Files extension enhances CKAN by treating files as primary objects within the system. It provides the capability to upload, manage, and remove files directly through CKAN, then associate them with datasets and resources. This file-centric approach offers a streamlined method to handle file attachments and ensure their proper management within the CKAN environment. Key Features: Direct File Upload: Enables users to upload files directly to CKAN, simplifying the process of attaching data or related documents. File Management: Provides tools for managing uploaded files, potentially including functionalities for renaming, moving, or updating files. File Removal: Offers mechanisms to remove files from CKAN, allowing for proper maintenance and cleanup of the file repository. Association with Datasets and Resources: Facilitates the linking of uploaded files to specific datasets or resources within CKAN, creating contextual relationships between data and associated files. Integration with CKAN: The extension integrates with CKAN by adding a plugin, as indicated by the requirement to add "files" to the ckan.plugins setting in the CKAN configuration file. This suggests an extension of CKAN's core functionality, adding new features for file management and association. The extension also necessitates running DB migrations, indicating it might introduce new database tables or modify existing schemas to store file-related metadata. Benefits & Impact: By enabling direct file management within CKAN, the Files extension offers a more convenient and organized approach to handling supplementary data. This can lead to better data discoverability, improved resource organization. The file management capabilities reduce management overhead, and associating files with datasets can enrich both sets of data resulting in greater data utility.

The ckanext-project extension enhances the CKAN platform to meet the specific needs of Cadasta by providing specialized workflows, APIs, permissions, and user interfaces. It facilitates the management of organizations and projects within the CKAN ecosystem, integrating with a separate Cadasta API and database to handle parcel data, relationships, survey responses, and geometries. This extension streamlines data management processes critical for Cadasta's operations. Key Features: Extended Roles/Permissions (cadastaroles plugin): Introduces custom roles and permissions tailored for the Cadasta application, enhancing access control within CKAN. It also includes a "pass-through" API, potentially for interacting with the Cadasta API. Organization Management (organization plugin): Provides a structured workflow for creating, editing, and deleting organizations within CKAN, simplifying organizational data management. Project Management (project plugin): Enables the creation, editing, and deletion of projects, providing a dedicated workflow for managing project-related information within CKAN. Angular.js Dashboards: Incorporates static resources for Angular.js applications, offering enhanced user interfaces for managing projects and organizations in ways that exceed the default CKAN interface. They likely provide a more interactive and visually driven experience tailored to Cadasta's needs. Cadasta API Integration: Designed to work in conjunction with a separate Cadasta API and database, allowing the extension to manage data specific to Cadasta, such as parcels, relationships, survey responses, and geometries. Deployment Automation: Provides a bash script to help automate the update and redeployment of various application components, indicating a focus on streamlining the maintenance and deployment process. CKAN API Wrappers: Includes documentation detailing the mapping between CKAN endpoints and Cadasta API endpoints, providing clarity and facilitating integration between the two systems. Technical Integration: The ckanext-project extension integrates with CKAN through plugins, enhancing the platform with custom roles, workflows, and APIs. It requires installation and configuration within a CKAN environment, and it’s explicitly designed to work with a separate Cadasta API and database. The extension also includes static resources that use CKAN's theming/extension mechanisms to serve Angular.js code for custom dashboards. Benefits & Impact: Implementing the ckanext-project extension allows CKAN to be specifically tailored to the Cadasta application's needs, streamlining workflows for managing organizations and projects, and enhancing data handling capabilities. By integrating with the Cadasta API, the extension enables a richer, more specialized data management environment. The automated deployment script simplifies maintenance, and the API wrappers documentation aids in understanding the integration between CKAN and the Cadasta API, allowing for improved efficiency and more seamless operation.

The Datapusherext extension is specifically designed for CKAN 2.1 instances, providing functionality to interact with the Datapusher service. Datapusher is a separate application used to push data from CKAN resources into data stores like relational databases, thus making resource data more accessible. This extension acts as a bridge, enabling users of CKAN 2.1 to leverage the Datapusher's capabilities. Key Features: Datapusher Integration for CKAN 2.1: Enables seamless integration with the Datapusher service from within CKAN 2.1, a feature that is natively available in later CKAN versions (2.2+). Configuration via CKAN Settings: Allows administrators to configure the Datapusher URL directly within the CKAN configuration file, simplifying the setup process. Data Pushing: Provides the ability to push data from CKAN resources to external data stores, enhancing the usability and accessibility of the data. Technical Integration: This extension integrates with CKAN by introducing the necessary components and configuration options (specifically ckan.datapusher.url) to communicate with the Datapusher service. It acts as an intermediary, relaying requests and managing the data transfer process between CKAN resources and the specified Datapusher instance. Setting the correct URL in the CKAN configuration is critical for the extension to function correctly. Benefits & Impact: By implementing the Datapusherext extension, CKAN 2.1 users can effectively transfer data from their CKAN resources into dedicated data stores. This facilitates more efficient data analysis, reporting, and integration with other systems. It bridges a functionality gap present in CKAN 2.1, allowing users to take advantage of the Datapusher's capabilities without upgrading to a newer CKAN version where this functionality is built-in.

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 maintenance plan shows, indicatively, the intervention sites distributed in the years 2007, 2008 and 2009.

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 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.

The statictheme extension for CKAN provides a mechanism for customizing the visual appearance of a CKAN instance using static HTML and CSS. It allows for modifications to the default CKAN templates, enabling organizations to implement their own branding and design elements. According to the Readme, it was specifically developed and used for the NFDI4Chem CKAN instance. Key Features: HTML/CSS Customization: Enables modification of CKAN's HTML structure and CSS stylesheets, allowing for complete control over the visual design. This is crucial for aligning CKAN with an organization's branding guidelines. Template Override: Facilitates overriding the default CKAN templates, enabling the insertion of custom HTML elements and layouts. This allows for more sophisticated design modifications beyond simple CSS changes. NFDI4Chem Specific: The theme has been specifically tested to meet the specific requirements of NFDI4Chem. CKAN 2.9 Compatibility: Explicitly tested and confirmed to be compatible with CKAN version 2.9. Compatibility with other versions has not been tested. Simple Installation: The installation process consists of activating the CKAN virtual environment, cloning the source code, installing the extension, adding 'statictheme' to the ckan.plugins setting, and restarting CKAN. Use Cases: Branding and Customization: Implementing organization-specific branding into a CKAN instance, ensuring a seamless user experience. Allows organizations to tailor the appearance of their CKAN platform to match their brand identity. Visual Overhaul: Overriding templates allows for a comprehensive visual overhaul of the CKAN interface, enabling organizations to create custom layouts and UI elements. This may include significant modifications to navigation, data display, and overall appearance. NFDI4Chem Implementation: Custom theme and HTML/CSS changes as per requirements by NFDI4Chem. Technical Integration: The statictheme extension integrates with CKAN through CKAN's plugin mechanism. By adding statictheme to the ckan.plugins setting in the CKAN configuration file (/etc/ckan/default/ckan.ini by default). No specific configuration settings are mentioned in the provided readme. Benefits & Impact: This extension enhances the presentational aspects of CKAN, permitting organizations to deliver branded and user-friendly data portals. By customizing the HTML and CSS, 'statictheme' improves user engagement and can contribute to higher adoption rates of the CKAN platform due to a better visual experience. The extension can also reduce maintenance costs by centralizing visual changes within the extension rather than implementing them directly into core CKAN files.

IDBLAB CKAN Service

The National Incident Feature Service (NIFS) is based on the National Wildfire Coordinating Group (NWCG) data standard for Wildland Fire Event. The Wildland Fire Event data standard defines the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting GIS Standard Operating Procedures on Incidents (GSTOP). The intent of this standard is to update existing data formats and provide a common set of attributes for use on wildland fires starting fire season 2016.

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.

To address Toronto's 2012 budget gap of $774 million, City Council has launched a review of all of its services and implemented a multi-year financial planning process. This data set contains the responses to the multiple- choice questions on the Core 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). The .SAV file may be viewed with Statistics software such as SPSS or SAS.

The statistics contained in this dataset were included in the Annual Human Rights Office Report for the Executive Committee and City Council. The full report is available on the City's Web site at http://app.toronto.ca/tmmis/index.do

This data is a graphic representation of natural gas utility service territories. The file has not been certified by a Professional Surveyor. This data is not suitable for legal purposes. The purpose of this data is to provide a generalized statewide view of electric service territories. The data does not include individual or commercial releases. A release is an agreement between adjoining utilities that release customers from one utility to be served by the adjoining utility. A customer release does not change the territory boundary. The file has been compiled from numerous sources and as such contains errors. The data only contains the electric utility service territories and the name of the utility.The data was derived from ESRI zipcode boundary and utility companies.California Energy Commission's Open Data Portal.

This feature service represents CAL FIRE's 21 operational units, that are designed to address fire suppression over a certain geographic area. Each unit operates within their local jurisdiction and strives to fulfill the department's mission whether it be responding to all-risk emergencies, participating in fire safety education and educating homeowners on how to keep their property fire safe.In addition, CAL FIRE provides funding to six 'Contract Counties' (Kern, Los Angeles, Marin, Orange, Santa Barbara and Ventura) for fire protection services, including wages of suppression crews, lookouts, maintenance of fire fighting facilities, fire prevention assistants, pre-fire management positions, dispatch, special repairs, and administrative services. The Department's budget also provides for infrastructure improvements, and expanded fire fighting needs when fires grow beyond initial attack.Contract Counties are responsible for providing initial response to fires on SRA. When a wildland fire escapes this initial attack, CAL FIRE responds with fire fighting resources to assist the county.This service represents the latest official version of the CAL FIRE Administrative Units dataset, and is updated whenever a new version is released. As of June, 2019 it represents cdfadmin19_1. Source data is available here.

This is an export of the data archived from the 2018 National Incident Feature Service.Sensitive fields and features have been removed.Each edit to a feature is captured in the Archive. The GDB_FROM and GDB_TO fields show the date range that the feature existed in the National Incident Feature Service.The National Incident Feature Service is based on the National Wildfire Coordinating Group (NWCG) data standard for Wildland Fire Event. The Wildland Fire Event data standard defines the minimum attributes necessary for collection, storage and dissemination of incident based data on wildland fires (wildfires and prescribed fires). The standard is not intended for long term data storage, rather a standard to assist in the creation of incident based data management tools, minimum standards for data exchange, and to assist users in meeting the NWCG Standards for Geospatial Operations (PMS 936).

This dataset includes the following categories of data: Languages, Calls Received, and Alarm Calls General Qualifiers Numbers provided represent calls received at Communications via 9-1-1 or the nonemergency number that used Language Line Services All Administrative, Field Administrative Events, Duplicate, Cancel, Filed Events are excluded. Download the ASR Documentation.

The (annual) maintenance report contains an overview of the specific payments, how much money is spent on them and what the expected developments are.

Predictive Service Areas (PSAs) are geographic areas for which national-level fire weather or fire danger services and products are produced by wildland fire agency meteorologists and intelligence staffs in support of resource allocation and prioritization. A PSA boundary defines areas where 2 or more weather elements or National Fire Danger Rating System (NFDRS) indices exist with a high correlation to historical significant fire size. "Significant fires" are the 95th percentile fire size for the PSA. 1/9/2023 - Spatial and tabular changes made at request of Basil Newmerzhycky (Great Basin), and Gina McGuire (Fire Meterologist). PSA boundaries between Great Basin (GB14) and Northern California (NC08) GACCs aligned to follow GACC boundary in area of East Fork High Rock Canyon Wilderness and Grassy Canyon. Edits by JKuenzi. 8/29/2022 - 8/30/2022 - Spatial and tabular changes made at request of Southern Area GACC (submitted by Dana "Nancy" Ellsworth and Subject Matter Experts). Edits by JKuenzi. Specific changes include:Puerto Rico changed from 6 PSAs to 1 PSA. PSAName changed to PR for all areas. PSANationalCode changed to "SA52A" for all areas. PSANames and PSANationalCodes = "PR Northwest (number SA52A remains active), PR Southwest (SA52B), PR North (SA53), PR Central (SA54), PR South (SA55), and PR East (SA56)" were all removed. Florida changed from 10 PSAs to 4 PSAs. PSANames and PSANationalCodes = "FL North Coast (SA44), FL Northeast (SA45A), FL Northeast Coast (SA45B), FL Pan (SA43), FL SE Coast (SA51B), and FL SW Coast (SA51A)" were all removed. Remaining PSAs realigned using linework by AHepworth, and authoritative datasets (Census Counties, and PADUS Modified Jurisdictional Boundaries) to cover all of Florida. Louisiana changed PSAName from "MS South" to "LA East" where PSANationalCode = "SA22B" .1/12/2022 - Spatial and tabular changes made while assigning PSAs to islands and merging a handful of small slivers with larger areas Islands identified by Geographic Area Coordination Center (GACC) PSA representatives, Heidi Strader, Julia Rutherford, Dana "Nancy" Ellsworth, and Matt Shameson. Edits by JKuenzi.1/10/2022 - Spatial and tabular changes made as part of the request to replace all PSAs in the Rocky Mountain Geographic Area Coordination Center (GACC) by Valerie Meyers and Coleen Haskell, both Predictive Services Fire Weather Meteorologists. The total number of PSAs within the Rocky Mountain area went from 74 to 28. Along with new linework, PSAs were re-numbered and named. Topology was used to find and remove gaps and overlaps.Edits by JKuenzi.10/29/2021 - Spatial changes made. Coastlines matched to other base data layers including: Geographic Area Coordination Centers (GACCs), Dispatch Areas, and Initial Attach Frequency Zones. Process completed with approval from the PSA representatives in each GACC, in order to begin process of vertical integration of PSA data, where appropriate, with other wildland fire base data layers. No interior lines moved except along coast. A few island areas were not specifically labeled with a PSA and have been assigned a PSANationalCode = "None" and "PSAName = "No PSA Assigned". Edits by JKuenzi, 10/25/2021 - Spatial and tabular changes made resulting from proposed change between Southwest and Southern Geographic Area Coordination Centers (GACCs) for use starting 1/10/2022. Seven Predictive Service Areas re-aligned boundaries as described by Charles Maxwell (USFS) Predictive Services Meteorologist, in conjunction with Rich Naden (NPS), Basil Newmerzhycky (BLM), Dana Ellsworth (USFS), and Calvin Miller (USFS). Edits by JKuenzi, USFS. Specific changes made include:SW13 - split at Texas/New Mexico state line. Area in NM remains SW13. Area in TX/OK becomes SA01.SW14N - split at Texas/New Mexico state line. Area in NM remains SW14N. Area in TX is split into SA04 and SA09SW14S - split at Texas/New Mexico state line. Area in NM absorbed by SW14N. Area in TX is split into SA09 and SA08 along county lines.SW09 - split at Texas/New Mexico state line. Area in NM remains SW09 or is absorbed by SW12. Area in TX is absorbed by SA08. SW12 - absorbs sliver of SW09 along TX/NM border and the Guadalupe Mtns in TX. 10/20/2021-10/21/2021 - Spatial and tabular changes made while completing topology checks for overlaps and gaps. Over 3400 errors found, but most were because of islands. 1367 errors remain, but are all marked as exceptions. Only major changes, such as complete deletion and re-creation of polygons were noted in the Comments or DateCurrent field. Edits by JKuenzi, USFS. 2/3/2021 - Tabular change made in Alaska to the peninsula where the St. Michael Airport is located. PSA National Code changed from AK14 to AK08 per Nicholas Nauslar, BLM, and Heidi Strader, Fire Weather Program Mgr at Alaska Interagency Coordination Center. Edits by JKuenzi, USFS. 6/20/2020 - PSA dataset attribute table brought into alignment with NWCG Data Standards for Predictive Service Areas. Edits by JKuenzi, USFS.8/3/2019 - Great Basin updated. Edits by DSampson, BLM.