If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor

Pedestrian Navigation

From Navipedia
Revision as of 23:29, 6 April 2011 by Rui.Pereira (talk | contribs) (Created page with "{{Article Infobox2 |Category=Applications |Title={{PAGENAME}} |Authors=Rui Barradas Pereira. |Level=Basic |YearOfPublication=2011 |Logo=GMV }} Pedestrian Navigation consists i...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


ApplicationsApplications
Title Pedestrian Navigation
Author(s) Rui Barradas Pereira.
Level Basic
Year of Publication 2011
Logo GMV.png


Pedestrian Navigation consists in the navigation of pedestrians in urban environments.


Application Architecture

Pedestrian Navigation applications are normally implemented using a standalone application running on a mobile device. This mobile device can be GNSS-enable phone with multimedia capabilities or a custom Personal Navigation Device.

Normally the map and database of these applications are local although in some case the local application is supported by an online services that provide database updates, additional ephemerous data (such as wheather) or even parts of the navigation fuctionality.

The process normally followed by these applications is:

  • The user uses the application to define a destination. Restrictions may be applied on how to get to the destination (e.g. use of public transport).
  • The application will guide the user using visual and audio information to its destination.
  • If the user diverts from the suggested route the application will recalculate the route.


Variants to this architecture are:

  • The more basic pedestrian navigation applications support only outdoor pedonal movements not supporting public transportation.
  • These applications can be combined with Location based Information Streams to provide additional information to the user.


These applications are considered non-critical applications.

The precision required by these applications is medium, being the current accuracy provided by civilian GPS enough in most situations but not in all. To support indoor navigation these applications would need addtional availability that might require the use of inertial sensor or other indoor localization technique.


Application Characterisation

Pedestrian Navigation as been seen wrongly as merely an extention of Road Navigation. But the fact is is that the environments where pedestrians move around are generally more difficult than the road environment. Pedestrians normally move in sidewalks where the buildings shadow the GNSS signals, in tree shadowed environments and in indoor tridimensional environments.

These environments are much more difficult than Road Navigation that even in urban environments will have better satellite visibility. Support indoor navigation these application would have to support inertial sensors integration or other indoor navigation technique.

In simplyfied models for these applications the maps used for road navigation can be reused but this limits the degree of functionality that the application can provide. Pedestrians move in the sidewalks, not in the roads and can move more freelly in the environment since they can use more narrow streats and to go accross open areas.

Also to support public transportation, the routes and the frequency or the timetable of the public transports must be supported making the database and the routing more complex.

Currently the interface for these applications is supported b


Application Examples

Application types that fit in this category are[1]:

  • Requesting the nearest business or service, such as an ATM or restaurant.
  • Receiving alerts, such as notification of a sale on gas or warning of a traffic jam.
  • Location-based mobile advertising.
  • Augmented reality.


Notes


References

  1. ^ Cite error: Invalid <ref> tag; no text was provided for refs named lbs