E-mails R. Avaltroni 2002

NYC 9/11 Public Portal Document

architecture and how it will link environmental data to geo-coded maps of lower Manhattan. Representatives of EPA, NYC Board of Education, NYS DOH, NYS DEC, NYC HPD, NYC DOB, DCAS and OSHA are requested to attend this meeting and participate in deciding the best means of managing this information. Please bring information on the structures of your databases and sample data printouts. The purposes of the inventory have been elucidated but not how the final product will look or how it will work. I'm taking a stab at this for the purpose of framing our discussion on the database architecture.

- The initial screen will be a map of lower Manhattan, similar to EPA maps found at http://www.epa.g0v/epah0me/wtc/index.html#m0nit0ring

- The user can view ambient environmental data points by selecting an environmental parameters and timeframes

- The user can zoom in on any neighborhood and select an individual building. Basic characteristics will be displayed for a selected building, including: Block / Lot / BIN etc. - to be defined

- Whether the building is scheduled to be cleaned or has been cleaned by DEP contractors or other parties will be noted

- Environmental monitoring data obtained from within or on the exterior of the building (if any) will be presented in summary fashion - to be defined (some data may not be accessible to the public for legal reasons)

- Selecting a specific parameter on the data summary page will call up spreadsheets containing detailed environmental monitoring data for that parameter

The environmental data present complexities. We have probably >200,000 individual analytical results. Some buildings will have no environmental data; others will have a large amount of data across a variety of contaminants, as well as variations in reporting formats, sampling durations, sampling methods, units of measurements, etc. We need to decide whether it is desirable/feasible to "clean and standardize" all the environmental data or present data sets as they currently exist, with consideration of the costs and timeframes associated with these options.

Meeting Agenda:

- The "end product” - what we want it to provide and when we want it to be functional - Update on buildings inventory - Develop a list of all building characteristics fields - Identify all environmental data sets by agency - "Clean & standardize" v. data "as is" - Database architecture development: process and timeframe

NYC-WTC_000160954