NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Brian,
You can check out the nightly release to test the newly added feature
for CSV text point data.
After installing the nightly release, you can open this slow bundle and
wait for it to finish. Then, go to display control of the point dataset and
set View > Times > Use Time Driver Times, then, you need to reload the file
in the same display control: File > Reload data. I tested your bundle and
the performance is very good.
When working on the new CSV point dataset, you also need to create the
display first and then set the Use Time Driver Times and reload the data.
This design is not perfect. For the CSV point data, we don't have any time
information until the user clicks the create display button. Also, this is
the quickest solution I can provide. Let me know if you see any
problem.
Yuan
On Tue, Sep 30, 2014 at 8:14 PM, Tom Whittaker <whittaker@xxxxxxxx> wrote:
> Not to confuse the issue or the path you are investigating, but you
> might also explore "Point Cloud" -- both as a data type and as a
> Display Type (under "Volume").
>
> It was designed to be a very efficient way to display many (many)
> points -- typically used for trajectories or (aircraft) tracks, but
> has been used before for other situations involving datasets with a
> large number of points. I have no idea how this might work with a time
> driver, however, as it was created before that concept was
> implemented.
>
> tom
> --
> Tom Whittaker
> Researcher-Emeritus
> Honorary Fellow
> Space Science and Engineering Center
> University of Wisconsin-Madison
> Madison, WI USA
>
idvusers archives: