Missing access point at road / stream crossings

[WilBublitz]

Issue Description:

Bridge crossing at road + stream intersection 47.063570, -115.218954 does not appear as an access point.

Expected Results:

road + stream crossing appears as clickable access point

Steps to Reproduce:

Navigate to Troutspotr.
Locate http://localhost:3000/id/north/heller-creek on map
Find road at intersection with http://localhost:3000/id/north/sherlock-creek
Confirm that access point appears and is clickable.

[andest01]

Both road and creek do appear to be present in raw data.

On closer inspection, we appear to have duplicate roads present.

This may be cause for concern.

[andest01]

The access point is indeed in our data set.

Investigating why it's not present.

[andest01]

Data is present in client TopoJSON. This is good.

However, due to a bug much deeper in the back-end TopoJSON generator, the distance_to_previous_neighbor property is 0.

Adding a new issue to fix the deeper backend bug. For now, a potential hack would be to say we only filter out "duplicate" roads if they are "extremely close" AND their distance to their neighbors is more than literally zero.

In Northern Idaho alone, this fix opens up 236 new access points.

@WilBublitz what do you think? Go forward with the hacky fix to get more access points?