Guidance and Requirements for Western Alaska LCC Data Management Plans

colonteeSoftware and s/w Development

Nov 4, 2013 (3 years and 7 months ago)

64 views

March 13, 2013

Version 1.0
-

DRAFT

Page
1


Guidance and
Requirements for

Western Alaska LCC

Data Management Plans

(Required for
Western Alaska LCC

Funded Projects)





Modified by Joel Reynolds, Science Coordinator, Western Alaska LCC
(
joel_reynolds@fws.gov
, 907
-
786
-
3914)
from

‘Guidance and Requirements for NCCWSC/CSC Data Management Plans’, v 1.0,
Prepared by the
CSC/NCCWSC
Data Management Working Group
, 29 Feb 2012,
Contact: Emily Fort, Data and IT
Manage
r for the National Climate Change and Wildlife Science Center,
efort@usgs.gov
, 703
-
648
-
4082

Last edit:
28

May

2013

Contents


Requirements for Western Alaska LCC Data Management Plans

................................
................................
..............
2

Background

................................
................................
................................
................................
.............................
2

Why Are Data Management Plans Required?

................................
................................
................................
........
2

Data Management Plan Description and Guidance

................................
................................
...............................
2

Resources

................................
................................
................................
................................
...............................
3

Template for Research Data Management Plan Requirements (RDMP)

................................
...............................
4

Appendix A


Research Data Management Plan, Example 1: initial draft

................................
................................
.
7

Appendix B


Research Data Management Plan, Example 2: more developed

................................
.........................
9

Project Title
Validation of YK Delta Storm Surge Model: Storm Surge Impacts on Biological Resources in the
YK Delta


Part A

................................
................................
................................
................................
.................
9





March 13, 2013

Version 1.0
-

DRAFT

Page
2


Requirements
for
Western Alaska LCC
Data Management Plans

Background

The
Western Alaska LCC

requires a data management plan for all funded projects. This document provides
guidance on what should be included as part of the data management plan.

T
he

required

Research Data Management Plan (RDMP)

includes

information
about data handling and
manag
ement throughout the project’s life cycle
.


The RDMP
includes

detail
s

to ensure that data products are
consistently formatted and documented during development, and that data deliverables are provided with
maximum utility. The RDMP will
help the
LCC

assist

the researcher

with data management activities and make
the project’s data and derived products
widely
available after project completion
.
The RDMP should be
reviewed and enhanced as the project evolves.
The initial version of the RDMP is due withi
n three months of
the proposal being funded
. Following that, the RDMP should be reviewed and updated quarterly
.
The RDMP

include
s

information
about data
used in proposed projects

including
: 1)

data inputs


existing data collections
, 2)
data inputs


colle
ctions of
new field
data

or model output
, and 3) data products and deliverables.

Why Are Data Management Plans Required?

-

Assists with reproducibility of research projects because data are well documented
.

-

Helps ensure data and data products are
accessible and available for the long term.

-

Consistent with the best practices

from m
any funding agencies such as the National Science Foundation
.

Data Management

Plan Description and Guidance

T
he RDMP
distinguishes four categories of
data
:

1.

Data Inputs


E
xisting Collections
;

2.

Data Inputs


New Collections (e.g., data collected from the field, new model output)
;

3.

Data Inputs


Software or Other
Needs

required to generate the new data outputs

(including, for
example, simulation code)
; and

4.

Data Outputs


E
xpect
ed deliverables, datasets, and products
.

Informat
ion should be provided for each
element

as appropriate. If a section is not appropriate (i.e., no new
data are being collected), that
shou
ld be

noted and

no additional information is necessary

for that section
. If
information is not known at the level of detail requested, as much information as possible

should be provided
.

Each input or output requires its own data description table.

The ‘Backup & Storage’ and ‘Access & Sharing’ information in

each data description table refers to the
procedures associated with the local version of the data. For example, if the project uses portions of the
National Elevation Dataset
1

as a ‘Data Input


Existing Collections’, these fields in the data descriptio
n table refer
to the backup procedures for the local version of the downloaded NED data and the access to that local version
(which is most often restricted to the project team).

‘Data Input


