| Image may be NSFW. Clik here to view.  |
| Fig. 1Golomb Ruler |
I downloaded updates which I will be posting in a day or so (WOD Updates).
They are May 2016 updates.
They threw me a curve by mixing casts from different zones in 4 large files (CTDS, CTDO, PFLS, and PFLO) of 205.7 MB + 15.6 MB +703.5 MB +83.1 MB = 1007.9 GB, covering about 434 different WOD zones.
I had to write a module to go through those files, byte by byte, to identify, then separate the casts in those files, and place them in files with other casts from the same zone (e.g. all 1212 zone casts in one 1212 file).
| Image may be NSFW. Clik here to view.  |
| Fig. 2 |
| Image may be NSFW. Clik here to view.  |
| Fig. 3 |
That meant that I also had to rewrite the WOD zones database engine, because the only way in general you can tell what WOD zone a cast came from is the name of the file (e.g. CTD01212, and all casts in it, are from zone 1212).
Absent that, when they are all mixed up, the latitude and longitude is the only clue as to where the measurements came from.
Finding those particular latitude and longitude values within the "PI stream" is at first daunting.
Now that I am accustomed to it, it does not take too long.
Nevertheless, I have been busy, as you can see by Fig. 2 and Fig. 3,
Those are screen captures of the directory the resulting files were stored in (the 4 files at the end of Fig. 3 are the WOD update files, the other 584 files came out of those 4).
The files are named according to the WOD zone the data came from.
Anyway, that said, let's admit that WOD is a popular, quality place for the scientists who study the ocean and the influence the ocean has on weather and climate:
"Also, forecasters at NOAA’s Ocean Prediction Center, part of NOAA’s National Weather Service, use the information from the database for quality control of real-time oceanographic information it distributes."(News Release).
Cheers.
