GMS:File Import Wizard Supported File Formats: Difference between revisions
Line 484: | Line 484: | ||
== Transient polygon data == | == Transient polygon data == | ||
Similar to [[GMS:File Import Wizard Supported File Formats#Transient point data|transient point data]] but for [[GMS:Feature Objects#Polygons|polygons]]. Since polygons don't have a single XY location they must be matched by ID or | Similar to [[GMS:File Import Wizard Supported File Formats#Transient point data|transient point data]] but for [[GMS:Feature Objects#Polygons|polygons]]. Since polygons don't have a single XY location they must be matched by ID or name. | ||
{| class="wikitable" | {| class="wikitable" |
Revision as of 14:09, 15 August 2017
The File Import Wizard can import various types of data as described in the tables below.
2D UGrid points
This will create new points in a new UGrid. Optionally the imported points can be filtered using the filter options available by selecting the Filter Options button.
Field | Type | Required | Comments |
---|---|---|---|
Point Zs are set to 0.0 if omitted | |||
Any number of steady-state or transient datasets can be imported. When importing transient datasets, a dataset 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 dataset should be given the same name. |
Examples
These examples can be copied and pasted into GMS.
Steady state
"x" "y" "xylene" "toluene1" "toluene2" 32.4 74.3 300 999 999 93.4 32.3 84 398 401 83.3 48.2 89 47 52 46.8 29.1 207 147 134
Transient
"x" "y" "xylene|01/01/2000 00:00" "xylene|01/01/2000 12:00" "xylene|01/02/2000 00:00" 32.4 74.3 300 87 276 93.4 32.3 84 310 187 83.3 48.2 89 148 198 46.8 29.1 207 147 134 40.3 50.1 158 213 32 60.7 52.0 27 41 300 78.7 72.9 264 275 206
3D UGrid points
This will create new points in a new UGrid.
Field | Type | Required | Comments |
---|---|---|---|
Any number of steady-state or transient datasets can be imported. When importing transient datasets, a dataset 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 dataset should be given the same name. |
Examples
These examples can be copied and pasted into GMS.
Steady state
"x" "y" "z" "xylene" "toluene|0.0" "toluene|2.0" 32.4 74.3 10.1 300 87 999 93.4 32.3 25.7 84 310 187 83.3 48.2 5.3 89 148 198 46.8 29.1 -42.2 207 147 134
Transient
"x" "y" "z" "xylene|01/01/2000 00:00" "xylene|01/01/2000 12:00" "xylene|01/02/2000 00:00" 32.4 74.3 10.1 300 387 276 93.4 32.3 25.7 84 310 187 83.3 48.2 5.3 89 148 198 46.8 29.1 -42.2 207 147 134
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 |
---|---|---|---|
Any number of steady-state or transient datasets can be imported. When importing transient datasets, a dataset 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 dataset should be given the same name. |
Examples
These examples can be copied and pasted into GMS.
Steady state
"id" "x" "y" "xylene" "toluene|0.0" "toluene|2.0" "OW-21" 32.4 74.3 300 999 999 "OW-22" 93.4 32.3 84 398 401 "OW-23" 83.3 48.2 89 47 52 "OW-24" 46.8 29.1 207 147 134
Transient
"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 74.3 300 87 276 "OW-22" 93.4 32.3 84 310 187 "OW-23" 83.3 48.2 89 148 198 "OW-24" 46.8 29.1 207 147 134 "OW-25" 40.3 50.1 158 213 32 "OW-26" 60.7 52.0 27 41 300 "OW-27" 78.7 72.9 264 275 206
3D scatter points
This will create new scatter points in a new 3D scatter set.
Field | Type | Required | Comments |
---|---|---|---|
Any number of steady-state or transient datasets can be imported. When importing transient datasets, a dataset 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 dataset should be given the same name. |
Examples
These examples can be copied and pasted into GMS.
Steady state
"id" "x" "y" "z" "xylene" "toluene|0.0" "toluene|2.0" "OW-21" 32.4 74.3 10.1 300 87 999 "OW-22" 93.4 32.3 25.7 84 310 187 "OW-23" 83.3 48.2 5.3 89 148 198 "OW-24" 46.8 29.1 -42.2 207 147 134
Transient
"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 74.3 10.1 300 387 276 "OW-22" 93.4 32.3 25.7 84 310 187 "OW-23" 83.3 48.2 5.3 89 148 198 "OW-24" 46.8 29.1 -42.2 207 147 134
Observation data
This creates new feature points in the existing, active coverage. The active coverage must exist and have a steady state observation attribute (such as "Head") defined.
Field | Type | Required | Comments |
---|---|---|---|
Example
"id" "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 or ID. If both Name and ID are specified then ID will take precedence.
Both Date and Time can be specified although data can be imported with only Date or only Time specified (at least one of these fields must be specified). If only the Date is specified then the time is set to 12:00:00 AM. If only Time is specified then it is assumed that date/time format is not being used and the time is treated as a relative time.
Field | Type | Required | Comments |
---|---|---|---|
Either Name or ID must be specified | |||
Either Name or ID must be specified | |||
Either Date or Time or both must be specified | |||
Either Date or Time or both must be specified |
Example
"id" "date" "time" "head" "OBS_Q5" 12/3/1999 18:00:00 238.5 "OBS_Q5" 1/30/2000 07: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 |
---|---|---|---|
Example
"id" "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
MODFLOW Well Package data
This creates new well boundary conditions in an existing MODFLOW simulation. Both steady state (one flow rate per well) or transient data (multiple flow rates at different times per well) can be imported. With transient data, multiple rows are used to list flow rates at different times (or date/times) and the Well Name field is used to associate the flow rates with the correct well. The times for changes in flow rate do not need to match the model stress period times. Flow rate curves are treated as stair step data and the rate for each stress period is found by temporal (time) interpolation. A prompt will ask if wanting to use the average flow rate for each stress period, or use the flow rate at the beginning of each stress period.
Field | Type | Required | Comments |
---|---|---|---|
Example
"Layer" "Row" "Column" "Rate" "Well Name" "Date" "Time" 1 2 2 -502 City Well #1 Jan 1, 1940 5:00 1 2 2 -431 City Well #1 July 1, 1940 5:00 1 4 4 0 W5088341 July 1, 1940 5:00 1 4 4 -1000 W5088341 July 1, 1941 6:00
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 |
---|---|---|---|
Either Date or Time or both must be specified. | |||
Either Date or Time or both must be specified. | |||
Example
"id" "date" "time" "Q" "well_1" 12/3/1999 18:00:00 625.0 "well_1" 1/30/2000 07:38:25 0 "well_2" 12/3/1999 18:00:00 0 "well_2" 3/3/2000 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 |
---|---|---|---|
"id" "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 |
---|---|---|---|
"id" "x" "y" "z" "data" "borehole_1" 0.0 0.0 20.0 495 "borehole_1" 0.0 0.0 15.0 484 "borehole_1" 0.0 0.0 10.0 454 "borehole_2" 5.0 0.0 6.0 259 "borehole_2" 5.0 0.0 1.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 existing points and the data being imported are matched by Name or ID or X and Y. The order of precedence for these fields is ID, Name, then X and Y.
Beginning with GMS version 10.1, if multiple multiple points in the coverage have the same name and the imported data are matched by Name then a new time series will be created for all of the points with that name.
Both Date and Time can be specified although data can be imported with only Date or only Time specified (at least one of these fields must be specified). If only the Date is specified then the time is set to 12:00:00 AM. If only Time is specified then it is assumed that date/time format is not being used and the time is treated as a relative time.
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 or ID or X and Y must be specified. | |||
Name or ID or X and Y must be specified. | |||
Either Date or Time or both must be specified. | |||
Either Date or Time or both must be specified. | |||
Name or ID or X and Y must be specified. | |||
Name or ID or X and Y must be specified. | |||
The value of the selected attribute at the given date/time. | |||
The value of the selected attribute at the given date/time. |
"id" "date" "time" "x" "y" "Flow rate" "well_1" 12/3/1999 18:00:00 123.5 843.2 625 "well_1" 1/30/2000 07: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 ID or XY location.
Field | Type | Required | Comments |
---|---|---|---|
Either ID or X and Y must be specified. | |||
Either Date or Time or both must be specified. | |||
Either Date or Time or both must be specified. | |||
Either ID or X and Y must be specified. | |||
Either ID or X and Y must be specified. | |||
The value of the selected attribute at the given date/time. | |||
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 ID or Name.
Field | Type | Required | Comments |
---|---|---|---|
Either Name or ID must be specified. | |||
Either Name or ID must be specified. | |||
Either Date or Time or both must be specified. | |||
Either Date or Time or both must be specified. | |||
The value of the selected attribute at the given date/time. | |||
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 ID or name.
Field | Type | Required | Comments |
---|---|---|---|
Name or ID must be specified. | |||
Name or ID must be specified. | |||
Either Date or Time or both must be specified. | |||
Either Date or Time or both must be specified. | |||
The value of the selected attribute at the given date/time. | |||
The value of the selected attribute at the given date/time. |
Dataset
Datasets can be imported from columnar text files and added to geometric objects (TINs, UGrids etc.). However text files containing datasets are not imported via the File|Open command (or pasting into the GMS window), but via the "Import Dataset" command found in the right-click menu of objects in the Project Explorer (objects that can have datasets). The format is similar as that of 2D or 3D Scatter Points as described above, but with only the dataset columns. The number of dataset values in the file must match the number of locations (points or cells) on the geometric object.
Field | Type | Required | Comments |
---|---|---|---|
Any number of steady-state or transient datasets can be imported. When importing transient datasets, a dataset 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 dataset should be given the same name. |
Steady state example
"xylene" "toluene 0.0" "toluene 2.0" 300 999 999 84 398 401 89 47 52 207 147 134
Transient example
"xylene|01/01/2000 00:00" "xylene|01/01/2000 12:00" "xylene|01/02/2000 00:00" 300 87 276 84 310 187 89 148 198 207 147 134 158 213 32 27 41 300 264 275 206
GMS – Groundwater Modeling System | ||
---|---|---|
Modules: | 2D Grid • 2D Mesh • 2D Scatter Point • 3D Grid • 3D Mesh • 3D Scatter Point • Boreholes • GIS • Map • Solid • TINs • UGrids | ![]() |
Models: | FEFLOW • FEMWATER • HydroGeoSphere • MODAEM • MODFLOW • MODPATH • mod-PATH3DU • MT3DMS • MT3D-USGS • PEST • PHT3D • RT3D • SEAM3D • SEAWAT • SEEP2D • T-PROGS • ZONEBUDGET | |
Aquaveo |