read ADCP data from TRDI and Nortek instruments
ADCPy - code to work with ADCP data from the raw binary using python 3.x
code to prepare large amounts of ADCP data from the raw binary for use with xarray
Written by Marinna Martini, 1/12/2017
Use at your own risk - this is a work in progress and a python learning project.
As the code stands now, a 3.5 GB, single ping Workhorse ADCP .pd0 file with 3 Million ensembles will take 4-5 hours to convert.
At USGS Coastal and Marine Geology we use the PMEL EPIC convention for netCDF as we started doing this back in the early 1990's. Downstream we do convert to more current CF conventions, however our diagnostic and other legacy code for processing instrument data from binary and other raw formats depends on the EPIC convention for time, so you will see a time (Time (UTC) in True Julian Days: 2440000 = 0000 h on May 23, 1968) and time2 (msec since 0:00 GMT) variable created as default. This may confuse your code. If you want the more python friendly CF time (seconds since 1970-01-01T00:00:00 UTC) set timetype to CF.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size ADCPy-0.0.0-py3-none-any.whl (62.8 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size ADCPy-0.0.0.tar.gz (54.2 kB)||File type Source||Python version None||Upload date||Hashes View|