I am trying to run the coastal vulnerability model for an area of coast on the Red Sea, but finding an error related to WaveWatchIII: “ValueError: No WaveWatchIII points were found near the area of interest. Is the area of interest far outside the coverage of [WaveWatchIII global dataset]”
Looking at the WaveWatchIII data, it looks like there are no data points within the Red Sea itself. Is there an alternative data source (or perhaps an interpolated version of the WaveWatchIII data) that covers the Red Sea?
Hello @pgs and welcome to the forums! I’m sorry that we haven’t responded to you until now. In case you hadn’t already found a similar post here, this issue is likely because the AOI is too far away from the coverage of the WaveWatchIII dataset. You can see another thread where this was discussed over here: Coastal Vulnerability Model - getting started - #5 by dave
Hi @pgs, were you able to find a solution to this? i am currently looking to run a coastal vulnerability model as well for a place in the red sea but notice through this forum that WWIII does not cover some extants.
I’m still trying to figure out the best approach to take given my own constraints - it would be great to talk through this if you’re up for it. I’ll send you a message.
I was wondering what file type i should request it in? They have a bunch of options like .csv, esriAscii, .geotif, .kml, but no shapefile. What file type can i request Wavewatch3 data in?
Unfortunately, since the Red Sea isn’t included in the WaveWatchIII dataset, the query turns up with just null values. I’m hoping a future iteration of the WaveWatch data will go beyond open open ocean, but for now it seems like other data has to be used (seems like ERA5 reanalysis might be the best option). Please let me know if you find a good alternative!
