-
-
Notifications
You must be signed in to change notification settings - Fork 315
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
Expose leafmap backend options to user #257
Comments
Unfortunately, the interactive GUI requires ipyleaflet and ipyleaflet. Folium is very limited. It can't handle user input. If you just need to display the image and segmentation results, you can still use the folium backend. I would suggest you use Colab before the ipyleaflet issue is resolved in Kaggle. |
I tried google Colab first but I wasn't able to get a working environment setup. After installing samgeo and its dependencies in a GPU session, the notebook was no longer able to access the GPU ( This is where I left off; If you know how to get a working environment with samgeo and cuda in Colab that would be a big help: |
did you try pip install segment-geospatial on Colab? |
Ah thanks that's much simpler and it does work. When I click segment in the interactive window, it does run the model, but it won't show the output segmentation layer on the map. Have you seen it work in Colab? |
It used to work. I have not used it recently. Need sometime to look into it |
Have you tried it on Google Colab? Did it work? I have not encourtered this issue before. Can you provide a notebook that can reproduce the issue? |
Based on this phenomenon (opengeos/leafmap#707 (comment)), I would like to be able to swap out the default backend for folium in hopes of getting this library to work with Kaggle Notebooks. Currently the API doesn't allow for this.
With how different backends are loaded, this may be a sensible way of changing the backend:
The text was updated successfully, but these errors were encountered: