SMF

Title(s): - Names(s) that refer to the engineering format.

Version ID: - Identification or version number of the engineering format.

Date released: - Date that the version was released.

Date: - Date the format was created (YYYY-MM-DD)

Creator(s): Entity Template - N/A

Contributor(s): - N/A

Relationships: - The SMF format is based on Wavefront's OBJ format. Some SMF files are valid OBJ files.

• Previous Version(s): - N/A

• Contains: - N/A

• Syntax Format(s): - N/A

• Family Format(s): - N/A

Description: - The SMF format describes triangular meshes by defining each 3D vertex used by the

model. Triangles are defined using the index of each vertex. This makes them difficult to modify by hand, but saves disk

space. Each vertex may also have a normal, color, texture, or texture coordinate associated with it. Some affine

transformations (no shearing) can be applied to sets of vertices to simplify the definition of a mesh or make it easier to

modify components within a model.

History: - Historical description depicting major events surrounding development, creation, and

maintenance of this format.

Example(s): Example Template - http://www.cs.drexel.edu/~david/Classes/CS586/Models/

Identifier: - A URL or other identifier that refers to the engineering format.

Documentation: Documentation Template - http://people.sc.fsu.edu/~burkardt/data/smf/smf.html

File Extensions: - smf

Applications: - Applications that the engineering format uses.

• Native application(s): Engineering Format Application Template - Applications which are

primarily designed to specifically run this engineering format.

• Interoperable applications: Engineering Format Application Template - IVCON, IVREAD

Magic numbers: - Unique identifying characters at the beginning of files for this engineering

format.

Format(s): - The MIME file types.

Rights: - The name or type of the license for the engineering format. Examples: BSD-style license,

Apache License, Proprietary license

Sustainability Factors: - Facts about the sustainability of this particular engineering format.

• Standardization: - Information regarding standardization attempts with this format.

• Adoption: - Information about how this format has been adopted by other organizations.

• • Licensing and patent claims: - Any licenses or patent claims that the

engineering format makes.

• Self-documentation: - Any self-documentation capabilities of the format.

• External dependencies: - Anything that the format depends on outside of its control to

function.

• Technical protection considerations: - Any considerations that are

necessary when it comes to technical protection.

Typical use: - Triangle mesh

File classification: - Specific properties that pertain to this engineering format.

• Type {Binary, Text}: - Text
• Raster data: - Section describes whether or not the engineering format supports raster data.
  • Raster data 2D: - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data

supports 2D raster data.

• • • Is Supported: - false
    • Description: - The format may contain texture coordinates,

but it does not contain the texture.

• • Raster data 3D: - Can the format support 3D raster data? Example: A format that can contain 2D pixelated data of a

3D model supports 3D raster data.

• • • Is Supported: - false
    • Description: - This field is used to describe the support

or lack of support of the feature.

• Geometric representation: - Section describes whether or not the engineering format supports geometric

representations.

• • Implicit representation: - Section describes whether or not the engineering format supports implicit

representations.

• • • Implicit surfaces: - Can the format support implicit surfaces? Example: A format that can contain surfaces that

are generated with mathematical equations that contain the independent variables x, y, and z, like x^2 + y^2 + z^2 * R^2 =

0, supports implicit surfaces.

• • • • Is Supported: - false
      • Description: -
    • Implicit curves: - Can the format support implicit curves? Example: A format that can contain curves that are

generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves.

• • • • Is Supported: - false
      • Description: -
    • Point set: - Can the format support point sets? Example: A format that supports surfaces and lines that are

generated by points that form triangles supports point sets.

• • • • Is Supported: - true
      • Description: - All polygons are defined by creating a triangle

from three defined points.

• • Mesh: - Section describes whether or not the engineering format supports mesh.
    • Manifold surface meshes: -
      • Is Supported: - true
      • Description: - The SMF format supports any

triangular mesh, manifold or not.

• • • Manifold volume meshes: -
      • Is Supported: - true
      • Description: - The SMF format supports any

triangular mesh, manifold or not.

• • • Non-manifold meshes: -
      • Is Supported: - true
      • Description: - The SMF format supports any

triangular mesh, manifold or not.

• • Parametric representation: -
    • Parametric surfaces: -
      • Is Supported: - false
      • Description: - The file may contain a triangular

mesh that approximates a parametric surface, but it cannot store the equations that define the parametric surface.

• • • Parametric curves: -
      • Is Supported: - false
      • Description: - No curves are supported, just

triangles.

• • Contour sets: - Can the format support contour sets?
    • Is Supported: - false
    • Description: - This is not supported.
  • NURBS: -
    • Is Supported: - false
    • Description: - No curves are supported, just triangles.
• Multi-resolution models: -
  • Is Supported: - false
  • Description: - Two disjoint models could be

specified in one SMF file, but there is no notation for specifying that two distinct models exist and one is a

lower-resolution model of the other.

• Dynamics: - Section describes whether or not the engineering format supports dynamics.
  • Kinematics: - Can the format support kinematics? Example: Does the format allow model parts to rotate?
    • Is Supported: - false
    • Description: - You can use some affine transformations (no

shearing) within the file to specify parts of the mesh. You cannot specify bounds on these transformations, so this feature

is intended to simplify the file, not allow for moving parts.

• • Assembly: -
    • Is Supported: - false
    • Description: - This is not supported.
  • Force(s): -
    • Is Supported: - false
    • Description: - This is not supported.
• Boundary representation -
  • Manifold surface boundary representations: -
    • Is Supported: - true
    • Description: - As long as every

surface in the BRep model is a polygon, this model can be represented as a triangular mesh and saved as an SMF file.

• • Manifold volume boundary representations: -
    • Is Supported: - true
    • Description: - As long as each

volume has a polygonal representation, the model can be represented as a triangular mesh and saved as an SMF file.

• • Non-manifold boundary representations: -
    • Is Supported: - true
    • Description: - Non-manifold geometry

that can be represented as a set of triangles can be represented by an SMF file.

• Material transparency: -
  • Is Supported: - true
  • Description: - A color can be associated with each

vertex.

References: - http://people.sc.fsu.edu/~burkardt/data/smf/smf.html