Collaborative area for discussing Bugs, Updates, and Modifications to Great Lakes to Gulf

Future ToDo:

  • Talk to Greg about updated Visualizations: Hold off on this for a while on initiating anything with him - this is a more future goal
  • Shannon will archive this page for completed items
  • Incorporate suggestions from Walton Grantees webinar into this page

Additional fixes and features, not necessarily critical to do before Webinar:

  1. Phosphorus scale needs to be recalibrated because range is much different than nitrate ( GLGVO-661 - Getting issue details... STATUS )
  2. In the Trend Sites view, need to replace Nitrate graphs with Phosphorus (Ted needs to get NCSA data) ( GLGVO-659 - Getting issue details... STATUS )
  3. HUC-8 data needs to be examined and replaced. Correct data from Greg McIsaac is in this spreadsheet, and rather than yearly data, it is just two time periods.
  4. Need to examine all the places where we use the terms nitrogen and nitrate and make them more specific- Total Nitrogen or Nitrate as N
  5. Need to prominently display the year on the map (there has been some user confusion thinking we were looking at an aggretation of years on the map)
  6. Also want to consider for the Illinois Drainage and Trend Sites sties how we will have an alternate visualization that looks at aggregations of years (for instance 1980-1996 and also 2013-2017. Or in WRTDS, how we indicate trends in certain decades or other time periods.
  7. Need to examine the polygon for the Rock River at Rockton- there is some portion of the watershed that will have to be in the "extrapolated" color. (In the image, it's the highlighted red polygon.) This is extrapolated because it is in Illinois, but when using the Rock River at Rockton to subtract the Wisconsin Portion of the watershed, the portion in Illinois has to be "added back in" to the Rock River numbers, and hence is extrapolated.
  8. Need to manually add the Chicago watershed back into the Illinois River due to the historic reversal of the river and hydrologic changes.
  9. Need to work on exploratory Analysis page
    1. make sure all data present
    2. when there is only a minimal change, we'll want to indicate that as "no trend" or "weak trend" instead of up or down.
    3. need more documentation on the "trending up/down"
    4. threshold needs units
    5. Need to explain what time period our threshold is for.
  10. Geostreaming app -
    1. associate discharge gauges with continuous monitoring sites and calculate loads
      1. overlay discharge onto the WQ data charts
    2. Need overlay of Mississippi River watershed on basemap
  11. Need to figure out how to direct people to storyboards from specific spots on the site.
  12. Clean up "search and download" page- specifically the search by area list.

Critical to do before Walton Grantees Webinar:


  1. Do we have polygons for the "unmonitored area" in illinois for the Illinois Drainage view? ... I think it would be clearer if we displayed those polygons along with the existing catchments and had a legend that said "Load from this area extrapolated" Aaron Hoyle-Katz ... This is a lower priority at this point, but still important.
      1. We need to think about this. If the polygon shows, then users want to click and try to see the data. Yes, what you say makes sense. What if we used an additional shading similar to "no data" shading, and have it say "area extrapolated to calculate statewide load"
      2. Yes, we have a polygon shows all the Illinois areas not covered by stations. This is the same polygon that we used in the "Tracking Trends with GLTG" storyboard, slide 2. -AHK
  2. Hoping to get the WRTDS output for this station and Valley City done today or this weekend so they can be implemented on the dashboard as an example of Sentinel Site.   WRTDS outputs for Illinois River Valley City and Iowa River Wapello are attached below. Annual "summary" should be the Annual Load. Data and example charts below. Phosphorus is not done yet, that will take some additional work, but can be added later.
  3. Hey Aaron Hoyle-Katzcan you take a look at the polygon for Iowa River at Wapello? It looks a little weird on the east side, especially compared to the one here
    1. Whoops, that was definitely generated with bad data. Updated geojson here:




  1. when you follow link to the geostreaming app, there is no way to get back to the landing page / dashboard page from the geostream app.
    • Already implemented. I will be deploied. We will inform you when it will be deploy
  2. on dashboard page, need to get rid of the "no data - avg of surrounding watersheds" thing under the legend. (Kaveh Karimi Asli)
    • Comments: 
      • Ted Kratschmer we actually have a situation with no data. and I think that it needs the information about no data as shown below: 
      • Ted Kratschmer Could you give us why do you want to remove this? or any other suggestion?
    • Proposed action:
      • Remove "avg of surrounding watersheds" and still leave "No data" for the year which doesn't have data. (I agree. That makes sense -TK)
      • Update "no data" icon
      • Is it possible to make the image for the "no data" legend clearer? It's hard to tell that it's a pattern. → Yes. we are working on it. (This looks great -TK)
      • Suggested design:
  3. Please replace the boundary type info box text on the Dashboard with the attachment Dashboard boundary type info box Dashboard Boundary type info box.docx (Kaveh Karimi Asli)
  4. BUG: in the watershed boundary view, there is no way to de-select the watershed polygon to go back to a main view (Kaveh Karimi Asli)
    1. We need to display station icon
    2. It's resolved in the new version. You can deselect the watershed by clicking on it again.
  5. On IL drainage dashboard, replace "Overall Summary" with "Statewide Summary" ; Also replace "Yearly Average - 2017" with "Average Yield - 2017" (Diego Calderon  GLGVO-628 - Getting issue details... STATUS )
  6. BUG: Dashboard, showing IL drainage boundary type: from beginning state, when you click on a watershed, the little popup box opens and shows contributing waterways and acres, but it does not give the name of the watershed. After you click a station icon, it does show the name, but when you click on a different watershed, the box moves, but the information does not change. Only after clicking another station does the information in the box change. (Already fixed in the new version).
  7. Add catchment polygon for 1) Iowa River at Wapello and 2) Illinois River at Valley City (Valley City is already in use in the Illinois Dashboard.) (Diego Calderon  GLGVO-629 - Getting issue details... STATUS )
  8. We need to add a link (citation) to McIsaac's report where the data comes from on the HUC-8 dashboard view  ... I think having something under the graph on the right hand side would work fine. (Aaraj Habib GLGVO-630 - Getting issue details... STATUS )
  9. Move variable dropdowns on the home page to the sidebar  GLGVO-631 - Getting issue details... STATUS (Kaveh Karimi Asli)
  10. Update partners and FAQ pages GLGVO-635 - Getting issue details... STATUS (Kaveh Karimi Asli)
  11. Fix popup bugs and fix disappearing markers (Kaveh Karimi Asli): GLGVO-634 - Getting issue details... STATUS
    1. Also need a way to get back to the Illinois "state-wide" or "overall summary" nutrient yield chart after clicking into a watershed while on the Illinois Drainage screen
        1. Ted Kratschmer currently, if you click the station again, it will go back to "overall summary" (ok- It seemed like the other day that was not happening, but maybe I missed it -TK)
      2. Bug: when turn off the selection of watershed, the popup should be disappeared. 
  12. Rename "watershed boundary" to "Trend Watersheds" under Boundary Types (Diego Calderon )  GLGVO-637 - Getting issue details... STATUS
  13. Need to have better explanation of the Avg. Annual Nutrient yield graph (Ted Kratschmerto provide information) (See below) (Kaveh Karimi Asli) GLGVO-640 - Getting issue details... STATUS
    1. "Yield is a measure of nutrients lost per unit area. This measure is useful because it removes the influence of watershed size in a measurement so that different size watersheds may be compared."
  14. BUG: in the Watershed boundary view, the title on the right says "Illinois" Please change to the state where the station is (Kaveh Karimi Asli) GLGVO-638 - Getting issue details... STATUS
  15. In the watershed boundary view before clicking a station, the "illinois overall summary" graph and chart are displayed. Need to either remove those until something is clicked on, or perhaps show the graph for the total load to the Gulf of Mexico (data can be found in the nitrate load tab of this worksheet. "Tons" is the main bar, and the confidence interval bounds are TONS_L95 and TONS_U95. Annual Load to Gulf of Mexico.csv (Kaveh Karimi Asli) GLGVO-638 - Getting issue details... STATUS
      1. Team needs to discuss this matter
      2. Confluence Page Loads to gulf of mexico for watershed dashboard
  16. On the Illinois Drainage page, we need to have under the Overall Summary, a box that says "The total nitrate load leaving the state of Illinois is estimated to be xxxx lb 2019" or whatever year, updated by year as the user explores different years in the graphs. We need can get that information from the graphs on page 10 & 11. (Aaron Hoyle-Katz  may have this, or perhaps he can get it from McIsaac) ... on the "Illinois Drainage" page we should also add an Annual Load graph along with the Annual Yield (Kaveh Karimi Asli GLGVO-641 - Getting issue details... STATUS
    • Comments:
      • Ted Kratschmer is "Illinois drainage page" a dashboard with "IL drainage" boundary type? or story board? I meant Illinois Drainage boundary type. I'm proposing we add text above the yield chart. Also need to add a chart above the yield chart that shows the statewide load, which is that data from the document linked above. -TK
    • Data is attached here.  In the TP and Nitrate-N tabs, we'll use column M for the statewide load estimate, in Million kg per year. Kaveh Karimi Asli  
  17. GLGVO-645 - Getting issue details... STATUS (Diego Calderon)
  18. The watershed boundary polygon in Minnesota says station USGS 05418720 ... This is the station name for a different station (Maquoteka river in Iowa). I'm unsure what the actual station number is. Something on the Minnesota River... Mankota? (Kaveh Karimi Asli) GLGVO-642 - Getting issue details... STATUS
      1. Ted Kratschmer who knows this info? Does Aaron know? Aaron Hoyle-Katz do you know what the catchment on the "Watershed Boundary" represents? the one in Minnesota that shows up.
        1. MI 0035 is the station number, I believe this mislabel will be fixed soon. -AHK 
        2. The station "pretty name" is the Minnesota River at Fort Snelling. The data is collected by the Metropolitan Council. I will not be able to do a WRTDS output for this in time for the meeting.
  19. GLGVO-643 - Getting issue details... STATUS (Kaveh Karimi Asli)
  20. GLGVO-644 - Getting issue details... STATUS (Kaveh Karimi Asli)
  21. GLGVO-648 - Getting issue details... STATUS (Kaveh Karimi Asli)
  22. Change favicon  GLGVO-649 - Getting issue details... STATUS
  23. GLGVO-647 - Getting issue details... STATUS (Kaveh Karimi Asli)
  24. GLGVO-650 - Getting issue details... STATUS  (Kaveh Karimi Asli)
  25. GLGVO-646 - Getting issue details... STATUS (Aaraj Habib)
  26. On HUC8 view, please remove "IL Drainage - Outside" ( GLGVO-660 - Getting issue details... STATUS )
  27. From Ted Kratschmer:
    1. Kaveh Karimi Asli Can you please update the legend here?
      1. It needs to be :
        1. Annual Load (blue)
        2. Flow Normalized Load (red)
        3. 95% Confidence Interval - Flow Normalized Load (orange)
      2. Also, the name of the chart should be "Annual Nitrate Load" instead of "annual nitrate flow"
  28. I'd like to see the rivers in the catchments (at least the major ones) ( GLGVO-658 - Getting issue details... STATUS )

  • No labels