|Fig. 1 Golomb Ruler|
I downloaded updates which I will be posting in a day or so (WOD Updates).
They are the 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 = 1.008 GB, covering 436 of 648 different WOD zones (note that many of the WOD zones cover only land, no ocean - see WOD Map).
I had to write a C++ module to go through those files, byte by byte, to identify, then separate the casts in those 4 files, and then place them in files with other casts from the same zone (e.g. all 1212 zone casts in one file named "1212").
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 furnish the only clues as to where the measurements came from.
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.
|Fig. 4 (from 1.008 GB of data)|
Those 436 files are now named according to the WOD zone the data came from (the ocean area where the water was tested - see WOD Map).
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). That is why I use it along with the PSMSL database.
Let's hope that the others using the updates noticed the mix (compare Fig. 4 to single-zone graphs here and here).