AndreaBozzo/ceres-open-data-index huggingface dataset:
Street Tree Removal Notifications

<strong>Dataset Update (July 31, 2025):</strong> This dataset is now sourced from a new system following a planned system migration. For questions or feedback, please contact support@datasf.org.

<strong>A. SUMMARY</strong>
Street Tree Removal public notifications managed by San Francisco Public Works.

<strong>B. HOW THE DATASET IS CREATED</strong>
Data is based on 24-hour, 15-day, or 30-day public notices posted on the trees after a Street Tree Removal Permit was issued by the City.

<strong>C. UPDATE PROCESS</strong>
Updated daily.

<strong>D. HOW TO USE THIS DATASET</strong>
Each record is a street tree removal public notice after a permit was issued and the tree was recommended for removal.

Tags: notification, posting, removal, schedule, tree, trees
Organization: City of San Francisco
Dataset inventory

<strong>A. SUMMARY</strong>
The dataset inventory provides a list of data maintained by departments that are candidates for open data publishing or have already been published and is collected in accordance with Chapter 22D of the Administrative Code. The inventory will be used in conjunction with department publishing plans to track progress toward meeting plan goals for each department.

<strong>B. HOW THE DATASET IS CREATED</strong>
This dataset is collated through 2 ways:
1. Ongoing updates are made throughout the year to reflect new datasets, this process involves DataSF staff reconciling publishing records after datasets are published
2. Annual bulk updates - departments review their inventories and identify changes and updates and submit those to DataSF for a once a year bulk update - not all departments will have changes or their changes will have been captured over the course of the prior year already as ongoing updates

<strong>C. UPDATE PROCESS</strong>
The dataset is synced automatically daily, but the underlying data changes manually throughout the year as needed

<strong>D. HOW TO USE THIS DATASET</strong>
<em>Interpreting dates in this dataset</em>
This dataset has 2 dates:
1. Date Added - when the dataset was added to the inventory itself
2. First Published - the open data portal automatically captures the date the dataset was first created, this is that system generated date

Note that in certain cases we may have published a dataset prior to it being added to the inventory. We do our best to have an accurate accounting of when something was added to this inventory and when it was published. In most cases the inventory addition will happen prior to publishing, but in certain cases it will be published and we will have missed updating the inventory as this is a manual process. 

First published will give an  accounting of when it was actually available on the open data catalog and date added when it was added to this list. 

<strong>E. RELATED DATASETS</strong>
<li> <u><a href="https://data.sfgov.org/City-Management-and-Ethics/Inventory-of-citywide-enterprise-systems-of-record/ebux-gcnq/about_data">Inventory of citywide enterprise systems of record</a></u>
<li> <u><a href="https://data.sfgov.org/City-Infrastructure/Dataset-Inventory-Column-Level-Details/cubx-fb3q/about_data">Dataset Inventory: Column-Level Details</a></u>

Tags: catalog, inventory, open-data, ref-inventory
Organization: City of San Francisco
SPU DWW Aba Rem Ditches and Culverts

