GMS:GSF File Format: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
A Grid Specification File (*.gsf) is used with MODFLOW-USG to define the unstructured grid geometry. The format is defined ([http://www.pesthomepage.org/getfiles.php?file=gwutil_a.pdf in this link]) and repeated in the image below:
A Grid Specification File (*.gsf) is used with MODFLOW-USG to define the unstructured grid geometry. The grid specification file for a structured grid is far less complex than for an unstructured grid. The lack of structure precludes omission of the coordinates of the vertices of each model cell. Hence the locations of these vertices must be specified in the grid specification file, together with the node that is associated with a model cell.
 
The format is defined in <!--[http://www.pesthomepage.org/getfiles.php?file=gwutil_a.pdf the Groundwater Data Utilities article] and repeated in--> the image <ref>Doherty, J. (November 2015). Groundwater Data Utilities, ''Watermark Numerical Computing'', 2(9): 26&ndash;37.</ref> below:


[[Image:gsf_format.png|600px]]
[[Image:gsf_format.png|600px]]
==References==
{{reflist}}




{{Navbox GMS}}
{{Navbox GMS}}
[[Category:Importing Data]]
[[Category:Importing Data]]
[[Category:MODFLOW|GSF]]
[[Category:GMS File Formats|GSF]]
[[Category:External Links]]
{{stub}}

Latest revision as of 15:08, 21 April 2022

A Grid Specification File (*.gsf) is used with MODFLOW-USG to define the unstructured grid geometry. The grid specification file for a structured grid is far less complex than for an unstructured grid. The lack of structure precludes omission of the coordinates of the vertices of each model cell. Hence the locations of these vertices must be specified in the grid specification file, together with the node that is associated with a model cell.

The format is defined in the image [1] below:

Gsf format.png

References

  1. ^ Doherty, J. (November 2015). Groundwater Data Utilities, Watermark Numerical Computing, 2(9): 26–37.