Hi,
I had problems with time axes with units of minutes some time ago, so I
expanded the LASConfig.java file for our internal LAS server. Now we can
use the unit "min" for axes like:
<time_axis type="t" units="min">
<arange start="01-AUG-2006 11:12" step="12" size="1905"
end="17-AUG-2006 08:12"/>
</time_axis>
If you don't fear editing the Java source code you can use it, but have
to change your LASUI.js (in /WebContent/JavaScript/ui/) in line 1524 from:
this.refs.DW = new
DateWidget(this.state.grid.getLo('t'),this.state.grid.getHi('t'));
to:
var scale = 1;
var tUnits = this.state.grid.getUnits('t');
var tDelta = this.state.grid.getDelta('t');
if (tUnits == "hour") {
scale = 60;
if ((24 % tDelta) != 0) {
tDelta = 1;
}
}
else {
if (tDelta == null || tUnits == "day") {
tDelta = 1440;
}
if (tUnits == "min") {
if ((1440 % tDelta) != 0) {
tDelta = 1;
}
}
}
this.refs.DW = new
DateWidget(this.state.grid.getLo('t'),this.state.grid.getHi('t'),(tDelta
* scale));
and replace /gov/noaa/pmel/tmap/las/jdom/LASConfig.java by the attached
LASConfig.java.
You should backup all files first!
I hope it works,
Bastian
On 02/24/2010 05:32 PM, Roland Schweitzer wrote:
Anton,
Anton Yoel Buenavista wrote:
Hello again everyone,
For an update on my problem, I was able to display the variables
which only depend on lat and lon using the documentation here:
http://ferret.pmel.noaa.gov/LAS/documentation/installer-documentation/adding-curvilinear-data/.
Thank you Roland for your guidance on that.
However, I am faced with a new problem. The remaining variables depend
on lat, lon, and a time dimension as well as you can see in the sample
variable definition below:
[...]
<time-t-id-01ced4ab23 type="t" units="minute">
<arange start="2008-01-23 00:00:00" size="84" step="15" />
</time-t-id-01ced4ab23>
</axes>
I have attached a screenshot of the error being returned when the plot
is trying to be loaded. Your kind help on the matter is greatly
appreciated!
Unfortunately the LAS user interface time widget does not understand
time increments of less than one hour. We'll be working on improving
that in future versions, but for now you'll need to create your time
axis by listing each individual time value. I know it's not practical
for all cases, but it's the only solution for the immediate future. For
example:
<time-t-id-01ced4ab23 type="t" units="minute">
<v>2008-01-23 00:00:00</v>
<v>2008-01-23 00:15:00</v>
<v>2008-01-23 00:30:00</v>
<v>2008-01-23 00:45:00</v>
<v>2008-01-23 01:00:00</v>
[...]
</time-t-id-01ced4ab23>
Roland