BK01 comments

Results 9 comments of


                                            BK01

In partitioning of best route, compute and return lengths (distances) of sub-partitions

Distance by partition is included in BC Route Planner 2.2.1. Inland vs. coastal ferry distinctions will be covered in another issue.

In route planner/directions, add support for a briefDirections parameter

This issue is addressed in BC Route Planner 2.2.1 with the use of the simplifyDirections and simplifyThreshold parameters.

Directions return bogus heading, text and name components for responses to routes that don't have a valid path.

The update appears to have been merged into the dev branch but not yet into the main branch.

Enable Transport Line ID’s in response

Validated in BC Route Planner 2.2 (router-dev.api.gov.bc.ca) on Dec 19, 2023.

Add reference data dates to response

Validated in BC Route Planner 2.2 (router-dev.api.gov.bc.ca) on Dec 19, 2023.

Add reference data dates to response

Confirmed after the latest data refresh that the dataProcessingTimestamp value was updated.

Snap tolerance parameter

Validated in BC Route Planner 2.2 (router-dev.api.gov.bc.ca) on Dec 19, 2023. Test case above used with a distance of 1000m (no route found) and 1200m (route found)

Geomark API Console update

On hold until new API console viewer is available.

Geomark JS API getGeomarkFeature(url) won't return multi polygons

Thank you for connecting with us. Would it be possible for you to submit this issue through the following form ([Get Help with the Geomark Web Service](https://dpdd.atlassian.net/servicedesk/customer/portal/1/group/7/create/6))?