New Collections: Citation’ There are increasing number of outl
ets for ‘Data Publications’, and the
National Science Foundation now gives equal weight to data products as they do to peer
-
reviewed publications
2
.

T
he information provided in the R
DMP will be reviewed
and
used to create initial records for the project in
the
LCC’s project tracking tool and in

USGS’ ScienceBase (
https://www.sciencebase.gov/catalog/
)
. The LCC will
contact the principal investigator of each funded project to assist with the development of
the RDMP.




1

National Elevation Dataset, 2013, U.S.
Geological Survey (USGS), Earth Resource Observation and Science Center (EROS).
http://ned.usgs.gov/.

2

http://blogs.library.ucla.edu/dmptool/2012/10/09/data
-
now
-
recognized/

March 13, 2013

Version 1.0
-

DRAFT

Page
3


Resources

Educational Modules on Data Management via the Dataone.org site
. See especially Modules 7 & 8.

https://www.dataone.org/education
-
modules

Metadata authoring tools:

-

search for ‘metadata’ on the ‘Software Tools’ webpage of Dataone.org

-

http://mercury
-
ops2.ornl.gov/OME/

(walks you through the process)

-

http://www.usgs.gov/core_science_systems/csas/metadata/

-

http://www.fgdc.gov/metadata/geospatial
-
metadata
-
tools

-

Alaska Data Integratio
n Working Group metadata standards: forthcoming




March 13, 2013

Version 1.0
-

DRAFT

Page
4


Template for
Research Data Management Plan Requirements

(RDMP)

Project Title:

[Insert Project Title]

Project PI contact:

Name, phone, email

Data Inputs


Existing Collections

1

[Name of Collection]

Description:

Describe the
data

that will be
used, including

its

geographic
(e.g., national, regional,
landscape, etc.)
and temporal
scale
s
.

Format:

Identify the formats in which the data
are

maintained

and made available.

Source:

Identif
y the source for
the data
; provide URLs if appropriate.

Data Processing &
Scientific Workflows:

Describe any data processing steps or provide a scientific workflow
you plan to use to
manipulate the data,
as appropriate.

Backup & Storage:

Describe the approach for backup
and storage of the information associated with the
research project.

What, if any,
local
backup is to be provided for this data input?

This is particularly important if time and expense were incurred in reviewing and
filtering
this
data from an external source prior to use in this research.


Recommend
ed

backup
strategy is to regularly backup
to a managed server
environment. If
that is
not

feasible
, keep a separate local drive off
-
site.


Volume E
stimate
:

Estimate

the volume of in
formation that will be generated:
megabyte (
MB
)
, GB, TB,
or PB.

Access & Sharing:

Prior to the completion of the project,
specify
who should have access to
this portion
of the project data (generally limited to your immediate project team)

and what type
of
access

(
Public,
Read, Write, No Access)
.

Restrictions:

Identify any limitations on access or reuse (e.g., sensitive data, restricted data,
software with license restrictions, etc.). Provide citation or documentation

describing
limitation
s

if due to policies or legal reasons.

Fees:

Identify any fees associated with acquiring the data.

Citation:

Provide citation for
data
source
.



Data Inputs


New Collections

1

[Provide a brief name to describe new data collection]

Description:

Describe the
data

that will be
collected, including

its

geographic
(e.g., national,
regional, landscape, etc.)
and temporal scales
.

Data Management
Budget:

Describe the proposal budget

portion allocated

for data management activities for
the new data collected.

Use a best guess of project dollars or staff time; does not
need to be overly precise.

Format:

Identify the formats in which the data will be generated, maintained, and made
available.

Data Pro
cessing &
Scientific Workflows:

Describe data processing steps or provide a scientific workflow
you plan to use to
manipulate the data,
as appropriate.

Protocols:

Identify any standard protocols or methodologies that will be used to collect the data,
if a
vailable.

Quality Checks:

Specify the procedures for ensuring data quality.

Backup & Storage:

Describe the approach for backup and storage of the information associated with the
research project.

Metadata:

Identify the metadata standard that will be
used to describe the document (FGDC,
ISO, EML, etc.)

March 13, 2013

Version 1.0
-

DRAFT

Page
5


1

[Provide a brief name to describe new data collection]

