Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Remove some redundant comments |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk | origin/master |
| Files: | files | file ages | folders |
| SHA3-256: |
0c4224822a68b30e869102d739708794 |
| User & Date: | base@atomicules.co.uk 2014-12-14 21:54:02 |
Context
|
2014-12-26
| ||
| 22:15 | Add basic implementation for selecting between route geometries Not a great implementation, but it works. If no route geometry choice is made it defaults to the default "route_geometry". If "alternative_geometries" is specified it uses the first one of the alternatives (because as far as I can tell there is only ever one alternative? I supposed at some point I could extend if needed, perhaps use a tuple argument: {"alternative_geomtries", 1}). Leaf check-in: 9c81571ac3 user: base@atomicules.co.uk tags: trunk, origin/master | |
|
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 made it defaults to the default "route_geometry". If "alternative_geometries" is specified it uses the first one of the alternatives (because as far as I can tell there is only ever one alternative? I supposed at some point I could extend if needed, perhaps use a tuple argument: {"alternative_geomtries", 1}). check-in: 6807958aad user: base@atomicules.co.uk tags: trunk, refs/stash | |
|
2014-12-14
| ||
| 21:54 | Remove some redundant comments check-in: 0c4224822a user: base@atomicules.co.uk tags: trunk, origin/master | |
| 21:53 | Update README to suit osrm branch check-in: ee1cd9e7e0 user: base@atomicules.co.uk tags: trunk, origin/master | |
Changes
Changes to osrm.erl.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
-module(osrm). -export([get_route/1, get_route/2, read_route/0]). -import(polyline, [decode/1]). %https://github.com/Project-OSRM/osrm-backend/wiki/Server-api %Idea: Given a lat and long, get the route %Then use that to build up list of compass directions and distances %And, for now, get weather for one location (probably good enough as relatively short distances weather wise; ultimately consider time as well?) %Then do distance and wind direction as percentage of overall distance to work out what wins, headwind, sidewind, etc. %To get lats and longs could also do a query for here: http://www.uk-postcodes.com/ (json again) -define(BASE_URL, "http://router.project-osrm.org/"). -define(VIAROUTE, "viaroute"). |
< < < | < |
1 2 3 4 5 6 7 8 9 10 11 12 13 |
-module(osrm).
-export([get_route/1, get_route/2, read_route/0]).
-import(polyline, [decode/1]).
%https://github.com/Project-OSRM/osrm-backend/wiki/Server-api
%For now, get weather for one location (probably good enough as relatively short distances weather wise; ultimately consider time as well?)
%To get lats and longs could also do a query for here: http://www.uk-postcodes.com/ (json again)
-define(BASE_URL,
"http://router.project-osrm.org/").
-define(VIAROUTE,
"viaroute").
|