search

glos / myglos

Repository for MyGLOS (GLOS Data Portal)
GNU General Public License v3.0
2 stars 2 forks source link

HEC Spill Viewer Tool - next steps #231

Open tslawecki opened 6 years ago

tslawecki commented 6 years ago

As suggested by @Bobfrat ... here's a draft short list of what could/should be done next:

@aggrimm, @ColinNBrooks - anything to modify or add? Suggested due date? @kknee and @cgalvarino copied FYI.

ColinNBrooks commented 6 years ago

That’s a good list. I would separate this into two parts - what we need soon to site effectively shareable with the water treatment operators so we can start getting feedback, and what is a stretch goal. In my opinion, we need the HEC Spill Scenario Tool to have the first four completed to be ready to share (assuming the restricted access at a password level is working for the water intake results).

I don’t think the spill location sharing is required at this point to get the tool out there for feedback. That’ll be good, but I think what we want the most is feedback on the presentation & ease of use of the modeling results.

I also think we want two points GIS layers added - one of the beach locations, and one restricted access layer of the water intakes (with names). Amanda, can you prep those for sharing, please?

Thanks, Colin

On Tue, Jun 19, 2018 at 3:04 PM Tad Slawecki notifications@github.com wrote:

As suggested by @Bobfrat https://github.com/Bobfrat ... here's a draft short list of what could/should be done next:

  • "HEC Spill Scenario Tool" as title.
  • Use ncWMS2 service for display.
  • Correct proxy operation so tool works from none-whitelisted address.
  • Correct WMS size bug
  • Test and document sharing workflow for a spill location:
    • Plant operator/ beach manager hears about a spill and logs in to HSST;
    • PO/BM turns on relevant map layers and adds a virtual buoy at suspected location;
    • PO/BM saves the collection with a relevant name (include date and abbreviated spill ID information);
    • PO/BM shares the collection link with others;
    • Others open the collection link:
      • Link opens HECSST, which prompts for authentication
      • If authentication fails, show nice message

@aggrimm https://github.com/aggrimm, @ColinNBrooks https://github.com/ColinNBrooks - anything to modify or add? Suggested due date? @kknee https://github.com/kknee and @cgalvarino https://github.com/cgalvarino copied FYI.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/glos/myglos/issues/231, or mute the thread https://github.com/notifications/unsubscribe-auth/ATZv7alNenlJnoXRDnV2k4ViUE6rJVp8ks5t-UsmgaJpZM4UuEQy .

--

Colin Brooks Senior Research Scientist Transportation and UAS Program Leader Michigan Tech Research Institute (MTRI) 3600 Green Court, Suite 100 Ann Arbor, MI 48105

Office Phone: 734-913-6858 Cell Phone: 734-604-4196 Fax: 734-913-6880 cnbrooks@mtu.edu www.mtri.org www.mtri.org/unpaved www.mtri.org/mdot_uav.html www.mtri.org/geoasset www.mtri.org/eurasian_watermilfoil.html http://mtri.org/eurasian_watermilfoil.html www.abj50.org/subcommittees/sensing-technologies/

Bobfrat commented 6 years ago

@tslawecki For "HEC Spill Scenario Tool" as title. I assume you mean the banner as well as the page title?

Bobfrat commented 6 years ago

Any thoughts on a pallette? I'm using x-Rainbox-inv for now

aggrimm commented 6 years ago

I'm good with x-Rainbox-inv

ColinNBrooks commented 6 years ago

Let's go with that then for the version of the Spill Scenario Tool we'll be sharing with the water treatment plant operators. - Colin

On Mon, Jun 25, 2018, 3:40 PM aggrimm notifications@github.com wrote:

I'm good with x-Rainbox-inv

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/glos/myglos/issues/231#issuecomment-400069704, or mute the thread https://github.com/notifications/unsubscribe-auth/ATZv7d_e_xXzssDRqLxF8Y3T36iTJ_Qrks5uATyZgaJpZM4UuEQy .

kkoch commented 6 years ago

We will also want to be sure we somehow link to the metadata record once we have the public in portal view working (for beaches). http://data.glos.us/metadata?uuid=ca2ce240-7da9-489c-80fa-b5326dc28e91

ColinNBrooks commented 6 years ago

Do we have a URL we can share with our water treatment operators? If so, how does the restricted access work?

Bobfrat commented 6 years ago

Right now the site requires users to login but its sharing the dev.oceansmap.com/myglos users database and anyone can create a new account and get access.

If we need to lock it down further we can remove the ability to create a new account and instead create accounts manually to distribute to users.

ColinNBrooks commented 6 years ago

For this testing, might it be possible & desirable to have a general WTP operators account that they could share?

Bobfrat commented 6 years ago

Absolutely so do we restrict the site to just that single account (and maybe a couple accounts for us)?

ColinNBrooks commented 6 years ago

I think that's a good way to go for this stage of testing with our WTP users. Makes it fairly simple, I'm hoping. We can mention that individual user accounts would be available for the final, deployed version.

ColinNBrooks commented 6 years ago

Hi Bob, is there a "water treatment plant username" (& password) we can share to our spills WTP user community to them to use with the URL. We'll be sharing this URL, correct: http://dev.oceansmap.com/myglos-spill/

As Tad noted, there's a few other things that need to be ready to share the URL & username/pwd, but I wanted to be ready for this. I would like to share this with them after the 4th of July holiday week, so perhaps as early as July 10th. The final meeting with the WTP operators is on Thursday, July 26th, so that would give us about 2 weeks for feedback from them and hopefully making some tweaks for the in-person demo on 7/26. We're also planning on having some computers available so they can use them during the live in-person demo session. Does this sound possible?

Bobfrat commented 6 years ago

No UN PW set up yet but I can do that. Do you want me to make up a UN/PW or do you have a preference? Feel free to email me any suggestions.

Bobfrat commented 6 years ago

@ColinNBrooks @tslawecki I've moved the spill portal onto its own user management system so your myglos dev accounts will no longer work. I will go ahead and create an account for the water treatment plant users but the user management system needs an email rather than username, and preferably an email that does exist in case you need to change the password or set up alerts.

Is there a good email account I can use for the water treatment plant users?

tslawecki commented 6 years ago

Colin,

I suggest for the short term creating a gmail account with an appropriate name ...

Tad

From: Bob Fratantonio notifications@github.com Sent: Monday, July 2, 2018 11:15 AM To: glos/myglos Cc: Tad Slawecki; Mention Subject: Re: [glos/myglos] HEC Spill Viewer Tool - next steps (#231)

@ColinNBrookshttps://github.com/ColinNBrooks @tslaweckihttps://github.com/tslawecki I've moved the spill portal onto its own user management system so your myglos dev accounts will no longer work. I will go ahead and create an account for the water treatment plant users but the user management system needs an email rather than username, and preferably an email that does exist in case you need to change the password or set up alerts.

Is there a good email account I can use for the water treatment plant users?

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/231#issuecomment-401839201, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3Pi0BdT1f80GcnQzLDAMeSxXLxIqAks5uCjkEgaJpZM4UuEQy.

ColinNBrooks commented 6 years ago

I've created the following gmail account: wtpgrouptesting@gmail.com with the following password: HECspills2018!

That should work for our upcoming user testing. Feel free to log in and test it if you want to. It's linked to my cnbrooks@mtu.edu gmail account for security purposes in case we need that.

benjwadams commented 6 years ago

I'm going to have to advise against posting account credentials over GitHub, even if a repo is set to private. Your account could be easily compromised by anyone in addition to scripts scraping public GitHub repos for account information. I'd advise you to change the password on the listed account and send it via some other secure means, i.e. a folder in an SSH location accessible to us or an encrypted message over other transmission media such as email via services such as Encrypto.

ColinNBrooks commented 6 years ago

OK, I've reset the password and won't post it here. I haven't done either of those two options before (SSH folder or encrypted message using a service like Encrypto) but I'll figure those out.

ColinNBrooks commented 6 years ago

We're going to need to transmit these credentials to WTP operators too, unless we backtrack and make them set up their own accounts after all for the feedback phase.

ColinNBrooks commented 6 years ago

I've encrypted a file using Encrypto that has the password in it. Should I post it it here, and people will contact me for the password to unencrypt it? I'm not sure what do to next.

tslawecki commented 6 years ago

I think that's the right way to handle it within the team.

I think it's too much, though, to ask the utilities to learn how use encrypto, and suggest that we have a less complex method for communicating the password to them. For example, I could see us sending the e-mail address and the password to them (or to SEMCOG) by postal mail, or if electronically, sending the e-mail address by e-mail and sending the unencrypted password by text.

From: Colin N. Brooks notifications@github.com Sent: Monday, July 2, 2018 2:23 PM To: glos/myglos Cc: Tad Slawecki; Mention Subject: Re: [glos/myglos] HEC Spill Viewer Tool - next steps (#231)

I've encrypted a file using Encrypto that has the password in it. Should I post it it here, and people will contact me for the password to unencrypt it? I'm not sure what do to next.

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/glos/myglos/issues/231#issuecomment-401892087, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE-3PtCoFbRKTH0-GS3d-0nrvH8hT7Ptks5uCmU_gaJpZM4UuEQy.

ColinNBrooks commented 6 years ago

Sending the WTP the username and then having them contact me to get the password seems reasonable. Will their log-on credentials for this GLOS Dev portal be the same as the updated username/password combo I have?

I can't post the Encrypto file here on Github (it says it's not a supported file type) but I'll email it to at least Tad & Bob to start with and they can contact me for the unencryption password.

tslawecki commented 6 years ago

That's just you being nice and all client-service oriented! As long as you're willing to accept the calls, this will work well!

ColinNBrooks commented 6 years ago

I've gotten one report of long loading times already, and in trying to use the site in the last 5 minutes, it's gone from loading data to not leading the site at all (trying on two computers & 3 browsers) to now getting a "404 Not Found". Are we the victim of our own success here in our WTP operators trying to use the HEC Spill Scenarios Tool? @Bobfrat @kknee could one of you take a look please?

kkoch commented 6 years ago

@cheryldmorse or @gitchrisadams > not sure which of you are punting in the above folks' absence but can one of you check @ColinNBrooks' issue?

gitchrisadams commented 6 years ago

@benjwadams and I are looking into this issue now.

ColinNBrooks commented 6 years ago

I can access the site, but I just tried 3 browsers (Chrome, Firefox, & Edge), and the spill modeling results are not loading. I get a screen like this one where under the layer I choose, it says "There was an error drawing this layer."

If our end users are trying out the site right now, I'm worried we're putting them off by not having a working tool right now. Any luck on figuring this out, fearless RPS colleagues?

ColinNBrooks commented 6 years ago

Here's the screen I was talking about: image

gitchrisadams commented 6 years ago

@ColinNBrooks We are still looking into the issues. We are seeing that the layers loading/not loading intermittently, so are still trying to find out why.

gitchrisadams commented 6 years ago

@ColinNBrooks We were finding some issues with this end point at the time: http://34.220.186.193:8080/ncWMS2/wms?SERVICE=WMS&REQUEST=GetCapabilities&VERSION=1.1.1 But looks to be working now. Also @benjwadams did a restart and added some logic and added a 15 second timeout for layers. We did some testing and things look to be loading fine. Can you let us know if you have further issues.

ColinNBrooks commented 6 years ago

I agree that things seem to be loading & displaying faster & more reliably now. Thanks! I'll keep an eye out on things, and I've asked SEMCOG to see how the users are doing.

kknee commented 6 years ago

@ColinNBrooks the work that @gitchrisadams and @benjwadams did today means that the entire site won't be impacted if the spill endpoints are down. Do note that if the endpoints are down you will still see the "There was an error drawing this layer." message - that is a normal response to a service being unavailable.

ColinNBrooks commented 6 years ago

Thanks @kknee - things seem to be more stable now so I'm hoping our water treatment plant operators are having a good experience and will be giving us lots of feedback next week.

ColinNBrooks commented 5 years ago

I'm seeing "There was an error drawing this layer" messages again when I try to use the site this morning. Any help appreciated!

image

kkoch commented 5 years ago

Becky noted that she is having trouble logging in to the spill viewer. I don't have the login info so can't test but she says > "I can login ok using the group email and password. When I click on the HEC Spills Scenario, nothing shows up in the catalog."

Can someone @gitchrisadams and @benjwadams maybe check on this?

tslawecki commented 5 years ago

Adding @cheryldmorse and @Bobfrat for completeness. Also, I checked and confirmed that the ncWMS2 server and services are good.

Bobfrat commented 5 years ago

NCWMS server was down which is why the layers weren't available. I restarted so they should be back on the portal within the hour. We need some monitoring on that server and need to figure out why its crashing (memory?, CPU?) before we move to production

beckypearson commented 5 years ago

I went to the development site (http://dev.oceansmap.com/myglos-spill/) and now I get a 404 error.

Bobfrat commented 5 years ago

We are currently experiencing issues with our dev server. Not sure if its related to the spill portal but we'll let you know once we can determine what's happening.

@benjwadams FYI