Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | WIP on osrm: 2a14782 Add basic implementation for selecting between route geometries |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | trunk | refs/stash |
| Files: | files | file ages | folders |
| SHA3-256: |
6463b2f68fdff436968e310359b6f39a |
| User & Date: | base@atomicules.co.uk 2014-12-26 12:40:54 |
Context
|
2014-12-26
| ||
| 12:40 | WIP on osrm: 2a14782 Add basic implementation for selecting between route geometries Leaf check-in: 6463b2f68f user: base@atomicules.co.uk tags: refs/stash, trunk | |
| 12:40 | index on osrm: 2a14782 Add basic implementation for selecting between route geometries check-in: 8438b5c356 user: base@atomicules.co.uk tags: refs/stash, trunk | |
|
2014-12-17
| ||
| 22:46 |
Add basic implementation for selecting between route geometries
Not a great implementation, but it works. If no route geometry choice is | |
Changes
Changes to README.md.
| ︙ | ︙ | |||
14 15 16 17 18 19 20 |
6. Run `erl -run headsilose headsilose <location id> -noshell` to get the result.
Since I wrote this to be semi-useful for me, the result returned depends on the time of the day. If it's run before 8am it looks for the 6am weather data (since data is in 3 hour periods) and assumes the route is being traversed normally, run between 8am and 7pm it looks for the 6pm data for going home and therefore also traverses the saved route in reverse, and run after that time it looks again for the 6am data, but for the next day, and thus the route is back to being traversed in the normal direction.
_Hint:_ I have a shell function defined as follows:
function headsilose {
| | | 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
6. Run `erl -run headsilose headsilose <location id> -noshell` to get the result.
Since I wrote this to be semi-useful for me, the result returned depends on the time of the day. If it's run before 8am it looks for the 6am weather data (since data is in 3 hour periods) and assumes the route is being traversed normally, run between 8am and 7pm it looks for the 6pm data for going home and therefore also traverses the saved route in reverse, and run after that time it looks again for the 6am data, but for the next day, and thus the route is back to being traversed in the normal direction.
_Hint:_ I have a shell function defined as follows:
function headsilose {
erl -pa /home/simon/Code/github/atomicules/heads-I-lose /home/simon/Code/github/atomicules/heads-I-lose/ebin -run headsilose headsilose XXXXXX alternative_geometries -noshell;
}
So I can just call
headsilose
Which will result in something like the following being printed out:
|
| ︙ | ︙ |