|
Questions presented to small group for response:
- How do we establish specifications for Baseline Mapping Data for mapping of large areas?
- How do we balance data density vs. costs?
- Within the BMD mapping, how do we allow for areas needing additional or higher resolution data that may be required to meet the needs of some program(s)?
- Can this be most cost-effectively accomplished by temporary changes to the routine mapping, or by separate mapping efforts?
M5 Small Group Work:
What comprises a baseline map? ("sea floor" characterization)
- Bathymetry- depth/geomorphology
- Substrate
- Surface sediments
- Sub surface control
- Living Resources
- Shoreline mapping (upland vs. wetland)
- Cultural, archeological (wrecks, etc.)
- Ground truth!
- Specifications
- Driven by user needs (resolution)
- Ground truth
- Repeatability
- QA/QC
- Spatial accuracy (vertical and horizontal)
- Classification (accuracy)
- Regional vs. site specific
- Cost- adhere to regulations/statutes
- Data Density vs. Cost- *what data are needed to define the problem*
- Project life cycle- realistic expectations
- Resolution required based on project (management) needs
- Data type to answer question- management/research
- Evaluate methods
- Study logistics- mobilization, production rates, location of site, etc.)
- Additional data at no additional cost
- COST SHARING
- Higher resolution in specific areas
- Regional overview (lay of the land)
- Site specific (high resolution detailed study)
- Agency (user) coordination
- Cost sharing
- Commonalities
- Changes to routine mapping to accommodate high resolution needs
- Anomalies
- Try to build into existing program (cannot be a "project buster")
- If not feasible-initiate another/secondary program
- Maintain flexibility
- Survey design, operation, etc.
- Site specific falls under "ground truth"
- Routine mapping is most cost effective
- Dependent on temporal variability
- Biomass movement, geology
M5: Baseline Mapping Data plenary comments following small group report:
- No such thing as getting additional data at no additional cost; maybe "minimal" cost but not no cost
- No one brought up there are a lot of projects ongoing across the state at different scales; we need to decide statewide what needs to be done for entire state; need consistency in what is done and shared with everyone
- Working definition of baseline working sets
- Data density vs. costs: frequently defined by different entities; budget may not give you what you need, comes down to lobbying for why/what you need
- should be most cost effective data at what minimum level of data is driving it
- Cost effective is not necessarily "cheap"
- Reps of agencies need to make a case for why they have their needs; don’t be limited by current budgets for defining needs
- National Spatial Data has very land based bias; we need to look at negative elevation; wedge in our needs; land cover should include benthic, that is bottom land cover; content standards
|