Volume Estimate:

Estimate

the volume of information generated:
megabyte (
MB
)
, GB, TB, or PB.

Archive Organizations
:

Identify the organization that will be responsible for the long
-
term archive and
pre
servation of the data collected.

Access & Sharing:

Prior to the completion of the project,
specify
who should have access to project
information/products

and what type of
access

(
Public, Read, Write, No Access)
.

Exclusive Use:

Project data and associated

products should be available publically at the end of the
project. If a request to limit access for a period of time after project completion is
needed, please identify the length of time and the reason for the extension. (Request
cannot be more than two

years.)

Restrictions:

Identify any limitations on access or reuse (e.g., sensitive data, restricted data,
software with license restrictions, etc.). Provide citation or documentation describing
limitations if due to policies or legal reasons.

Citation:

Specify how the project’s data should be cited.

M楧楴慬⁏扪散e⁉ 敮瑩晩敲e
⡄佉OIL楮k:

P牯v楤攠a
T楧楴慬iob橥jW⁩摥n瑩晩敲

M佉
)
I汩n欠Wo⁴U攠p牯橥j琠睨敮⁡v慩a慢汹lpub汩捡c汹l

䍯n瑡W琺

P牯v楤攠a⁰ 楮W⡳( o映fon瑡捴c楦ⁱu敳瑩Wn猠慲a獥sr敬慴eT⁴o 瑨攠摡瑡Wa
nT⁡獳o捩c瑥T
p牯Tu捴c
nameⰠ,m慩aⰠ慮,⁰ on攠numb敲⤮



Software and Other Needs

1

[Name of Software or Other Need]

Description:

Describe any software or other needs tha
t are required for the project.

Restrictions:

Identify any limitations on access or reuse that accompany the
software or other needed
items.

Fees:

Identify any fees or other costs associated with acquiring the software or other items.

Source/Link:

Provide a link or a source for the need if available
.


Data Outputs (e.g., Project Deliverables or Products)

1

[Name of Output]

Description:

Describe the data
product, including it geographic and temporal scales
.


Data Management
Budget:

Describe
the
proposal budget

portion allocated

for data management
activities for the
data output.

Format:

Identify the formats in which the data will be generated, maintained, and made
available.


Data Processing &
Scientific
Workflows:

Describe data processing steps or provide a scientific workflow

you plan to use to
manipulate the data
, as

appropriate.

Quality Checks:

Specify the procedures for ensuring data quality during the project.

Backup & Storage:

Describe the approach for backup and storage of the information associated with the
research
project.

Metadata:

Identify the metadata standard that will be used to describ
e the data and products

(FGDC, ISO, EML, etc.)

Volume Estimate
:

Estimate
the vo
lume of information

generated:
megabyte (
MB
)
, GB, TB, or PB.


March 13, 2013

Version 1.0
-

DRAFT

Page
6


Access & Sharing:

Prior to the
completion of the project
,
specify
who should have access to project
information
/products

and what type of
access

(
Public,
Read, Write, No Access)
.

Exclusive Use:

Project data and associated products should be available publically at the end of the
projec
t. If a request to limit access for a period of time after project completion is
needed, please identify the length of time and the reason for the extension. (Request
cannot be more than
a year
.)

Archive
Organizations
:

Identify the organization that will

be responsible for the long
-
term archive and
pres
ervation of the data collected.

Restrictions:

Identify any limitations on access or reuse (e.g., sensitive data, restricted data, software
with license restrictions, etc.). Provide citation or documentation
describing limitations
if
du
e to policies or legal reasons.

I.e.,
indicate specifically what d
ata in the output dataset
needs to be protected from public view and why.

Citation:

Specify how the

project’s data should be cited

(or ‘TBD’).

M楧楴慬⁏扪散e
䥤敮瑩晩敲e(M佉OIL楮k:

P牯v楤攠a⁤楧楴慬iob橥jW⁩摥n瑩晩敲
M佉O
I汩n欠Wo⁴U攠p牯橥j琠睨敮w
av慩a慢汹lpub汩捡c汹l

䍯n瑡W琺

P牯v楤攠a⁰ 楮W⡳( o映fon瑡捴c楦ⁱu敳瑩Wn猠慲a獥sr敬慴eT⁴o 瑨攠摡瑡W慮T⁡獳o捩c瑥T
p牯Tu捴c
nameⰠ,m慩aⰠ慮,⁰ on攠numb敲⤮





March 13, 2013

Version 1.0
-

DRAFT

Page
7


Appendix
A



Research Data Management Plan
,

Example
1: initial draft

Project Title:

Wyoming Landscape Conservation Initiative Integrated Assessment


Data Inputs


Existing Collections

1

Wyoming Geographic Information Center

Description:

This is a collection of over 100 natural resource geospatial datasets

Format:

Shapefile (vector) and

geotiff (raster)

Source:

Various data contributors including: land management agencies (e.g., BLM), University
of Wyoming, and local state agencies.


Data Processing &
Scientific Workflows:

Data download and rasterizing

Backup & Storage:

Handled by Wyo
ming Geographic Information
Science
Center

Volume Estimate:

200 GB

Access & Sharing:

Data distributed by the Wyoming Geographic Information
Science
Center

Restrictions:

Data are publically available with no restrictions.

Fees:

No fees

Citation:

Wyoming GISC Data Server
http://wygl.wygisc.org/DataServer/


2

Bureau of Land Management Disturbance Tracking System

Description:

Disturbance and
reclamation

areas associated with energy development on Bureau of
Land Management areas

Format:

Shapefiles

Source:

Wyoming BLM State Office

Data Processing &
Scientific Workflows:

Data download and rasterizing

Backup & Storage:

Handled by BLM

Volume Estimate:

10

GB

Access & Sharing:

Data distributed by BLM

Restrictions:

No restrictions

Fees:

No fees

Citation:

Not known


Data Inputs


New Collections

No new data will be collected.


Software and Other Needs

1

ArcGIS

Description:

Geographic Information
Software for data processing

Restrictions:

Proprietary/license software

Fees:

USGS provides ArcGIS to USGS staff under an enterprise license agreement. All spatial
processing can be effected using open source geospatial tools.

Source/Link:

http://www.esri.com



2

Python

Description:

Scripting language

March 13, 2013

Version 1.0
-

DRAFT

Page
8


Restrictions:

Open source software

Fees:

No fees

Source/Link:

http://www.python.org



Data Outputs (e.g., Project
Deliverables or Products)

1

WLCI Integrated Assessment

Description:

The Integrated Assessment will result in a set of ESRI grids, shapefiles, and
geodatabases that will allow land managers to assess the resource value associated
with a cell or polygon.
These assessments will cover the WLCI area, the southwest
portion of the state of Wyoming.

Data Management
Budget:

The proje
ct will provide a total of $100
K for data management for FY 11/12. This
includes data storage, data organization support, integrati
on, and custom presentation
utilities along with data protection, storage, backup, replication, and archive.

Format:

Final products will include geotiffs, shapefiles, and python scripts (.py files).

Data Processing &
Scientific Workflows:

Sets of GIS data collected through collaborative efforts get partitioned into four
categories (resource, condition, change agent, and future agent). The datasets are
converted to 30m grids with a common origin, and then
categorically

combined. The
values
of each component grid get normalized, the combined grid converted to an index
value, and the four categorical grids combined. Custom python scripts provide
geoprocessing for resource assessment.

Quality Checks:

The project provides a quality assurance te
am to validate all interim and final products.
ScienceBase provide
s

periodic checksum validation of all repository items, audits all
inputs, and provides reviewable logs.

Backup & Storage:

The project uses ScienceBase for storage, replication, backup, and

archive. This includes
both interim and final products.

Metadata:

FGDC

Volume Estimate:

The final volume (source, interim, and final datasets, metadata, and processing scripts)
will comprise less than 1TB.


Access & Sharing:

Prior to the completion of the project,
only USGS
staff has

access to the data. The USGS
requires review and approval of a publication or data series prior to wider distribution.

Exclusive Use:

All project final and interim datasets will be available afte
r completion of the data series
publication. This will be complete at the conclusion of the project.

Archive
Organizations
:

The USGS Library will maintain the long
-
term repository for the publication, data series,
and datasets.

Restrictions:

All interim
and final products will be released without restriction. Source data contains
both proprietary and sensitive data.

Citation:

The USGS Library provides citation information.

Digital Object
Identifier (DOI)/Link:

The USGS Library provides DOI/Links for pro
ject products.

Contact:

Sarah Doe,
sdoe@agency.gov



March 13, 2013

Version 1.0
-

DRAFT

Page
9


Appendix
B



Research Data Management Plan
,

Example
2
: more developed

Project Title

Validation of YK Delta Storm Surge Model
:
Storm Surge Impacts on Biological
Resources in the YK Delta


Part A


Data Inputs


Existing Collections

1

National Elevation Database

Description:*

Two
-
arc
-
second geospatial digital elevation model (DEM)

Format:

Raster

Source:

United States Geological Survey (USGS)
http://ned.usgs.gov/

Data Processing &
Scientific Workflows:

Data download. Topography extracted for model DEM.

Backup & Storage:

Local backup of downloaded data on secondary and network drives.

Volume Estimate:

1 G
B

Access & Sharing:

Downloaded data access limited to project team.

Restrictions:*

No restrictions

Fees:

No fees

Citation:

National Elevation Dataset, 2013, U.S. Geological Survey (USGS), Earth Resource
Observation and Science Center (EROS)




2

National Land Cover Database (NLCD 2001)

Description:*

Thirty
-
meter resolution geospatial dataset containing 19 land cover types

Format:

Raster

Source:

Multi
-
Resolution Land Characteristics Consortium (MRLC)
http://www.mrlc.gov/

Data Processing &
Scientific Workflows:

Data download. Extracted to estimate topography for low
-
elevation regions of model
DEM.

Backup & Storage:

Local backup on secondary and network drives drive.

Volume Estimate:

250 MB

Access &
Sharing:

Downloaded data access limited to project team.

Restrictions:*

No restrictions

Fees:

No fees

Citation:

Homer, C., Dewitz, J., Fry, J., Coan, M., Hossain, N., Larson, C., Herold, N., McKerrow,
A., VanDriel, J.N., and Wickham, J. 2007.
Completion of the 2001 National Land Cover
Database for the Conterminous United States
.
Photogrammetric Engineering and
Remote Sensing
, Vol. 73, No. 4, pp 337
-
341.


March 13, 2013

Version 1.0
-

DRAFT

Page
10




3

SRTM30_PLUS: Shuttle Radar Topography Mission (SRTM30), COASTAL & RIDGE
MULTIBEAM, ESTIMATED TOPOGRAPHY

Description:*

Thirty
-
arc
-
second geospatial dataset of topography and bathymetry, the latter based
on one
-
arc
-
minute Smith and Sandwell

global model

Format:

ASCII

Source:

Scripps Institution of Oceanography
http://topex.ucsd.edu/WWW_html/srtm30_plus.html

Data Processing &
Scientific Workflows:

Data download and nearest
-
neighbor kriging. Bathymetry extracted for model DEM.

Backup & Storage:

Local backup of downloaded data on secondary and network drives.

Volume Estimate:

10 MB

Access & Sharing:

Downloaded data access limited to project team.

Restrictions:*

No restrictions

Fees:

No fees

Citation:

Global Bathymetry and Elevation Data at 30 Arc Seconds Resolution: SRTM30_PLUS
Marine Geodesy
, Vol. 32, No. 4. (2009), pp. 355
-
371,
doi:10.
1080/01490410903297766

by J. J. Becker, D. T. Sandwell, W. H. F. Smith, et al.




4

Ecosystem Mapping and Topographic Modeling for the Central Coast of the Yukon
-
Kuskokwim Delta

Description:*

One
-
meter resolution geospatial DEM strip over coastal
portion of model domain
derived from LIDAR and vegetative analysis

Format:

Raster and shapefile

Source:

National Wetlands Inventory, US Fish and Wildlife Service


http://www.fws.gov/wetlands/index.html

Data Processing &
Scientific Workflows:

Data download. Topography extracted for model DEM.

Backup & Storage:

Local backup of downloaded data on secondary and network drives.

Volume Estimate:

100 GB

Access &
Sharing:

Downloaded data access limited to project team.

Restrictions:*

No restrictions

Fees:

No fees

Citation:

Not k
nown



March 13, 2013

Version 1.0
-

DRAFT

Page
11



5

Wave Information Studies (WIS)

Description:*

Modeled geospatial wind and wave data as continuous records for 1985 to present
and individual storm records for 1954

1984⸠

䙯牭a琺

䅓䍉C

卯u牣r:

啓⁁牭y⁃o牰猠o映䕮f楮敥r猠sng楮敥爠r敳e慲捨⁡cT⁄敶敬opm敮琠e敮瑥e
䕒M䌩 慮T
䍯慳瑡a⁡湤⁈祤牡 汩捳cL慢o牡ro特
䍈L)
U瑴p:II睩献ws慣攮慲ay.m楬I睩献獨Wml

M慴愠Pro捥c獩sg…
卣S敮瑩晩挠Por武汯睳w

M慴愠
To睮wo慤⸠啴楬.z敤e慳amoT敬⁢eunT慲y⁦ 牣楮g⁤ 瑡W

䉡捫異…⁓瑯牡r攺


Mo睮汯慤敤⁦o牣楮g⁤慴愠 o爠r敬散W敤eT敳e獴or敤n 捡氠摲iv攠睩瑨⁢慣歵kn
獥sonT慲y⁡湤 瑷o牫⁤物v敳e

噯汵m攠䕳瑩Wa瑥:

100 MB

䅣捥獳A☠卨慲ang:


Mo睮汯慤敤⁤e瑡W慣捥獳sm楴敤⁴o⁰牯j散e⁴敡m.

剥獴物r瑩Wns:*

No⁲ s瑲楣瑩ons

䙥敳F

No⁦ 敳

䍩瑡瑩Cn:

Hubertz, J.M., 1992, “User’s Guide to the Wave Information Studies (WIS)
Wave Model: Version 2.0”, WIS Report 27, US Army Corps of Engineers,
Waterwa
ys Experiment Station, Vicksburg, MS, 41 pp.




6

Storm
-
Induced Water Level Prediction Study for the Western Coast of Alaska

Description:*

Modeled geospatial water level data for selected storm records for 1954 to
present.

Format:

ASCII

Source:

US Army

Corps of Engineers Engineer Research and Development Center
(ERDC) and Coastal and Hydraulics Laboratory (CHL)

Data Processing &
Scientific Workflows:

Data download. Utilized as model boundary forcing data.

Backup & Storage:


Forcing data for selected n
odes stored on local drive with backup on
secondary and network drives.

Volume Estimate:

10 MB

Access & Sharing:

Only accessible to project personnel.

Restrictions:*

No restrictions

Fees:

No fees

Citation:

Chapman et al. Storm
-
Induced Water Level
Prediction Study for the Western
Coast of Alaska. US Army Corps of Engineers Engineer Research and
Development Center. October 2009.


March 13, 2013

Version 1.0
-

DRAFT

Page
12




7

Water level time series

Description:*

Water level data collected at multiple locations on the Kashunuk

River during
field studies in 2009 and 2010.

Format:

ASCII

Source:

University of Alaska at Anchorage (UAA)

Data Processing &
Scientific Workflows:

Data is downloaded from water
-
level probes, converted to water level time
series and used for model
validation.

Backup & Storage:

Stored on local drive with backup on secondary and network drives.

Volume Estimate:

10 MB

Access & Sharing:

Only accessible to project personnel.

Restrictions:*

No restrictions

Fees:

No fees

Citation:

None




8

Water
level time series

Description:*

Continuous water level data at two coastal gages located on the Tutakoke River for
2009 to present.

Format:

ASCII

Source:

Torre Jorgenson and USGS Alaska Science Center

Data Processing &
Scientific Workflows:

Data
download. Determination of tidal constituents and validation of forcing data.

Backup & Storage:


Stored on local drive with backup on separate drive.

Volume Estimate:

60 MB

Access & Sharing:

Item is an intermediate data product.

Restrictions:*

No
restrictions

Fees:

No fees

Citation:

None


Data Inputs


New Collections


No new data will be collected.


Software and Other Needs

March 13, 2013

Version 1.0
-

DRAFT

Page
13


1

Delft 3D

Description:*

Comprehensive hydrodynamic modeling suite

Restrictions:*

Proprietary/license software

Fees:*

2000 Euros

Source/Link:

http://www.deltaressystems.com



2

MATLAB

Description:*

Mathematical programming language for data processing

Restrictions:*

Proprietary/license software

Fees:*

UAA

provides
MATLAB

to
UAA

staff

and students under a
license agreement.

Source/Link:

http://www.mathworks.com/products/matlab/



3

ArcGIS

Description:*

Geographic Information Software
(GIS)
for data processing

Restrictions:*

Proprietary/license software

Fees:*

UAA

provides ArcGIS to
UAA

staff

and students under a
license agreement.

Source/Link:

http://www.esri.com


Data Outputs (e.g., Project Deliverables or Products)

1

Inundation index map

Description:*

Geospatial inundation index across model domain. This index, in units of meter
-
days, measures storm surge flood potential based on water level, wind and wave
forcing data for selected representative storms.

Data
Management
Budget:*

40 hours

Format:*

geoTIFF

Data Processing &
Scientific
Workflows:

Raw model output is processed with custom MATLAB scripts to determine
inundation index. Data sets are normalized to aggregate inverse return periods of
included storms,

sampled to 50
-
meter resolution across model domain and
output in various formats.

Quality Checks:*

The project includes multiple stages of validation, both for forcing data and model
setup, utilizing field measurements and time
-
stamped, georeferenced sat
ellite
imagery.

Backup & Storage:

The project uses
multiple local and network hard drives

for storage, replication,
backup, and archive. This includes both interim and final products.

Metadata:

Federal Geographic Data Committee

(FGDC)

March 13, 2013

Version 1.0
-

DRAFT

Page
14


Volume Estimate:

1

GB

Access & Sharing:

Prior to the completion of the project, only
UAA
staff
and involved parties have

access to the data
.

Exclusive Use:*

All project final and interim datasets will be available after completion of the data
series publication. This will

be complete
d

by

the conclusion of the project

or
within one year following the end of the period of performance (whichever is
earliest)

Archive
Organizations:

TBD

Restrictions:*

All interim and final products will be released without restriction.

Citation:

TBD

Digital Object
Identifier
(DOI)/Link:

TBD

Contact:*

Tom Ravens
tmravens@uaa.alaska.edu



2

Inundation index map

Description:*

Geospatial inundation index across model domain. This index, in units of meter
-
days, measures storm surge flood potential based on water level, wind and wave
forcing data for selected representative storms.


Data Management
Budget:*

40 hours

Format:*

shapefile

Data Processing &
Scientific
Workflows:

Raw model output is processed with custom MATLAB scripts to determine
inundation index. Data sets are normalized to aggregate inverse return periods of
included storms, sampled to 50
-
meter resolution acros
s model domain and
output in various formats.

Quality Checks:*

The project includes multiple stages of validation, both for forcing data and model
setup, utilizing field measurements and time
-
stamped, georeferenced satellite
imagery.

Backup & Storage:

Th
e project uses
multiple local and network hard drives

for storage, replication,
backup, and archive. This includes both interim and final products.

Metadata:

Federal Geographic Data Committee

(FGDC)

Volume Estimate:

1 GB

Access & Sharing:

Prior to the completion of the project, only
UAA
staff
and involved parties have

access to the data
.

March 13, 2013

Version 1.0
-

DRAFT

Page
15


Exclusive Use:*

All project final and interim datasets will be available after completion of the data
series publication. This will be complete
d

by

the co
nclusion of the project

or
within one year following the end of the period of performance (whichever is
earliest)

Archive
Organizations:

TBD

Restrictions:*

All interim and final products will be released without restriction.

Citation:

TBD

Digital
Object
Identifier
(DOI)/Link:

TBD

Contact:*

Tom Ravens
tmravens@ua
a.alaska.edu








3

Digital elevation model (DEM)

Description:*

A custom 50
-
meter resolution DEM will be assembled from field measurements,
satellite imagery and topographic and bathymetric models.

Data Management
Budget:*

40 hours

Format:*

geoTIFF

Data Processing &
Scientific
Workflows:

LiDAR strip provides high resolution elevation data for coastal region. Bathymetry
is extracted from SRTM30 data. High elevation data is extracted from NED.
Remaining elevation data is based on NLCD, due to low qual
ity of low
-
elevation,
coastal NED. The resulting aggregate DEM is smoothed, as needed, at constituent
boundaries to eliminate unrealistic elevation gradients and resampled to fifty
-
meter resolution.

Quality Checks:*

Aggregate DEM is tested for inconsisten
cies at constituent DEM boundaries and
compared to field observations.

Backup & Storage:

The project uses
multiple local and network hard drives

for storage, replication,
backup, and archive. This includes both interim and final products.

Metadata:

Federal Geographic Data Committee

(FGDC)

Volume Estimate:

2 GB

Access & Sharing:

Prior to the completion of the project, only
UAA
staff
and involved parties have

access to the data.


March 13, 2013

Version 1.0
-

DRAFT

Page
16


Exclusive Use:*

All project final and interim datasets will be
available after completion of the data
series publication. This will be complete
d

by

the conclusion of the project

or
within one year following the end of the period of performance (whichever is
earliest)

Archive
Organizations:

TBD

Restrictions:*

All final products will be released without restriction.

Citation:

TBD

Digital Object
Identifier
(DOI)/Link:

TBD

Contact:*

Tom Ravens
tmravens@uaa.alaska.edu



4

Storm
-
Induced Water Level Prediction Study for the Western Coast of Alaska

Description:*

Modeled geospatial water level data for selected storm records for

1954 to
present.

Data Management
Budget:*

20 hours

Format:*

ASCII

Data Processing &
Scientific
Workflows:

Data download. Utilized as model boundary forcing data.

Quality Checks:*

Water levels from selected nodes of the data set are compared to
observed water
levels at coastal gages over identical time periods.

Backup & Storage:

The project uses
multiple local and network hard drives

for storage, replication,
backup, and archive. This includes both interim and final products.

Metadata:

Federal
Geographic Data Committee

(FGDC)

Volume Estimate:

10 MB

Access & Sharing:

Prior to the completion of the project, only
UAA
staff
and involved parties have

access to the data.

Exclusive Use:*

All project final and interim datasets will be available after

completion of the data
series publication. This will be complete
d

by

the conclusion of the project

or
within one year following the end of the period of performance (whichever is
earliest)

Archive
Organizations:

TBD

Restrictions:*

All interim and final
products will be released without restriction.

March 13, 2013

Version 1.0
-

DRAFT

Page
17


Citation:

Chapman et al. Storm
-
Induced Water Level Prediction Study for the Western
Coast of Alaska. US Army Corps of Engineers Engineer Research and
Development Center. October 2009.

Digital Object
Identif
ier
(DOI)/Link:

TBD

Contact:*

Tom Ravens
tmravens@uaa.alaska.edu



5

Water level time series

Description:*

Water level data collected at multiple locations on the Kashunuk River during field
studies in 2009 and 2010.

Data Management
Budget:*

20 hours

Format:*

ASCII

Data Processing &
Scientific
Workflows:

Data is
downloaded from water
-
level probes, converted to water level time series
and used for model validation.

Quality Checks:*

Water gages calibrated prior to deployment and secured to eliminate movement.

Backup & Storage:

The project uses
multiple local and n
etwork hard drives

for storage, replication,
backup, and archive. This includes both interim and final products.

Metadata:

Federal Geographic Data Committee

(FGDC)

Volume Estimate:

10 MB

Access & Sharing:

Prior to the completion of the project, only
UAA
staff
and involved parties have

access to the data.

Exclusive Use:*

All project final and interim datasets will be available after completion of the data
series publication. This will be complete
d

by

the conclusion of the project

or
within one year fo
llowing the end of the period of performance (whichever is
earliest)

Archive
Organizations:

TBD

Restrictions:*

All interim and final products will be released without restriction.

Citation:

None

Digital Object
Identifier
(DOI)/Link:

TBD

Contact:*

Tom Ravens
tmravens@uaa.alaska.edu


*Indicates that this informati
on is also collected for the PDMP.