The Text Import Wizard can import various types of data as described in the tables below.
2D scatter points
This will create new scatter points in a new 2D scatter set. Optionally the imported points can be filtered using the filter options available by selecting the Filter Options button.
| Field
|
Type
|
Required
|
Comments
|
| X |
Number |
yes |
|
| Y |
Number |
yes |
|
| Label |
Text |
no |
|
| Data Set |
Number |
no |
Any number of steady-state or transient data sets can be imported. When importing transient data sets, a data set name and a time step must be specified for each transient column. Names and time steps are entered into the header row, separated by a vertical slash using the following format: "Name|Timestep". For example, "Dataset1|January 1, 1900". All time steps of a transient data set should be given the same name.
|
EXAMPLES
| "id"
|
"x"
|
"y"
|
"xylene"
|
"toluene 0.0"
|
"toluene 2.0"
|
| "OW-21" |
32.4 |
5234.3 |
300 |
999 |
999
|
| "OW-22" |
93.4 |
5832.3 |
84 |
398 |
401
|
| "OW-23" |
83.3 |
8438.2 |
89 |
47 |
52
|
| "id"
|
"x"
|
"y"
|
"xylene|01/01/2000 00:00"
|
"xylene|01/01/2000 12:00"
|
"xylene|01/02/2000 00:00"
|
| "OW-21" |
32.4 |
5234.3 |
300 |
310 |
312
|
| "OW-22" |
93.4 |
5832.3 |
84 |
87 |
93
|
| "OW-23" |
83.3 |
8438.2 |
89 |
93 |
93
|
"id" "x" "y" "xylene|01/01/2000 00:00" "xylene|01/01/2000 12:00" "xylene|01/02/2000 00:00"
"OW-21" 32.4 5234.3 300 310 312
"OW-22" 93.4 5832.3 84 87 93
"OW-23" 83.3 8438.2 89 93 93
"OW-24" 46.8 7829.1 207 147 134
3D scatter points
This will create new scatter points in a new 3D scatter set.
| Field
|
Type
|
Required
|
Comments
|
| X |
Number |
yes |
|
| Y |
Number |
yes |
|
| Z |
Number |
yes |
|
| Label |
Text |
no |
|
| Material ID |
Number |
no |
|
| Data Set |
Number |
no |
Any number of steady-state or transient data sets can be imported. When importing transient data sets, a data set name and a time step must be specified for each transient column. Names and time steps are entered into the header row, separated by a vertical slash using the following format: "Name|Timestep". For example, "Dataset1|January 1, 1900". All time steps of a transient data set should be given the same name.
|
EXAMPLES
| "id"
|
"x"
|
"y"
|
"z"
|
"xylene"
|
"toluene 0.0"
|
"toluene 2.0"
|
| "OW-21" |
32.4 |
5234.3 |
10.1 |
300 |
999 |
999
|
| "0W-22" |
93.4 |
5832.3 |
25.7 |
84 |
398 |
401
|
| "0W-23" |
83.3 |
8438.2 |
5.3 |
89 |
47 |
52
|
| "id"
|
"x"
|
"y"
|
"z"
|
"xylene|01/01/2000 00:00"
|
"xylene|01/01/2000 12:00"
|
"xylene|01/02/2000 00:00"
|
| "OW-21" |
32.4 |
5234.3 |
10.1 |
300 |
310 |
312
|
| "OW-22" |
93.4 |
5832.3 |
25.7 |
84 |
87 |
93
|
| "OW-23" |
83.3 |
8438.2 |
5.3 |
89 |
93 |
93
|
Observation data
This creates new feature points in the existing, active coverage. The active coverage must exist and have a steady state observation attribute (like "Head") defined.
| Field
|
Type
|
Required
|
Comments
|
| Point Name |
Text |
no |
|
| X |
Number |
yes |
|
| Y |
Number |
yes |
|
| Z |
Number |
no |
|
| Layer |
Number |
no |
The 3D grid layer the point is associated with.
|
| Measurement |
Text |
no |
Measurement name. Multiple measurements allowed.
|
| Interval |
Number |
no |
Use Interval and Confidence, or Std. Dev. but not both.
|
| Confidence |
Number |
no |
Use Interval and Confidence, or Std. Dev. but not both.
|
| Standard Deviation |
Number |
no |
Use Interval and Confidence, or Std. Dev. but not both.
|
EXAMPLE
| "name"
|
"x"
|
"y"
|
"z"
|
"lay"
|
"hd"
|
"int"
|
"conf"
|
| "OBS_Q5" |
23.3 |
44.2 |
32.2 |
1 |
567.5 |
1.2 |
95
|
| "OBS_Q6" |
83.3 |
84.3 |
32.2 |
1 |
555.3 |
1.4 |
90
|
| "OBS_Q7" |
85.3 |
39.3 |
33.2 |
1 |
999 |
0 |
0
|
Transient observation data
This adds time series curves to existing points in an existing observation coverage. The targeted coverage must be the active coverage. The existing points and the data being imported are matched by name.
| Field
|
Type
|
Required
|
Comments
|
| Point Name |
Text |
yes |
|
| Date (MM/DD/YYYY) |
Date |
yes |
|
| Time (HH:MM:SS) |
Time |
yes |
|
EXAMPLE
| "name"
|
"date"
|
"time"
|
"head"
|
| "OBS_Q5" |
12/3/1999 |
18:00:00 |
238.5
|
| "OBS_Q5" |
1/30/2000 |
7:38:25 |
834.7
|
| "OBS_Q6" |
3/27/2000 |
18:00:00 |
878.3
|
| "OBS_Q6" |
12/3/1999 |
18:00:00 |
733.2
|
Well data
This creates new feature points in an existing coverage. The point types are set to "well" and the flow rate and other data are assigned to the points. A coverage with the "Wells" attribute must already exist and be the active coverage.
| Field
|
Type
|
Required
|
Comments
|
| Name |
Text |
no |
|
| X |
Number |
yes |
|
| Y |
Number |
yes |
|
| Z |
Number |
no |
Elevation of top of well.
|
| Depth |
Number |
no |
Depth to top of screen.
|
| Screen Length |
Number |
no |
|
| Flow Rate |
Number |
no |
Positive for injection, negative for extraction.
|
EXAMPLE
| "name"
|
"x"
|
"y"
|
"z"
|
"depth"
|
"len"
|
"Q"
|
| "well_1" |
123.5 |
843.2 |
62.0 |
51.4 |
6.0 |
120.5
|
| "well_2" |
134.2 |
789.4 |
62.8 |
60.7 |
5.4 |
100.3
|
| "well_3" |
147.2 |
678.1 |
61.4 |
110 |
10.0 |
300.5
|
Pumping data
This adds time series curves to existing points in an existing coverage containing wells. The targeted coverage must be the active coverage. The existing points and the data being imported are matched by name.
| Field
|
Type
|
Required
|
Comments
|
| Well Name |
Text |
yes |
Must match an existing well, or else data is ignored.
|
| Date(MM/DD/YYYY) |
Number |
yes |
|
| Time(HH:MM:SS) |
Number |
yes |
|
| Flow Rate |
Number |
yes |
|
| Depth |
Number |
no |
Depth to top of screen.
|
| Screen Length |
Number |
no |
|
| Flow Rate |
Number |
no |
Positive for injection, negative for extraction.
|
EXAMPLE
| "name"
|
"date"
|
"time"
|
"Q"
|
| "well_1" |
12/3/1999 |
18:00:00 |
625.0
|
| "well_1" |
1/30/2000 |
7:38:25 |
0
|
| "well_2" |
13/3/1999 |
18:00:00 |
0
|
| "well_2" |
15/5/1999 |
14:48:32 |
100.0
|
Borehole data
This creates new boreholes. Optionally, a borehole folder name can be specified to organize the imported boreholes.
| Field
|
Type
|
Required
|
Comments
|
| Borehole Name |
Text |
yes |
|
| X |
Number |
yes |
X location of the contact.
|
| Y |
Number |
yes |
Y location of the contact.
|
| Z |
Number |
yes |
Z location of the contact.
|
| HGU ID |
Number |
yes |
HGU Material below the contact
|
| Material ID |
Number |
no |
Material below the contact.
|
| Horizon ID |
Number |
no |
|
EXAMPLE
| "name"
|
"x"
|
"y"
|
"z"
|
"material"
|
"horizon"
|
| "borehole_1" |
0.0 |
0.0 |
0.0 |
3 |
1
|
| "borehole_1" |
0.0 |
0.0 |
10.0 |
1 |
2
|
| "borehole_1" |
0.0 |
0.0 |
15.0 |
6 |
4
|
| "borehole_2" |
5.0 |
0.0 |
1.0 |
2 |
3
|
| "borehole_2" |
5.0 |
0.0 |
6.0 |
2 |
4
|
Borehole sample data
This creates new sample data on existing boreholes, or new sample data on new boreholes if no boreholes with matching names exist. All existing sample data is replaced with that being imported.
| Field
|
Type
|
Required
|
Comments
|
| Name |
Text |
yes |
New Borehole Name
|
| X |
Number |
yes |
X location of the borehole.
|
| Y |
Number |
yes |
Y location of the borehole.
|
| Z |
Number |
yes |
Z location of the borehole.
|
| Data Set |
Number |
yes |
|
EXAMPLE
| "name"
|
"x"
|
"y"
|
"z"
|
"data"
|
| "borehole_1" |
0.0 |
0.0 |
0.0 |
495
|
| "borehole_1" |
0.0 |
0.0 |
10.0 |
484
|
| "borehole_1" |
0.0 |
0.0 |
15.0 |
454
|
| "borehole_2" |
5.0 |
0.0 |
1.0 |
259
|
| "borehole_2" |
5.0 |
0.0 |
6.0 |
248
|
Transient point data
This creates new time series curve data on existing feature points similar to the Pumping data option above. This option is more generic than the Pumping data option, however, because it will work with feature points of any type and any attribute (that can be transient) of that feature point. The imported data is matched to the existing points by name or by XY location. Data for more than one attribute can be imported at the same time. The attributes of the active coverage are listed as available fields that can be mapped.
| Field
|
Type
|
Required
|
Comments
|
| Name |
Text |
no |
Either this or X and Y must be mapped.
|
| Date (MM/DD/YYYY) |
Date |
yes |
|
| Time (HH:MM:SS) |
Time |
yes |
|
| X |
Number |
no |
Either this or Name must be mapped.
|
| Y |
Number |
no |
Either this or Name must be mapped.
|
| [Attribute1...] |
Number |
No |
The value of the selected attribute at the given date/time.
|
| [AttributeN] |
Number |
No |
The value of the selected attribute at the given date/time.
|
EXAMPLE
| "name"
|
"date"
|
"time"
|
"X"
|
"Y"
|
"Flow rate"
|
| "well_1" |
12/3/1999 |
18:00:00 |
123.5 |
843.2 |
625
|
| "well_1" |
1/30/2000 |
7:38:25 |
123.5 |
843.2 |
0
|
| "well_2" |
3/27/2000 |
18:00:00 |
134.2 |
789.4 |
0
|
| "well_2" |
12/3/1999 |
18:00:00 |
134.2 |
789.4 |
100.0
|
Transient node data
Similar to Transient point data but for nodes. Since nodes don't have names they must be matched by XY location.
| Field
|
Type
|
Required
|
Comments
|
| Date (MM/DD/YYYY) |
Date |
yes |
|
| Time (HH:MM:SS) |
Time |
yes |
|
| X |
Number |
yes |
|
| Y |
Number |
yes |
|
| [Attribute1...] |
Number |
No |
The value of the selected attribute at the given date/time.
|
| [AttributeN] |
Number |
No |
The value of the selected attribute at the given date/time.
|
Transient arc data
Similar to Transient point data but for arcs. Since arcs don't have a single XY location they must be matched by name.
| Field
|
Type
|
Required
|
Comments
|
| Name |
Text |
yes |
|
| Date (MM/DD/YYYY) |
Date |
yes |
|
| Time (HH:MM:SS) |
Time |
yes |
|
| [Attribute1...] |
Number |
No |
The value of the selected attribute at the given date/time.
|
| [AttributeN] |
Number |
No |
The value of the selected attribute at the given date/time.
|
Transient polygon data
Similar to Transient point data but for polygons. Since polygons don't have a single XY location they must be matched by name.
| Field
|
Type
|
Required
|
Comments
|
| Name |
Text |
yes |
|
| Date (MM/DD/YYYY) |
Date |
yes |
|
| Time (HH:MM:SS) |
Time |
yes |
|
| [Attribute1...] |
Number |
No |
The value of the selected attribute at the given date/time.
|
| [AttributeN] |
Number |
No |
The value of the selected attribute at the given date/time.
|
