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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
Tropical Cyclone Wind Exposure (Eastern Pacific, 1987-2016)
1.2. Summary description of the data:

These data represent modeled, historical exposure of U.S. offshore, coastal, and international waters to tropical cyclone activity within the Eastern Pacific Ocean basin (1987-2016). BOEM Outer Continental Shelf Lease Blocks were used to construct the grid by which exposure was quantified. Exposure was quantified using intersecting storm tracks, overlapping wind intensity areas, and mathematical return intervals. Symbology is based on the modeled occurrence of tropical storm force (34-knot) or greater winds per lease block. Due to the way winds were calculated differently over land and over water, the interpretation of wind exposure metrics within coastal areas should be interpreted carefully. Data represent past climatology only and do not suggest predicted future impacts or exposure.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
Edit
1.3. Is this a one-time data collection, or an ongoing series of measurements?
No information found
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Edit
1.4. Actual or planned temporal coverage of the data:
No information found
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Edit
1.5. Actual or planned geographic coverage of the data:
W: -115.96093920878, E: -179.99998590213, N: 74.99635398335, S: 15.95616534695
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
Edit
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
No information found
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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Person
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
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Organization
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
2.4. E-mail address:
coastal.info@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
(843) 740-1202
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
No information found
Taken From: Support Roles (Data Steward) | Person
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
3.2. Position Title:
Data Steward
Always listed as "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?
No information found
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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:

  • 2018-08-01 00:00:00 - CREATE THE GRID 1. Within the Pacific Ocean basin, download the OCS lease blocks as the grid by which exposure will be modeled. 2. Remove all unnecessary fields and modify attributes as needed.
  • 2018-09-01 00:00:00 - MODELING EXPOSURE 23. Buffer each (Eastern Pacific) subset (Cat 1, Cat 2, etc.) based on the respective MEW calculations (34 data sets total). Set Side Type field to right or left, depending on the buffer being run. Merge respective wind speed buffers (34kt, 50kt, 64kt) and then dissolve by storm ID (Serial_Num), storm name (Name), and season (Season). 24. Perform Spatial Join of the composite grid and buffers (34kt, 50kt, 64kt) to generate wind threshold counts per grid cell. 25. Perform Spatial Join of the composite grid and IBTrACS storm segments to generate storm segment counts per block. 26. Join count values of all outputs (34kt, 50kt, 64kt, and segments) together, based on the gridID field. 27. Calculate an average "return interval" value (30 years / count) per grid cell for each wind threshold (34kt, 50kt, 64kt). 28. Remove all unnecessary fields and populate others according to data dictionary.
  • 2018-08-01 00:00:00 - CLIMATOLOGY STEPS (MEW calculations) 3. Using the Extended Best Track (EBT) dataset (NOTE: this is an Atlantic Ocean basin data set), calculate the Maximum Extent of Winds (MEW) values following these steps. MEW are wind radii distances per standard wind threshold (34kt, 50kt, 64kt). 4. From http://rammb.cira.colostate.edu/research/tropical_cyclones/tc_extended_best_track_dataset/data/ebtrk_atlc_1988_2016.txt, right-click and save the EBT data (1988-2016) as a text file and open in Excel, setting custom fixed-width columns within the import wizard. Insert missing column breaks where necessary and set the width carefully, capturing the appropriate characters per column. Save file. 5. Assign each column a field name based on metadata here: (http://rammb.cira.colostate.edu/research/tropical_cyclones/tc_extended_best_track_dataset/docs/ebtrk_readme.txt). 6. Remove all EBT features in which storm type equals L, W, or D. (NOTE: No storm type values of 'D' were noted in the EBT data, even though the designation is stated within the metadata.) 7. Remove -99 values within fields. 8. Remove features if wind radii values in all four quadrants are zero. Per feature, even if only one of the four quadrants (per wind threshold) has a value above zero, retain the zero values in the other three cells for that wind threshold. 9. Remove all features with maximum wind values below 34 knots. (By definition, no wind radii values exist for EBT features with maximum winds below 34 knots, so these features are not relevant for MEW calculations.) 10. Modify the "longitudeWest" column by converting the values to negative values, so that features will plot appropriately (i.e. in the eastern hemisphere). Where necessary, convert longitude values within the eastern hemisphere by subtracting the value from 360. 11. Add the modified EBT data to ArcMap and export table as feature class. 12. Perform Select By Location, where all EBT points occurring over land (using a global countries layer) are selected. Include a 150nm buffer of the countries layer (with small islands removed) to select those EBT points occurring over land. (This is based on tropical cyclone literature, from Kruk 2010.) Export these selected features as a new feature class. These features will be used to calculate the average MEW values (buffer distances) for overland storm track segments. Switch the selection to select those features over water only. Export these selected features as a new feature class. These features will be used to calculate the average MEW values (buffer distances) for overwater storm track segments. If any overwater points exist over the Pacific Ocean basin, remove these. 13. For the overwater feature class, generate (storm) "category" values in a new field, based on wind speed values (see http://www.nhc.noaa.gov/aboutsshws.php). Due to the low sample of Cat 5 storms (1988-2016 = 28 points), combine these storms' (EBT points) wind radii values with the Cat 4 points when calculating MEW. 14. For the overland feature class, generate (storm) "category" values in a new field, based on wind speed values (see http://www.nhc.noaa.gov/aboutsshws.php). Due to the low sample of Cat 5 storms (1988-2016 = 24 points), combine these storms' (EBT points) wind radii values with the Cat 4 points when calculating MEWs. 15. Calculate MEW values per category for the overwater and overland features (separately) and record in a table. Compute averages for right (northeast, southeast) and left (northwest, southwest) quadrants. 16. Multiply all values by 0.67 to compute buffers for Eastern Pacific (EPAC) storms. This calculation is based on literature that has compared tropical cyclone sizes across global basins. This literature notes that wind swaths of EPAC tropical storms are approximately 33% smaller than North Atlantic tropical storms. (NOTE: size proportions between the North Atlantic and Eastern Pacific storms are variable within the literature.)
  • 2018-08-01 00:00:00 - STORM TRACKS STEPS 17. Extract those features in the IBTrACS data that are: 1) attributed to the Eastern Pacific (EP) basin; 2) occur in or after 1987; and 3) have maximum wind values above 33 knots. 18. Extract those features (per basin) that are attributed as extratropical (ET), subtropical (SS), or tropical (TS). The Eastern Pacific only had one feature denoted at subtropical, so it was removed and not included in the exposure modeling. 19. Feature (segments) from EPAC that crossed the International Dateline were trimmed, as these features cause issues when running the buffer tool in subsequent steps. 20. Create a (storm) "Category" field. For features (per basin) that are tropical storms ('TS'), modify the field value to the appropriate category, based on wind speed (see http://www.nhc.noaa.gov/aboutsshws.php). Also designate features as 'ET', 'SS', or 'TS' accordingly. 21. Separate the overland and overwater storm segments into separate feature classes. Do this by extracting all segments "completely contained" within the "land + 150nm buffer" layer. (NOTE: This was only done for the North Atlantic segments. The vast majority of Eastern Pacific segments (about 99%) within BOEM's Pacific lease blocks do not occur over land. Additionally, the MEW values for segments that do intersect land (i.e. Hawaiian Islands) compared to MEW values over water would be very minimal.) 22. Separate EPAC storm segments by the seven categories (SS, ET, TS, 1, 2, 3, 4/5) into separate layers. (NOTE: For the ET, SS, and TS subsets, make additional subsets of these for the following segments: a) segments =34-49kt; b) segments =50-63kt; and c) segments >=64kt. This is required since not every ET, SS, and TS segment has winds greater than 50kt or 64kt, like Cat 1-Cat 5 segments do by definition.)
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 other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

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.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 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.2. Name of organization of facility providing data access
  • 7.2.1. If data hosting service is needed, please indicate
  • 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?
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
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_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
No information found
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:
No information found.
7.2. Name of organization of facility providing data access:
No information found
Taken From: Support Roles (Distributor) | Organization
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
7.2.1. If data hosting service is needed, please indicate:
No information found
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
Edit
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Edit
7.3. Data access methods or services offered:
No information found
7.4. Approximate delay between data collection and dissemination:
No information found
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 to identify, 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)
No information found
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
Edit
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Edit
8.2. Data storage facility prior to being sent to an archive facility (if any):
Partial information found
Charleston, SC
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Edit
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank