|
Notes |
|
|
(0011748)
|
|
Ken Moreland
|
|
2008-05-08 10:39
|
|
The support for CSV files is all messed up. We hope to address these issues in version 3.6 with better support for table data sets. I envision this scenario playing out as follows:
1. Load in the CSV file. The file becomes a table data type, which is shown by default in a spreadsheet view. Makes sense since it's basically just regurgitating the CSV contents.
2. Run a filter that imposes connectivity. Taking every three rows and making a triangle from those makes as much sense as anything else. |
|
|
|
(0014955)
|
|
Ken Moreland
|
|
2009-02-16 15:19
|
|
Now CSV files are read as tables. There is a filter to convert tables to a poly data set with a bunch of vertex cells using some columns as coordinates.
If you want a filter that provides other connectivity, either implement that as a programmable filter or issue another bug. |
|
|
|
(0014989)
|
|
Alan Scott
|
|
2009-02-16 19:07
|
|
I could not get this to work.
* I was able to read the CSV file into a table.
* Table to Points and Table to Structured Grid then produced junk. Does it work for you? How did you get it to work? |
|
|
|
(0015024)
|
|
Ken Moreland
|
|
2009-02-17 11:48
|
|
It works fine for me. I loaded in a CSV file with the contents exactly like those specified on this bug. I then ran Table To Points. I set X Column to X::Point, Y Column to Y::Point and Z Column to Z::Point. When I make the result visible in a 3D view, I get three points at exactly the coordinates specified in the CSV file.
Did you perhaps forget to set the values for the X/Y/Z Column parameters of the Table To Points filter? |
|
|
|
(0015195)
|
|
Alan Scott
|
|
2009-02-18 19:19
|
|
|