Data Management PlanDMP Template v2.0.1 (2015-01-01)

Please provide the following information, and submit to the NOAA DM Plan Repository.
Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits
provisions from a higher-level DM Plan already submitted to the Repository, then this more-specificPlan only needs to provide information that differs from what was provided in the Master DM Plan.
URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
1. General Description of Data to be Managed
1.1. Name of the Data, data collection Project, or data-producing Program:
Demographic Trends (1970-2010) for Coastal Geographies
1.2. Summary description of the data:
The Demographic Trends (1970-2010) were derived from Census Block Group Data for
13 different coastal geographies. For a full listing of the geographies available, see: http://
www.coast.noaa.gov/htdata/SocioEconomic/DemographicTrends/
DemographicTrends_DataDescription.pdf. The land area reported in the county andstate file are the 2010 land areas reported in the attribute table of the shapefiles
provided by Census.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
1.4. Actual or planned temporal coverage of the data:
1970 to 2010
1.5. Actual or planned geographic coverage of the data:
W: -178.217598, E: -66.969271, N: 71.406235, S: 18.921786
1.6. Type(s) of data:(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
1.7. Data collection method(s):(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy,
research vessel, autonomous underwater vehicle, animal tagging, manual surveys,
enforcement activities, numerical model, etc.)
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
1.8.1. If data are from another observing system, please specify:

Data Management Plan Template, v2.0.1

Effective 2015 Jan 01

Page 1 of 5

Data Management PlanDMP Template v2.0.1 (2015-01-01)

2. Point of Contact for this Data Management Plan (author or maintainer)
2.1. Name:NOAA Office for Coastal Management (NOAA/OCM)
2.2. Title:
Metadata Contact2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
2.4. E-mail address:
coastal.info@noaa.gov
2.5. Phone number:(843) 740-1202
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management ofthe data produced by their Program. Please indicate the responsible party below.
3.1. Name:
3.2. Title:
Data Steward
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
4.1. Have resources for management of these data been identified?
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):

5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality,objectivity, utility, and integrity of information which it disseminates.
5.1. Processing workflow of the data from collection or acquisition to making it publicly
accessible(describe or provide URL of description):
Process Steps:- 2011-01-01 00:00:00 - The Census 1990 and 2000 block group data were obtainedfrom Geolytics - CensusCDs - Long Form SF3, Release 2.1. The 2010 block group data
were obtained from the Census Bureau. For these 1990, 2000, and 2010, Census

Data Management Plan Template, v2.0.1

Effective 2015 Jan 01

Page 2 of 5

Data Management PlanDMP Template v2.0.1 (2015-01-01)

Block Group polygons were imported into a GIS system to assign these polygons topolitical, place-based management program boundaries, and watershed/otherjurisdictions. Estimates were obtained through a GIS overlay operation of Census
Block Groups with all boundaries or study areas of interest. Block Groups that fellpartially in the areas of interest were prorated by area to be included in theestimates (block group area proration methodology). The demographic variables
data of block groups were then summarized by the study areas of interest. The
exception of this process is County and State level estimates which were obtainedby summarizing the demographic variables by the existent appropriate geographycode in the file associated to each Census Block Group data. For description ofjurisdictions or geographies used in STICS, refer to http://coastalsocioeconomics.
noaa.gov/coast_defined.html. (Citation: 1970 Census data)
5.1.1. If data at different stages of the workflow, or products derived from these
data, are subject to a separate data management plan, provide reference to otherplan:
5.2. Quality control procedures employed (describe or provide URL of description):

6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented,
specifies the use of ISO 19115 and related standards for documentation of new data, and provides
links to resources and tools for metadata creation and validation.
6.1. Does metadata comply with EDMC Data Documentation directive?
No
6.1.1. If metadata are non-existent or non-compliant, please explain:
Missing/invalid information:- 1.6. Type(s) of data
- 1.7. Data collection method(s)- 3.1. Responsible Party for Data Management- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to datamanagement- 5.2. Quality control procedures employed- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected- 7.3. Data access methods or services offered- 7.4. Approximate delay between data collection and dissemination- 8.1. Actual or planned long-term data archive location- 8.3. Approximate delay between data collection and submission to an archive
facility

Data Management Plan Template, v2.0.1

Effective 2015 Jan 01

Page 3 of 5

Data Management PlanDMP Template v2.0.1 (2015-01-01)- 8.4. How will the data be protected from accidental or malicious modification ordeletion prior to receipt by the archive?
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
6.2.1. If service is needed for metadata hosting, please indicate:
6.3. URL of metadata folder or data catalog, if known:
https://www.fisheries.noaa.gov/inport/item/48000
6.4. Process for producing and maintaining metadata(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation
Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PDData_Documentation_v1.pdf
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution isexplicitly limited by law, regulation, policy (such as those applicable to personally identifiable
information or protected critical infrastructure information or proprietary trade information) or by
security requirements. The EDMC Data Access Procedural Directive contains specific guidance,
recommends the use of open-standard, interoperable, non-proprietary web services, provides
information about resources and tools to enable data access, and includes a Waiver to be submitted
to justify any approach other than full, unrestricted public access.
7.1. Do these data comply with the Data Access directive?
7.1.1. If the data are not to be made available to the public at all, or withlimitations, has a Waiver (Appendix A of Data Access directive) been filed?
7.1.2. If there are limitations to public data access, describe how data are protectedfrom unauthorized access or disclosure:
7.2. Name of organization of facility providing data access:
NOAA Office for Coastal Management (NOAA/OCM)
7.2.1. If data hosting service is needed, please indicate:
7.2.2. URL of data access service, if known:
7.3. Data access methods or services offered:

Data Management Plan Template, v2.0.1

Effective 2015 Jan 01

Page 4 of 5

Data Management PlanDMP Template v2.0.1 (2015-01-01)

7.4. Approximate delay between data collection and dissemination:
7.4.1. If delay is longer than latency of automated processing, indicate under what
authority data access is delayed:

8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how toidentify, appraise and decide what scientific records are to be preserved in a NOAA archive.
8.1. Actual or planned long-term data archive location:(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To
Be Determined, Unable to Archive, or No Archiving Intended)
8.1.1. If World Data Center or Other, specify:
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office for Coastal Management - Charleston, SC
8.3. Approximate delay between data collection and submission to an archive facility:
8.4. How will the data be protected from accidental or malicious modification ordeletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage
relevant to the data collection

9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.

Data Management Plan Template, v2.0.1

Effective 2015 Jan 01

Page 5 of 5