AndreaBozzo/ceres-open-data-index huggingface dataset:
Wetland Types

<div style='text-align:Left;'><div><div><p><span>This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). The National Wetlands Inventory - Version 2, Surface Waters and Wetlands Inventory was derived by retaining the wetland and deepwater polygons that compose the NWI digital wetlands spatial data layer and reintroducing any linear wetland or surface water features that were orphaned from the original NWI hard copy maps by converting them to narrow polygonal features. Additionally, the data are supplemented with hydrography data, buffered to become polygonal features, as a secondary source for any single-line stream features not mapped by the NWI and to complete segmented connections. Wetland mapping conducted in WA, OR, CA, NV and ID after 2012 and most other projects mapped after 2015 were mapped to include all surface water features and are not derived data. The linear hydrography dataset used to derive Version 2 was the U.S. Geological Survey's National Hydrography Dataset (NHD). Specific information on the NHD version used to derive Version 2 and where Version 2 was mapped can be found in the 'comments' field of the Wetlands_Project_Metadata feature class. Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands_Project_Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.</span></p></div></div></div>

Tags: biota, bogs, district-of-columbia, doee, environment, fens, hydrography, hydrologic, marshes, national-wetlands-inventory, nwi, surface-and-manmade-feature, surface-water, swamps, u-s-fish-and-wildlife-service, united-states, usfws, washington-dc, water, wetlands
Organization: District of Columbia
Subwatersheds

<div style='text-align:Left;'><div><p><span>This dataset is a complete digital hydrologic unit boundary layer to the subwatershed (12-digit) 6th level at 1:24,000 scale. This data set consists of geo-referenced digital data and associated attributes created in accordance with the FGDC Proposal, Version 1.0 - Federal Standards For Delineation of Hydrologic Unit Boundaries 3/01/02. The hydrologic unit boundaries provide a uniquely identified and uniform method of subdividing large drainage areas. Polygons are attributed with hydrologic unit codes, names, downstream hydrologic unit, flow modifications, and hydrologic unit type for 4th level (8-digit) sub-basin, 5th level (10-digit) watershed, 6th level (12-digit) subwatershed, and acres for subwatershed. An accompanying line shapefile is attributed with the highest hydrologic unit level for each hydrologic unit, line source, and a metadata reference file. </span></p></div></div>

Tags: district-of-columbia, environment, environmental, hydrology, open-data, subwatershed, washington, washington-dc
Organization: District of Columbia
DC Watersheds

