Best Practices¶

Professional tips and techniques for creating high-quality MapBoot maps.

Blueprint Preparation¶

Before You Start Mapping¶

Get Quality Images: - ✅ Request CAD exports or high-resolution PDFs from facilities team - ✅ Minimum 1000px width per floor - ✅ PNG or JPG format (PNG preferred for line clarity) - ✅ Remove unnecessary annotations (furniture, labels) if possible

Ensure Consistency: - ✅ All floors for the same building should use the same scale - ✅ Load-bearing walls/columns should align vertically across floors - ✅ Blueprints should show dimensions or include a scale bar

Pre-Processing: - ✅ Crop to just the building footprint (remove excess whitespace) - ✅ Rotate to north-up or standard orientation - ✅ Adjust contrast if blueprint is faded - ✅ Convert to web-optimized JPG if file is too large (> 5MB)

Drawing Techniques¶

Walls¶

Start with Structure: 1. Draw exterior perimeter first 2. Draw major interior walls (load-bearing) 3. Fill in partition walls last 4. Apply styles after drawing (perimeter vs. interior)

Use Snap for Clean Lines: - Enable Snap to Grid for straight walls - Zoom in when drawing to avoid micro-misalignments - For angled walls, place points carefully

Handle Corners Properly: - Ensure corners truly connect (shared point, not overlapping) - Use Snap to ensure clean intersections - Check in Debug mode (corner points should show 2+ connections)

Draw Walls as Visual Elements: - Walls are purely visual (Graphics sub-layer) - Draw walls as they appear on your blueprint (with or without door gaps) - Door gaps in walls are for visual representation only - Walls don't affect routing (routing is on Routes sub-layer)

Routing Network¶

Graphics vs Routes

The routing network is on a separate routes layer from graphics/walls. Routes define where people can walk and are completely independent of wall graphics.

Think Like a Walker: - Draw paths where people actually walk on the routes layer - Include common shortcuts (even diagonal paths across open areas) - Follow center of corridors and walkways - Routes pass through doorways and connect all accessible areas

