1 / 10

Accessible BMP data in the NYC watershed ag program

Accessible BMP data in the NYC watershed ag program. Steve Pacenka, volunteer data censor with WAP and Cornell BEE staff 10 June 2009 for CEAP review. Basic WAC data policy. Intention: protect privacy of farmers Intention: maintain separation between farmers and regulators

kristian-vidar
Download Presentation

Accessible BMP data in the NYC watershed ag program

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Accessible BMP data in the NYC watershed ag program Steve Pacenka, volunteer data censor with WAP and Cornell BEE staff 10 June 2009 for CEAP review

  2. Basic WAC data policy • Intention: protect privacy of farmers • Intention: maintain separation between farmers and regulators • Default: all data confidential between farmer and selected WAP staff

  3. Access to data for science (2007) • Release mechanism: • signatures including each covered farmer • access by named individuals only • Bulk data: censored detail data if not traceable to farm directly or indirectly • Cornell received censored detail data for Cannonsville farms, and uncensored data from two farms.

  4. BMP related data held at WAC(as of early 2008) • Nutrient management plans - full detail, very complete history; xls and mdb files • Field maps - good map history since about 2000; ESRI shapefiles • BMPs - WAC approval records, contracts, engineering documents, spending spreadsheets; eclectic storage, hard for someone not knowing the farm to identify history and BMP locations

  5. Data released to Cornell: counts of BMP types by major subbasin • From a payment tracking database • Each of five subbasins of Cannonsville • Uncensored counts except low end blurred as 0-6 to prevent indirect disclosure. • 128 distinct types • Text description by code, chosen manually as representative of several descriptions used for that code in WAC data • Nothing about dimensions or costs of BMPs (data are in WAC's set, but not well proofread)

  6. Structure of BMP tallies Example description: NRCSCODE 194= "Barnyard water management system" (Numbers not available to people who have not signed data agreement.)

  7. Five HUC subbasins for BMP tally

  8. Data released to Cornell: field level details • Data: Field size, and presence/absence of certain funded BMPs: crop rotation, riparian buffer, drainage, tree planting (w/description) • Field is not identified spatially. • Time when BMP established not available. • This was not ready for release due to weak data quality – fixable, expensive; BMP records are tagged with a field ID when they are paid for, but this ID was never updated -- thus BMPs can disappear on later maps.

  9. Data released to DEP from nutrient management plans • Records: one per field per year covered by any NMP; 2000-2005 • Fields identified by an obfuscated ID that is consistent over time; doesn't work for split and joined fields • Attributes: crop, soil type, dryness index, Morgan’s P, rounded animal units on associated farm, computed P indices, rough manure P application rate, old hydrologic sensitivity code, a couple of funded BMPs • Future?: improved time tracing using consecutive map overlays, 2006+2007 data, hopefully 1999

  10. Discussion: Usability of WAC BMP Records in Modeling • BMP counts for the five subbasins. • Make friends with more than two farmers. • Fund WAP (if willing) to improve pilot BMP database quality. Associate field-level BMPs with points or polygons. Provide other field attributes as in the NMP retrieval.

More Related