Appearance
Tips & Best Practices
Layer Management Tips
Keep It Clean
Tip: Only show 3-5 layers during analysis.
Why: More layers = visual noise = harder to see patterns.
How:
- Turn off ALL layers
- Add back only what you need for current task
- Remove when done
Organize by Purpose, Not Source
Tip: Group layers by how you use them, not where they came from.
Good:
- "Base Layers"
- "Analysis Layers"
- "Working Data"
Bad:
- "Government Data"
- "Downloaded Files"
Why: Your brain works in tasks, not sources.
Name Layers Clearly
Tip: Future-you will forget what "Layer1" means.
Format: [Purpose]_[Location]_[Date]
Examples:
Buffer_SchoolZones_500m_2026-02-09Selected_Parcels_ProjectX_2026-02-01
Why: Clear names save time later.
Clean Up Weekly
Tip: Delete old layers every Friday.
Remove:
- Test layers
- Failed outputs
- Superseded data
- One-time use layers
Why: Clean workspace = faster navigation.
Analysis Tips
Always Validate Visually
Tip: Never report analysis you haven't looked at.
Process:
- Run analysis
- Look at the map (does it make sense?)
- Spot-check 2-3 features manually
- Overlay reference layers
- Ask "what if I'm wrong?"
Why: Automated analysis can fail silently. Visual check catches errors.
One Question at a Time
Tip: Break complex analysis into simple steps.
Bad: "Find parcels within 500m of schools AND 100m of roads AND in residential zones"
Good:
- Buffer schools 500m
- Buffer roads 100m
- Select parcels in both buffers
- Filter for residential zones
Why: Easier to debug, explain, and validate.
Save Intermediate Results
Tip: Don't run multi-step analysis without saving steps.
Pattern: Data → Step 1 (save) → Step 2 (save) → Final Output
Why: If Step 3 fails, you don't start over.
Name Analysis Outputs
Tip: Add date and purpose to analysis results.
Good:
Analysis_RoadBuffer_MainSt_2026-02-09Selected_Parcels_500mSchool_2026-02-09
Bad:
Analysis1Output_Final
Why: You'll run many analyses. Names prevent confusion.
Admin Console Tips
Test Before Publishing
Tip: Always preview layers before users see them.
Check:
- Layer name is clear
- Features display correctly
- Attributes are useful
- No duplicates
Why: Users trust published data. Don't break that trust.
Organize Categories for Users
Tip: Design categories from user perspective, not yours.
Ask:
- What will users search for?
- What task are they doing?
- What's the common workflow?
Good: "Zoning", "Infrastructure", "Environment" Bad: "Server1 Data", "New Layers", "Misc"
Why: Users shouldn't need training to find data.
Document Data Sources
Tip: Add notes when connecting new services.
Include:
- Source URL
- Who provided it
- Update frequency
- Known issues
Why: 6 months later, you'll need this info.
Use Audit Logs
Tip: Check logs weekly for unusual activity.
Look for:
- Unexpected deletions
- Access at odd hours
- Bulk data exports
- Configuration changes
Why: Catch issues before they become problems.
Search & Filtering Tips
Use Attribute Filters for Large Datasets
Tip: Filter first, then analyze.
Pattern:
- Filter data to relevant subset
- Run spatial analysis on filtered result
Example: Filter parcels by zone type before buffer analysis.
Why: Faster performance, clearer results.
Save Complex Filters
Tip: Don't rebuild the same filter repeatedly.
How: Create filtered view, save to My Layers.
Why: Reuse common filters without remembering syntax.
Export & Sharing Tips
Add Map Context
Tip: Include scale bar, north arrow, and legend in exports.
Why: Recipients need context to understand the map.
Export Data for Further Analysis
Tip: Export to CSV for spreadsheets, GeoJSON for code, Shapefile for GIS.
Choose based on:
- CSV: Simple attribute tables, Excel analysis
- GeoJSON: Web mapping, developers
- Shapefile: Desktop GIS, compatibility
Why: Right format for right audience.
Name Exports Clearly
Tip: Export filename should explain content.
Good:
Zoning_Analysis_MainSt_2026-02-09.pdfSelected_Parcels_Project5_2026-02-09.csv
Bad:
Map.pdfExport1.csv
Why: Your export folder will fill up fast.
Performance Tips
Close Layers You're Not Using
Tip: Toggle off layers not needed for current task.
Why: Fewer active layers = faster rendering.
Use Appropriate Zoom Levels
Tip: Don't zoom to full region when working on small area.
Why: Rendering millions of features is slow. Zoom to work area.
Team Collaboration Tips
Use Consistent Naming
Tip: Agree on naming convention as a team.
Example standard:
- Date format: YYYY-MM-DD
- Separator: Underscore
- Order: Purpose_Location_Date
Why: Consistency makes handoffs easier.
Share Bookmarks
Tip: Save common project areas as bookmarks, share with team.
Why: Everyone zooms to the same extent.
Document Workflows
Tip: Write down your common analysis steps.
Format:
- Step 1: Add X layers
- Step 2: Filter by Y
- Step 3: Run Z analysis
- Step 4: Export result
Why: Onboard new team members faster.
Security & Governance Tips
Limit Admin Access
Tip: Only give admin role to those who need it.
Why: Fewer admins = clearer responsibility.
Review Access Periodically
Tip: Quarterly audit of who has access to what.
Check:
- Former employees still have access?
- Roles still appropriate?
- Unused accounts to deactivate?
Why: Access creep is real. Clean it up.
Use Strong Passwords
Tip: Enable OAuth (Google, Microsoft) instead of password-only.
Why: Fewer passwords = more secure.
Troubleshooting Tips
Layer Won't Load?
Check:
- Is the service URL still active?
- Do you have permission?
- Is your internet connected?
- Try refreshing the page
Analysis Results Look Wrong?
Check:
- Correct layers selected?
- Right coordinate system?
- Null values in data?
- Try visual validation
Can't Find a Layer?
Check:
- Is it published?
- Do you have access?
- Is it in expected category?
- Try search function
More Help
Need more specific help?
Have a tip to share? Let us know and we'll add it here.