<div style='text-align:Left;'><div><div><p><span>This dataset is a digital hydrologic unit boundary layer for the District of Columbia only - to the watershed (10-digit) 6th level at 1:24,000 scale. It is a clipped version of the regional dataset using the DC Boundary. This data set consists of geo-referenced digital data and associated attributes created in accordance with the FGDC Proposal, Version 1.0 - Federal Standards For Delineation of Hydrologic Unit Boundaries 3/01/02 (</span><a href='https://www.nrcs.usda.gov:443/' style='text-decoration:underline;' rel='nofollow ugc'><span>https://www.nrcs.usda.gov</span></a><span>). The hydrologic unit boundaries provide a uniquely identified and uniform method of subdividing large drainage areas. Polygons are attributed with hydrologic unit codes, names, downstream hydrologic unit, flow modifications, and hydrologic unit type for 4th level (8-digit) sub-basin, 5th level (10-digit) watershed, 6th level (12-digit) subwatershed, and acres for subwatershed.</span></p></div></div></div>

Tags: dc, district-of-columbia, doee, drainage-area, hydrology, river, washington-dc, water, watershed
Organization: District of Columbia
DC Subwatersheds

<div style='text-align:Left;'><div><div><p><span>This layer depicts the conglomeration of the 4 layers used for TMDLs. It contains TMDL Subsheds, Direct Drain Overland (not piped), Direct Drain Sewersheds (piped), and Combined Sewer (CSS) Subsheds. This layer provided the granularity needed to facilitate further analysis.</span></p></div></div></div>

Tags: combined-sewershed, cso, css, direct-drain-overland, direct-drain-sewersheds, doee, drainage-areas, environment, ms4, ms4-sewersheds, sewershed, subsheds, tmdl, watershed
Organization: District of Columbia
Wetland Creation

<div style='text-align:Left;'><div><div><p><span>This feature class is a GIS point layer containing potential wetland creation/mitigation sites assessed by Wetland Studies and Solutions, Inc. (WSSI).</span></p><p><span /></p></div></div></div>

Tags: district-of-columbia, doee, environment, mitigation, open-data, potential-mitigation, restoration, washington-dc, wetland, wssi
Organization: District of Columbia
Wetland Inventory

<div style='text-align:Left;'><div><div><p><span>This data set represents the extent, approximate location and type of wetlands and deepwater habitats in the United States and its Territories. These data delineate the areal extent of wetlands and surface waters as defined by Cowardin et al. (1979). The National Wetlands Inventory - Version 2, Surface Waters and Wetlands Inventory was derived by retaining the wetland and deepwater polygons that compose the NWI digital wetlands spatial data layer and reintroducing any linear wetland or surface water features that were orphaned from the original NWI hard copy maps by converting them to narrow polygonal features. Additionally, the data are supplemented with hydrography data, buffered to become polygonal features, as a secondary source for any single-line stream features not mapped by the NWI and to complete segmented connections. Wetland mapping conducted in WA, OR, CA, NV and ID after 2012 and most other projects mapped after 2015 were mapped to include all surface water features and are not derived data. The linear hydrography dataset used to derive Version 2 was the U.S. Geological Survey's National Hydrography Dataset (NHD). Specific information on the NHD version used to derive Version 2 and where Version 2 was mapped can be found in the 'comments' field of the Wetlands_Project_Metadata feature class. Certain wetland habitats are excluded from the National mapping program because of the limitations of aerial imagery as the primary data source used to detect wetlands. These habitats include seagrasses or submerged aquatic vegetation that are found in the intertidal and subtidal zones of estuaries and near shore coastal waters. Some deepwater reef communities (coral or tuberficid worm reefs) have also been excluded from the inventory. These habitats, because of their depth, go undetected by aerial imagery. By policy, the Service also excludes certain types of "farmed wetlands" as may be defined by the Food Security Act or that do not coincide with the Cowardin et al. definition. Contact the Service's Regional Wetland Coordinator for additional information on what types of farmed wetlands are included on wetland maps. This dataset should be used in conjunction with the Wetlands_Project_Metadata layer, which contains project specific wetlands mapping procedures and information on dates, scales and emulsion of imagery used to map the wetlands within specific project boundaries.</span></p></div></div></div>

Tags: biota, bogs, district-of-columbia, doee, environment, fens, hydrography, hydrologic, marshes, national-wetlands-inventory, nwi, surface-and-manmade-feature, surface-water, swamps, u-s-fish-and-wildlife-service, united-states, usfws, washington-dc, water, wetlands
Organization: District of Columbia
Chesapeake Bay Watersheds

<div style='text-align:Left;'><div><div><p><span>The dataset contains locations and attributes of HUC-11 watersheds. The USGS presents a detailed explanation of HUCs at </span><a href='https://water.usgs.gov:443/GIS/huc.html' target='_blank' style='text-decoration:underline;' rel='nofollow ugc noopener noreferrer'><span>https://water.usgs.gov/GIS/huc.html</span></a><span>. HUC-11 boundaries are compiled by each state. The export files of HUC-11 at the state level were provided by each respective state and are unmodified. HUC-11 boundaries for Delaware are not yet available. Also, a small portion of the Chesapeake Basin in NY State has not yet been completed.</span></p></div></div></div>

Tags: chesapeake-bay-watershed, dc, district-of-columbia, doee, hydrography, river, washington-dc, water, watershed
Organization: District of Columbia
Watersheds

<div style='text-align:Left;'><div><div><p><span>This data set consists of geo-referenced digital data and associated attributes created in accordance with the FGDC Proposal, Version 1.0 - Federal Standards For Delineation of Hydrologic Unit Boundaries 3/01/02 (</span><a href='http://www.nrcs.usda.gov:80/' style='text-decoration:underline;' rel='nofollow ugc'><span>http://www.nrcs.usda.gov</span></a><span>). The hydrologic unit boundaries provide a uniquely identified and uniform method of subdividing large drainage areas. Polygons are attributed with hydrologic unit codes, names, downstream hydrologic unit, flow modifications, and hydrologic unit type for 4th level (8-digit) sub-basin, 5th level (10-digit) watershed, 6th level (12-digit) subwatershed, and acres for subwatershed. An accompanying line shapefile is attributed with the highest hydrologic unit level for each hydrologic unit, linesource, and a metadata reference file.</span></p></div></div></div>

Tags: dc, district-of-columbia, doee, drainage-area, hydrology, river, washington-dc, water, watershed
Organization: District of Columbia
Unique Building Identifier

<div style='text-align:Left;'><div><div><p><span>The dataset contains constructed unique geospatial identifier for buildings. A buildings UBID is the north axis aligned "bounding box" of its footprint represented as the centroid (in the GDAL grid reference system format), which is represented by the first set of characters before the first dash, and four cardinal extents, which are represented by the four sets of numbers after the first dash (North, East, South, West),</span></p><p><span>The data has been constructed by spatially joining the latest (2019) building footprints published in DC Open Data with the Common Ownership Lot shapefile. The UBIDs were coded using US DOE’s Implementation code. </span></p><p><span>Please note that the current data set may include some unnecessary structures identified as buildings. These included sheds, overhangs, bus stops, and other structures that do not need to be assigned a UBID. An updated version of the UBID dataset will be released when this issue is resolved. </span></p><p><span>This project is the result of the US DOE Better Buildings Building Energy Data Analysis (BEDA) Accelerator. US DOE is working with stakeholders including state and local governments, commercial and residential building data aggregators, property owners, and product and service providers to develop the UBID system and to pilot it in real-world settings. US DOE and its partners are demonstrating the benefits of UBID in managing and cross-referencing large building datasets and in reducing the costs and enhancing the value proposition of leveraging building energy data. UBIDs For more information regarding UBIDs please visit: </span><a href='https://www.energy.gov/eere/buildings/unique-building-identifier-ubid' rel='nofollow ugc'><span>https://www.energy.gov/eere/buildings/unique-building-identifier-ubid</span></a><span /></p></div></div></div>

Tags: beda, better-buildings-energy-data-analysis-accelerator, buildings, district-of-columbia, doee, energy, environment, gdal, ubid, unique-building-identifier, us-doe, washington-dc
Organization: District of Columbia
DC Public Employee Salary

<div style='text-align:Left;'><div><div><p><span>DC Department of Human Resources provides District government employees with a variety of services and programs on employee benefits, policy and procedures, performance management, and compensation. This dataset includes public employee salary compensation information found on the DCHR web application https://dchr.dc.gov/public-employee-salary-information.</span></p></div></div></div>

Tags: dchr, district-of-columbia, public-employee-salary, salaries, washington-dc
Organization: District of Columbia
Enterprise Dataset Inventory as of March 2020

<div style='text-align:Left;'><div><div><p><span>Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall:</span></p><ul><li><p><span>Maintain an inventory of its enterprise datasets;</span></p></li><li><p><span>Classify enterprise datasets by level of sensitivity;</span></p></li><li><p><span>Regularly publish the inventory, including the classifications, as an open dataset; and</span></p></li><li><p><span>Strategically plan and manage its investment in data.</span></p></li></ul><p><span>The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. </span></p><p><span>For more information, please visit </span><a href='https://octo.dc.gov/page/district-columbia-data-policy' rel='nofollow ugc'><span>https://octo.dc.gov/page/district-columbia-data-policy</span></a><span>. Previous years of EDI can be found on </span><a href='http://opendata.dc.gov/' rel='nofollow ugc'><span>Open Data</span></a><span>.</span></p></div></div></div>

Tags: cdo, data-policy, dc, disctric-of-columbia, edi, enterprise-dataset-inventory, interagency-data-team, octo, washington-dc
Organization: District of Columbia
Enterprise Dataset Inventory as of March 2022

<div style='text-align:Left;'><div><div><p><span>Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall:</span></p><ul><li><p><span>Maintain an inventory of its enterprise datasets;</span></p></li><li><p><span>Classify enterprise datasets by level of sensitivity;</span></p></li><li><p><span>Regularly publish the inventory, including the classifications, as an open dataset; and</span></p></li><li><p><span>Strategically plan and manage its investment in data.</span></p></li></ul><p><span>The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. </span></p><p><span>For more information, please visit </span><a href='https://octo.dc.gov/page/district-columbia-data-policy' rel='nofollow ugc'><span>https://octo.dc.gov/page/district-columbia-data-policy</span></a><span>. Previous years of EDI can be found on </span><a href='http://opendata.dc.gov/' rel='nofollow ugc'><span>Open Data</span></a><span>.</span></p></div></div></div>

Tags: cdo, data-policy, dc, disctric-of-columbia, edi, enterprise-dataset-inventory, interagency-data-team, octo, washington-dc
Organization: District of Columbia
Enterprise Dataset Inventory as of March 2019

<div style='text-align:Left;'><div><div><p><span>Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall:</span></p><ul><li><p><span>Maintain an inventory of its enterprise datasets;</span></p></li><li><p><span>Classify enterprise datasets by level of sensitivity;</span></p></li><li><p><span>Regularly publish the inventory, including the classifications, as an open dataset; and</span></p></li><li><p><span>Strategically plan and manage its investment in data.</span></p></li></ul><p><span>The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. </span></p><p><span>For more information, please visit </span><a href='https://octo.dc.gov/page/district-columbia-data-policy' rel='nofollow ugc'><span>https://octo.dc.gov/page/district-columbia-data-policy</span></a><span>. Previous years of EDI can be found on </span><a href='http://opendata.dc.gov/' rel='nofollow ugc'><span>Open Data</span></a><span>.</span></p></div></div></div>

Tags: cdo, data-policy, dc, disctric-of-columbia, edi, enterprise-dataset-inventory, interagency-data-team, octo, washington-dc
Organization: District of Columbia
Film and Television Rebate Fund

<div style='text-align:Left;'><div><div><p><span>This data includes information on completed programs for channels the District of Columbia Network, (DCN), the District of Columbia Council Channel, (DCC), and the District Knowledge Network, (DKN). It includes total run times, date completed, editor, and presentation titles. https://entertainment.dc.gov/page/cable-tv.</span></p></div></div></div>

Tags: cable-television, dc, dcn, district-of-columbia, dkn, entertainment, film, octfme, washington-dc
Organization: District of Columbia
Enterprise Dataset Inventory as of March 2018

<div style='text-align:Left;'><div><div><p><span>Enterprise Dataset Inventory as of March 2018. Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall:</span></p><ul><li><p><span>Maintain an inventory of its enterprise datasets;</span></p></li><li><p><span>Classify enterprise datasets by level of sensitivity;</span></p></li><li><p><span>Regularly publish the inventory, including the classifications, as an open dataset; and</span></p></li><li><p><span>Strategically plan and manage its investment in data.</span></p></li></ul><p><span>The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. </span></p><p><span>For more information, please visit </span><a href='https://octo.dc.gov/page/district-columbia-data-policy' rel='nofollow ugc'><span>https://octo.dc.gov/page/district-columbia-data-policy</span></a><span>. The latest EDI can be found on </span><a href='http://opendata.dc.gov/' rel='nofollow ugc'><span>Open Data</span></a><span>.</span></p></div></div></div>

Tags: cdo, data-policy, dc, disctric-of-columbia, district-of-columbia, edi, enterprise-dataset-inventory, interagency-data-team, octo, washington-dc
Organization: District of Columbia
Enterprise Dataset Inventory - Retired Datasets

<div style='text-align:Left;'><div><div><p><span>Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall: maintain an inventory of its enterprise datasets; classify enterprise datasets by level of sensitivity; regularly publish the inventory, including the classifications, as an open dataset; and strategically plan and manage its investment in data.</span></p><p><span>The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. </span></p><p><span>For more information, please visit </span><a href='https://opendata.dc.gov/pages/edi-overview' style='text-decoration:underline;' rel='nofollow ugc'><span>https://opendata.dc.gov/pages/edi-overview</span></a><span>. Previous years of EDI can be found on </span><a href='https://opendata.dc.gov/' style='text-decoration:underline;' rel='nofollow ugc'><span>Open Data</span></a><span>.</span></p></div></div></div>

Tags: cdo, data-policy, dc, district-of-columbia, edi, enterprise-dataset-inventory, interagency-data-team, washington-dc
Organization: District of Columbia
Enterprise Dataset Inventory

<div style='text-align:Left;'><div><div><p><span>Mayor's Order 2017-115 establishes a comprehensive data policy for the District government. The data created and managed by the District government are valuable assets and are independent of the information systems in which the data reside. As such, the District government shall: maintain an inventory of its enterprise datasets; classify enterprise datasets by level of sensitivity; regularly publish the inventory, including the classifications, as an open dataset; and strategically plan and manage its investment in data.</span></p><p><span>The greatest value from the District’s investment in data can only be realized when enterprise datasets are freely shared among District agencies, with federal and regional governments, and with the public to the fullest extent consistent with safety, privacy, and security. </span></p><p><span>For more information, please visit </span><a href='https://opendata.dc.gov/pages/edi-overview' style='text-decoration:underline;' rel='nofollow ugc'><span>https://opendata.dc.gov/pages/edi-overview</span></a><span>. Previous years of EDI can be found on </span><a href='https://opendata.dc.gov/' style='text-decoration:underline;' rel='nofollow ugc'><span>Open Data</span></a><span>.</span></p></div></div></div>

Tags: cdo, data-policy, dc, district-of-columbia, edi, enterprise-dataset-inventory, interagency-data-team, washington-dc
Organization: District of Columbia