Satisfying Navigation-To-Thing and Context-Focused “ Around Me ” Use Cases

1. Satisfying Navigation-To-Thing and Context-Focused “Around Me” Use Cases Paul Bouzide

2. Context and detail precedent: vehicle navigation use case What should be suppressed? What should be emphasized? A familiar problem of appropriate context in vehicle navigation

3. Some 3D solutions for vehicle navigation • Note inclusion of non-motorway and non-ramp road elements in scene. • Note inclusion of terrain, bridge guards and support columns in scene. • Note removal of irrelevant signage from scene.

4. Context driven detail: pedestrian-indoor-transit navigation What should be enhanced? What should be suppressed? Where in the service chain? • In what situations? • For which kinds of users? • Key context information: • Location/heading • Navigation Intent • Ever more critical for these higher feature and geometry volumes • Even at pedestrian velocities and cognitive attention profiles • “Byte sized content right sized for each user’s individual context”

5. But maximum LOD depends on the device and the network Fully apart from the question of detail enhancement or suppression… • “Byte sized content”… • End user context also includes • Device capabilities • Network performance and cost

6. Geospatial features and properties aren’t static • Approaches: • Partition replacement • Feature property updates • Geo/topo update transactions • Everything changes… • Walls and fixtures • Color schemes/decor • Local addressing schemes • Signage • Space occupancy • … • Any change can matter crucially • to the contextual behavior of the app • to maintaining believability, realism • Most changed features or properties • exist in relation to others • can depend on prior changes for consistency

7. Low change latency & contextual detail app service chain Vector feature model creation from observations Model transformation for contextual assembly, styling, rendering Context-aware customization, filtering, styling and rendering Context-aware service integration, interactive visualization, selection GeospatialContent Creator Content Delivery Network Mobile Device Application (Client) Geospatial Content Transformation/ Aggregation Mobile Device Application (Server) Mobile Network Mobile Device Application (Client) Mobile Device Application (Client) Mobile Device Application (Client) Mobile Device Application (Client) AppAPIs Streaming Data APIs Pub/Sub GeospatialContent Creator Sensor Observations Usage analytics, user observations, <product requests> Processed context, feature & scene requests/subscriptions Location, camera other user & device context GeospatialContent Creator Context categorized located scenes & features Differentiated & componentized new/updated vector feature sets …“Right sized” contextualized scenes, styled vector features … GeospatialContent Creator

8. What locations have a content creation business case? • Varying LODs across geographies: • How does this affect navigability? • What are the key differences between these location types • Build out locations that have • High foot traffic density • Time-criticality of an effective navigation Ux • Generators of economic activity • Some good candidates • Multimodal transit hubs • Airports, rail/transit stations, … • Retail clusters • “Big box” + satellites, malls, urban retail zones • Tourism, mass entertainment, mass business • Museums, stadiums, theaters • Businesses and Academia • Convention centers, office complexes, university campuses, … • Emergency related • Hospitals, Zones of security monitoring/enforcement

9. What contributes to this content creation business case? • Partnering with existing mobile device/application ecosystems • Application geospatial “fuel” • Federate collection and maintenance with pluggable aggregation • Building complex developers/management • Governments, transit authorities • Building architects/contractors • Adjuncts to road vehicle navigation (“integrated walk, ride, drive”) • Leverage and integrate with vehicle-bound applications and content • Also taxi, bus, logistics fleets • Integrate usage analytics for lower content maintenance cost • Alternatives to supply-based advertising for end user “desire fulfillment” • And of course location+context based advertising doesn’t go away…

10. Technology Enablers: APIs and interoperable standards • Relevant standards: • WMS, WFS, GML, KML • Eventing • WPS • W3DS, WVS, X3D • SVG, PNG, JPG, JPG2K

11. Other key technology enablers • Pluggable Spaces • Recursively subdivided spaces • Homogeneity of LOD within a spaces • Stable location identity at integration points • Change-based feature publication • Low latency observation to end user • Pub/sub SDI eventing • Critical needs: • Effective indoor positioning • Interoperable micro location referencing • Interoperable pluggable space topologies • Parallel processing architectures • Observation processing, data transformation, styling/rendering • Indoor micro-positioning • Low tens of cm • Radio (WiFi, Bluetooth, RFID, NFC) • Image recognition • IoT “massive triangulation”