In order to query the DB for CWMS locations (Dams, etc.) and WQ locations, we'll need to keep track of either/both kinds of IDs somehow. My first thoughts are:
Use a generic ID field on the UI side, as well as the location source ('CWMS' vs. 'WQ'). This would probably need to be included in the URL to allow for page reloading/bookmarking. Then the UI can query the right REST endpoint based on whether the source is CWMS or WQ. (The information and detail data will be different for CWMS and WQ, so they'll need to be different REST endpoints).
Use two different IDs on the UI side, either location_code or wqid. Then we wouldn't have to track the source in the URL as well. So if we have a location_code, we hit the CWMS REST endpoint, and if we have wqid, we hit the WQ REST endpoint.
In order to query the DB for CWMS locations (Dams, etc.) and WQ locations, we'll need to keep track of either/both kinds of IDs somehow. My first thoughts are: