Terence Tuhinanshu

- Fixed a comment in [3068c1d](https://github.com/WikiWatershed/model-my-watershed/pull/3559/commits/3068c1d3c9bfda4d1aa5b6512029f79953b8ffe4) - Removed unused chart region in [5d224b4](https://github.com/WikiWatershed/model-my-watershed/pull/3559/commits/5d224b4f5e979e76780db2034212a0c5cc599567) - Added reference to TODO item in [0eda2dd](https://github.com/WikiWatershed/model-my-watershed/pull/3559/commits/0eda2dd182cfc47606f2c969ea41689cde05cbfe)

Thanks for the review! After talking with the clients, they no longer want to have a special analysis for Drainage Areas. It is too disruptive a flow, and creates special...

Some additional context: If you run `gwlf-e/prepare` and `subbasin/prepare` for the same HUC-12, you'll see that the output is slightly different. In subbasin, the GMS JSON is nested under the...

We'll look into this. Thanks for reporting it.

As it says in [the documentation](https://modelmywatershed.org/api/docs/), you have to prefix the "Authorization" header's value with the word "Token". So the following works for me: ```python >>> import requests >>> MMW_API_KEY...

Hi Saurav, thanks for pointing out the 401 vs 403 distinction. I'll look into that. For the API documentation, if you paste in "Token xyz" in the box as instructed,...

Just got the 100th error for this. Seeing it consistently since last release.

Also here: https://rollbar.com/WikiWatershed/ModelMyWatershed/items/205/

Some discussion in Slack about this problem (but no clear solutions) here: https://azavea.slack.com/archives/CBM6Y3ZT8/p1639630257021600

Also fix tests disabled in #3461.