SMS:Importing Non-native SMS Files: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
Line 1: Line 1:
SMS can import many files generated by other software in their native format. The files that can be imported to SMS are shown in the tables below. Each file type is identified by the file extension. The file filter corresponding to the desired extension should be selected in the ''Open File'' dialog. In addition to the file types listed below, several other types of data can be imported via the [[SMS:File_Import_Wizard|Import Wizard]]. Refer to the [[SMS:File_Import_Wizard|Import Wizard]] article for more information.
SMS can import many files generated by other software in their native format. The files that can be imported to SMS are shown in the tables below. Each file type is identified by the file extension. The file filter corresponding to the desired extension should be selected in the ''Open File'' dialog.
 
In addition to the file types listed below, several other types of data can be imported via the [[SMS:File_Import_Wizard|Import Wizard]]. Refer to the [[SMS:File_Import_Wizard|Import Wizard]] article for more information.


== Import File Types ==
== Import File Types ==
{|class="wikitable"
 
{| border="1" cellpadding="2"
!width="250"|File Type
!width="100"|File Ext
!width="650"|Description
 
|-
|<center>Model Simulation Files</center>|| *.sim, *.fpr, *.cmcards, *.par||Numerous numerical engines use simulation files to help organize model files.  These simulation files usually reference a number of other model specific geometry, parameter or data files.  Opening the simulation file will import the entire model and all associated model files.  This will NOT open any SMS specific data, such as Map data or TIN data etc.  The models associated with each super file extension are as follows: *.sim = TABS or STWAVE or CMS-Wave, *.fpr = FST2DH, *.cmcards = CMS-Flow, *.par = BOUSS2D
|-
|<center>Model Geometry Files</center>||*.net, *.geo, *.dep, *.cgi, fort.14, *.grd ||The numerical engines each support their own format for storing geometry (mesh or grid).  Opening the geometry file will import create a geometric object of the appropriate type (mesh or grid) and set the current model to be the associated type. Some models use standard file formats such as *.2dm or *.3dm. Themodels associated with each geometry file extension are as follows: *.net = FST2DH, *.geo = RMA2 (TABS), *.dep =CMS-Wave , *.cgi = CGWAVE, fort.14 = ADCIRC (also uses *.grd), *.grd = BOUSS2D
|-
|<center>DXF/DWG</center>||<center>*.dxf, *.dwg</center>||Vector drawing data used for background display or for conversion to feature objects.
|-
|<center>JPEG - TIFF</center>||<center>*.jpg, *.tif</center>||Raster image files used for background display or for texture mapping to a surface.
|-
|<center>Shapefiles</center>||<center>*.shp</center>||ArcView shapefiles.
|-
|<center>DEM / Grid</center>||<center>*.asc, *.ddf, *.ggd, *.dem</center>||ASCII 2D grid exported from Arc/Info or ArcView, ASCII 2D grid exported from GRASS
|-
|<center>ARC/INFO® ASCII Grid  Files]</center> ||<center>*.arc </center>|| Cartesian grid and associated datasets.
|-
|-
!File Type
|<center>[[SMS:Drogue Files *.pth|Drogue Files]]</center> ||<center>*.pth </center>||Particle / path data from ADCIRC.
!File Extension
!Purpose
|-
|-
|[[SMS:ARC/INFO® ASCII Grid  Files *.arc|ARC/INFO® ASCII Grid  Files]]
|<center>[[SMS:MIKE 21 *.mesh|MIKE 21 *.mesh]]</center>||<center> *.mesh </center>|| Grid file in DHI grid format.
| *.arc
|Cartesian grid and associated datasets
|-
|-
|[[SMS:Drogue Files *.pth|Drogue Files]]
|<center>[[SMS:ARC/INFO® Shape Files *.arc|ARC/INFO® Shapefiles]]</center> ||<center>*.shp </center>|| Geographical shapes and associated attributes.
| *.pth
|Particle / path data from ADCIRC
|-
|-
|[[SMS:MIKE 21 *.mesh|MIKE 21 *.mesh]]
|<center>MapInfor® MIF/MID Pairs]]</center> ||<center>*.mid/*.mid </center>|| Geographical shapes and associated attributes.
| *.mesh
|
|}
|}



Revision as of 21:41, 15 April 2013

SMS can import many files generated by other software in their native format. The files that can be imported to SMS are shown in the tables below. Each file type is identified by the file extension. The file filter corresponding to the desired extension should be selected in the Open File dialog.

In addition to the file types listed below, several other types of data can be imported via the Import Wizard. Refer to the Import Wizard article for more information.

Import File Types

File Type File Ext Description
Model Simulation Files
*.sim, *.fpr, *.cmcards, *.par Numerous numerical engines use simulation files to help organize model files. These simulation files usually reference a number of other model specific geometry, parameter or data files. Opening the simulation file will import the entire model and all associated model files. This will NOT open any SMS specific data, such as Map data or TIN data etc. The models associated with each super file extension are as follows: *.sim = TABS or STWAVE or CMS-Wave, *.fpr = FST2DH, *.cmcards = CMS-Flow, *.par = BOUSS2D
Model Geometry Files
*.net, *.geo, *.dep, *.cgi, fort.14, *.grd The numerical engines each support their own format for storing geometry (mesh or grid). Opening the geometry file will import create a geometric object of the appropriate type (mesh or grid) and set the current model to be the associated type. Some models use standard file formats such as *.2dm or *.3dm. Themodels associated with each geometry file extension are as follows: *.net = FST2DH, *.geo = RMA2 (TABS), *.dep =CMS-Wave , *.cgi = CGWAVE, fort.14 = ADCIRC (also uses *.grd), *.grd = BOUSS2D
DXF/DWG
*.dxf, *.dwg
Vector drawing data used for background display or for conversion to feature objects.
JPEG - TIFF
*.jpg, *.tif
Raster image files used for background display or for texture mapping to a surface.
Shapefiles
*.shp
ArcView shapefiles.
DEM / Grid
*.asc, *.ddf, *.ggd, *.dem
ASCII 2D grid exported from Arc/Info or ArcView, ASCII 2D grid exported from GRASS
ARC/INFO® ASCII Grid Files]
*.arc
Cartesian grid and associated datasets.
Drogue Files
*.pth
Particle / path data from ADCIRC.
MIKE 21 *.mesh
*.mesh
Grid file in DHI grid format.
ARC/INFO® Shapefiles
*.shp
Geographical shapes and associated attributes.
MapInfor® MIF/MID Pairs]]
*.mid/*.mid
Geographical shapes and associated attributes.

Related Topics