A Message generated by the application, either instantly or on request. In WFP 1.3.0, automatic route messages are destination-backed when the target point is bound to a destination. See: Automatic and manual messages.

A quick process (about 15–20 seconds) that sets the drawing’s scale to real‑world dimensions; ±0.5 m accuracy is typically sufficient. See: Level properties.

A junction in the Path Network where visitors choose a direction; compatible with Direction or Navigation Sign Faces. See: Path points and segments, Sign categories.

A dictionary entry representing a destination message, such as a room, gate, department, or attraction. A Destination can be bound to one target point and can belong to one or more Destination Groups. See: Destination Dictionary.

The project-wide dictionary of Destinations and Destination Groups used for automatic message generation, manual destination-backed messages, grouping, progressive disclosure, and CSV import/export. See: Destination Dictionary.

A dictionary entry that groups related Destinations so WFP can display a broader group message when progressive-disclosure and capacity rules allow it. See: Destination Dictionary.

Four 90° sectors (Forward, Left, Right, Backward) relative to a Sign Face’s rotation; used to assign routes to directions. See: Direction zones.

An optional background image (e.g., floor plan) that provides context and enables realistic walking‑distance calculations; requires calibration after import. See: Level properties.

A two‑dimensional plane at a fixed height (elevation) above ground (a building floor is a typical example). Each Level contains its own Path Network and an optional background drawing. Identified by a code such as L1—used in reports and to generate unique Sign and Sign Face IDs. Only one Level may exist at a given elevation. See: Levels.

A directional sign type face configuration that dynamically creates virtual faces from the path network topology around the decision point. Fingerpost signs use per-direction and whole-sign message capacity. See: Sign types.

A Message entered and maintained by the user. See: Automatic and manual messages.

Content displayed on Sign Faces (labels/directions). Determined by Sign Type, Path Network layout, Sign Face rotation, Destination Dictionary content, and manual overrides. See: Messages.

A destination or group message field that stores both a value and a type. It can be Text or Number. Destinations and groups can store Main Message, Message 1, and Message 2. See: Editing Message Atom Fields.

The WFP planning layer that resolves routes, applies destination dictionary groups and progressive disclosure, packs messages into sign capacity, preserves manual overrides, and creates selected or overflow automatic messages. See: Message generation layer.

A report or view listing Messages with the Sign ID, Sign Category, Sign Type description, and, where applicable, Direction. When exported, it uses CSV format. Example:

The representation of physical space and signage: Levels, Path Networks (Path Points + Path Segments), Destination Dictionary, Signs, Sign Faces, and Messages. See: Model overview.

An automatic message generated by WFP but left unselected because a sign face or Fingerpost sign has reached its message capacity. See: Message generation layer.

The graph of walkable paths on a Level, consisting of Path Points connected by Path Segments; it maps how people move through the space. See: Model overview, Path points and segments.

A 2‑D point within a Level’s plane; can be a Target Point, Decision Point, or Supportive Point. See: Path points and segments.

A straight line connecting two Path Points; its property is the walking distance (length). See: Path points and segments.

A destination or group value used by the message generation layer to prefer higher-priority messages when capacity is limited. See: Destination Dictionary.

The orientation of a Sign Face, measured counterclockwise from the positive X‑axis. See: Sign faces.

The Sign is a fixed set of sign faces as defined by its Sign Type. The Sign is attached to a Path Point, has a position on the Level and a rotation angle. The Sign is identified by a unique code combining the Sign Type code, Level Code, and a sequential number (e.g., D2-L0.01). See: Signs.

A functional class of Sign Types that determines the kind of Messages shown. Categories include: Direction, Navigation, and Identification. See: Sign categories.

The sign's surface that displays Messages to guide visitors. A Sign Face belongs to a Sign and is identified by a unique identifier combining the Sign ID code and sign face's label, usually a Latin letter (e.g., D2-L0.01A). See: Sign Face

A drawing in PDF or SVG format showing sign faces on the Level's plan. If the Level has a drawing, it is used as a background. Example:

A report or a view containing counts of sign faces by Sign Type, combined with Sign Type's properties. Exported in CSV format. Example:

A template used to create Sign instances. Belongs to a Sign Category and defines a face configuration, message capacity, and sign properties such as fixing, connectivity, dimensions, drawing reference, and outline. Identified by a code such as D2. See: Sign types.

An optional destination or group distance limit used by automatic message generation. If a route is longer than the effective signing distance, that destination or group is not signed from that route position. See: Destination Dictionary.

An ancillary Path Point used solely to shape the Path Network; no Sign Face can be attached. See: Path points and segments.

A path point representing the physical location of a destination. A Target Point can be bound to a Destination Dictionary entry and can host an Identification Sign Face. See: Path points and segments.

A project setting that enables and orders fallback fonts for destination dictionary text, including Arabic, Simplified Chinese, Traditional Chinese, Hong Kong Traditional, Japanese, and Korean. See: Destination Dictionary.

A complete project, stored as a single .wfp file, containing the model and all design metadata. See: Model overview.