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 ForestrypartnerThese data were extracted from the Adirondack Trail Registry Database (ADK-TReD; Larkin 2017) (see Adirondack Park trail register data for 2012 dataset in this project). We linked visitor-reported origin data recorded in trail register books to spatial cadastral data (Federal Information Processing Standards, FIPS). If the origin information and the FIPS data could not be matched, we examined the entry to determine if the reported origin was part of a larger town (e.g., boroughs of NYC) or a misspelling. If we could not determine the exact location of a visitor, we removed this entry.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.Adirondack Park hiker origin data for 2012These data were extracted from the Adirondack Trail Registry Database (ADK-TReD; Larkin 2017) (see Adirondack Park trail register data for 2012 dataset in this project). We linked visitor-reported origin data recorded in trail register books to spatial cadastral data (Federal Information Processing Standards, FIPS). If the origin information and the FIPS data could not be matched, we examined the entry to determine if the reported origin was part of a larger town (e.g., boroughs of NYC) or a misspelling. If we could not determine the exact location of a visitor, we removed this entry.VMC.1627.3226mySQL/femc/data/archive/project/adktrailheads/dataset/trail-registry-origin-data2019-08-012020-01-31COUNTYFPCOUNTYFPCounty codeintCOUNTYNAMECOUNTYNAMENo description for this attributetextfkOriginGroupIDfkOriginGroupIDID assigned to towns, towns share a group ID if they are spatially contiguous and in the same countyintNAMENAMEName of towntextNAMELSADNAMELSADExtended town nametextOBJECTIDOBJECTIDNo description for this attributeintpkOriginIDpkOriginIDID unique ID for each town political boundary even if it shares a name and county with another townintShape_AreaShape_AreaNo description for this attributedecimalmeternaturalShape_LengthShape_LengthNo description for this attributedecimalmeternaturalSTATEABBRSTATEABBRState abbreviationtextSTATEFPSTATEFPState codeint