You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user brought this up on the forum today, noting that SWY does not require that the watershed input have a ws_id field, but SDR does. I'm pretty sure that the only reason that SDR does is legacy from the days when we provided a valuation step, such that different watersheds had different valuation parameters assigned. But we don't do that any more, so is there any reason to require the ws_id field in SDR? Can we remove that requirement?
The text was updated successfully, but these errors were encountered:
Looking at the SDR source code, I can confirm that the ws_id field is no longer required and is not used except to validate that the field exists. So no need to have it there! I'll pull it.
This field is a relic from earlier versions of the model where we
provided an optional valuation step that associated valuation parameters
with the watersheds via the WS_ID field. We removed the valuation
component, but forgot to remove the required WS_ID field.
RE:natcap#1201
A user brought this up on the forum today, noting that SWY does not require that the watershed input have a ws_id field, but SDR does. I'm pretty sure that the only reason that SDR does is legacy from the days when we provided a valuation step, such that different watersheds had different valuation parameters assigned. But we don't do that any more, so is there any reason to require the ws_id field in SDR? Can we remove that requirement?
The text was updated successfully, but these errors were encountered: