Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tried out in Google Colab - geemap Map not working #2

Closed
BuddyVolly opened this issue Apr 6, 2020 · 2 comments
Closed

Tried out in Google Colab - geemap Map not working #2

BuddyVolly opened this issue Apr 6, 2020 · 2 comments

Comments

@BuddyVolly
Copy link

Google colab with pip install

Description

I clicked on the Google colab button in the repo, opened it and ran it. geemap.eefolium did give me back a map, but the standard geemap not. Since I would like to use the advanced features of split map etc, I rely on the standard function.

What I Did

I opened https://gishub.org/geemap-colab and executed one cell after the other.
no crash here, the output just remains empty.

@giswqs
Copy link
Member

giswqs commented Apr 6, 2020

@BuddyVolly Unfortunately, Google Colab currently does not support ipyleaflet (source). Therefore, the ipyleaflet-based geemap won't be able to display the map even the code executes without errors.
Please see the Important Note in the Usage section. I would encourage you to install geemap on your local computer. You can also try binder, but I want to make sure you are aware of the security risks. I am quoting a note from @tylere

When a user authenticates to the Earth Engine servers (i.e. uses ee.Authenticate), a 'credentials' file is created in a subfolder of the user's home directory. For example: ~/.config/earthengine/credentials. Anyone who gets access to this file will have access to your Earth Engine data, due to the very significant permissions you have granted (i.e. 1. View and manage your Google Earth Engine data; 2. Manage your data and permissions in Google Cloud Storage). This is fine on a computer that you control like your local machine or a cloud VM that you have created (and secured), but creating this file on a remote server that you don't control is a security risk. You are trusting that the organization or individual who manages the server will prevent others from accessing your credentials file. Binder instances are examples of these remote servers where your credentials file may be created.

@giswqs giswqs closed this as completed Apr 6, 2020
@BuddyVolly
Copy link
Author

Thanks for the clarification. Will try it locally then. In any case, great work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants