Transport / Mobility / Micro-Logistics — Resource Library Atlas

Global baseline for streets as public space and mobility networks. Useful across jurisdictions because it emphasizes design patterns (not legal doctrine).

• Street typology library (widths, modal allocation, context fit).
• Intersection and crossing transformations (conflict reduction).
• Curb management and public-space integration patterns.

• Retrofit corridors without “reinventing” geometry.
• Anchor a shared street language across multiple teams.
• Set “minimum viable safety” as non-negotiable baseline.

• Copy/paste without matching local vehicle mix + enforcement reality.
• Ignoring freight/servicing needs at the curb.

A practical design guide for contexts where walking and cycling are already dominant, with attention to retrofit feasibility and safety under mixed traffic.

• Low-cost walking/cycling retrofit treatments.
• Safety-first intersection/crossing patterns suitable for high pedestrian volumes.
• Implementation logic for resource-constrained street upgrades.

• Fuel/vehicle access is inconsistent and human-scale mobility must remain functional.
• Street use is mixed (vendors, informal stops, pedestrians everywhere).

• Extract design patterns; treat donor-style framing as optional.

Strong template set for streets as public space under extreme mixed use: high pedestrian volumes, informal modes, and constant curbside friction.

• Street function framework (movement + access + social economy).
• Cross-section templates that tolerate real-world disorder.
• Design process logic for quickly improving safety and walkability.

• Urban streets are simultaneously market, corridor, and shelter.
• Formal enforcement is inconsistent; geometry must carry safety.

• Over-cleaning streets (removing informal function) and triggering backlash.

A measurement system that prevents “design theater.” Walkability becomes legible through repeatable indicators.

• Indicator hierarchy (infrastructure, activity, priority).
• Assessment workflow that scales from neighborhood to city.
• Before/after evaluation scaffolding for retrofit programs.

• Baseline needs to be proven before investment.
• Competing priorities require a neutral diagnostic language.

• Indicators are not truth; they are instrumentation. Pair with field observation.

A measurable definition of transit-oriented urban form. Useful because it forces land use and transport to cohere (walk + cycle + transit + mix + density).

• Metrics for walk/cycle connectivity, mix, density, and parking suppression.
• Scoring logic for station areas (design-as-evaluation).

• Station areas are being designed or audited.
• Transit investment needs defensible urban form targets.

• Use metrics; do not import the implied governance model unless desired.

The most complete pattern book for bus rapid transit: political setup, operations, stations, lanes, fleet, fares, and implementation sequencing.

• Station and corridor design requirements that produce real BRT performance.
• Operations and business model templates (service planning, fleet, fare collection).
• Implementation phases (what must exist before launch vs after).

• High-capacity corridors are required without rail costs.
• Transit must remain operational under fuel volatility (buses are flexible).

• “BRT in name only” (painted lanes, weak stations, slow boarding).

A guardrail against dilution. Defines which elements reliably create high-performance bus corridors.

• Point/criteria list to audit corridor design.
• Minimum feature set (alignment, stations, boarding, intersections).

• Evaluating a proposed “BRT” corridor for real performance.
• Converting political promises into checkable specs.

• Score is not reality; field ops and enforcement still matter.

• Lane allocation logic and dimensional conventions.
• Traffic calming toolkit usable in most cities.
• Curbside elements that directly affect deliveries and loading.

• Assumes certain enforcement and liability cultures; port patterns to local reality.

• Stop placement patterns and platform/station logic.
• Intersection priority treatments for buses.
• Street-level integration between transit + walking + cycling.

• Building BRT-lite or bus priority without full BRT rebuilds.

• Protected lane typologies and intersection conflict management.
• Design patterns that also support cargo bikes (width, turns, loading).

• Adapt dimensions for cargo bike fleets and local vehicle behavior.

• Hub typologies (pop-up, shared, dedicated).
• Siting criteria (density, access, conflicts, curb rules).
• Layout + operations patterns (handoff, storage, security, staffing).

