SMS:Importing Non-native SMS Files: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
No edit summary |
|||
(34 intermediate revisions by 2 users not shown) | |||
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|''File Import Wizard'']]. Refer to the [[SMS:File_Import_Wizard|File Import Wizard]] article for more information. | |||
== Import File Types == | == Import File Types == | ||
{| | |||
{| class="wikitable" | |||
!width="250"|File Type | |||
!width="100"|File Ext | |||
!width="450"|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>[[SMS:CAD Data|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, *.tiff</center>||Raster image files used for background display or for texture mapping to a surface. | |||
|- | |||
|<center>[[SMS:Shapefiles|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>[[SMS:ARC/INFO ASCII Grid Files *.arc|ARC/INFO® ASCII Grid Files]]</center> ||<center>*.arc </center>|| Cartesian grid and associated datasets. | |||
|- | |||
|<center>[[SMS:Drogue Files *.pth|Drogue Files]]</center> ||<center>*.pth </center>||Particle / path data from ADCIRC. | |||
|- | |||
|<center>[[SMS:MIKE 21 *.mesh|MIKE 21 *.mesh]]</center>||<center> *.mesh </center>|| Grid file in DHI grid format. | |||
|- | |||
|<center>ARC/INFO® [[SMS:Shapefiles|Shapefiles]]</center> ||<center>*.shp </center>|| Geographical shapes and associated attributes. | |||
|- | |||
|<center>[[SMS:MapInfo MID/MIF|MapInfor® MIF/MID Pairs]]</center> ||<center>*.mid/*.mid </center>|| Geographical shapes and associated attributes. | |||
|- | |- | ||
|<center>[[SMS:NOAA HURDAT|NOAA HURDAT]], ATCF</center> ||<center>*.hurdat, *atcf</center> || Tropical cyclones database. | |||
|- | |- | ||
|[[SMS: | |<center>[[SMS:NOAA HURDAT|NOAA HURDAT 2]]</center> ||<center>*.hurdat2</center> || Tropical cyclones database in unprocessed format. | ||
| *. | |||
| | |||
|- | |- | ||
|[[ | |<center>[[Lidar Support|LIDAR]]</center> || <center>*.las, *.laz</center> || Light detection and ranging. | ||
| *. | |||
| | |||
|} | |} | ||
== Related Topics== | == Related Topics== | ||
Line 23: | Line 44: | ||
* [[SMS:Native_SMS_Files|Native File Formats]] | * [[SMS:Native_SMS_Files|Native File Formats]] | ||
* [[SMS:File Formats|File Formats]] | * [[SMS:File Formats|File Formats]] | ||
* [[Data Sources]] | |||
{{Template: | {{Template:Navbox SMS}} | ||
[[Category:SMS File Formats| | [[Category:SMS File Formats|Non]] | ||
[[Category:Importing Data|Non]] |
Latest revision as of 14:58, 26 June 2018
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 File Import Wizard. Refer to the File Import Wizard article for more information.
Import File Types
File Type | File Ext | Description |
---|---|---|
*.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 | |
*.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 | |
Vector drawing data used for background display or for conversion to feature objects. | ||
Raster image files used for background display or for texture mapping to a surface. | ||
ArcView shapefiles. | ||
ASCII 2D grid exported from Arc/Info or ArcView, ASCII 2D grid exported from GRASS | ||
Cartesian grid and associated datasets. | ||
Particle / path data from ADCIRC. | ||
Grid file in DHI grid format. | ||
Geographical shapes and associated attributes. | ||
Geographical shapes and associated attributes. | ||
Tropical cyclones database. | ||
Tropical cyclones database in unprocessed format. | ||
Light detection and ranging. |
Related Topics
SMS – Surface-water Modeling System | ||
---|---|---|
Modules: | 1D Grid • Cartesian Grid • Curvilinear Grid • GIS • Map • Mesh • Particle • Quadtree • Raster • Scatter • UGrid | |
General Models: | 3D Structure • FVCOM • Generic • PTM | |
Coastal Models: | ADCIRC • BOUSS-2D • CGWAVE • CMS-Flow • CMS-Wave • GenCade • STWAVE • WAM | |
Riverine/Estuarine Models: | AdH • HEC-RAS • HYDRO AS-2D • RMA2 • RMA4 • SRH-2D • TUFLOW • TUFLOW FV | |
Aquaveo • SMS Tutorials • SMS Workflows |