Update for more robust scraping from NDBC websites#242
Update for more robust scraping from NDBC websites#242krober10nd merged 4 commits intoCHLNDDEV:Projectionfrom
Conversation
|
Thanks! A quick test worked out nicely for the elevation data. producing something like this after writing a fort.15 file. However, if I want to record both elevation and velocity at various stations, it would only populate elevation stations. and if I did just want velocity recording stations: I got an error like this: My other thought is perhaps we could get Anyway thank you again. |
|
I should've mentioned the following thing at the same time. I'm not sure if this is relevant to the error that @krober10nd mentioned, but it seems that the correct way to call the function is different from what the manual suggests. |
|
Also, as far as I could read from the source code, it didn't look like we can have both CO-OPS and NDBC for elevation stations (nor velocity/met stations). I may be wrong about this. |
|
ah yes that makes more sense. We'll have to fix the user guide. By the way, I've already incorporated some of the changes on the Overleaf that you sent through but the appendix still remains out to date. Coming back to this, when I try to add on NDBC data I get this (my mesh covers the entire WNAT so it should have some stations show up) because on 107-108 these indices can't seem to locate any strings with |
|
What do you get if you type in the following line in the matlab console? <pre> |
|
@shinbunya interestingly I get . Maybe it's because I'm in Brasil? |
|
Ah so my browser automatically redirects to |
|
|
|
Fantastic, thanks for updating this! |
|
Thanks guys! |

This makes the following changes for NDBC website scraping: