{"action":"created","issue":{"url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/issues/98","labels_url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/issues/98/labels{/name}","comments_url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/issues/98/comments","events_url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/issues/98/events","html_url":"https://github.com/caryfitzhugh/NYCCSC-map-viewer/issues/98","id":119956664,"number":98,"title":"enhancement of ClimAID data visualization","user":{"login":"colinbeier","id":7375034,"avatar_url":"https://avatars.githubusercontent.com/u/7375034?v=3","gravatar_id":"","url":"https://api.github.com/users/colinbeier","html_url":"https://github.com/colinbeier","followers_url":"https://api.github.com/users/colinbeier/followers","following_url":"https://api.github.com/users/colinbeier/following{/other_user}","gists_url":"https://api.github.com/users/colinbeier/gists{/gist_id}","starred_url":"https://api.github.com/users/colinbeier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/colinbeier/subscriptions","organizations_url":"https://api.github.com/users/colinbeier/orgs","repos_url":"https://api.github.com/users/colinbeier/repos","events_url":"https://api.github.com/users/colinbeier/events{/privacy}","received_events_url":"https://api.github.com/users/colinbeier/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/labels/beta-feedback","name":"beta-feedback","color":"009800"},{"url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":55,"created_at":"2015-12-02T14:44:59Z","updated_at":"2016-01-07T21:55:51Z","closed_at":"2016-01-07T18:36:21Z","body":"Steve and I have discussed that the ClimAID data currently is not very interesting or useful.  Art and others have confirmed our opinion.  \r\n\r\nThere are a number of reasons and a few possible solutions, some of which might minimize the amount of work on our end.  I'm posting this issue so we can keep track of everything.  \r\n\r\nBelow is an email thread that discusses the issue:\r\n\r\nFrom: Colin Beier [mailto:cbeier@esf.edu] \r\nSent: Tuesday, November 24, 2015 6:51 PM\r\nTo: Arthur T. Degaetano\r\nCc: Steve Signell; Lisa Rector\r\nSubject: RE: ClimAID projections\r\n \r\nArt, I agree with your take... we can do the dynamic color bars and scanning using d3 code but building and customizing this is time consuming. I also am not sure that the map needs to provide such high end function at this stage, given the resources and time left, or at all (your oft used Hyundai vs Maserati argument). I would rather exceed expectations, which is why i have been pressing you and Bill for these data for over a year now... I figured this would be a big time sink, but one that was absolutely worth the investment.\r\n\r\nAfter the holiday, Steve, Cary and I will discuss the time and effort needed to build d3 visualizations into the map, and then we'll provide that info to the project team, to get guidance for how to move forward.\r\n\r\nEnjoy the holiday all...\r\n\r\nCheers\r\nColin\r\n\r\nColin Beier\r\nSUNY ESF\r\n\r\nOn Nov 24, 2015 5:32 PM, \"Arthur T. Degaetano\" <atd2@cornell.edu> wrote:\r\nHi all,\r\n\r\nBill and I had a conversation about this today.  We both came to the conclusion that the second option (\"We can use a gradient color bar, but have the numerical values / range change based on the subset of the data being shown\") was the best.  \r\n\r\nOur reasoning is as follows.  On the PRISM maps, the idea is probably to see how the values vary across the state, so keeping the color bar constant as you scroll through months is not too informative…you would see the map change from all blue to all red as you go from summer to winter.   Thus you would only highlight the season cycle by sliding through months which is the option on this map.  Everyone know there is a seasonal cycle in temperature so this is not a very informative option as it is now.  These maps beg for a dynamic color that perhaps goes from blue (coldest to pink warmest in winter and perhaps from light blue coolest to red warmest in summer).\r\n\r\nThe projections are different.  My opinion is that users would like both. On the projects I am involved with people are very often as interested in the spatial variation of the changes across the state as they are about how the values change through time or between scenarios.  This would argue that these maps also need a dynamic colorbar controlled with a toggle option allowing users to choose between seeing the spatial variation in a single frame across the state (narrower color bar intervals) or sliding through (and highlighting) changes through time or between scenarios.   Again this solution requires a dynamic color bar spanning the full range 2010-2090 of deltas, not just the deltas for a single decade/scenario.\r\n\r\nRight now it seems that the colorbar have been determined a priori and this static image is used in the map legend.  Is that correct.  As you point out this is probably no viable option for moving forward.  I did just a little bit of Googling and found javscript code to make the colorbar dynamic.  Hopefully the existence of such a code snippet will make this an easier task.  At the least the colorbar needs to be able accommodate difference in the overall color range of values, the number of bins to include in the colorbar, and the colors to use.  For instance convention is brown to green for precip and blue to red for temp.  As I stated above for winter probably want dark blue to pink, but in summer light blue to red.\r\n\r\nPlease mull this over and let us know what you think.\r\n\r\nHave a happy Thanksgiving,\r\n\r\nArt\r\n\r\nArt DeGaetano\r\nProfessor  Earth and Atmospheric Sciences\r\nDirector, NOAA Northeast Regional Climate Center\r\n________________________________________\r\nFrom: Colin Beier [cbeier@esf.edu]\r\nSent: Thursday, November 19, 2015 9:37 AM\r\nTo: Arthur T. Degaetano; Lisa Rector\r\nCc: Steve Signell\r\nSubject: ClimAID projections\r\n\r\nHi Art and Lisa,\r\n\r\nI think we all agree that the current visualization of the ClimAID projections in the map viewer is less than desirable.  Art, Steve and I communicated briefly about this via email when we first got the data up in the map a couple of weeks ago.  I wanted to resume that conversation so that we can explore alternatives and decide how best to proceed.  I believe these data are very important to NYSERDA so we may need to wrap Amanda and/or Mark in as well.\r\n\r\nWe have some different options to address this, but there are also some fundamental issues with the data itself that make it less than ideal as eye-candy in a map.  A few thoughts:\r\n\r\n- We can change the color bar from a gentle gradient to something with more abrupt transitions between colors.  The actual range of the data would not change, just the colors for each bin.  This would allow us to keep a consistent range of numerical values but reveal a more visual pattern in the data.  The benefit of doing this is that the relative values are directly comparable when a user toggles between different time periods, scenarios, percentiles, etc.  The downside is that it may artificially or arbitrarily bias certain patterns over others... and it may be problematic to use a color scheme that is not intuitive to most users.\r\n\r\n- We can use a gradient color bar, but have the numerical values / range change based on the subset of the data being shown, i.e., the combination of scenario, percentile, time period.  This provides a visually intuitive pattern for each of the data subsets, but it makes it difficult / impossible to visually compare the values across the scenarios, percentiles, time periods, etc.  It can be misleading if the user does not pay careful attention to how the numerical values in the legend / color bar are changing each time they change to a different subset.   This would also require Steve to write some D3 code so the GUI would dynamically respond to the range of the data being provided - and this is not a trivial task.\r\n\r\n- We can split out, or un-bundle, the projections from a single layer into multiple layers, based on one or more of the categorical variables, such as emissions scenario or time period.  This would allow us to have tighter numerical ranges so that more spatial patterns can be visualized, but it creates a lot of extra layers in the directory for users to select from, and could get quite messy.  I'm also not sure it will help very much.\r\n\r\n- Lastly, we could convert the data to a netCDF format and serve them using a THREDDs server, as we did earlier with the PRISM and UCAR rasters that were demo-ed in the alpha map.  This is labor-intensive and has some technical issues to navigate, but it would provide a more robust basis for visualizing and providing access to ClimAID and other raster climate data from NYCCSC.  I don't know if Art and Bill have any plans for setting up THREDDs on ACIS, or if its already there.  Steve and I could set up another THREDDs server, but Cary is opposed to this idea because of the work involved in setting up everything, and we are not sure if it is needed.  We are also not sure it will lead to more than marginal improvements in the visual quality of the data itself.\r\n\r\nLet's follow up on this next week if we can find some time.  I know its a holiday week for many of us, so if that doesn't work we could try for the week after.   Happy to include Allison and others from the Content Team if necessary.  This would fall squarely within the 'map content call' that Lisa proposed, but for which I'm not sure if we have a time scheduled.  I can send out a Doodle poll to scope a time.\r\n\r\nCheers\r\nColin\r\n"},"comment":{"url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/issues/comments/169818753","html_url":"https://github.com/caryfitzhugh/NYCCSC-map-viewer/issues/98#issuecomment-169818753","issue_url":"https://api.github.com/repos/caryfitzhugh/NYCCSC-map-viewer/issues/98","id":169818753,"user":{"login":"sasignell","id":4191479,"avatar_url":"https://avatars.githubusercontent.com/u/4191479?v=3","gravatar_id":"","url":"https://api.github.com/users/sasignell","html_url":"https://github.com/sasignell","followers_url":"https://api.github.com/users/sasignell/followers","following_url":"https://api.github.com/users/sasignell/following{/other_user}","gists_url":"https://api.github.com/users/sasignell/gists{/gist_id}","starred_url":"https://api.github.com/users/sasignell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sasignell/subscriptions","organizations_url":"https://api.github.com/users/sasignell/orgs","repos_url":"https://api.github.com/users/sasignell/repos","events_url":"https://api.github.com/users/sasignell/events{/privacy}","received_events_url":"https://api.github.com/users/sasignell/received_events","type":"User","site_admin":false},"created_at":"2016-01-07T21:55:51Z","updated_at":"2016-01-07T21:55:51Z","body":"WOOT!\n\na thought for your discussion tomorrow, Colin: maybe the percentiles should\nbe a slider too with 'mean' replaced by a '50'.\n\n\nOn Thu, Jan 7, 2016 at 4:52 PM, Cary FitzHugh <notifications@github.com>\nwrote:\n\n> ok. re-released the candidate for release.\n>\n> On Thu, Jan 7, 2016 at 4:51 PM, Steve Signell <notifications@github.com>\n> wrote:\n>\n> > Great. I just changed the default symbology to 'scenario' and pushed. I\n> > think that is the most intuitive, because it shows the colors getting\n> > redder and redder over time, as one would expect.\n> >\n> > On Thu, Jan 7, 2016 at 4:38 PM, Cary FitzHugh <notifications@github.com>\n> > wrote:\n> >\n> > > ok. I've pushed what I've got here to gh-pages.\n> > >\n> > > Please review. I'll release early tmw morning (and Colin can demo w/\n> Art\n> > /\n> > > Lisa on the integration gh-page).\n> > >\n> > > Sound good?\n> > >\n> > > https://caryfitzhugh.github.io/NYCCSC-map-viewer/dist/map_viewer.html\n> > >\n> > > —\n> > > Reply to this email directly or view it on GitHub\n> > > <\n> >\n> https://github.com/caryfitzhugh/NYCCSC-map-viewer/issues/98#issuecomment-169813203\n> > >\n> >\n> > > .\n> > >\n> >\n> >\n> >\n> > --\n> > Steve Signell\n> > Frontier Spatial, L.L.C.\n> > 1062 Dean St.\n> > Schenectady, NY 12309\n> > 518-232-1008\n> > frontierspatial.com\n> > steve@frontierspatial.com\n> >\n> > —\n> > Reply to this email directly or view it on GitHub\n> > <\n> https://github.com/caryfitzhugh/NYCCSC-map-viewer/issues/98#issuecomment-169817191\n> >\n> > .\n>\n> >\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/caryfitzhugh/NYCCSC-map-viewer/issues/98#issuecomment-169817506>\n> .\n>\n\n\n\n-- \nSteve Signell\nFrontier Spatial, L.L.C.\n1062 Dean St.\nSchenectady, NY 12309\n518-232-1008\nfrontierspatial.com\nsteve@frontierspatial.com\n"}}