Product: IESX

Version: GeoFrame 3.5

Application: DataManager

Search Type: FAQ


Topic:
What are the minimum requirements to import fault boundaries into IESX?

Description:


Solution:
The minimum requirements to import fault boundaries into IESX using Data Manager > Interpretation > Import are as follows: 1.) A Header line that includes the Profile label and name; and the Type label and name. 2.) The X Coordinate and the Y Coordinate - can be either float, exponent, or integer. 3.) The Z Coordinate - even if the values are 0. 4.) The Segment ID - MUST be in columns 29-31, any other position will result in error. Note - Each segment ID needs to begin and end with the same data point (x,y,z) in order to be a closed polygon. If the first and last points are not identical, the fault polygon will be open. 5.) EOD marker at the end of the file otherwise only the first segment id in the file will load. If a fault boundary does not exist for the horizon, one is created. However, if a fault boundary does exist, the data is imported into the preferred fault boundary set for that horizon. In GeoFrame 3.1 it was necessary to exit GeoFrame after the import in order to see the new fault boundary in Basemap > Post > Interpretation. This is not the case in higher versions of GeoFrame. An example of a fault boundary file with the minimum requirements: PROFILE fb_test TYPE 3 1267559.8 263375.0 2 0.0 1289772.9 269848.1 2 0.0 1290181.7 268621.6 2 0.0 1276622.2 264397.0 2 0.0 1269672.0 261875.9 2 0.0 1267696.0 261875.9 2 0.0 1267559.8 263375.0 2 0.0 1275448.6 233907.2 3 1652.0 1275654.1 235548.1 3 1624.0 1276925.6 237845.4 3 1612.0 1279961.5 241722.0 3 1590.0 1284700.4 245003.9 3 1588.0 1290053.8 247404.3 3 1564.0 1298259.0 253598.5 3 1544.0 1299900.0 254870.6 3 1556.0 1299900.0 254665.1 3 1604.0 1298259.0 253106.2 3 1636.0 1291694.9 248183.4 3 1664.0 1289315.4 246537.9 3 1672.0 1286423.5 245498.8 3 1668.0 1276925.6 237353.2 3 1670.7 1275694.8 233907.2 3 1712.0 1275448.6 233907.2 3 1652.0 EOD

Last Modified on: 31-AUG-99