<div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Ditches are small to moderate depressions that are created to channel water.  Culverts are pipes that are open on both ends that conduct water under a road or railway. </div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><div style='font-family:inherit;'>Displays data from the feature class DWW.ditch_culvert_ln_pv, SPU DWW Ditches and Culverts uses the following query:  (DCH_LIFECYCLE_CODE IN ( 'C' , 'UNK' , 'T', 'TBC', 'U', 'PC') AND DCH_FEATYPE_CODE IN( 'DCH' , 'CUL' ,'PHM').  SPU DWW Proposed Ditches and Culverts uses the following query:  DCH_LIFECYCLE_CODE = 'PRO' And DCH_FEATYPE_CODE IN ('DCH', 'CUL', 'PHM').  SPU DWW Aba Rem Ditches and Culverts has the following query:  DCH_LIFECYCLE_CODE IN ('A', 'R', 'AT').  This layer does not display when zoomed out beyond 1:7,000.  Labels do not display when zoomed out beyond 1:4800.  Label is based on the attribute DCH_OWNER_CODE.  Maintained by SPU GIS DWW Data Maintenance staff.  </div><div style='font-family:inherit;'><br /></div></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Refreshed weekly.</div>

Tags: culvert, ditch, dww, public-utility, seattle-gis-open-data, surface-drainline
Organization: City of Seattle
Lining Status Varies by Location

A grouped feature layer that includes Water Mains, Water Services, Same Side Tap Only and No New Taps layers.<div><br /><div><ul><li>Water Mains are large buried pipes that distribute water from a supply source ultimately to customer's service lines. </li><li>Water Services are lines representing a water service delivered from a watermain to a property.</li><li>Same Side Tap Only and No New Taps are water main restrictions which represent the availability or access to water main assets. Same Side Tap Only are lines representing where water services are only allowed to be tapped on one side of the water main. </li><li>No New Taps are lines representing water mains where new water services are no longer permitted to tap into the water main.</li></ul></div><div>This data provides a limited view of Seattle's water infrastructure. For example, the data does not include transmission pipelines or feeder mains for reasons of water system network security. The data may show water mains that are not eligible for new water service connections (e.g., obsolete or &quot;no-tap&quot; water mains).<br /></div></div>

Tags: mains, no-new-taps, same-side-tap-only, seattle-gis-open-data, services, water, water-main, water-mains, water-services
Organization: City of Seattle
Basketball Court Points

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Basketball Courts maintained by Seattle Parks and Recreation.</span><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Refresh Cycle: Weekly</span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Feature Class: </span>DPR.BasketballCourts</div>

Tags: basketball-courts, common-data-layers, courts, parks, seattle-gis-open-data, sports, spr
Organization: City of Seattle
Tree Service Provider Registry

Database of all active Tree Service Providers registered to do business in Seattle and have met the registration requirements for the Seattle Department of Construction & Inspections (SDCI) registry for tree work on private property, for the Seattle Department of Transportation’s (SDOT) registry for tree work in the public right-of-way, or both. All commercial tree work on private property, including removal, reportable work, or consulting services must be conducted by a SDCI registered tree service provider. All major pruning or tree removal work within the public right-of-way must be conducted by a SDOT registered tree service provider.

Tags: registry, service, tree, tree-service, tree-service-provider, tree-service-provider-registry
Organization: City of Seattle
Non-Mainline Detention Lines

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Active, proposed, abandoned and removed secondary sewer and storm pipes that are not part of the mainline system (i.e. side sewers, service drains, etc.). Side Sewers are wastewater pipes from buildings and establishments that connect to mainline pipes. Service drains are stormwater pipes from buildings that connect to mainline pipes. Probable flow is the derived use classification based on what is the best estimation of usage broken out by drainage and sanitary.</span><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /><div style='font-family:inherit;'>Refreshed weekly.</div></div>

Tags: aba-rem-non-mainlines, detention-lines, detention-polygons, non-mainlines, proposed-non-mainlines, seattle-gis-open-data, spu-non-mainlines
Organization: City of Seattle
Piped Creek Watersheds

<div style='text-align:Left;font-size:12pt'><div><div><p><span>Creek watersheds which are piped to outfall.  This is an expansion of the creek watershed to include the portions collected by the PSD network which were not originally included in the basin, but now discharge to the piped creek. </span><span><span>Displays data from DWW.Piped_CrkWtrshd, will not display when zoomed out beyond 1:200,000.  Labels are based on the attribute PCWS_NAME and do not display when zoomed out beyond 1:50,000.</span></span></p><p><span /></p></div></div></div>

Tags: creek-watersheds, dww, seattle-gis-open-data, spu
Organization: City of Seattle
Creek Watersheds

<p><span style='font-family:&quot;Segoe UI&quot;, Arial, sans-serif; font-size:16px;'>This layer displays the urban creek watersheds.  Creek watershed flow is in the contentious and intermittent natural surface water flow identified and recognized as a stream by the Seattle Public Utilities.  The polygons are intended for use by the City of Seattle as planning-level tool for a preliminary understanding of the drainage patterns in particular areas of the City.  The layer is not complete and does not reflect any City determination about how specific locations should be characterized.  Creek watersheds were delineated using topography, utility infrastructure and field verification. The data source is DWW.urban_crk_wtrshd_plgn_pv.  The layer does not display when zoomed out beyond 1:200,000.  Labels are based on the attribute ALT_NAME and NAME, and do not display when zoomed out beyond 1:50,000.  Refreshed weekly.  Maintained by SPU USM.</span><br /></p>

Tags: dww, polygon, seattle-gis-open-data, urban-creek, watershed
Organization: City of Seattle
Parking Categories

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Displays </span><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Parking Categories</span><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'> maintained by the Seattle Department of Transportation.</span><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><div style='font-family:inherit;'>Refresh Cycle: Daily</div><div style='font-family:inherit;'><br /></div><div style='font-family:inherit;'>Feature Class: SDOT.ParkingCategories</div></div>

Tags: common-data-layers, parking, parking-categories, sdot, seattle-gis-open-data, transportation
Organization: City of Seattle
Street Closures due to Construction Activities by Intersection

DOT Street Closure data identifies locations in the New York City Street Closure map where a street is subject to a full closure, restricting through traffic, for the purpose of conducting construction related activity on a City street. Details about DOT construction permits can be found at Street Works Manual, http://streetworksmanual.nyc. Full Closure Permits are issued for a period of time during which the street may be closed to through traffic for only a portion of the time, and open at other times.

Tags: closure, closures, construction, milling, paving, repair, resurfacing, road, roadway, street
Organization: City of New York
Motor Vehicle Collisions - Crashes

The Motor Vehicle Collisions crash table contains details on the crash event. Each row represents a crash event. The Motor Vehicle Collisions data tables contain information from all police reported motor vehicle collisions in NYC. The police report (MV104-AN) is required to be filled out for collisions where someone is injured or killed, or where there is at least $1000 worth of damage (https://www.nhtsa.gov/sites/nhtsa.dot.gov/files/documents/ny_overlay_mv-104an_rev05_2004.pdf).  It should be noted that the data is preliminary and subject to change when the MV-104AN forms are amended based on revised crash details.For the most accurate, up to date statistics on traffic fatalities, please refer to the <a href="https://www1.nyc.gov/site/nypd/stats/traffic-data/traffic-data-collision.page" style="color:#187bcd;">NYPD Motor Vehicle Collisions page</a> (updated weekly) or <a href="http://www.nycvzv.info/" style="color:#187bcd;">Vision Zero View</a> (updated monthly).

</p>
Due to success of the CompStat program, NYPD began to ask how to apply the CompStat principles  to other problems.  Other than homicides, the fatal incidents with which police have the most contact with the public are fatal traffic collisions.  Therefore in April 1998, the Department implemented TrafficStat, which uses the CompStat model to work towards improving traffic safety.  Police officers complete form MV-104AN  for all vehicle collisions.  The MV-104AN is a New York State form that has all of the details of a traffic collision.  Before implementing Trafficstat, there was no uniform traffic safety data collection procedure for all of the NYPD precincts.  Therefore, the Police Department implemented the Traffic Accident Management System (TAMS) in July 1999 in order to collect traffic data in a uniform method across the City.  TAMS required the precincts manually enter a few selected MV-104AN fields to collect very basic intersection traffic crash statistics which included the number of accidents, injuries and fatalities. As the years progressed, there grew a need for additional traffic data so that more detailed analyses could be conducted. The Citywide traffic safety initiative, Vision Zero started in the year 2014.  Vision Zero further emphasized the need for the collection of more traffic data in order to work towards the Vision Zero goal, which is to eliminate traffic fatalities.  Therefore, the Department in March 2016 replaced the TAMS with the new Finest Online Records Management System (FORMS).  FORMS enables the police officers to electronically, using a Department cellphone or computer, enter all of the MV-104AN data fields and stores all of the MV-104AN data fields in the Department’s crime data warehouse.  Since all of the MV-104AN data fields are now stored for each traffic collision, detailed traffic safety analyses can be conducted as applicable.

Tags: big-apps, bigapps, collisions, nycopendata, nypd, traffic-data, vision, visionzero, zero
Organization: City of New York
Legend and Symbols

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>View of Channelization data represents roadway paint lines, curbs, and other markings that delineate traffic lanes, bike routes, bus zones, etc. which are critical for public safety.</span><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Common Data Layer: Common data layer created from a read only view from this feature layer. It is owned by SDOT Transportation account and will be made available in Open Data.</div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Refresh Cycle: None, Dynamic via AutoCAD updates</div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Channelization data consists of the following layers:</div><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><ol><li>Vertical Elements</li><li>Lane Widths</li><li>Panel Markings</li><li>Longitudinal Markings</li><li>Transverse Markings</li><li>Legend and Symbols</li><li>General Background</li></ol></div>

Tags: channelization, sdot, seattle-gis-open-data
Organization: City of Seattle
SPU DWW Mainlines (Probable Flow)

SPU DWW Mainlines is a Group Layer containing all Lifecycles, Ownerships, and other variations of Drainage and Wastewater Mainlines. The Connected Mainlines are symbolized differently in two different layers, one displaying the Permitted Use of the pipe and another displaying the Probable Flow.<div><br /></div><div>Permitted Use describes the intended use of the pipe, including Sanitary, Combined, or Drainage flows. Probable Flow takes into account upstream pipes and makes an assumption on the type of flow within the pipes.</div><div><br /></div><div>Proposed Mainlines are planned but not yet installed or as-built.</div><div><br /></div><div>SPU DWW Aba Rem Mainlines refers to Abandoned and Removed Mainlines.</div><div><br /></div><div>Force Mainlines are Mainlines under pressure. Detention Lines and Polygons refer to Mainline Detention Infrastructure.</div><div><br /></div><div>The data is refreshed weekly and is maintained by the SPU GIS Data Maintenance Team. </div>

Tags: combined, drainage, dww, mainline, seattle-gis-open-data, sewer, spu
Organization: City of Seattle
Non-Mainline Detention Polygons

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Active, proposed, abandoned and removed secondary sewer and storm pipes that are not part of the mainline system (i.e. side sewers, service drains, etc.). Side Sewers are wastewater pipes from buildings and establishments that connect to mainline pipes. Service drains are stormwater pipes from buildings that connect to mainline pipes. Probable flow is the derived use classification based on what is the best estimation of usage broken out by drainage and sanitary.</span><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /><div style='font-family:inherit;'>Refreshed weekly.</div></div>

Tags: aba-rem-non-mainlines, detention-lines, detention-polygons, non-mainlines, proposed-non-mainlines, seattle-gis-open-data, spu-non-mainlines
Organization: City of Seattle
Aba Rem Non-Mainlines

<span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Active, proposed, abandoned and removed secondary sewer and storm pipes that are not part of the mainline system (i.e. side sewers, service drains, etc.). Side Sewers are wastewater pipes from buildings and establishments that connect to mainline pipes. Service drains are stormwater pipes from buildings that connect to mainline pipes. Probable flow is the derived use classification based on what is the best estimation of usage broken out by drainage and sanitary.</span><div style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /><div style='font-family:inherit;'>Refreshed weekly.</div></div>

Tags: aba-rem-non-mainlines, detention-lines, detention-polygons, non-mainlines, proposed-non-mainlines, seattle-gis-open-data, spu-non-mainlines
Organization: City of Seattle
COVID-19 Daily Counts of Cases, Hospitalizations, and Deaths

Daily count of NYC residents who tested positive for SARS-CoV-2, who were hospitalized with COVID-19, and deaths among COVID-19 patients.

Note that this dataset currently pulls from https://raw.githubusercontent.com/nychealth/coronavirus-data/master/trends/data-by-day.csv on a daily basis.

Tags: coronavirus, covid-19, sars-cov-2
Organization: City of New York