The DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index; none of the 5 sources its claims cite is checked for support yet.
geemap: A Python package for interactive mapping with Google Earth Engine
Open accessAbstract
geemap is a Python package for interactive mapping with Google Earth Engine (GEE), which is a cloud computing platform with a multi-petabyte catalog of satellite imagery and geospatial datasets (e.g., Landsat, Sentinel, MODIS, NAIP) (Gorelick et al., 2017).During the past few years, GEE has become very popular in the geospatial community and it has empowered numerous environmental applications at local, regional, and global scales.Some of the notable environmental applications include mapping global forest change (Hansen et al., 2013), global urban change (Liu et al., 2020), global surface water change (Pekel, Cottam, Gorelick, & Belward, 2016), wetland inundation dynamics (Wu et al., 2019), vegetation phenology (Li et al., 2019), and time series analysis (Kennedy et al., 2018).GEE provides both JavaScript and Python APIs for making computational requests to the Earth Engine servers.Compared with the comprehensive documentation and interactive IDE (i.e., GEE JavaScript Code Editor) of the GEE JavaScript API, the GEE Python API lacks good documentation and lacks functionality for visualizing results interactively.The geemap Python package is created to fill this gap.It is built upon ipyleaflet and ipywidgets, enabling GEE users to analyze and visualize Earth Engine datasets interactively with Jupyter notebooks.
Overview
CoChat Summary
TL;DR
geemap is a Python package that adds interactive mapping and visualization to the Google Earth Engine Python API, which the author argues lacks good documentation and interactive visualization functionality relative to the JavaScript API. It is built on ipyleaflet and ipywidgets so that GEE datasets can be explored interactively in Jupyter notebooks.
Key findings
- The GEE Python API "lacks good documentation and lacks functionality for visualizing results interactively"; geemap is created to fill this gap by building on ipyleaflet and ipywidgets for interactive analysis and visualization in Jupyter notebooks.
- Functionality is organized into modules: `geemap` (main interactive mapping with GEE, ipyleaflet, ipywidgets), `eefolium` (mapping with Earth Engine and folium, designed for Google Colab), `conversion` (automatic conversion of Earth Engine JavaScripts to Python scripts and Jupyter notebooks), `basemaps` (XYZ and WMS tiled basemaps), and `legends` (customized legends).
- Google Colab does not currently support ipyleaflet; users there must import `geemap.eefolium as geemap`, which "provides limited interactive mapping functionality," whereas full functionality requires a local computer or secured server with Jupyter notebook installed.
- Supporting materials reported: 20+ video tutorials with corresponding notebook examples, 360+ Jupyter notebook examples for using Google Earth Engine, and complete documentation on geemap modules and methods.
Methods
- Design: a software package description rather than an empirical study; geemap is built upon ipyleaflet and folium for interactive mapping, with ipyleaflet built on ipywidgets to allow bidirectional frontend–backend communication and capture of user input, while folium is described as meant for displaying static data only.
- Data or sample: Not stated in the paper (no dataset, sample, or user population is analyzed; the paper describes intended audiences of students, researchers, and existing GEE users transitioning from JavaScript to Python).
- Main analysis: Not stated in the paper (no evaluation, benchmark, or quantitative analysis is reported).
Limitations
- Stated by the paper: Google Colab does not support ipyleaflet, so Colab users get only the limited interactive mapping functionality of `geemap.eefolium`; full functionality requires a local computer or secured server with Jupyter notebook installed.
- Evident from the text: the paper reports no performance measurements, accuracy evaluation, usability testing, or comparison against alternative tools — the claims about reducing conversion time and filling the documentation/visualization gap are asserted rather than empirically demonstrated.
- Evident from the text: the paper provides no version number, release history, dependency version constraints, or installation instructions, and no quantitative usage or adoption metrics beyond the counts of tutorials and notebook examples.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
0 Valid · 1 Not valid · 3 Not checked · 12 Own results and interpretations
4 references still to check
A free account verifies the references that are still open.
- Probably not a substantial claim. 15
- It may state two separate claims as one. 6
Citations
Cites
Google Earth Engine: Planetary-scale geospatial analysis for everyone
Gorelick, N., Hancher, M., Dixon, M., Ilyushchenko, S., Thau, D., & Moore, R. (2017) · Remote Sensing of Environment · doi:10.1016/j.rse.2017.06.031 · Cited by 14,719
High-Resolution Global Maps of 21st-Century Forest Cover Change
Hansen, M. C., Potapov, P. V., Moore, R., Hancher, M., Turubanova, S. A., Tyukavina, A., Thau, D., Stehman, S. V., Goetz, S. J., Loveland, T. R., et al. (2013) · Science · doi:10.1126/science.1244693 · Cited by 11,704 · cited 2×
“Some of the notable environmental applications include mapping global forest change (Hansen et al., 2013), global urban change (Liu et al., 2020), global surface water change (Pekel, Cottam, Gorelick, & Belward, 2016), wetland inundation dynamics (Wu et al., 2019), vegetation phenology (Li et al.,…”
BackgroundHigh-resolution mapping of global surface water and its long-term changes
Pekel, J.-F., Cottam, A., Gorelick, N., & Belward, A. S. (2016) · Nature · doi:10.1038/nature20584 · Cited by 5,513
High-spatiotemporal-resolution mapping of global urban change from 1985 to 2015
Liu, X., Huang, Y., Xu, X., Li, X., Li, X., Ciais, P., Lin, P., Gong, K., Ziegler, A. D., Chen, A., et al. (2020) · Nature Sustainability · doi:10.1038/s41893-020-0521-x · Cited by 874
Self-citationImplementation of the LandTrendr Algorithm on Google Earth Engine
Kennedy, R. E., Yang, Z., Gorelick, N., Braaten, J., Cavalcante, L., Cohen, W. B., & Healey, S. (2018) · Remote Sensing · doi:10.3390/rs10050691 · Cited by 562
Wu, Q., Lane, C. R., Li, X., Zhao, K., Zhou, Y., Clinton, N., DeVries, B., Golden, H. E., & Lang, M. W. (2019) · Remote Sensing of Environment · doi:10.1016/j.rse.2019.04.015 · Cited by 186
Self-citationLi, X., Zhou, Y., Meng, L., Asrar, G., Lü, C., & Wu, Q. (2019) · Earth system science data · doi:10.5194/essd-11-881-2019 · Cited by 115
Self-citation
Cited by
Google Earth Engine and Artificial Intelligence (AI): A Comprehensive Review
Yang, L., Driscol, J., Sarigai, S., Wu, Q., Chen, H., & Lippitt, C. D. (2022) · Remote Sensing · doi:10.3390/rs14143253 · Cited by 264
Self-citationFlood Risk Mapping by Remote Sensing Data and Random Forest Technique
Farhadi, H., & Najafzadeh, M. (2021) · Water · doi:10.3390/w13213115 · Cited by 210
Applications of Google Earth Engine in fluvial geomorphology for detecting river channel change
Boothroyd, R. J., Williams, R. D., Hoey, T. B., Barrett, B., & Prasojo, O. A. (2021) · WIREs Water · doi:10.1002/wat2.1496 · Cited by 140
Estévez, J., Salinero-Delgado, M., Berger, K., Pipia, L., Rivera-Caicedo, J. P., Wocher, M., Reyes-Muñoz, P., Tagliabue, G., Boschetti, M., & Verrelst, J. (2022) · Remote Sensing of Environment · doi:10.1016/j.rse.2022.112958 · Cited by 126
Gong, C., Lyu, F., & Wang, Y. (2023) · Ecological Indicators · doi:10.1016/j.ecolind.2023.111060 · Cited by 113
Metadata
- Authors
- Wu, Q.
- Affiliations
- University of Tennessee at Knoxville (US)
- Corresponding author
- Wu, Qiusheng
- ORCID
- Wu, Qiusheng
- Venue
- Journal of Open Source Software
- Publisher
- The Open Journal
- Published
- 2020-07-15
- Volume
- 5
- Issue
- 51
- Pages
- 2305
- ISSN
- 2475-9066 (ISSN-L)
- OpenAlex
- W3042626839
- Semantic Scholar
- 87a20f95c2f6bf00a08492c637c638ab303ae3a5
- Cited by
- 340
- References
- 7
- Citations by year
- 2026: 69 · 2025: 70 · 2024: 75 · 2023: 67 · 2022: 30 · 2021: 26 · 2020: 3
- Type
- software paper
- Language
- en
- Open access
- diamond
- doi.org
- Licence
- cc-by
- creativecommons.org/licenses/by/4.0/ (vor)
- creativecommons.org/licenses/by/4.0/ (am)
- creativecommons.org/licenses/by/4.0/ (tdm)
- Locations
- The Journal of Open Source Software (publishedVersion, cc-by)
- Topics
- Physical Sciences › Computer Science › Software › Computational Physics and Python Applications
- Social Sciences › Geography, Planning and Development › Geographic Information Systems Studies
- Physical Sciences › Environmental Science › Ecology › Remote Sensing in Agriculture
- Keywords
- Google Earth Engine, interactive maps, Python interface, Jupyter notebooks, ipywidgets, satellite imagery, spatial data visualization
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
A language model drew the claims from the paper on 2026-11-18, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-11-18 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: geemap: A Python package for interactive mapping with Google Earth Engine. https://app.cochat.ai/papers/10.21105/joss.02305
- The paper
- Wu, Q. (2020). geemap: A Python package for interactive mapping with Google Earth Engine. Journal of Open Source Software. https://doi.org/10.21105/joss.02305
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.