Quality Checklist¶

Use this checklist before publishing your map to ensure professional quality and reliable routing.

Quick Quality Test (5 minutes)¶

Run these tests to catch major issues:

Test Route Generation
✅ Can generate a route between any two locations
✅ Routes follow logical paths (no strange detours)
✅ Routes use appropriate doors/entrances
Test Location Search
✅ All important locations appear in search
✅ Location names are clear and descriptive
✅ Selecting locations highlights correct areas
Test Multi-Floor/Building (if applicable)
✅ Can route between different floors
✅ Can route between different buildings
✅ Transitions appear in correct locations
Visual Check
✅ Walls render cleanly (no gaps or overlaps)
✅ Surfaces fill correctly (no holes)
✅ Labels and icons appear in logical positions

Detailed Quality Checklist¶

Map Structure¶

✅ Map name is descriptive and professional
✅ Reference unit (m or ft) is correct for your region
✅ Allowed domains includes your website (if embedding)
✅ Groups are named clearly (e.g., "Main Library", not "Group 1")
✅ Layers are named clearly (e.g., "Ground Floor", not "Layer 1")
✅ No unnecessary DEV-tagged groups/layers in final version

Blueprint Quality¶

✅ All blueprints uploaded for all floors
✅ Blueprint scale matches real-world dimensions
Verify by measuring multiple known distances
Standard door width (0.9m / 3ft) is accurate
✅ Blueprints aligned across floors (for multi-floor buildings)
Elevators/stairs appear at same XY coordinates
Load-bearing walls align vertically
✅ Blueprint opacity set appropriately (60-70% recommended)

Graphics Layer Quality¶

Walls¶

✅ All walls drawn as they appear on blueprint
✅ Wall corners connect properly (no overlaps or micro-gaps)
✅ Exterior walls have "Thick" style
✅ Interior walls have "Thin" style
✅ Wall lines are clean (use Snap for straight walls)
✅ Walls are on Graphics sub-layer (separate from Routes)

Surfaces¶

✅ Floor has base surface ("Basic" style)
✅ Polygons fill completely (no holes or artifacts)
✅ Public areas use "Public" style
✅ Private/restricted areas use "Private" style
✅ Surfaces match intended areas (zoom in to verify edges)

Routes Layer Quality¶

✅ Routes network drawn through all accessible areas
✅ Routes drawn on Routes sub-layer (not Graphics sub-layer)
✅ All location access points connected to routes network
Enable Debug mode
Verify each access point shows 2+ connections
✅ Network is continuous (no isolated segments)
Test by routing to various locations
✅ Realistic paths (follows actual walking routes)
✅ Routes pass through entrances and accessible areas
✅ Shortcuts included where people actually walk
✅ No micro-gaps in routes network
Zoom in to verify true connections
Points must share vertices, not just appear close

Locations¶

Basic Requirements¶

✅ All important places added as locations
✅ Every location has a name (searchable)
✅ Every location has at least one access point
✅ Access points are connected to routing network

Quality Standards¶

✅ Names are clear and descriptive
Good: "Conference Room A - First Floor"
Bad: "Room 201"
✅ Names include floor for multi-floor buildings
✅ Metadata filled in for better search
Keywords, tags, categories
Think about how users will search
✅ Descriptions are helpful (optional but recommended)
What the location is used for
Capacity, features, etc.
✅ Location markers positioned logically
Near center or main entrance
Not obscured by other elements
✅ All entrance doors added as access points
If room has 3 doors, add all 3 as access points
Router will choose optimal door automatically
✅ Surfaces assigned where appropriate
Rooms that should highlight when searched
Multiple surfaces if location spans areas

Transitions (Multi-Floor/Building)¶

Floor-to-Floor¶

✅ All elevators twinned across all floors they serve
✅ All stairwells twinned across floors they connect
✅ Escalators twinned (and one-way if appropriate)
✅ Transition points at same XY across floors
✅ Dashed arrows visible for all transitions
✅ Transition points connected to routing networks on both floors
Debug mode shows 2+ connections on each floor
✅ Bidirectional unless intentionally one-way

Building-to-Building¶

✅ Transit group created (type: Transit)
✅ Outdoor paths drawn connecting all buildings
✅ All building entrances have access points
✅ Building entrances twinned to outdoor network
✅ Outdoor network is continuous (no gaps)
✅ Paths follow realistic routes (sidewalks, not through grass)

Testing¶

Routing Tests¶

✅ Test within single floor
Pick 5+ random location pairs
Verify routes generate
Verify routes are logical
✅ Test multi-floor (if applicable)
Route from ground to top floor
Route between adjacent floors
Route using different transitions
✅ Test multi-building (if applicable)
Route between all building pairs
Verify correct entrances used
Verify outdoor paths are followed
✅ Test edge cases
Locations near map boundaries
Locations with multiple access points
One-way transitions (if any)

Search Tests¶

✅ Search for each location by name
✅ Search for locations by metadata/keywords
✅ Verify all locations found
✅ Verify search results are relevant

Visual Tests¶

✅ Zoom in and out to check rendering at all scales
✅ Check all floors visually
✅ Verify transitions appear in correct positions
✅ Check location labels don't overlap excessively
✅ Test on preview mode

Performance & Optimization¶

✅ Geometry is not overly complex
Avoid hundreds of tiny segments where one line would suffice
Simplify walls that don't need extreme detail
✅ Routing network is efficient
Not every wall corner needs a routing point
Main paths with logical connections are sufficient
✅ Polygon count reasonable
Don't create separate polygons for tiny areas unless necessary
✅ Location count is manageable
Focus on searchable, navigable places
Avoid creating locations for every desk/seat

