RoomScan Pro LiDAR floor plans vs Wikilayer

Professional floor plan scanning that works in every room. If your work requires floor plans every day and you aren't using RoomScan Brick Mode, then you are literally wasting time. Includes Apple RoomPlan, as well as the fast & accurate RoomScan Brick Mode for LiDAR devices, and Touch Mode which works in dim light on any device. Also compatible with a range of Bosch and Leica Bluetooth laser measures. Exports to PNG, PDF, DXF (for CAD), IFC (great in Autodesk® and SketchUp®), FML (for Symbility® etc), Xactimate® ESX, Sweet Home 3D, OBJ, PLY, XYZ, RapidSketch, Metropix® and more. • Automatically measures ceiling height and calculates wall areas and heat loss parameters, great for contractors. • Take photos and type or dictate notes onto them, and see them automatically positioned on the plan. Perfect for surveys, inventories, etc. • Annotate your plans with Apple Pencil. • Also scans building exteriors (great for getting GLA for appraisers) and plots. Questions or comments? We're here to help: service@locometric.com US Patents 8,868,375 (2014) and 11,269,060 (2022). http://locometric.com/privacy.html https://www.locometric.com/terms-and-conditions Unlock RoomScan Pro LiDAR with a monthly auto-renewable subscription. Payment will be charged to iTunes Account at confirmation of purchase. Subscription automatically renews unless auto-renew is turned off at least 24-hours before the end of the current period. Account will be charged for renewal within 24-hours prior to the end of the current period. Subscriptions may be managed and auto-renewal may be turned off by going to your iTunes Account Settings after purchase. Any unused portion of a free trial period will be forfeited if you purchase a subscription.

Wikilayer is a wiki that an AI assistant can read and edit on your behalf. You and your agent work on the same tree. The agent writes through MCP tools: it adds a node, rewrites one, moves a subtree, and reads back by outline instead of loading everything into its context. You read the result here, as ordinary pages. Every block has an address of its own. Rename it, rewrite it, move it under another parent, and links to it still land. Pages that lead to a block are listed under it, and nobody maintains that list by hand. History is kept per node, so a change to one paragraph is a change to one node, not to a whole document. WHAT PEOPLE KEEP HERE Personal notes: a second brain the agent reads selectively instead of holding a whole vault in context. Adding is a message in chat, not an app switch. Project memory: long-running context the agent writes and you audit. Hierarchy and full-text search across titles and bodies, without a separate vector store. Team workspace: decisions, context and meeting digests, written by the team and refactored by the agent. Public reference: guides, handbooks, fan wikis. Readers arrive from search and never touch the editing surface. VISIBILITY A wiki can be open to everyone, private to a team, or run on your own machine. Public wikis are crawlable the day you write them: server-rendered pages, Open Graph, sitemap, structured data, and addresses that survive a rename. WHAT IT IS NOT Not a block editor: bodies are plain markdown edited through MCP, not click-to-edit blocks, and the tree is hierarchical nodes rather than a relational document store. Not a real-time co-editor: each edit lands atomically, and conflicts resolve at write time rather than by merging keystrokes. Not an approval workflow: edits land on the live tree, and the audit trail is a snapshot of each node as it stood before the change. Bodies are markdown and the tools are MCP. Both are public formats, so a wiki reads out as plain documents whenever you want it somewhere else.