If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor
Road Navigation: Difference between revisions
Rui.Pereira (talk | contribs) No edit summary |
Rui.Pereira (talk | contribs) No edit summary |
||
| Line 14: | Line 14: | ||
== Application Architecture == | == Application Architecture == | ||
Road Navigation applications are implemented using a | Road Navigation applications are implemented using a in-vehicle navigation device, a standalone [[Personal Navigation Device]] or a standalone application running on a GNSS-enabled [[Wikipedia:Mobile device|mobile device]]. | ||
Normally the map and database of these applications are local although in some case the local application is supported by online services that provide database updates, additional dynamic data (such as | Normally the map and database of these applications are local although in some case the local application is supported by online services that provide database updates, additional dynamic data (such as traffic information) or even parts of the navigation functionality. | ||
The process normally followed by these applications is: | The process normally followed by these applications is: | ||
* The user configures the application by defining a destination. Restrictions may be applied on how to get to the destination (e.g. use of | * The user configures the application by defining a destination. Restrictions may be applied on how to get to the destination (e.g. use of tolled road). | ||
* The application will guide the | * The application will guide the driver turn by turn using visual and audio information. | ||
* If the user diverts from the suggested route the application will recalculate the route. | * If the user diverts from the suggested route the application will recalculate the route. | ||
Variants to this architecture are: | Variants to this architecture are: | ||
* These applications normally include a point-of-interest (POI) database including hotel, restaurant, gas station and other landmark information. | |||
* These applications | |||
These applications are considered non-critical applications. | These applications are considered non-critical applications. | ||
| Line 34: | Line 33: | ||
== Application Characterization == | == Application Characterization == | ||
These applications can work typically offer 2 routing algorithms: | |||
* Fastest Route: Calculates the fastest route based on a the speed classification of the streets and roads. | |||
* Shortest Route: Calculates the shortest route | |||
Some manufacturers offer additional routing modes that take into consideration traffic conditions to choose the fastest route. These routing modes either use online servers that provide the current road conditions and incorporate this information in the routing algorithm or can use a | |||
Revision as of 16:10, 14 April 2011
| Applications | |
|---|---|
| Title | Road Navigation |
| Author(s) | Rui Barradas Pereira. |
| Level | Basic |
| Year of Publication | 2011 |
Car navigation is currently the main application of GNSS. GNSS data combined with electronic maps allow positioning and guidance of the road user.
Route guidance using satellite navigation is already a well-established product offered by both by car manufacturers and standalone navigation devices. The majority of these systems are based on satellite navigation systems that can be integrated with onboard sensors (odometer and gyros) to compute optimal routes in real-time[1].
Application Architecture
Road Navigation applications are implemented using a in-vehicle navigation device, a standalone Personal Navigation Device or a standalone application running on a GNSS-enabled mobile device.
Normally the map and database of these applications are local although in some case the local application is supported by online services that provide database updates, additional dynamic data (such as traffic information) or even parts of the navigation functionality.
The process normally followed by these applications is:
- The user configures the application by defining a destination. Restrictions may be applied on how to get to the destination (e.g. use of tolled road).
- The application will guide the driver turn by turn using visual and audio information.
- If the user diverts from the suggested route the application will recalculate the route.
Variants to this architecture are:
- These applications normally include a point-of-interest (POI) database including hotel, restaurant, gas station and other landmark information.
These applications are considered non-critical applications.
The precision required by these applications is low. The current accuracy provided by civilian GPS is enough in most situations.
Application Characterization
These applications can work typically offer 2 routing algorithms:
- Fastest Route: Calculates the fastest route based on a the speed classification of the streets and roads.
- Shortest Route: Calculates the shortest route
Some manufacturers offer additional routing modes that take into consideration traffic conditions to choose the fastest route. These routing modes either use online servers that provide the current road conditions and incorporate this information in the routing algorithm or can use a
Application Examples
Notes
References
- ^ Galileo Application Sheet - Road Applications, ESA and European Commission, October 2002