public read Forest Ecosystem Monitoring Cooperative

705 Spear StreetSouth BurlingtonVermont05403United States of America

(802) 656-0683femc@uvm.eduwww.uvm.edu/femcForest Ecosystem Monitoring Cooperative (FEMC) leadNYC Department of Environmental Conservation The State University of New York (SUNY) College of Environmental Science and ForestrypartnerInvasive plant observation locations were extracted from three databases: (1) iNaturalist research-grade observations (GBIF 2019), (2) EDDMapS (University of Georgia Center for Invasive Species and Ecosystem Health 2019), and (3) iMapInvasives (NatureServe 2019). Each entry was updated with the currently-accepted and previously-accepted scientific names based from ITIS (2019). Previously-accepted scientific names were retained in the case that an invasive plant record was collected using that name. All common names were also retained. We selected only observations made prior to 2012 from states of CT, MA, ME, NH, NJ, NY, PA, RI, VT.Forest Ecosystem Monitoring CooperativeAlexandraKosibaprincipalInvestigatorJamesDuncancontentProviderEmmaTaitcontentProviderColinBeiercontentProviderJustinPerrycontentProviderMatthiasSirchcontentProviderThe Forest Ecosystem Monitoring Cooperative (FEMC) collaborated with Dr. Colin Beier (SUNY-ESF) and the New York State Department of Environmental Conservation to expand on the work by Rockefeller (2016) and Larkin (2017) to examine the risk of invasive plant propagule transport by visitors to trailheads in the Adirondack Park, NY. The Adirondack Park contains over 300 trailheads, each usually has a parking area for visitors and a trail register for each party to record their location of origin. As visitors may travel from areas outside the Park, there is a risk that visitors could unwillingly transport invasive plants on boot treads, dog fur, or clothing that could become established in the Park. While this work only includes visitor data from 2012, it provides valuable information on the possible travel routes, hotspots, and vulnerabilities in invasive plant management in the park. Additionally, summary information on visitor use and travel distances can help with resource allocation and planning.Invasive plant observationsInvasive plant observation locations were extracted from three databases: (1) iNaturalist research-grade observations (GBIF 2019), (2) EDDMapS (University of Georgia Center for Invasive Species and Ecosystem Health 2019), and (3) iMapInvasives (NatureServe 2019). Each entry was updated with the currently-accepted and previously-accepted scientific names based from ITIS (2019). Previously-accepted scientific names were retained in the case that an invasive plant record was collected using that name. All common names were also retained. We selected only observations made prior to 2012 from states of CT, MA, ME, NH, NJ, NY, PA, RI, VT.VMC.1627.3229mySQL/femc/data/archive/project/adktrailheads/dataset/invasive-plant-observations2019-08-012020-01-31COMMON_NAME1COMMON_NAME1The secondary common name of the speciestextCOMMON_NAME2COMMON_NAME2Additional common names for speciestextCOMMON_NAME3COMMON_NAME3Additional common names for speciestextCOMMON_NAME4COMMON_NAME4Additional common names for speciestextCOMMON_NAME5COMMON_NAME5Additional common names for speciestextCOMMON_NAME6COMMON_NAME6Additional common names for speciestextCOMMON_NAME7COMMON_NAME7Additional common names for speciestextCOMMON_NAME8COMMON_NAME8Additional common names for speciestextCOMMON_NAME_PRIMARYCOMMON_NAME_PRIMARYThe primary common name of the speciestextDATEDATEDate of the observationdateYYYY-MM-DDfkOriginGroupIDfkOriginGroupIDThe origin group ID based on a spatial match with the town boundariesintfkOriginIDfkOriginIDThe origin ID based on a spatial match with the town boundariesintJoin_CountJoin_CountNo description for this attributeintmeternaturalOBJECTIDOBJECTIDNo description for this attributeintSCIENTIFIC_NAME1SCIENTIFIC_NAME1Additional scientific names for speciestextSCIENTIFIC_NAME10SCIENTIFIC_NAME10Additional scientific names for speciestextSCIENTIFIC_NAME11SCIENTIFIC_NAME11Additional scientific names for speciestextSCIENTIFIC_NAME12SCIENTIFIC_NAME12Additional scientific names for speciestextSCIENTIFIC_NAME13SCIENTIFIC_NAME13Additional scientific names for speciestextSCIENTIFIC_NAME2SCIENTIFIC_NAME2Additional scientific names for speciestextSCIENTIFIC_NAME3SCIENTIFIC_NAME3Additional scientific names for speciestextSCIENTIFIC_NAME4SCIENTIFIC_NAME4Additional scientific names for speciestextSCIENTIFIC_NAME5SCIENTIFIC_NAME5Additional scientific names for speciestextSCIENTIFIC_NAME6SCIENTIFIC_NAME6Additional scientific names for speciestextSCIENTIFIC_NAME7SCIENTIFIC_NAME7Additional scientific names for speciestextSCIENTIFIC_NAME8SCIENTIFIC_NAME8Additional scientific names for speciestextSCIENTIFIC_NAME9SCIENTIFIC_NAME9Additional scientific names for speciestextSCIENTIFIC_NAME_PRIMARYSCIENTIFIC_NAME_PRIMARYThe primary scientific name of the speciestextTARGET_FIDTARGET_FIDNo description for this attributeint