Skip to main content

Example stakeholder input session prompts

For inaugural stakeholder meeting:

image.png

Crowdsourced Bathymetry (CSB) in Tampa Bay/Florida  

Developing a Stakeholder-Driven Process  

Stakeholder Input Session #1: Awareness and use of bathymetric information 
  1. Do you currently use seafloor mapping information? If so, what are your sources of information? 


  1. Do current seafloor mapping products meet your needs?  


  1. Can you provide an example of personal and/or professional benefit that might result from participating in CSB data collection and/or using information generated from CSB activities? 

 

Stakeholder Input Session #2: Acquiring CSB Information 
  1. What features would you want to see on a data logging system, from set-up to use?  


  1. Do you have current capabilities that would allow you to participate in CSB with minimal adjustments to your activities/operations? 


  1. What are the major internal and external barriers to CSB participation (e.g., logistics, resources to purchase loggers, instrument and data sharing knowledge and use, long-term leadership of CSB program; see pipeline reference) 


  1. Is remaining an anonymous data provider important to you/your organization?  

 

Stakeholder Input Session #3: Sustaining CSB Data Collection 
  1. What types of incentivization could encourage participation in CSB data collection?  


  1. How should or could CSB data be used to ensure we’re not “collecting data for data’s sake” 

 
  1. What assurances would you need to confidently use CSB data? (e.g., concern about liability for data you provide and/or accuracy of data you use) 

 

For second stakeholder meeting:

image.png

Crowdsourced Bathymetry (CSB) in Tampa Bay/Florida  
Developing a Stakeholder-Driven Process  

Stakeholder Input Session #1: Practical Implementation of CSB in Tampa Bay
  1. What is the best way to implement CSB? What might be some possible challenges? More importantly, solutions?   


  1. Based on what’s been discussed about participant expectations (e.g. physically installing loggers, downloading and sending data), are any of these concerning to participants? Alternatives and solutions? 


  1. What issues do you see preventing your participation? Can these barriers be overcome or are they non-starters? 


  1. What types of incentivization could encourage, and more importantly SUSTAIN participation in CSB data collection? 

 

Stakeholder Input Session #2: Products Derived from CSB Data 
  1. A (near) real-time change map may be a “holy grail” product, but this will require significant R&D. What are other products of interest and/or use? What file types/formats? What does “timely” data mean to you? 


  1. For the maps that you may use currently for maritime navigation, research, management, etc., what’s missing and does it appear that CSB can fill in those gaps? 


  1. What assurances would you need to confidently use CSB data? (e.g., error/accuracy, liability)