How automatic map generation will work

The intended pipeline

1. 1

   Upload

   The recording (trajectory, frames and their links) is sent from Veeee Mapper to the organization’s indoor map. Coming soon.

2. 2

   Generation

   Veeee turns the trajectory into a navigation graph: destinations become locations, corridor junctions and turns become hidden navigation geometry, and the walked distances become connections in metres. Frames taken at each destination become its reference images. Coming soon.

3. 3

   Review

   The generated map appears in the workspace as a draft for the team to check: rename locations, fix types and floors, add missing aliases, and only then publish. Coming soon.

Importing a generated map today

Owners and administrators can already bring a generated map into a workspace. On a map that is not archived, open More actions › Import generated map. The dialog accepts a navigation_package.zip generated from a Veeee Mapper recording, or the older generated navigation graph, points-of-interest and node-to-frame JSON files with the frame images or their zip archive.

• A navigation package is reviewed before anything is added. The plan shows the clean navigation map: corridors, intersections, turns and destination candidates. A map drawn from the phone’s tracked walk alone is marked Approximate layout; low-confidence corridors are dashed and listed under To check with the generator’s explanation. The walked track can be shown faintly for comparison.
• Drag intersections and turns to correct the drawing. Connections keep the distance measured on the walk unless you type another length for a corridor; when the drawing and the distance differ a lot, both are shown.
• Destination candidates are the places where the walk started, ended or stood still. Confirm the real destinations and give each the name visitors use and a type, and choose which suggested frames to attach as reference images. Nothing is named for you; a candidate you don’t confirm stays a hidden navigation point.
• For the older JSON files, Scale (metres per world unit) is required and has no default: a measured walking distance divided by the generated weight of the same route. Generated weights are not metres until this is applied.
• Confirmed destinations and points of interest become locations. Every other generated node becomes a hidden navigation point. Connections are hallway connections in both directions, in metres.
• Frames are attached to locations only. A location needs at least two usable images to be recognised; three are recommended.
• The import keeps a ledger, so Import again continues where it left off without creating duplicates.