No description found

This dataset tracks the updates made on the dataset "MeSH 2023 Update - Merge Report" as a repository for previous versions of the data and metadata.

This dataset is no longer updated regularly. Last update was on 6/29/23. For additional information contact MHDepi@minneapolismn.gov. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.

The machine-rate methodology provides a basis for estimating the total hourly costs to own and operate logging equipment and comprises fixed, variable, and labor costs. The calculations form a simple approach to estimate machine costs and evaluate new machine alternatives consistently. The methodology has been used extensively since its development in 1942 with periodic updates. The machine-rate method has been widely cited and is regularly used by researchers, logging contractors, harvest managers, and procurement foresters. Since the last update in 2002, machine manufacturers, purchase prices, operating costs, and data sources have changed significantly. Therefore, the objective of this study was to update and modernize the methodology using current machinery, assumptions, and inputs to improve its accuracy and usability. Machine-rate inputs including interest rates, purchase prices, economic life, repair and maintenance, fuel consumption, and lubrication cost were collected for 123 unique machines from whole-tree and cut-to-length equipment dealers in the southeastern United States. In addition, empirical data were used to provide estimates for variables that previously relied on rules of thumb. Finally, guidance was provided to enable users to update assumptions with publicly available information. Prospective users can view and download the updated costing approach spreadsheet in the Supplementary Material linked to this article online.

Updates to Website: (Please add new items at the top of this description with the date of the website change) May 9, 2012: Uploaded experimental data in matlab format for HIRENASD November 8, 2011: New grids, experimental data for HIRENASD configuration, new FEM for HIRENASD configuration. (JHeeg) Oct 13: Uploaded BSCW grids (VGRID) (PChwalowski) Oct 5: Added HIRENASD experimental data for test points #159 and #132 (JHeeg, PChwalowski)

Groundwater withdrawal estimates for 1913-2016 for the Death Valley regional groundwater flow system (DVRFS) are compiled in this Microsoft® Access database to support a regional, three-dimensional, transient groundwater flow model (Belcher and others, 2017; Halford and Jackson, 2020). This database (version 2) updates previously published databases that compiled estimates of groundwater withdrawals for 1913-1998 (Moreo and others, 2003), 1913-2003 (Moreo and Justet, 2008), and 1913-2010 (Elliott and Moreo, 2018; version 1 of this data release). Version 2 of this data release is the most current version of the database and supersedes all previous versions. A total of about 41,000 acre-ft of groundwater were withdrawn from DVRFS in 2016 of which 51 percent was used for irrigation, 20 percent for domestic, and 27 percent for public supply, commercial, and mining activities. The total groundwater withdrawals for Pahrump Valley (hydrographic area 162) increased from 17,000 acre-ft in ...

This file includes data pertaining to Additions to Properties. The "ParcelNumber" field can be joined to the "ParcelNumber" field in the "Parcel Area Details" data set for mapping purposes (current parcels only). This data set is updated on a daily basis and reflects the Real Estate system as of the previous business day.

Note: Active and Retired parcels are included in this data set so joining this data set to the data sets: ‘Real Estate (Base Active)’ or ‘Parcel Area Details’ will not result in all parcels matching since ‘Real Estate (Base Active)’ and ‘Parcel Area Details’ only contain currently active parcels.

[Update 04/16/2018]: We are still developing the automation for the new dataset. We do not have an updated publishing date at the moment. We have a target schema and have provided a crosswalk document attached to the existing dataset in advance of the changes. We will update this document if there's new information to share.

[Change Notice 03/13/2018]: By the end of this month, this dataset will become historical and a new one will be created starting with incident data in 2018. This one will remain here, but no longer be updated. The new one will have data coming from a new system, will not have a 2 week lag, and have updated districts among other quality improvements. We will attach a guide here with more detailed change updates as soon as we have them.

+++++++++

As of July 19, 2015, the PD District boundaries have been updated through a redistricting process. These new boundaries are not reflected in the dataset yet so you cannot compare data from July 19, 2015 onward to official reports from PD with the Police District column. We are working on an update to the dataset to reflect the updated boundaries starting with data entered July 19 onward.

