Description

Keywords & XML

Citation

• Description

  The U.S. Geological Survey maintains a network of observation wells to measure changes in water level in Chester County in cooperation with the Chester County Water Resources Authority. The water level in these wells is measured monthly. The data are used for drought prediction and management, monitoring the water table in different aquifers and different parts of Chester County, and monitoring and assessing the effects of urbanization on the water table.

• Keywords

  Christina River basin, Pennsylvania, hydrology

  XML Metadata

  criticalzone.org/christina/data/xml-metadata-test/2516/

  XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.

• Citation for This Dataset

  The following is an example of how to cite this website in a publication. U.S. Geological Survey, 2001, National Water Information System data available on the World Wide Web (Water Data for the Nation), accessed [June 10, 2001], at URL [http://waterdata.usgs.gov/pa/nwis/]. You would need to substitute the applicable items enclosed in brackets (remove the brackets too) for the date you accessed the data and URL you are referring to within Water Data for the Nation.

  Citation for This Webpage

  US Geological Survey (2015). "CZO Dataset: Chester County, PA - Groundwater Depth (1951-2015) - USGS." Retrieved 07 Dec 2019, from http://criticalzone.org/christina/data/dataset/2516/

Data

CH 2, Honey Brook, Chester County, PA - Groundwater Depth 1951-current

(=rdb)   Data Level 0

CH 10, West Marlborough, Chester County, PA - Groundwater Depth 1951-current

(=rdb)   Data Level 0

CH 12, West Bradford, Chester County, PA - Groundwater Depth 1951-current

(=rdb)   Data Level 0

CH 38, New Garden, Chester County, PA - Groundwater Depth 1974-current

(=rdb)   Data Level 0

CH 89, East Whiteland, Chester County, PA - Groundwater Depth 1986-current

(=rdb)   Data Level 0

CH 210, Tredyffrin, Chester County, PA - Groundwater Depth 1978-current

(=rdb)   Data Level 0

CH 254, East Nottingham, Chester County, PA - Groundwater Depth 1987-current

(=rdb)   Data Level 0

CH 1201, West Sadsbury, Chester County, PA - Groundwater Depth 1973-current

(=rdb)   Data Level 0

CH 1247, West Vincent, Chester County, PA - Groundwater Depth 1973-current

(=rdb)   Data Level 0

CH 1387, Thornbury, Chester County, PA - Groundwater Depth 1974-current

(=rdb)   Data Level 0

CH 1571, East Vincent, Chester County, PA - Groundwater Depth 1974-current

(=rdb)   Data Level 0

CH 1921, New Garden, Chester County, PA - Groundwater Depth 1974-current

(=rdb)   Data Level 0

CH 2273, West Brandywine, Chester County, PA - Groundwater Depth 1975-current

(=rdb)   Data Level 0

CH 2313, East Whiteland, Chester County, PA - Groundwater Depth 1967-current

(=rdb)   Data Level 0

CH 2328, East Nantmeal, Chester County, PA - Groundwater Depth 1975-current

(=rdb)   Data Level 0

CH 2457, East Goshen, Chester County, PA - Groundwater Depth 1982-current

(=rdb)   Data Level 0

CH 2561,Charlestown, Chester County, PA - Groundwater Depth 1983-current

(=rdb)   Data Level 0

CH 2584, East Marlborough, Chester County, PA - Groundwater Depth 1983-current

(=rdb)   Data Level 0

CH 2663, New Garden, Chester County, PA - Groundwater Depth 1984-current

(=rdb)   Data Level 0

CH 3289, Tredyffrin, Chester County, PA - Groundwater Depth 1988-current

(=rdb)   Data Level 0

CH 5422, Londonderry, Chester County, PA - Groundwater Depth 2000-current

(=rdb)   Data Level 0

CH 6513, North Coventry, Chester County, PA - Groundwater Depth 2002-current

(=rdb)   Data Level 0

CH 6516, Pennsbury, Chester County, PA - Groundwater Depth 2001-current

(=rdb)   Data Level 0

CH 6517, West Caln, Chester County, PA - Groundwater Depth 2001-current

(=rdb)   Data Level 0

CH 6518, Lower Oxford, Chester County, PA - Groundwater Depth 2001-current

(=rdb)   Data Level 0

CH 7007, Wallace, Chester County, PA - Groundwater Depth 2005-current

(=rdb)   Data Level 0

CH 7269, Newlin, Chester County, PA - Groundwater Depth 2008-current

(=rdb)   Data Level 0

Data Use Policy

Data Sharing Policy

• Data Use Policy

  DRAFT v.0.4.0

  1. Use our data freely. All CZO Data Products* except those labelled Private** are released to the public and may be freely copied, distributed, edited, remixed, and built upon under the condition that you give acknowledgement as described below. Non-CZO data products — like those produced by USGS or NOAA — have their own use policies, which should be followed.

  2. Give proper citation and acknowledgement. Publications, models and data products that make use of these datasets must include proper citation and acknowledgement. Most importantly, provide a citation in a similar way as a journal article (i.e. author, title, year of publication, name of CZO “publisher”, edition or version, and URL or DOI access information. See http://www.datacite.org/whycitedata). Also include at least a brief acknowledgement such as: “Data were provided by the NSF-supported Southern Sierra Critical Zone Observatory” (replace with the appropriate observatory name).

  3. Let us know how you will use the data. The dataset creators would appreciate hearing of any plans to use the dataset. Consider consultation or collaboration with dataset creators.

  *CZO Data Products.  Defined as a data collected with any monetary or logistical support from a CZO.

  **Private. Most private data will be released to the public within 1-2 years, with some exceptionally challenging datasets up to 4 years. To inquire about potential earlier use, please contact us.

• Data Sharing Policy

  DRAFT v.0.2.5

  All CZO investigators and collaborators who receive material or logistical support from a CZO agree to:

  1. Share data privately within 1 year. CZO investigators and collaborators agree to provide CZO Data Products* — including data files and metadata for raw, quality controlled and/or derived data — to CZO data managers within one year of collection of samples, in situ or experimental data. By default, data values will be held in a Private CZO Repository**, but metadata will be made public and will provide full attribution to the Dataset Creators†.

  2. Release data to public within 2 years. CZO Dataset Creators will be encouraged after one year to release data for public access. Dataset Creators may chose to publish or release data sooner.

  3. Request, in writing, data privacy up to 4 years. CZO PIs will review short written applications to extend data privacy beyond 2 years and up to 4 years from time of collection. Extensions beyond 3 years should not be the norm, and will be granted only for compelling cases.

  4. Consult with creators of private CZO datasets prior to use. In order to enable the collaborative vision of the CZO program, data in private CZO repositories will be available to other investigators and collaborators within that CZO. Releasing or publishing any derivative of such private data without explicit consent from the dataset creators will be considered a serious scientific ethics violation.

  * CZO Data Products. Defined as data collected with any monetary or logistical support from a CZO. Logistical support includes the use of any CZO sensors, sampling infrastructure, equipment, vehicles, or labor from a supported investigator, student or staff person. CZO Data Products can acknowledge multiple additional sources of support.

  ** Private CZO Repository. Defined as a password-protected directory on each CZO’s data server. Files will be accessible by all investigators and collaborators within the given CZO and logins will be maintained by that local CZO’s data managers. Although data values will not be accessible by the public or ingested into any central data system (i.e. CUAHSI HIS), metadata will be fully discoverable by the public. This provides the dual benefit of giving attribution and credit to dataset creators and the CZO in general, while maintaining protection of intellectual property while publications are pending.

  † Dataset Creators. Defined as the people who are responsible for designing, collecting, analyzing and providing quality assurance for a dataset. The creators of a dataset are analogous to the authors of a publication, and datasets should be cited in an analogous manner following the emerging international guidelines described at http://www.datacite.org/whycitedata.