Deprecated: Since 5.0.0: Calling Table::get() with options array is deprecated. Use named arguments instead. /application/src/Controller/ParagraphsController.php, line: 67 You can disable all deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED`. Adding `src/Controller/ParagraphsController.php` to `Error.ignoredDeprecationPaths` in your `config/app.php` config will mute deprecations from that file only. in /application/vendor/cakephp/cakephp/src/Core/functions.php on line 377

Warning: Unable to emit headers. Headers sent in file=/application/vendor/cakephp/cakephp/src/Core/functions.php line=377 in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 65

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 158

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 191

Warning: Cannot modify header information - headers already sent by (output started at /application/vendor/cakephp/cakephp/src/Core/functions.php:377) in /application/vendor/cakephp/cakephp/src/Http/ResponseEmitter.php on line 228
Dave's PCF WIP: Paragraphs

7627

Application North UP Head UP Orientations
Matter Number KBR-1 1400.2.623 Reference Case 1 KBR-1 1400.2.623
Created 2/25/22, 12:00 AM Modified 2/25/22, 12:00 AM
Application Number
Paragraph Number

105

Content

In one example, the context 400 may be influenced by a history factor 424. The history factor 424 is a factor that is based on how often a user has taken a particular route, included a particular waypoint along the route, visited a particular destination, and/or been to a locale that includes the route. The history factor 424 may be referred to as a navigation history or visit history. "Navigation history" or “visit history” refers to a set of data that identifies one or more places, waypoints, or locations, a person or user has visited and/or navigated through or to, in the past. "Locale" refers to a specific location and the areas immediately surrounding the specific location. Often a locale has a particular set of attributes that may relate to its geography, scenery, climate, or the like. Data for the history factor 424 may be stored by a navigation apparatus 220 in storage 214. The history factor 424 can include whether or not a user has visited a locale and/or how often a user has visited a locale, waypoint, or taken a particular route.

Notes

Added by DJM 2 2022