Incidents derived from SFPD Crime Incident Reporting system Updated daily, showing data from 1/1/2003 up until two weeks ago from current date. Please note: San Francisco police have implemented a new system for tracking crime. The dataset included here is still coming from the old system, which is in the process of being retired (a multi-year process). Data included here is no longer the official SFPD data.

The anion data for the East River Watershed, Colorado, consists of fluoride, chloride, sulfate, nitrate, and phosphate concentrations collected at multiple, long-term monitoring sites that include stream, groundwater, and spring sampling locations. These locations represent important and/or unique end-member locations for which solute concentrations can be diagnostic of the connection between terrestrial and aquatic systems. Such locations include drainages underlined entirely or largely by shale bedrock, land covered dominated by conifers, aspens, or meadows, and drainages impacted by historic mining activity and the presence of naturally mineralized rock. Developing a long-term record of solute concentrations from a diversity of environments is a critical component of quantifying the impacts of both climate change and discrete climate perturbations, such as drought, forest mortality, and wildfire, on the riverine export of multiple anionic species. Such data may be combined with stream gauging stations co-located at each monitoring site to directly quantify the seasonal and annual mass flux of these anionic species out of the watershed. This data package contains (1) a zip file (anion_data_2014-2024.zip) containing a total of 381 files: 380 data files of anion data from across the Lawrence Berkeley National Laboratory (LBNL) Watershed Function Scientific Focus Area (SFA) which is reported in .csv files per location and a locations.csv (1 file) with latitude and longitude for each location; (2) a file-level metadata (v6_20250515_flmd.csv) file that lists each file contained in the dataset with associated metadata; and (3) a data dictionary (v6_20250515_dd.csv) file that contains terms/column_headers used throughout the files along with a definition, units, and data type. Missing values within the anion data files are noted as either "-9999" or "0.0" for not detectable (N.D.) data. There are a total of 46 locations containing anion data.Update on 2022-06-10: versioned updates to this dataset was made along with these changes: (1) updated anion data for all locations up to 2021-12-31, (2) removal of units from column headers in datafiles, (3) added row underneath headers to contain units of variables, (4) restructure of units to comply with CSV reporting format requirements, and (5) the addition of the file-level metadata (flmd.csv) and data dictionary (dd.csv) were added to comply with the File-Level Metadata Reporting Format.Update on 2022-09-09: Updates were made to reporting format specific files (file-level metadata and data dictionary) to correct swapped file names, add additional details on metadata descriptions on both files, add a header_row column to enable parsing, and add version number and date to file names (v2_20220909_flmd.csv and v2_20220909_dd.csv).Update on 2022-12-20: Updates were made to both the data files and reporting format specific files. Conversion issues affecting ER-PLM locations for anion data was resolved for the data files. Additionally, the flmd and dd files were updated to reflect the updated versions of these files. Available data was added up until 2022-03-14.Update on 2023-08-08: Updates were made to both the data files and reporting format specific files. New available anion data was added, up until 2023-05-19. The file level metadata and data dictionary files were updated to reflect the additional data added.Update on 2024-03-11: Updates were made to both the data files and reporting format specific files. New available anion data was added, up until 2023-09-11. Further, revisions to the data files were made to remove incorrect data points (from 1970 and 2001). The reporting format specific files were updated to reflect the additional data added.Update on 2025-05-15: Updates were made to both the data files and reporting format specific files. New available anion data was added, up until the end of WY2024 (September 30, 2024). International Generic Sample Numbers (IGSNs), when registered, were added to the data files. The reporting format specific files were updated to reflect the additional data added.

The data set is refreshed on a daily basis by 1:45 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.

Employment, Commuting, Occupation, Income, Health Insurance, Poverty, and more. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: District-wide. Current Vintage: 2019-2023. ACS Table(s): DP03. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 2, 2025. National Figures: data.census.gov. Please cite the Census and ACS when using this data. Data Note from the Census: Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables. Data Processing Notes: This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

