Using the ExtData component: Difference between revisions
Line 101: | Line 101: | ||
There are several special options and cases that the user should be aware of. | There are several special options and cases that the user should be aware of. | ||
==== Time Offset in Continuous Update ==== | ==== Time Offset in Continuous Update ==== | ||
If the user specifies a refresh template of 0, they can tell ExtData to apply a time offset when updating the variable. If they enter 0;0300 when updating the variable it will use an offset of +30 minutes when time interpolating to update the variable. | If the user specifies a refresh template of 0, they can tell ExtData to apply a time offset when updating the variable. If they enter 0;0300 when updating the variable it will use an offset of +30 minutes when time interpolating to update the variable. Likewise they can enter 0;-3000 to use an offset of -30 minutes. In general you can specify 0;%h2%n2%s2 where you can leave out the hour and just do 0;%n2%s2. | ||
==== Climatologies ==== | ==== Climatologies ==== | ||
Sometimes data represents a yearly climatology. ExtData currently only supports 12 month climatologies, i.e. one time per month. If the climatology keyword is set to yes you are telling ExtData that you have a file with 12 times spanning at year or 12 files, one per month. In either case ExtData does not use the application clock's year but replaces it with the year in the file for interpolation and wraps the data around at the end of the year. | Sometimes data represents a yearly climatology. ExtData currently only supports 12 month climatologies, i.e. one time per month. If the climatology keyword is set to yes you are telling ExtData that you have a file with 12 times spanning at year or 12 files, one per month. In either case ExtData does not use the application clock's year but replaces it with the year in the file for interpolation and wraps the data around at the end of the year. |