Closed GoogleCodeExporter closed 9 years ago
Following this refactoring the DAPloader class could be further modified to
better support the Climate Forecast Discrete Geometry feature types:
http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.6/ch09.html
DAPloader inherently supports the trajectory feature type, but it should also
support the timeSeries and timeSeriesProfile feature types so that station data
can also be loaded.
Original comment by MBARIm...@gmail.com
on 17 Jan 2013 at 7:37
With changeset
https://code.google.com/p/stoqs/source/detail?r=264f15f7e6f7e53945f86fd3d956a6ef
12a8625d DAPloaders.py is now ready for changes to better support different
discrete geometry feature types. The proposed class hierarchy is something
like:
Base_Loader(STOQS_Loader)
|
+-- Trajectory_Loader
| |
| +-- Lrauv_Loader
| +-- Dorado_Loader
| +-- Glider_Loader
|
+-- TimeSeries_Loader
|
+-- Mooring_Loader
+-- Station_Loader
Original comment by MBARIm...@gmail.com
on 18 Jan 2013 at 11:46
Original comment by MBARIm...@gmail.com
on 27 Feb 2013 at 12:00
Started work on DAPloaders.py with adding methods _genTimeSeries(),
_genTimeSeriesProfile() and _genTrajectory that will key off of global
attribute featureType in CF-1.6 as a hint of which one _genData() should call.
Verification of the choice will occur by peeking at the shape of the data
source.
Original comment by MBARIm...@gmail.com
on 8 May 2013 at 9:30
The Discrete Sampling Geometry featureTypes of trajectory, timeSeries, and
timeSeriesProfile are now supported by DAPLoaders.py. The UI visualization
functionality is being implemented and perhaps some bugs will arise, but for
now I'll mark this issue as fixed.
Original comment by MBARIm...@gmail.com
on 10 Jul 2013 at 11:51
Original issue reported on code.google.com by
MBARIm...@gmail.com
on 11 Jun 2012 at 9:39