Accessibility Considerations¶

✅ Wheelchair-accessible routes considered
Ramps marked (if relevant to routing)
Step-free paths available (if campus supports this)
✅ Accessible entrances marked
Can be metadata on locations/access points
✅ Elevator access for all floors (if building has elevators)

Documentation & Metadata¶

✅ Location metadata includes useful information
Building names, floor numbers, room numbers
Department names, services offered
Keywords users might search for
✅ Custom location types used appropriately (if feature available)
Restrooms, parking, services, etc.
Consistent iconography

Final Pre-Publication¶

✅ All work saved
✅ Tested in preview mode
✅ No placeholder names (e.g., "Location 1", "Room TODO")
✅ No DEV-tagged items in final version (unless intentional)
✅ Team has reviewed (if applicable)
✅ Map ID recorded for embedding
✅ Allowed domains configured (if embedding)

Common Quality Issues¶

Issue: Routes Go Wrong Way¶

Symptoms: - Route takes a long detour instead of direct path - Route uses distant door instead of nearby door - Route backtracks unnecessarily

Likely Causes: - Missing routing shortcut - Misconnected routing network - Wall-styled line blocking direct path

Fixes: 1. Enable Debug mode 2. Trace the expected path 3. Verify all segments exist and connect 4. Add missing routing lines on Routes sub-layer 5. Verify routing lines are on Routes sub-layer (not Graphics)

Issue: Location Not Found in Search¶

Symptoms: - Location doesn't appear when searched - Location appears but can't be selected

Likely Causes: - No name filled in - No access points defined - Access points not connected to routing network

Fixes: 1. Verify location has a Name 2. Verify location has at least one Access Point 3. Verify access point connects to routing network (2+ connections in Debug) 4. Re-publish map after fixing

Issue: No Route Between Floors¶

Symptoms: - Can route within a floor but not between floors - "No route found" when trying cross-floor navigation

Likely Causes: - Transition not twinned - Transition point not in routing network - Missing routing line to transition point

Fixes: 1. Verify dashed arrow appears between floors 2. Select transition point, check Twins list 3. Enable Debug, verify transition point has 2+ connections on both floors 4. Add routing line connecting to transition point if needed

Issue: No Route Between Buildings¶

Symptoms: - Can route within each building but not between them - Outdoor path doesn't connect

Likely Causes: - Building entrances not twinned to outdoor network - Outdoor network has gap - Building entrance not connected to internal routing

Fixes: 1. Verify dashed arrows from each building to Transit layer 2. Trace outdoor path between buildings, ensure no gaps 3. Verify building entrance access points have 2+ connections internally 4. Verify outdoor connection points have 2+ connections to paths

Issue: Surfaces Don't Fill¶

Symptoms: - Polygon style applied but area doesn't fill - Partial fill or holes in surface

Likely Causes: - Line loop not completely closed - Micro-gap in wall connections - Overlapping points instead of shared points

Fixes: 1. Zoom in to verify all endpoints truly connect 2. Enable Snap, move points to ensure connections 3. Check for duplicate points at same location 4. Reapply polygon style after fixing

Quality Scoring¶

Use this simple scoring system to assess your map:

Bronze (Minimum Publishable)¶

✅ Map structure complete
✅ Basic geometry drawn
✅ Routing works for most locations
✅ Major locations added

Silver (Good Quality)¶

✅ All Bronze requirements
✅ All locations searchable
✅ Clean visual appearance
✅ Routing works for all locations
✅ Multi-floor/building routing works (if applicable)

Gold (Professional Quality)¶

✅ All Silver requirements
✅ Rich location metadata
✅ Optimal routing paths
✅ No visual artifacts
✅ Comprehensive testing completed
✅ Accessibility considered

Platinum (Exceptional)¶

✅ All Gold requirements
✅ Custom location types and icons
✅ Advanced metadata and search optimization
✅ Accessibility routes fully mapped
✅ Regular updates and maintenance plan

Aim for at least Silver before publishing to customers.

Checklist Templates¶

Quick Pre-Publish Checklist (Print/Copy)¶

Text Only

□ Map saved
□ All floors complete
□ Test: Route between 5 location pairs
□ Test: Search for 5 locations
□ Test: Multi-floor routing (if applicable)
□ No placeholder names
□ Allowed domains configured
□ Map published
□ Map ID recorded

Comprehensive Quality Audit (For Large Projects)¶

Text Only

Structure:
□ Map name
□ Units
□ Groups named
□ Layers named
□ Blueprints uploaded
□ Blueprints scaled
□ Blueprints aligned

Geometry:
□ Walls complete
□ Doors marked
□ Surfaces applied
□ No gaps or overlaps

Routing:
□ Network drawn
□ Style is None
□ Doors connected
□ Network continuous
□ Debug verified

Locations:
□ All added
□ All named
□ Metadata filled
□ Access points defined
□ Access points connected

Transitions:
□ Elevators twinned
□ Stairs twinned
□ Outdoor connections (if applicable)
□ Transitions connected to routing

Testing:
□ Single-floor routes
□ Multi-floor routes
□ Multi-building routes
□ Search functionality
□ Visual check

Final:
□ Saved
□ Published
□ Map ID recorded

Need Help?¶

If your map fails quality checks:

Review Troubleshooting Guide
Revisit Core Concepts
Check workflow guides for your scenario
Email contact@mapboot.com with specific issues

Remember: Quality over speed. Taking extra time to ensure routing works correctly will save support headaches later.