Given an hygeo waterbody network and a set of related hydrologic locations, we need to be able to generate a cross walk.
The use cases here is where we have a set of hydrologic locations that are at the outlet of each NHDPlusHR flowline. We need to know where they land along the waterbody network of an hygeo object.
This should be implemented as a function that takes the waterbody data of an hygeo object and a set of locations. The locations should have a known main-id that is the same identifier space as the main-id of the hygeo waterbodies.
The response should include the hygeo waterbody id that each input node should be associated to.
This function may also include NHDPlus data attributes to allow a tie back to reachcode/measure linear referencing. Potential to mock reachcode/measure attributes such that the nhdplusTools get_flowline_index() function can be used.
Given an hygeo waterbody network and a set of related hydrologic locations, we need to be able to generate a cross walk.
The use cases here is where we have a set of hydrologic locations that are at the outlet of each NHDPlusHR flowline. We need to know where they land along the waterbody network of an hygeo object.
This should be implemented as a function that takes the waterbody data of an hygeo object and a set of locations. The locations should have a known main-id that is the same identifier space as the main-id of the hygeo waterbodies.
The response should include the hygeo waterbody id that each input node should be associated to.
This function may also include NHDPlus data attributes to allow a tie back to reachcode/measure linear referencing. Potential to mock reachcode/measure attributes such that the nhdplusTools get_flowline_index() function can be used.