Add a search box to the map

[giswqs]

Useful resources for a implementing a search control:

• ipymaps @deeplook
• leaflet-search @stefanocudini
• ipyleaflet discussion @SylvainCorlay

[giswqs]

Added search control and geocoding.

[stefanocudini]

hi!
where can I find a working demo?

[giswqs]

@stefanocudini I have not pushed the update to pypi and conda-forge yet. You will need to install the latest update from github using pip install git+https://github.com/giswqs/geemap. Then you can use the following lines within Jupyter notebook to create a map. Once the map is created, you should see the search button on the upper left corner.

import geemap
m = geemap.Map()
m

[stefanocudini]

you should publish a public working notebook on google colab or mybinder ;-)
for users who are not programmers

[giswqs]

Unfortunately, Google Colab currently doesn’t support ipyleaflet. See here. I have another repo of 360+ jupyter notebooks that can be used on Colab with limited functionality using the folium package. Binder has security risks for Earth Engine.

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]

Implemented.

[stefanocudini]

great!