Tree Contract Work Details contains information related to work performed on specific tree work contracts. This dataset can be joined to the Forestry Work Orders dataset (https://data.cityofnewyork.us/Environment/Forestry-Work-Orders/bdjm-n7q4) by joining work_order_id from Tree Contract Work Details to OBJECTID from Forestry Work Orders. There are many work_order_ids per single contract_number. Not all work orders in Forestry Work Orders are represented in this dataset because it is only used to track work on specific contracts.

Data Dictionary found here: https://docs.google.com/spreadsheets/d/1rAQL_d8yQ5axRIGl9vLxpr73rDmQUZ23VKQC8QQWIYI/edit?usp=sharing

• One line of data represents the location of a canine waste bag dispenser, including what surface it is mounted on, who refills it, who made it, and when it was installed.
• Data is collected by analysts located in each borough and collated by Parks’ Innovation & Performance Management team.
• Data is updated as needed using an ArcGIS Online web application.
• Records for dispensers that are no longer active have been removed
• Not all records have an installation date. Records will only have an OMPPropID and SubProperty name if they fall within the bounds of a sub property.

This data tracks the blocks that have been planted through NYC Parks’ street tree block planting program, a major component of the MillionTreesNYC initiative. When a block planting is completed for specific street segment, all available and appropriate locations for street tree installation have been planted. This dataset is based on the Citywide Street Centerline data.

Indoor pools in New York City Department of Parks & Recreation properties.

This table is the primary table for information about work orders, and contains general information - including a description of the work, assigned title, request date and completion date - about each work order. Each row represents a single work order. The primary key field is EVT_CODE. The EVT_OBJECT field can be joined to the Assets table on OBJ_CODE to know which asset the work order was for.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

In response to the COVID-19 pandemic, NYC Parks temporarily closed several amenities, including Adult Exercise Equipment. This data collection contains the status of each Adult Exercise Equipment, and is subject to change. Although the data feed is refreshed daily, it may not reflect current conditions.

Data Dictionary:

Supervisor Inspections are conducted by Park Supervisors in order to assess the conditions and identify issues at parks in their districts. Park Supervisors follow the standards set out in the Parks Inspection Program (PIP) Inspection Manual but are not trained in the protocol to the same degree as PIP inspectors, and supervisor inspections are not subject to the thorough review that PIP inspections receive.

During the course of an inspection, Park Supervisors separately rate each feature within a park. This table contains the features inspected, with ratings and notes for each feature.

Overall results and inspection-level records are contained in the Parks Supervisor Inspections - Inspection Results dataset; each row in this table represents one inspection of an individual property (park, playground, or zone).

Specific feature-level records are contained in the Parks Supervisor Inspections - Feature Findings dataset; each row in this table represents the specific feature's details/rating from each inspection.

Data Dictionary: https://docs.google.com/spreadsheets/d/17nwvIsPdAInf-DzGAcwq8hu6SXIzQYabUDktw3BwwLY/edit#gid=1553660070

The NYC Parks Events Listing database is used to store event information displayed on the Parks website, nyc.gov/parks. There are seven related tables that make up the this database:

1. Events_Events table (This is the primary table that contains basic data about every event. Each record is an event.)
2. Events_Categories (Each record is a category describing an event. One event can be in more than one category.)
3. Events_Images (Each record is an image related to an event. One event can have more than one image.)
4. Events_Links (Each record is a link with more information about an event. One event can have more than one link.)
5. Events_Locations (Each record is a location where an event takes place. One event can have more than one location.)
6. Events_Organizers (Each record contains a group or person organizing an event. One event can have more than one organizer.)
7. Events_YouTube (Each record is a link to a YouTube video about an event. One event can have more than one YouTube video.)

The Events_Events table is the primary table. All other tables can be related by joining on the event_id. This data contains records from 2013 and on. For a complete list of related datasets, please follow This Link

Blockface data from the TreesCount! 2015 Street Tree Census, conducted by volunteers and staff organized by NYC Parks & Recreation and partner organizations. Blockface data includes tree counts and data collection status by block. Accompanying street tree data is available, indicating tree-level details such as tree species, size and other characteristics.

Citywide street tree data from the 2005 Street Tree Census, conducted partly by volunteers organized by NYC Parks & Recreation. Trees were inventoried by address, and were collected from 2005-2006. Data collected includes tree species, diameter, condition.

Eateries in in New York City Department of Parks & Recreation properties including snack bars, food carts, mobile food trucks, and restaurants.

In response to the COVID-19 pandemic, NYC Parks temporarily closed several amenities, including Dog Runs. This data collection contains the status of each Dog Run, and is subject to change. Although the data feed is refreshed daily, it may not reflect current conditions.

Data Dictionary:

Tennis courts in New York City Department of Parks & Recreation properties.

This dataset, formally referred to as ""Functional Parkland"" consists of park properties under the jurisdiction of NYC Parks. The shapes in this dataset are drawn to make printed maps clear and easy to read. Consequently, the shapes in this file should not be used for any spatial calculations. For non-cartographic purposes, consult https://data.cityofnewyork.us/Recreation/Parks-Properties/enfh-gkve

This dataset uses the standard NYC projection of NAD_1983_StatePlane_New_York_Long_Island_FIPS_3104_Feet. Lengths are in feet and areas in square feet.

New York City Department of Parks & Recreation public beaches.

The NYC Parks Events Listing database is used to store event information displayed on the Parks website, nyc.gov/parks. There are seven related tables that make up the this database:

1. Events_Events table (This is the primary table that contains basic data about every event. Each record is an event.)
2. Events_Categories (Each record is a category describing an event. One event can be in more than one category.)
3. Events_Images (Each record is an image related to an event. One event can have more than one image.)
4. Events_Links (Each record is a link with more information about an event. One event can have more than one link.)
5. Events_Locations (Each record is a location where an event takes place. One event can have more than one location.)
6. Events_Organizers (Each record contains a group or person organizing an event. One event can have more than one organizer.)
7. Events_YouTube (Each record is a link to a YouTube video about an event. One event can have more than one YouTube video.)

The Events_Events table is the primary table. All other tables can be related by joining on the event_id. This data contains records from 2013 and on. For a complete list of related datasets, please follow This Link

This dataset contains GPS coordinates for each ice ladder NYC Parks places around lakes and ponds. These ladders are intended for rescuing anyone who falls through the ice of a lake or pond during winter. Each record is an ice ladder location. Some locations have multiple ice ladders, which is shown in the LADDER_COUNT field. This dataset is updated annually before winter so maps can be included in borough snow manuals.

User guide: https://drive.google.com/open?id=1gELBkKYvcaDIw29eBQVHJfFEwk7rYO2zuJ9OMCx0irA
Data Dictionary: https://drive.google.com/open?id=1-u7kKCoRWo3l1p5sKfaMY7jCbG0PoTBrgSa28BKLN7E

Hiking trails in New York City Department of Parks & Recreation properties.

The Walk to a Park initiative focuses on increasing access to parks and open spaces, concentrating on areas of the city that are under-resourced and where residents are living further than a walk to a park. NYC Parks calculates the number of New Yorkers within walking distance of a park and reports on this as part of the Mayor’s Management Report. “Walking distance” is defined as a 1/4-mile or less for sites such as small playgrounds and sitting areas; or a 1/2-mile or less for larger parks that serve a wider region, typically over 8 acres or situated on the waterfront. Certain properties in NYC Parks' portfolio, such as cemeteries, community gardens, or sites with no recreational equipment were not included in this analysis. Similarly, some parks and open-space amenities not under the jurisdiction of NYC Parks were included in this analysis, as they provide recreational value.

This dataset includes two ESRI shapefiles of access points, one for sites that get a 1/4-mile buffer and one for sites that get a 1/2-mile buffer. It also includes an ESRI shapefile of the combined polygon that is the output of this analysis. This polygon represents the total area within walking distance of a park. To generate the number of New Yorkers within that distance, the polygon is compared with data from the U.S. Census.

This information is only current as of the publication date. For more information about this analysis and the Walk to a Park Initiative, visit: https://www.nycgovparks.org/planning-and-building/planning/walk-to-a-park

This table contains work order labor records. Each record in this table corresponds to one labor entry and includes general information about that piece of labor. The primary key is BOO_CODE. The BOO_EVENT field can be joined to the Work Orders table on EVT_CODE to know how much labor was booked to each work order.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

This table all comments for all tables in AMPS. The record for each comment indicates which record and table the comment pertains to. Each record is a single comment. The ADD_CODE field can be joined to another table according to the value in ADD_ENTITY.

For the User Guide, please follow this link
For the Data Dictionary, please follow this link

NYC Parks uses a Commercial Off-The-Shelf database for maintaining its concession-related data. In its raw form, the Parks data within the Yardi Voyager database has a convoluted structure, the majority of which is not being used by Parks to store any data. In an effort to make the data more user friendly, the multitude of tables used by the source database have been distilled into two that contain the essential information for a concessions database. One table (Parks Concessions) represents the concession asset – the place and thing which is being operated – and who holds the contract. The other (Parks Concession Transactions) represents transactions between those contract holders and NYC Parks. Parks Concessions is here https://data.cityofnewyork.us/City-Government/Parks-Concessions/53m8-jdtg and can be joined to Parks Concession Transactions using PersonID, PropertyID and UnitID.

Historic Houses in New York City Department of Parks & Recreation properties.

Citywide street tree data from the 1995 Street Tree Census, conducted by volunteers organized by NYC Parks & Recreation. Trees were inventoried by address, and were collected from 1995-1996. Data collected includes tree species, diameter, condition.

The NYC Parks Events Listing database is used to store event information displayed on the Parks website, nyc.gov/parks. There are seven related tables that make up the this database:

1. Events_Events table (This is the primary table that contains basic data about every event. Each record is an event.)
2. Events_Categories (Each record is a category describing an event. One event can be in more than one category.)
3. Events_Images (Each record is an image related to an event. One event can have more than one image.)
4. Events_Links (Each record is a link with more information about an event. One event can have more than one link.)
5. Events_Locations (Each record is a location where an event takes place. One event can have more than one location.)
6. Events_Organizers (Each record contains a group or person organizing an event. One event can have more than one organizer.)
7. Events_YouTube (Each record is a link to a YouTube video about an event. One event can have more than one YouTube video.)

The Events_Events table is the primary table. All other tables can be related by joining on the event_id. This data contains records from 2013 and on. For a complete list of related datasets, please follow This Link