A path is a compound spatial object containing one or more segments (Lines or Arcs). Path segments must be contiguous. The geometry parts are lines or arcs that connect end-to-end to form a continuous line or area. Paths may also be referred to as chains.

Because a path contains segments, each segment may have its own name, traits, and other attributes. There does not need to be consistency between the names or traits in any of the segments of a path.

If the Path is 3D or has measures, all segments may have unique z and/or measure values. The segments must all be 2D or all be 3D and must have the same number and named measures, but the values of any of these between them may differ.

Not all formats support path geometries. If a path geometry is written to a format that does not support paths (or the equivalent), FME will stroke the path into a continuous linear feature (replacing arcs with vertices if necessary).

Paths add more flexibility to geometry representation. Also, paths allow you to preserve certain characteristics of the individual geometry parts as traits or measures.

Paths are different from aggregates. Paths have a definitive structure in that the parts join end to end (that is, they have a topology), whereas there is no requirement for geometric connectivity in aggregates.

Transformers that can handle path geometries are:

  • PathBuilder
  • PathSplitter
  • GeometryRefiner

Path Attributes

fme_geometry = fme_line

fme_type = fme_line