Multi-Building Campus Workflow¶
Scenario: Create a comprehensive campus map with multiple buildings connected by outdoor paths
Time: 8+ hours Difficulty: Advanced Best for: Universities, hospital campuses, corporate parks, convention centers
Prerequisites¶
Before starting, ensure you have:
- ✅ Completed Multi-Floor Workflow or equivalent experience
- ✅ Floorplans for all buildings and all floors
- ✅ Site map showing building positions and outdoor paths
- ✅ List of building entrances and connections
- ✅ Understanding of Transit Groups concept
Workflow Overview¶
1. Plan Structure (30-60 min)
└── Map out all buildings
└── Identify outdoor connections
└── Plan Transit group strategy
2. Create All Buildings (4-8 hours)
└── Follow multi-floor workflow for each
└── Mark entrance access points
└── Complete each building fully
3. Create Transit Group (1-2 hours)
└── Add "Outside" group
└── Draw outdoor paths layer
└── Connect all building entrances
4. Link Buildings to Transit (30-60 min)
└── Twin building entrances to outdoor paths
└── Verify campus-wide connectivity
5. Test & Publish (30 min)
└── Test cross-building routes
└── Optimize problematic paths
└── Publish
Step 1: Plan Structure (30-60 minutes)¶
1.1 Map Your Campus¶
Before creating anything in MapBoot, plan on paper or spreadsheet:
List all buildings:
1. Main Library (4 floors)
2. Science Building (3 floors)
3. Student Center (2 floors)
4. Administration (2 floors)
...
Identify connections:
- Library ← outdoor path → Science Building
- Science Building ← outdoor path → Student Center
- Student Center ← outdoor path → Administration
- Library ← outdoor path → Administration (shortcut)
Mark entrances:
Library:
- Main entrance (south side)
- Side entrance (east side)
Science Building:
- Front entrance (west side)
- Loading entrance (north side, staff only)
...
1.2 Decide on Transit Strategy¶
Option A: Single Transit Layer (Recommended for most) - One "Outside" group with one "Paths" layer - All outdoor connections on the same layer - Simpler to manage
Option B: Multiple Transit Layers - Separate layers for different outdoor levels - Use if buildings have entrances at different elevations - Example: Ground level paths + Elevated walkways
Recommendation
Start with Option A. Only use multiple transit layers if you truly have distinct elevation levels for outdoor paths.
✅ Checkpoint: Campus structure is planned with all buildings, entrances, and connections documented.
Step 2: Create All Buildings (4-8 hours)¶
2.1 Create Each Building Completely¶
For each building, follow the Multi-Floor Workflow:
- Create a Group (e.g., "Library")
- Add Layers for each floor
- Upload and align blueprints
- Draw geometry for all floors
- Create routing networks
- Twin internal transitions (elevators/stairs)
- Add locations
Team Collaboration
This is where team collaboration shines. Assign each building (or each floor) to different team members. See Collaboration Guide.
2.2 Mark Building Entrances¶
Critical for campus connectivity:
On each building's ground floor (or appropriate entrance floor): 1. Identify all entrances (main, side, emergency, service) 2. Place access points (key icon) at each entrance 3. Connect these entrance points to the building's internal routing network 4. Name them clearly (e.g., "Library Main Entrance", "Library East Entrance")
Entrance Connection
Each entrance access point MUST be connected to the building's internal routing network. Otherwise, cross-building routes will fail.
2.3 Document Entrance Positions¶
As you complete each building, note the XY coordinates of entrances:
Library Main Entrance: X: 100, Y: 50
Library East Entrance: X: 150, Y: 70
Science Building Front: X: 200, Y: 55
Student Center Main: X: 150, Y: 150
...
You'll use these coordinates when drawing outdoor paths.
✅ Checkpoint: All buildings are complete, all entrances are marked and connected to internal routing.
Step 3: Create Transit Group (1-2 hours)¶
3.1 Create the Transit Group¶
- At Map level, click "Add Group"
- Name it "Outside" (or "Campus Paths")
- Important: Set Type to "Transit"
- This marks it as a non-building transition area
3.2 Add Transit Layer¶
- Select the "Outside" group
- Click "Add Layer"
- Name it "Outdoor Paths" (or simply "Paths")
3.3 Optional: Upload Site Map¶
If you have a site/campus map image: 1. Select the "Outdoor Paths" layer 2. Upload the site map as blueprint 3. Scale and position it so buildings align with their groups 4. Set opacity to 50% for visibility
3.4 Draw Outdoor Paths¶
Strategy: - Draw routing lines (style: None) that follow actual walkways, sidewalks, and paths - Connect each building entrance to this outdoor network - Create realistic paths (don't draw straight lines through grass if no path exists)
Step-by-step: 1. Select Line tool 2. Set line style to "None" 3. Start at one building entrance coordinates (from your notes) 4. Draw line following the actual walkway path 5. Continue to the next building entrance 6. Connect all building entrances via realistic paths
Example:
Library Main (100, 50)
→ sidewalk line to (125, 50)
→ sidewalk line to (150, 60)
→ sidewalk line to (175, 55)
→ Science Building Front (200, 55)
3.5 Create Path Intersections¶
Where paths cross: 1. Draw lines that intersect 2. MapBoot will automatically create shared points at intersections 3. This creates a realistic network with multiple route options
3.6 Add Access Points at Connections¶
At each point where outdoor path meets a building entrance: 1. Create an access point (key icon) 2. These will be twinned with building entrance points
Naming Convention
Name outdoor access points to match buildings (e.g., "Library Main - Outside", "Science Front - Outside")
✅ Checkpoint: Transit group exists with outdoor path network covering all building entrance locations.
Step 4: Link Buildings to Transit (30-60 minutes)¶
4.1 Understand Cross-Group Twinning¶
You'll twin points across different Groups: - Building entrance point (inside building) - Outdoor path point (on Transit layer)
Same process as floor-to-floor, but across groups instead.
4.2 Link Each Building Entrance¶
For each building entrance:
- Multi-select the two layers:
- Ctrl/Cmd+Click the building's ground floor layer (or appropriate entrance floor)
-
Ctrl/Cmd+Click the "Outdoor Paths" layer (primary)
-
Select the outdoor access point (on Outdoor Paths layer)
-
In Properties, find "Twins"
-
Click "Pick"
-
Click the matching building entrance point (should be at same XY position)
-
Verify dashed arrow appears between the layers
-
Repeat for all building entrances
Linking Library to Outside
- Ctrl+Click "Library - Ground Floor"
- Ctrl+Click "Outside - Outdoor Paths" (primary)
- Select "Library Main - Outside" point on outdoor layer
- Click "Pick" in Twins
- Click "Library Main Entrance" point on Library layer
- Dashed arrow connects them
4.3 Verify All Connections¶
After twinning all entrances: 1. Enable Debug mode 2. Check each entrance point shows 2+ connections 3. Check each outdoor connection point shows 2+ connections 4. If any show "1", they're not properly connected
✅ Checkpoint: All building entrances are twinned to outdoor paths, dashed arrows visible for all connections.
Step 5: Test & Publish (30 minutes)¶
5.1 Test Within-Building Routes¶
Verify each building still works independently: 1. Select two locations in the same building 2. Verify route generates 3. Repeat for each building
5.2 Test Cross-Building Routes¶
Critical tests:
Test 1: Adjacent Buildings - Start: Location in Library - End: Location in Science Building - Expected: Route exits Library, follows outdoor path, enters Science Building
Test 2: Distant Buildings - Start: Location in Building A - End: Location in Building D (opposite side of campus) - Expected: Route follows logical outdoor path, possibly through multiple path segments
Test 3: Multiple Entrances - Start: Location near Library's east side - End: Location in Science Building - Expected: Route uses Library's east entrance (closest), not main entrance
Test 4: Multi-Floor Cross-Building - Start: Location on Library 2nd floor - End: Location on Science Building 3rd floor - Expected: Route descends in Library, exits, traverses outdoor, enters Science, ascends
5.3 Analyze Route Quality¶
For each test route, check: - ✅ Uses appropriate building entrance (closest/most logical) - ✅ Outdoor path follows realistic walkways - ✅ Total distance makes sense - ✅ No strange detours or backtracking
5.4 Optimize Problematic Routes¶
If routes are suboptimal:
Issue: Route uses distant entrance instead of closest - Cause: Outdoor path makes distant entrance "shorter" in graph distance - Fix: Adjust outdoor path geometry to better reflect real walking distance
Issue: Route backtracks - Cause: Missing shortcut in outdoor network - Fix: Add more outdoor paths for realistic shortcuts
Issue: Route won't cross between specific buildings - Cause: Outdoor path doesn't connect those buildings - Fix: Add outdoor path segment connecting them
5.5 Save & Publish¶
- Click "Save All"
- Click "Publish"
- Record Map ID
✅ Checkpoint: Campus-wide routing works correctly, map is published.
Final Checklist¶
Structure¶
- ✅ All buildings created as separate Groups
- ✅ Each building has complete floor structure
- ✅ Transit group created (type: Transit)
- ✅ Transit group has outdoor paths layer
Per-Building¶
- ✅ Each building is complete with geometry, routing, transitions
- ✅ All building entrances marked with access points
- ✅ Entrance points connected to internal routing networks
Transit Network¶
- ✅ Outdoor paths layer drawn
- ✅ Paths follow realistic walkways
- ✅ All building entrance locations have corresponding outdoor points
- ✅ Outdoor network is connected (no isolated segments)
Cross-Building Connections¶
- ✅ Every building entrance twinned to outdoor network
- ✅ Dashed arrows visible for all building-outdoor connections
- ✅ Connection points show proper connection counts in Debug
Locations¶
- ✅ All important places added across all buildings
- ✅ Location names include building information
- ✅ All locations have access points
Testing¶
- ✅ Within-building routing works for each building
- ✅ Cross-building routing works for all building pairs
- ✅ Routes use appropriate entrances
- ✅ Routes follow realistic outdoor paths
- ✅ Multi-floor cross-building routes work
Publication¶
- ✅ Map saved and published
- ✅ Map ID recorded
Common Issues¶
"No route between buildings"¶
Diagnosis: - Buildings not twinned to outdoor network - Outdoor network not connected between buildings
Fix: 1. Verify dashed arrows exist from each building to outdoor layer 2. Trace outdoor path from Building A's connection point to Building B's 3. Ensure no gaps in outdoor routing network 4. Check all connection points have 2+ connections in Debug
"Route exits wrong door"¶
Diagnosis: - Router chooses door based on graph distance, not real-world convenience
Fix: - Adjust outdoor path geometry near that entrance - May need to lengthen alternate path to make correct entrance "shorter" - Verify all entrance access points are properly connected
"Outdoor paths appear in wrong location"¶
Diagnosis: - Transit layer positioned incorrectly relative to buildings
Fix: - Buildings don't share coordinate space with Transit layer (this is normal) - Twin connections define the logical link, not visual alignment - Visual position only matters within the same layer
Note: Buildings and Transit layer won't visually align in editor. That's OK—the twins define connections.
"Route uses strange path across campus"¶
Diagnosis: - Missing outdoor paths create artificially long alternate routes
Fix: - Add more realistic outdoor path connections - Ensure common shortcuts exist in network - Verify outdoor network follows how people actually walk
Advanced Topics¶
Multi-Level Transit¶
For campuses with elevated walkways or underground tunnels:
- Create multiple layers in Transit group
- "Ground Level Paths"
- "Elevated Walkways"
-
"Underground Tunnels"
-
Twin building entrances at appropriate levels
- Building 1, Floor 2 ↔ Elevated Walkway
-
Building 2, Basement ↔ Underground Tunnel
-
Create transitions between transit layers
- Stairs/elevators connecting ground to elevated
- Stairs connecting ground to underground
Restricted Paths¶
For staff-only outdoor paths:
Approach 1: Omit them - Don't draw restricted paths at all - Public routes will use public paths only
Approach 2: Mark them - Draw restricted paths - Add metadata to nearby locations - (Requires custom viewer configuration for access control)
Parking & Transportation¶
To include parking lots, bus stops:
- Add locations on Transit layer
- Place them along outdoor paths
- Use appropriate location types (parking, bus stop, etc.)
- Users can now route from parking to buildings
Large Campuses (20+ Buildings)¶
Optimization strategies:
- Phase the work: Complete one section of campus, publish, then add more
- Use collaboration: Assign buildings or sections to team members
- Simplify outdoor network: Use major paths only, skip minor shortcuts
- Test incrementally: Don't wait until all buildings are done to test
Team Collaboration Strategy¶
For large campuses, divide work efficiently:
Option A: By Building - Person 1: Buildings A, B, C - Person 2: Buildings D, E, F - Owner: Transit group and final connections
Option B: By Floor - Person 1: All ground floors - Person 2: All upper floors - Person 3: All basement levels - Owner: Transit group and final connections
Option C: By Zone - Person 1: North campus buildings + north outdoor paths - Person 2: South campus buildings + south outdoor paths - Owner: Connect zones and final verification
See Collaboration Guide for setup details.
Next Steps¶
Enhance Your Campus Map¶
- Add more outdoor locations (sculptures, fountains, landmarks)
- Include parking and transportation
- Add more path shortcuts
- Optimize routing for accessibility
Advanced Features¶
- Custom location types with icons
- Rich location metadata for better search
- Accessibility routing (step-free paths)
Maintenance¶
- See Updating Published Maps
- Plan for ongoing updates as campus changes
Time-Saving Tips¶
- Complete one building fully before moving to the next
- Document entrance coordinates as you go
- Test building-to-building connections incrementally (don't wait until all buildings are done)
- Reuse naming conventions across buildings
- Use copy-paste for similar building structures
Need help with complex campus mapping? Email contact@mapboot.com for consultation.