• Replacing vans in constrained districts.
• Converting parking/curb space into logistics capacity.

• Regulatory changes that unlock cargo bike adoption.
• Parking/loading and network requirements.
• Implementation checklist for cities and operators.

• Promoting cargo bikes without safe network continuity and loading space.

• Dimensional standards for cargo bike movement and storage.
• How to allocate space in streets and developments.

• Designing inner-city logistics that remains functional under fuel constraints.

• Assessment checklist: regulations, curb environment, network gaps.
• Growth strategies: incentives, pilot programs, curb changes, procurement.
• Design notes for longer/wider bikes (cargo geometry).

• City staff and operators need a shared, practical blueprint.

Station siting logic transfers directly to micro-depots, locker placement, and neighborhood logistics nodes.

• Siting principles and typologies.
• Trade-off logic for visibility, access, and conflict points.

• Designing node placement for distributed mobility and delivery networks.

• Urban Consolidation Centre (UCC) trade-offs and failure modes.
• Access regulation patterns, dynamic routing concepts, ITS levers.
• Case logic: “cityporto” model and similar schemes.

• Many strategies assume enforcement capacity and data infrastructure.
• Micro-hub + cargo-bike patterns often survive scarcity better than large UCCs.

• Stepwise planning structure for city logistics (stakeholders → measures → monitoring).
• Measure catalogues that can be remapped into low-energy equivalents.

• Framework is governance-heavy; extract method and measurement loops.

• Methodologies for low-cost crossing upgrades and staged construction.
• Cost evaluation of spot improvements rather than mega-project bias.
• Organizational frameworks for decentralized road maintenance.

• Rural access must be improved with minimal capital and long timelines.

• How informal transport services actually function (pricing, routes, associations).
• Regulatory failure patterns and practical options (not fantasies).
• Vehicle ecology: motorcycles, 3-wheelers, minibuses, pickups.

• Planning is required without destroying existing adaptive services.

• Requirements from actual rural users: affordability, predictability, safety, freight carriage.
• Why passenger trucks can be more realistic than buses in many settings.
• Motorcycles as “default infrastructure” on poor roads.

• Policy talk must be anchored in operational truth.

• Indicator set for service quality (cost, frequency, acceptability, safety).
• Field methodology that works where data is sparse.

• Baseline measurement is needed for rural mobility interventions.

• Policy and regulatory constraints that suppress private service quality.
• Options for improving services without assuming universal subsidies.

• Designing interventions that must survive weak institutions.

• End-to-end logistics workflow, roles, and common templates.
• Customs and documentation patterns under emergency timelines.
• Operational service concepts (common storage, transport requests, coordination).

• Cluster governance assumptions are optional; SOP patterns are portable.

• IM roles, minimum products, and reporting cadence.
• How to make logistics legible to multiple actors without drowning in data.

• Multi-actor logistics needs shared situational awareness.

• Competency map: warehousing, transport, coordination, IM, assessments.
• Training modules as “operator bootstraps.”

• Building a logistics cell that needs repeatable skill transfer.

• Quantification methods and reorder logic.
• Inventory control procedures and LMIS design patterns.
• Warehouse and transport basics for health commodities.

• Medicine, consumables, and regulated goods are in the flow.

• Field-ready SOP style: receiving, storage, dispatch, tracking.
• Practical logistics planning and roles under disaster response.

• Small-to-medium ops need concrete procedures immediately.

• Health supply chain management under emergency constraints.
• Quality control and handling logic for pharmaceuticals/medical goods.

• Cold chain, regulated items, and medical distribution must not fail.

• Fleet management system structure (roles, logs, maintenance schedules).
• Standard contract templates (rental, fuel purchase, maintenance, sale).
• Logbook forms usable even in paper-first operations.

• Vehicles are mission-critical and must be managed as an asset system.

• Priority codes and screening logic for scarce transport capacity.
• Cargo Movement Request structure (fields and validation requirements).

• Any scarce-capacity transport asset exists (air, boat, guarded convoy).

