Data Management Plan
Office for Coastal Management
Data Set (DS) | Cat ID: 54374 | Published / External
Data Management Plan
DMP 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-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
This is a derivative product that only contains districts within 12 Nautical Miles and the three closest to the U.S. coastline created specifically for the MarineCadastre.gov Ocean Reporting Tool. The 2016 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. SLDU stands for State Legislative District Upper Chamber. State Legislative Districts (SLDs) are the areas from which members are elected to state legislatures. The SLDs embody the upper (senate) and lower (house) chambers of the state legislature. Nebraska has a unicameral legislature and the District of Columbia has a single council, both of which the Census Bureau treats as upper-chamber legislative areas for the purpose of data presentation; there are no data by SLDL for either Nebraska or the District of Columbia. A unique three-character census code, identified by state participants, is assigned to each SLD within a state. In Connecticut, Illinois, Louisiana, Maine, Maryland, Massachusetts, Michigan, Ohio, and Puerto Rico, the Redistricting Data Program (RDP) participant did not define the SLDs to cover all of the state or state equivalent area. In these areas with no SLDs defined, the code "ZZZ" has been assigned, which is treated as a single SLD for purposes of data presentation. The boundaries of the 2016 state legislative districts were provided by state-level participants through the RDP and reflect the districts used to elect members in or prior to the November 2016 election.
Notes: Only a maximum of 4000 characters will be included.
Edit
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Edit
Notes: All time frames from all extent groups are included.
Edit
Notes: All geographic areas from all extent groups are included.
Edit
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(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.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Edit
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
Edit
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
Edit
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
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.
(describe or provide URL of description):
Process Steps:
- 2018-03-26 00:00:00 - Created a 12 NM buffer around the coast line. Selected the overlapping polygons (also the three closest polygons to the coast) and extracted them to a new feature class.
- 2018-04-26 00:00:00 - The American Samoa Districts were received from the American Samoa Coastal Management Program. American Samoa Counties were used to designate the administrative district of Manu'a, which is made up of the counties on the islands of Ofu, Olosega and Ta'u (the Manu'a group).The counties file originates from the American Samoa Atlas of 1981. Villages on the islands of Tutuila and Aunu'u in American Samoa were dissolved to make up the Eastern and Western Districts. The villages file originates from the American Samoa Atlas of 1981.
- 2018-03-26 00:00:00 - Downloaded individual state shapefiles from the US Census Bureau. Merged all shapefiles into one feature class. Projected into World Mercator
- 2018-03-26 00:00:00 - Added attributes for StateName, INTPTLON, INTPTLAT, NAMELSAD. The NAMELSAD attribute is a combination between NAME and the domain value associtted with the LSAD attribute. LA, MA, MD, and PR had waterway slivers coded as "State House Districts not defined" which were removed from the dataset. The StateName is based off of the StateEFP and the INTPTLON/INTPTLAT are the Longtitude and Latitude Coordinates of the polygons Centroid
- 2018-04-25 00:00:00 - U.S Territories districts of the Commonwealth of the Northern Mariana Islands, Guam, and the U.S. Virgin Islands were downloaded from the US Census Bureau TIGER/Line- Island Areas Demographic Profiles and processed as follow: Virgin Islands sub districts were dissolved into the two separate main districts of St. Croix and St. Tomas/St. John. Then merged into the coastal State Legislative Districts- House FC.
Edit
(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.
Missing/invalid information:
- 1.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the 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 data management
- 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.2. Data storage facility prior to being sent to an archive facility
- 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 or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly 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.
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Edit
Notes: This field is required if a Distributor has not been specified.
Edit
https://coast.noaa.gov/arcgis/rest/services/OceanReportingTool/
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Edit
Notes: This field is required if applicable.
Edit
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(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)
Notes: This field is required if archive location is World Data Center or Other.
Edit
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Edit
North Charleston, SC
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Edit
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.
