Hi, All!
I am trying to import a simple data set with 2-d (x,y) positions and
multiple data fields. The data file looks somewhat like this (with x-coord
varying the fastest):
x y z temperature wind_vx wind_vy
-2 -1 0.1 100 0.3 0.2
-1.8 -1 0.2 98 0.4 0.2
-1.6 -1 0.2 99 0.3 0.1
I'd like to import the data so that it is a field with regular-gridded
positions (and appropriate connections), replacing the x-y positions. The
z, temperature, and wind_v components should be components of that field.
I've had success using the IMPORTSPREADSHEET module and then hardcoding in a
CONSTRUCT and REPLACEing the positions and connections fields (the
constructed-positions need a little bit of massaging, since my file has
x-coord varying fastest).
But that method requires a page or so of data-import-manipulation blocks.
What I'd really like to do is to make a little header file to pass to the
IMPORT block that'll import my data in one step, in the form I mentioned
above (regular-gridded positions/connections, and data values as field
components). Any hints on how to write a header file to do this? The
native DX-format header files don't seem to have a way to deal with data
interleaving in columns, as above. And when I do a general-format import,
it loads the data set in as a group, with separate fields for each data
value. I'm looking for a sort of cross between the two.
Any advice would be much appreciated!
Thanks,
Jeremy Zoss
PS -- I was also noticing while playing around with EXPORT today that when
you export a field with regular-gridded positions, it always dumps the
numerical position values in the output file, rather than the regular-grid
notation. Even when using dx-native format. Can anyone explain to me why
it uses this behavior? Are there cases where you would not want to use the
gridded notation when dumping to dx-native format? Not a big deal, I was
just curious...
