mark padgham

It's in the check results. Under "*4. Other Checks*", you'll see a "Details of other checks (click to open)". You can also generate those yourself by running: ``` r library(pkgcheck)...

Cross ref [this additional `stplanr` issue](https://github.com/ropensci/stplanr/issues/237#issuecomment-534213116)

Relevant [Stack Overflow discussion here](https://stackoverflow.com/questions/849211/shortest-distance-between-a-point-and-a-line-segment).

Those commits add the required functionality, and introduce a breaking change: https://github.com/ATFutures/dodgr/blob/5fd8b4f458c84c8e72ce4c5cd7c1941a80b6975c/NEWS.md?plain=1#L3-L6 Only remaining task is to add another function to insert new points/vertices in the network, as with ropensci/stplanr/issues/237

``` r library (dodgr) packageVersion ("dodgr") #> [1] '0.2.14.90' graph [1] 6813 15 verts

Re-opening to add ability to return actual distances to nearest edge. These distances can be very useful for routing tasks, to construct some measure of weighted distance to some kinds...

Those commits add the distance to the output of the C++function. It's not yet used, but can be added directly to the R output from there. ###TODO - [ ]...

That commit adds the geometric distances. Just need to run a few test cases to make sure everything is okay, and then modify the return value to include those distances.

If it's only used as an entry point into C++ functions, then you could just pass `paste0(x)` through to C++?

It shouldn't matter on such a large feed, because most of the time is the main scanning of each row of transfers anyway, and the re-indexing back out to all...