|
I am leading a small team of surveyors in conducting a visual assessment using Open Foris Collect Earth. Each and every single one of us has the latest version of Collect Earth (v 1.9.2) and has a Google Earth Engine account (we can all log in to the Google Earth Engine Code Editor page). I created separate Collect Earth projects (*.cep) for each surveyor using my Open Foris Collect’s survey designer. For me, everything runs fine. I can assess points normally within Google Earth Pro. The Google Earth Engine popup window also opens up fine for me. However, for the rest of my team, none of them can get the Google Earth Engine pop-up window to open. When the window first pops up, it asks them; “Trusted Tester Sign In. Additional features available only to members of our trusted tester program. Continue?”. When they click ‘Ok’ and type in their User ID and password, then another prompt comes up saying; “This browser or app may not be secure. Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in.” Has anyone experienced this issue before? Why does this happen, and how do we solve it? Warmest regards, Johanness |
|
Dear all, Excuse the delay on the fix. If you update to Collect Earth version 1.10.0 the problem with the trusted tester should not happen any more as now there is the possibility to use a Google Earth Engine APP that does not require the users to be logged in Google! You can chose this option in the Properties dialog:
|
|
Ciao Khongor! The GEE Code Editor integration stopped working for some users (usually does ones that had never used Collect Earth before January 2020) due to a new way that GEE authenticates the users when you log in. In order to fix this we introduced a new integration to GEE using an GEE App rather than the code editor. To activate this new option go to Properties and then in the "Integrated Services" tab and check the option for "Google Earth Engine APP (no sing-in)" while you un-check the other old option as you don't need that window any more "Open GEE Code Editor (requires Trusted Tester access)"
The window that opens now does not need the user to sign-in. This window will show the NDVI graphs for MODIS, Landsat7/8 and Sentinel-2. If you click on the Landsat or Sentinel-2 graphs you will be able to see the sindle images! This means that if you click on the "top"of the NDVI graph you can see the image with the most vegetation of the year rather than the default yearly mosaic. The result looks like this
|
|
This is a glitch that has happened once before in a training in Equatorial Guinea. It eventually fixed itself, probably all related to the use of Selenium for opening the GEE window. Could you please check if this is still a problem?? |
|
Hi Juliette Were you able to use the GEE Code Editor integration previously? When was the last time it worked? We are trying to fix the issue but it is difficult to reproduce from our office. Have you tried to work using the GEE Explorer integration until the issue is fixed? Here is a video on how to use that integration, not as good as the Code Editor but might be helpful until the fix arrives:
|
|
Hi Open Foris, It is working for me but not for my colleague. When she tries to connect to GEE to view Sentinel-2's NDVI profile for instance, it does not work. She can log on to GEE separately but not when using Collect Earth. No, I do not know what is GEE explorer integration and the link to the video does not work. |
|
Hi Johanness, Did you solve the problem? We also have same problem here in Mongolia Please let us know if you have managed the problem. Thanks, Khongor |
|
Thanks for the quick response. We are now using option you have suggested. But, one of our operator's internet browser got empty window for the GEE APP (no sign-in) option. Do you have any suggestion to solve this issue? I also have another question but it is not relevant to this topic. How do we connect other available national geoportal or restricted server which contains high resolution images to the CE? Does CE supports WNS or WMTS extensions? Please make sure that the operator is using the latest Collect Earth version and that also the Google Chrome version that is used is updated to the latest version 80 ( updating Google Chrome LINK https://support.google.com/chrome/answer/95414?co=GENIE.Platform%3DDesktop&hl=en ) For the WMS use please refer to this post: https://openforis.support/questions/495/how-to-add-very-high-resolution-imagery-to-google-earth-wms Otherwise you can set an integration with a separate service via the Extra URL setting (in the Integrated Services ). Please ask a question on the forum so I can extend |
|
I faced a similar issue when using the Trusted Tester Authorization (I am using the latest versions for Collect Earth as well as my Google Chrome browser). This problem persists despite switching to Mozilla's Firefox. Good news is that the option to use the GEE app (which requires no sign-in) works! I can now view the Landsat & Sentinel False Color Composites in GEE, as well as the time-series plots for Landsat and MODIS NDVI and the MODIS burned area. Thank you for solving this problem Open Foris! I have a question though - can I modify the eePlaygroundScript.fmt and add it to the survey in Open Foris Collect > Survey Designer to customize what imagery/plots to view? Or will that only work with the Trusted Tester Authorization option? |
|
Unfortunately, this problem is still unresolved for me and my team. I tried troubleshooting it by using Open Foris Collect on one of my team member's computer device to create a brand new Collect Earth survey from scratch. I tried this because I was wondering if the Google Earth Engine Trusted Tester Authorization error arose because I shared my .cep with them (i.e. if there was something wrong with transferring .cep and associated files across computers). However, even when I tried that, they were still unable to use Google Earth Engine during the visual assessment exercise. I find this very weird as each of them is able to independently operate on the Google Earth Engine Code Editor. I have raised this issue in the Google Earth Engine Developer Forum, but have not heard anything from them yet. When I do, I will update this forum as well, for others who happen to experience this problem. Any advice, assistance and/or comments is very much appreciated. Thank you. Warmest regards, Johanness |