• How a warehouse system was actually implemented (clean-up, stock inventory, records).
• Training structure usable as a local warehouse bootcamp template.

• Warehouse exists but inventory reality is unknown or unreliable.

• Preparedness workshop structure across government/UN/NGO/private partners.
• Practical improvements: layout, processes, safety, and documentation.

• Multi-stakeholder warehousing needs a single operational language.

• Assessment timing logic across response phases.
• How to avoid assessment noise and produce usable logistics intelligence.

• Infrastructure status and constraints must be mapped quickly and credibly.

• Distributed mapping workflow (divide, map, validate, merge).
• Operational pattern: volunteers produce a usable map quickly under crisis time.

• Roads/buildings/POIs must be mapped or updated fast.

• Onboarding pathway for new mappers.
• Tasking Manager mapper guide and validation concepts.

• Local capacity is needed to keep maps alive after volunteers leave.

• Minimal toolkit for field mapping (free/low-cost).
• Operational map products and production cadence.
• Data collection + cleaning workflows that survive bad connectivity.

• Maps must support logistics decisions (routes, hubs, population movement).

• Workflow patterns: requests, resources, facilities, roles, reporting.
• Self-hostable coordination layer (reduces dependency on proprietary platforms).

• Requires configuration and operational discipline; not “magic software.”

• Offline forms for needs assessment, inventory checks, route status, and distribution logs.
• Data pipeline usable as “truth ingest” for logistics dashboards.

• Pair with data responsibility guidance (see constraints layer).

• KPI framework that fits humanitarian operations (not retail warehouses).
• Indicator selection logic tied to visibility and accountability.

• Deciding what to measure before building dashboards and incentives.

• Taxonomy of emergency logistics problem classes.
• Known weaknesses: damaged infrastructure, uncertain demand, multi-actor coordination.

• Evaluating optimization claims and deciding where modeling is worth it.

• Practitioner-grounded KPI prioritization (responsiveness, agility, reliability, cost).
• Indicator weighting method usable for local KPI selection.

• Local KPI sets must be chosen under conflicting priorities.

• Five-phase cycle for mapping local supply chains and failure points.
• Private-sector engagement logic for restoring critical goods flows.

• Local continuity planning needs explicit mapping of supply dependencies.

• Green specs and decision points across supply planning, fleet, travel, and waste.
• Practical checklists usable in procurement and warehouse ops.

• Logistics decisions must incorporate environmental cost as a real constraint.

• Concrete field actions (not just policy) across logistics domains.
• Operational trade-offs explained in field language.

• Reducing footprint without collapsing field effectiveness.

• Governance mechanisms for environmental responsibility.
• Integration pathways into logistics planning and procurement.

• Environmental constraints must be embedded across organizations.

• Risk controls for collecting/storing personal and operational data.
• Principles to prevent harm via exposure, profiling, or misuse.

• Using tools like KoboToolbox, Sahana, mapping, or beneficiary registries.

• Distribution hub patterns and rapid volunteer mobilization.
• Friction points: vehicles, warehousing, and coordination at scale.

• Designing community-first logistics cells that can activate fast.

• How movement + emplacement form an “insurgent infrastructure.”
• Why mutual aid logistics is also a governance layer.

• Operating outside or parallel to institutional relief channels.

• How official actors evaluate and respond to volunteer/mutual-aid signal flows.
• Operational lessons on communication, situational awareness, and rumor control.

• Building resilient comms and ops against narrative capture and noise.

• Strength/weakness comparison of open platforms under real disaster data.
• Where geospatial analysis and data management break under stress.

• Choosing tools for community-led or hybrid (community + institutional) response.

• Formal vocabulary for supply chain design in disaster conditions.
• Case-based reasoning on trade-offs and constraints.

• Training analysts/lead logisticians to model and redesign systems.

• Structured skills ladder for logistics roles (field → coordination → IM).

• Building rapid training for multi-organization operations.

• Training + tooling that produces a living, local map base.

• Maps must remain accurate after the initial crisis window.