This dataset is comprised of data submitted to HCAI by prescription drug manufacturers for wholesale acquisition cost (WAC) increases that exceed the statutorily-mandated WAC increase threshold of an increase of more than 16% above the WAC of the drug product on December 31 of the calendar year three years prior to the current calendar year. This threshold applies to prescription drug products with a WAC greater than $40 for a course of therapy. Required WAC increase reports are to be submitted to HCAI within a month after the end of the quarter in which the WAC increase went into effect. Please see the statute and regulations for additional information regarding reporting thresholds and report due dates.

Key data elements in this dataset include the National Drug Code (NDC) maintained by the FDA, narrative descriptions of the reasons for the increase in WAC, and the five-year history of WAC increases for the NDC. A WAC Increase Report consists of 27 data elements that have been divided into two separate Excel data sets: Prescription Drug WAC Increase and Prescription Drug WAC Increase – 5 Year History. The datasets include manufacturer WAC Increase Reports received since January 1, 2019. The Prescription Drugs WAC Increase dataset consists of the information submitted by prescription drug manufacturers that pertains to the current WAC increase of a given report, including the amount of the current increase, the WAC after increase, and the effective date of the increase. The Prescription Drugs WAC Increase – 5 Year History dataset consists of the information submitted by prescription drug manufacturers for the data elements that comprise the 5-year history of WAC increases of a given report, including the amount of each increase and their effective dates.

There are 2 types of WAC Increase datasets below: Monthly and Annual. The Monthly datasets include the data in completed reports submitted by manufacturers for calendar year 2025, as of April 7, 2025. The Annual datasets include data in completed reports submitted by manufacturers for the specified year. The datasets may include reports that do not meet the specified minimum thresholds for reporting.

The Quick Guide explaining how to link the information in each data set to form complete reports is here: https://hcai.ca.gov/wp-content/uploads/2024/03/QuickGuide_LinkingTheDatasets.pdf

The program regulations are available here: https://hcai.ca.gov/wp-content/uploads/2024/03/CTRx-Regulations-Text.pdf

The data format and file specifications are available here: https://hcai.ca.gov/wp-content/uploads/2024/03/Format-and-File-Specifications-version-2.0-ada.pdf

DATA NOTES: Due to recent changes in Excel, it is not recommended that you save these files to .csv format. If you do, when importing back into Excel the leading zeros in the NDC number column will be dropped. If you need to save it into a different format other than .xlsx it must be .txt

DATA UPDATES: Annual datasets of reports from the preceding year are reviewed in the second half of the current year to identify if any revisions or additions have been made since the original release of the datasets. If revisions or additions have been found, an update of the datasets will be released. Datasets will be clearly marked with 'Updated' in their titles for convenient identification. Not all datasets may require an updated release. The review of previously released datasets will only be conducted once to determine if an updated release is necessary. Datasets with revisions or additions that may have been made after the one-time review can be requested. These requests should be sent via email to ctrx@hcai.ca.gov. Due to regulatory changes that went into effect April 1, 2024, reports submitted prior to April 1, 2024, will include the data field "Unit Sales Volume in US" and reports submitted on or after April 1, 2024, will instead include "Total Volume of Gross Sales in US Dollars".

Update on StatsCan/Data Access Division (DAD), EAC/DLI, PDC

An updated database of geothermal direct-use systems in the U.S. has been compiled and analyzed, building upon the Oregon Institute of Technology (OIT) Geo-Heat Center direct-use database. Types of direct-use applications examined include hot springs resorts and pools, aquaculture farms, greenhouses, and district heating systems, among others; power-generating facilities and ground-source heat pumps were excluded. Where possible, the current operation status, open and close dates, well data, and other technical data were obtained for each entry. The database contains 545 installations, of which 407 are open, 108 are closed, and 30 have an unknown status. A report is also included which details and analyzes current geothermal direct-use installations and barriers to further implementation.

No description found

This dataset tracks the updates made on the dataset "East Port Orchard Elementary School Update" as a repository for previous versions of the data and metadata.

This blog post was posted by CEBS-support on November 7, 2019.

