Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | index on osrm: 2a14782 Add basic implementation for selecting between route geometries |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk | refs/stash |
| Files: | files | file ages | folders |
| SHA3-256: |
8438b5c356a990de79d35ae59c9e311c |
| User & Date: | base@atomicules.co.uk 2014-12-26 12:40:53 |
| Original 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: trunk, refs/stash | |
| 12:40 | index on osrm: 2a14782 Add basic implementation for selecting between route geometries check-in: 8438b5c356 user: base@atomicules.co.uk tags: trunk, refs/stash | |
|
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 | |
Changes