Network Topology: - Routes are on a separate layer from graphics - Style must be "None" for all routing lines - Create a continuous network (no isolated segments) - All location access points must connect to the routes network - Use reasonable node density (don't need a point every meter)

Verify Connectivity: - Enable Debug mode frequently - Access points should show 2+ connections in routes network - Test routing to various locations before moving to next floor

Avoid Common Mistakes: - Don't confuse graphics layer with routes layer - Don't use wall-styled lines for routing - Don't leave access points unconnected to routes network - Don't create isolated routing islands

Surfaces & Polygons¶

Create Clean Polygons: - Ensure loops are completely closed (no micro-gaps) - Zoom in to verify endpoints connect - Use Snap when closing loops

Use Styles Appropriately: - Basic — Base floor surface (everything) - Public — Areas users should search for (rooms, departments) - Private — Staff areas, maintenance (exists but not highlighted)

Keep It Simple: - Don't create tiny polygons (combine small adjacent areas) - Don't over-segment large spaces unless necessary - Surfaces are visual only — don't need perfect precision

Location Strategy¶

Creating Location Markers¶

Routes Layer Only

Location markers (orphan points) can only be created on the routes layer. If you create an orphan point on the graphics layer, it will be automatically deleted. This is because locations are part of the routing system.

How to create: 1. Switch to routes layer 2. Click the Add Point button (+) in the toolbar 3. Click where you want the label 4. Press Esc immediately to create orphan point

Drawing vs Selection

The Point/Line/Polygon buttons are for selection mode. To draw, use the Add Point button (+).

What Deserves a Location?¶

Create locations for: - ✅ Searchable destinations (offices, conference rooms, departments) - ✅ Services (restrooms, cafeteria, help desk) - ✅ Points of interest (exhibits, collections, departments) - ✅ Building entrances (for wayfinding reference)

Don't create locations for: - ❌ Every desk or seat - ❌ Purely decorative elements - ❌ Locations users won't search for - ❌ Temporary/frequently changing places

Naming Conventions¶

Good Names: - Clear and descriptive: "Conference Room A - First Floor" - Include context: "Dr. Smith's Office - Psychology Department" - Use official names: "Marie Curie Science Center"

Bad Names: - Cryptic codes: "RM-201-B" - Ambiguous: "Conference Room" (which one?) - No floor info in multi-floor: "Break Room" (which floor?)

Consistency Matters: - Use same naming pattern throughout - Include floor numbers in multi-floor buildings - Use official department/room names

Metadata & Searchability¶

Fill in Rich Metadata: - Add all alternative names/spellings - Include department names, building names - Add function keywords ("meeting", "restroom", "food") - Think about how users will search

Examples:

Text Only

Name: Conference Room A - Second Floor
Description: Large conference room with video conferencing, seats 20
Meta Data: meeting, conference, presentation, video call, 2nd floor, room A

Access Points¶

Add All Entrances: - If a room has 3 doors, define all 3 as access points - Router will automatically choose the closest/best one - More access points = better routes

Connect to Network: - Every access point must connect to routing network - Verify with Debug mode (2+ connections) - Don't just place access points — ensure connectivity

Location Markers¶

Position Thoughtfully: - Place marker where label should appear - Usually near center or main entrance - Avoid overlap with other labels - Consider visibility at different zoom levels

Multi-Floor Best Practices¶

Alignment is Critical¶

Before Drawing: 1. Upload all floor blueprints first 2. Identify fixed reference points (elevator shafts, structural columns) 3. Scale all blueprints identically 4. Position so references align vertically

Why It Matters: - Transitions appear at same XY coordinates - Visual continuity when switching floors - Less confusing for users

Transition Placement¶

Mark Transitions Clearly: - Place access points at exact transition locations - Use same XY coordinates across floors - Name them clearly ("Main Elevator - Ground", "Main Elevator - 1st")

Twin Systematically: - Complete one building fully before starting next - Twin all elevators first, then all stairs - Test each transition immediately after creating

Connection Strategy: - Chain method for most elevators (Ground ↔ 1st ↔ 2nd ↔ 3rd) - Full mesh only if needed (express elevators, special access) - Test cross-floor routing after all transitions created

Multi-Building Best Practices¶

Planning is Essential¶

Before You Start: - Draw a site map on paper showing all buildings and connections - List all building entrances - Plan outdoor path routes - Identify which entrances connect to which paths

Transit Group Strategy¶

Create One Transit Group: - Name it "Outside" or "Campus Paths" - Set type to Transit - Keep all outdoor connections in this one group - Simplifies management

Draw Realistic Outdoor Paths: - Follow actual sidewalks and walkways - Don't draw straight lines through grass/buildings - Include common shortcuts - Create path intersections where paths cross

Building Connections¶

Systematic Approach: 1. Complete all buildings individually first 2. Mark all building entrances with access points 3. Create Transit group and outdoor path network 4. Twin each building to outdoor network 5. Test each building-to-building route pair

Entrance Strategy: - Mark all entrances (main, side, service) - Twin all of them to outdoor network - Router will choose optimal entrance automatically

Performance Optimization¶

Keep Maps Efficient¶

Geometry: - Simplify where possible (don't trace every tiny detail) - Use straight lines for straight walls - Combine small segments into fewer, longer lines - Remove duplicate or overlapping geometry

Routing Network: - Don't create routing nodes every meter - Use logical spacing (intersections, doors, turns) - Remove unnecessary routing complexity - Test that simplified network still routes correctly

Locations: - Focus on searchable, important destinations - Don't create locations for every possible spot - Combine similar/nearby items into single locations

Blueprint Optimization¶

File Size: - Optimize images before upload (< 5MB recommended) - Use JPG for photos/scans, PNG for line drawings - Reduce resolution if blueprint is unnecessarily large - Crop to just the building footprint

Quality Assurance¶

Test As You Go¶

Per-Floor Testing: - Test routing after completing each floor - Verify all locations are searchable - Check surfaces fill correctly - Fix issues immediately (easier than debugging later)

Integration Testing: - Test multi-floor routing after twinning transitions - Test multi-building routing after outdoor connections - Try various location pairs, not just one

Before Publishing¶

Run Full Checklist: - Use Quality Checklist - Test routing between 10+ location pairs - Search for all major locations - Check visual appearance at multiple zoom levels - Test on mobile device

After Publishing¶

Monitor Initial Usage: - Check for user-reported issues first few days - Spot-check some routes in live viewer - Be ready to hotfix critical problems

Collaboration Best Practices¶

For Owners¶

Setup: - Create entire structure (all groups, all layers) before assigning - Use clear naming for everything - Document which collaborator is assigned to what

Assignment Strategy: - By building — Person A does Library, Person B does Science Building - By floor — Person A does all ground floors, Person B does all upper floors - By zone — Person A does north campus, Person B does south campus

Communication: - Set clear expectations and deadlines - Provide naming conventions and standards - Review work regularly - Owner handles all cross-building connections

For Collaborators¶

Follow Standards: - Use owner's naming conventions - Match style and detail level to other floors - Save frequently - Communicate issues promptly

Stay in Scope: - Only edit assigned floors - Don't modify structure or add/remove groups - For cross-floor transitions, coordinate with owner - Test your work in preview mode

Maintenance & Updates¶

Regular Maintenance¶

Monthly: - Spot-check routing functionality - Review user-reported issues - Update location information as needed

Quarterly: - Full routing test - Update location metadata - Check for blueprint updates (renovations) - Optimize routing network if needed

Annually: - Comprehensive quality audit - Major updates for facility changes - Blueprint refresh if renovations occurred

Making Updates Safely¶

Process: 1. Document what needs to change 2. Make changes in editor (don't publish yet) 3. Test thoroughly in preview mode 4. Publish during low-traffic period 5. Test immediately in live viewer 6. Monitor for issues

See: Updating Published Maps for detailed guidance

Common Pitfalls to Avoid¶

❌ Don't Do These¶

Drawing without Snap — Creates misaligned geometry
Not verifying connections — Leads to routing failures
Using wall styles on routing lines — Blocks pathfinding
Forgetting to publish — Changes remain private
Not testing multi-floor routing — Transitions may not work
Skipping metadata — Locations hard to find in search
No backup strategy — Risk losing work to browser crash
Batch all changes before testing — Makes debugging hard
Not using Debug mode — Can't verify connectivity
Assuming visual proximity = connection — Must be true shared points

Advanced Techniques¶

Efficient Bulk Operations¶

Copy-Paste Similar Structures: - Draw one typical room fully - Copy and paste to similar rooms - Adjust positioning as needed - Saves time on repetitive layouts

Batch Styling: - Draw all walls first without styles - Select multiple lines at once - Apply style to entire selection - Faster than styling individually

Complex Routing Scenarios¶

One-Way Paths: - Remove reverse twin for escalators - Use for exit-only stairs - Document clearly

Restricted Access: - Create locations but mark in metadata - Or omit from public map entirely - Consider separate "staff" map for facilities

Accessibility Routing: - Mark step-free transitions (elevators, ramps) - Can be done via metadata on transitions - (Future feature: accessibility-specific routing)

Professional Polish¶

Visual Quality¶

Clean, straight walls (use Snap)
Consistent styling across floors
No overlapping labels
Realistic location marker positions
Appropriate surface highlighting

Functional Quality¶

All routes work correctly
All locations searchable
Optimal paths chosen by router
Multi-floor/building navigation seamless
No "dead end" errors

Documentation¶

Clear location names and descriptions
Rich metadata for search
Consistent naming conventions
Internal documentation of map structure
Change log for updates

Resources¶

Quality Checklist — Pre-publication verification
Workflows — Step-by-step guides
Troubleshooting — Fix common issues
Core Concepts — Understand the fundamentals

Remember: Quality takes time. A well-built map saves countless hours of troubleshooting and user support later.