Terms of UseData Limitations and DisclaimerThe user’s use of and/or reliance on the information contained in the Document shall be at the user’s own risk and expense. MassDEP disclaims any responsibility for any loss or harm that may result to the user of this data or to any other person due to the user’s use of the Document.This is an ongoing data development project. Attempts have been made to contact all PWS systems, but not all have responded with information on their service area. MassDEP will continue to collect and verify this information. Some PWS service areas included in this datalayer have not been verified by the PWS or the municipality involved, but since many of those areas are based on information published online by the municipality, the PWS, or in a publicly available report, they are included in the estimated PWS service area datalayer.Please note: All PWS service area delineations are estimates for broad planning purposes and should only be used as a guide. The data is not appropriate for site-specific or parcel-specific analysis. Not all properties within a PWS service area are necessarily served by the system, and some properties outside the mapped service areas could be served by the PWS – please contact the relevant PWS. Not all service areas have been confirmed by the systems.Please use the following citation to reference these data:MassDEP, Water Utility Resilience Program. 2025. Community and Non-Transient Non-Community Public Water System Service Area (PubV2025_3).IMPORTANT NOTICE: This MassDEP Estimated Water Service datalayer may not be complete, may contain errors, omissions, and other inaccuracies and the data are subject to change. This version is published through MassGIS. We want to learn about the data uses. If you use this dataset, please notify staff in the Water Utility Resilience Program (WURP@mass.gov).This GIS datalayer represents approximate service areas for Public Water Systems (PWS) in Massachusetts. In 2017, as part of its “Enhancing Resilience and Emergency Preparedness of Water Utilities through Improved Mapping” (Critical Infrastructure Mapping Project ), the MassDEP Water Utility Resilience Program (WURP) began to uniformly map drinking water service areas throughout Massachusetts using information collected from various sources. Along with confirming existing public water system (PWS) service area information, the project collected and verified estimated service area delineations for PWSs not previously delineated and will continue to update the information contained in the datalayers. As of the date of publication, WURP has delineated Community (COM) and Non-Transient Non-Community (NTNC) service areas. Transient non-community (TNCs) are not part of this mapping project.Layers and Tables:The MassDEP Estimated Public Water System Service Area data comprises two polygon feature classes and a supporting table. Some data fields are populated from the MassDEP Drinking Water Program’s Water Quality Testing System (WQTS) and Annual Statistical Reports (ASR).The Community Water Service Areas feature class (PWS_WATER_SERVICE_AREA_COMM_POLY) includes polygon features that represent the approximate service areas for PWS classified as Community systems.The NTNC Water Service Areas feature class (PWS_WATER_SERVICE_AREA_NTNC_POLY) includes polygon features that represent the approximate service areas for PWS classified as Non-Transient Non-Community systems.The Unlocated Sites List table (PWS_WATER_SERVICE_AREA_USL) contains a list of known, unmapped active Community and NTNC PWS services areas at the time of publication.ProductionData UniversePublic Water Systems in Massachusetts are permitted and regulated through the MassDEP Drinking Water Program. The WURP has mapped service areas for all active and inactive municipal and non-municipal Community PWSs in MassDEP’s Water Quality Testing Database (WQTS). Community PWS refers to a public water system that serves at least 15 service connections used by year-round residents or regularly serves at least 25 year-round residents.All active and inactive NTNC PWS were also mapped using information contained in WQTS. An NTNC or Non-transient Non-community Water System refers to a public water system that is not a community water system and that has at least 15 service connections or regularly serves at least 25 of the same persons or more approximately four or more hours per day, four or more days per week, more than six months or 180 days per year, such as a workplace providing water to its employees.These data may include declassified PWSs. Staff will work to rectify the status/water services to properties previously served by declassified PWSs and remove or incorporate these service areas as needed.Maps of service areas for these systems were collected from various online and MassDEP sources to create service areas digitally in GIS. Every PWS is assigned a unique PWSID by MassDEP that incorporates the municipal ID of the municipality it serves (or the largest municipality it serves if it serves multiple municipalities). Some municipalities contain more than one PWS, but each PWS has a unique PWSID. The Estimated PWS Service Area datalayer, therefore, contains polygons with a unique PWSID for each PWS service area.A service area for a community PWS may serve all of one municipality (e.g. Watertown Water Department), multiple municipalities (e.g. Abington-Rockland Joint Water Works), all or portions of two or more municipalities (e.g. Provincetown Water Dept which serves all of Provincetown and a portion of Truro), or a portion of a municipality (e.g. Hyannis Water System, which is one of four PWSs in the town of Barnstable).Some service areas have not been mapped but their general location is represented by a small circle which serves as a placeholder. The location of these circles are estimates based on the general location of the source wells or the general estimated location of the service area - these do not represent the actual service area.Service areas were mapped initially from 2017 to 2022 and reflect varying years for which service is implemented for that service area boundary. WURP maintains the dataset quarterly with annual data updates; however, the dataset may not include all current active PWSs. A list of unmapped PWS systems is included in the USL table PWS_WATER_SERVICE_AREA_USL available for download with the dataset. Some PWSs that are not mapped may have come online after this iteration of the mapping project; these will be reconciled and mapped during the next phase of the WURP project. PWS IDs that represent regional or joint boards with (e.g. Tri Town Water Board, Randolph/Holbrook Water Board, Upper Cape Regional Water Cooperative) will not be mapped because their individual municipal service areas are included in this datalayer.PWSs that do not have corresponding sources, may be part of consecutive systems, may have been incorporated into another PWSs, reclassified as a different type of PWS, or otherwise taken offline. PWSs that have been incorporated, reclassified, or taken offline will be reconciled during the next data update.Methodologies and Data SourcesSeveral methodologies were used to create service area boundaries using various sources, including data received from the systems in response to requests for information from the MassDEP WURP project, information on file at MassDEP, and service area maps found online at municipal and PWS websites. When provided with water line data rather than generalized areas, 300-foot buffers were created around the water lines to denote service areas and then edited to incorporate generalizations. Some municipalities submitted parcel data or address information to be used in delineating service areas.Verification ProcessSmall-scale PDF file maps with roads and other infrastructure were sent to every PWS for corrections or verifications. For small systems, such as a condominium complex or residential school, the relevant parcels were often used as the basis for the delineated service area. In towns where 97% or more of their population is served by the PWS and no other service area delineation was available, the town boundary was used as the service area boundary. Some towns responded to the request for information or verification of service areas by stating that the town boundary should be used since all or nearly all of the municipality is served by the PWS.Sources of information for estimated drinking water service areasThe following information was used to develop estimated drinking water service areas:EOEEA Water Assets Project (2005) water lines (these were buffered to create service areas)Horsely Witten Report 2008Municipal Master Plans, Open Space Plans, Facilities Plans, Water Supply System Webpages, reports and online interactive mapsGIS data received from PWSDetailed infrastructure mapping completed through the MassDEP WURP Critical Infrastructure InitiativeIn the absence of other service area information, for municipalities served by a town-wide water system serving at least 97% of the population, the municipality’s boundary was used. Determinations of which municipalities are 97% or more served by the PWS were made based on the Percent Water Service Map created in 2018 by MassDEP based on various sources of information including but not limited to:The Winter population served submitted by the PWS in the ASR submittalThe number of services from WQTS as a percent of developed parcelsTaken directly from a Master Plan, Water Department Website, Open Space Plan, etc. found onlineCalculated using information from the town on the population servedMassDEP staff estimateHorsely Witten Report 2008Calculation based on Water System Areas Mapped through MassDEP WURP Critical Infrastructure Initiative, 2017-2022Information found in publicly available PWS planning documents submitted to MassDEP or as part of infrastructure planningMaintenanceThe

Deprecated report. This report was created early in the response to the COVID-19 pandemic. Increased reporting and quality in hospital data have rendered the estimated datasets obsolete. Updates to this report will be discontinued on July 29, 2021. The following dataset provides state-aggregated data for estimated patient impact and hospital utilization. The source data for estimation is derived from reports with facility-level granularity across two main sources: (1) HHS TeleTracking, and (2) reporting provided directly to HHS Protect by state/territorial health departments on behalf of their healthcare facilities. Estimates Basis: These files are representative estimates for each state and are updated weekly. These projections are based on the information we have from those who reported. As more hospitals report more frequently our projections become more accurate. The actual data for these data points are updated every day, once a day on healthdata.gov and these are the downloadable data sets.