280 likes | 410 Views
LBS that work. Jonathan Raper gicentre.net. Where are the LBS that work?. That depends on: How you define LBS… Who produces the LBS… What constitutes success…. How you define LBS. Platform: generic or custom device Position: GPS or cell ID Package: client-server or standalone
E N D
LBS that work Jonathan Raper gicentre.net
Where are the LBS that work? That depends on: • How you define LBS… • Who produces the LBS… • What constitutes success…
How you define LBS • Platform: generic or custom device • Position: GPS or cell ID • Package: client-server or standalone e.g. Wherifone = custom/ GPS/ client-server e.g. AA Roadwatch= generic/ cell ID/ client-server e.g. TomTom= custom/ GPS/ standalone
Who produces the LBS • Operators who have invested in location platforms • KDDI Japan (EZ Naviwalk) • 3 UK (Locate) • Nextel (TeleNav) • 3rd party developers with access to innovative devices • Camineo (HP iPAQ 6515 with SIM free A-GPS) • AllSportGPS (Nextel i series with A-GPS)
What constitutes success? • No early killer app • But see http://flickr.com/groups/mappingflickr/ • LBS like the Internet Long Tail? • thousands of niche apps with common properties
Some of the LBS that work… • EZ Naviwalk (http://www.kddi.com/english/corporate/news_release/2003/1006/attachment.html) • Camineo (http://www.camineo.com) • BlisInfo (http://www.blisinfo.de/) • AllsportGPS (http://www.allsportgps.com) • Wherifone (http://www.wherifywireless.com/) • Clearly there is scope for much more…
Why are LBS so challenging? • Place and position • Context and geo-information • Development and deployment • Interfaces and interaction • Cost and acceptability • These headings define our research
1 Place and position • LBS need to deal with place • Points/ lines/ areas of interest need to be real • Query responses need to be geographically relevant • “bring the information to where the questions are” • Positioning needs error assessment • Honesty in positioning prized above precision
By following n space-time paths, emanating from a point location, for a given time budget, can define the region of space accessibly from that location, based upon previous spatial behaviour e.g. 5 minutes from London Bridge Mobile trajectory analyses Bounded by convex hull Bounded by buffer
GPS experiences in the street • Positioning in the worst case scenarios: the street and indoors • Need to know typical quality of fixes under a range of circumstances • Long term personal tracking experiments to collect mobile trajectories by GPS • Can predict GPS availability- constellation repeats each day
2 Context and geo-information • Context matters • All usage is defined by personal situation • Geo-information is crucial • Locations/ footprints must be accurate • Users expect information ranking like Google • Routes must be personal • Need detailed models of urban environments with semantic model
Context • Who? • Who with? • Doing what?
Spatial and temporal footprints • LBS have greater potential with • Things that change rapidly (not in guides) • Things that are easier to find with positioning
Information ranking • Information needs ranking for users • Use movement to model likely span • of attention for information need
3 Development and deployment • Architectures • Open web approach • Proprietary e.g. Telcontar • Development approaches • Waterfall model- no • Rapid prototyping- yes
Prototype Prototype Test (Re)design Test (Re)design Evaluate Evaluate Development strategy • Rapid prototyping • Evolving what we can offer • ‘Focus group’ feedback • Evaluation-led development
Webpark architecture GML SVG Interfaces, standards Client/server architecture with standardized interfaces GPS Portal IFOI2Headers Transformation Animal and Vegetation data User Locator component Internet WFS OGC requests POIs IFOI Broker GML cache Local HTTP Server Map Broker SVG cache Display Data, Maps and Location in HTML Pocket IE Topographic maps - Background WMS OGC requests Client (PDA) Server Bluetoothconnection
4 Interface/interaction • Need innovative ways to present place and progress • Web browser the universal interface • Though NOT for older people • Ways to solve the self-localisation problem?
Usability feedback from old • Device weight OK • Screen size about right • Screen visibility so-so • Too much screen clutter • Scale indicator obscure • Autoscroll unreliable • Click affordances poor • Writing size about right • Need a strap • Need instructions
Innovative interfaces • The ‘GPS button’? • Cross-media linkage • QR codes
VR/ MR/ AR experiments • Value is in cognitive richness of AR/MR/VR cf map • Spectrum of representations/ interactions • VR (scene graph)-> MR-> AR (PVT overlaid video) • Tangible user interfaces • How to display/ manipulate on small 2D screen • Use device camera and registered target card
Cost and acceptability • Experience of many user tests shows us the importance of acceptability • Users won’t take on technology that they don’t understand, that they fear or that they don’t trust • That’s before they evaluate cost! • Egocentric applications need engagement from the service provider
Thanks… any questions? • http://www.gicentre.net