EOmaps

[raphaelquast]

Submitting Author: Raphael Quast (@raphaelquast)
Package Name: EOmaps One-Line Description of Package: https://eomaps.readthedocs.io/en/latest/ Repository Link (if existing): https://github.com/raphaelquast/EOmaps

---

Code of Conduct & Commitment to Maintain Package

• [x] I agree to abide by pyOpenSci's Code of Conduct during the review process and in maintaining my package after should it be accepted.
• [x] I have read and will commit to package maintenance after the review as per the pyOpenSci Policies Guidelines.

Description

• Include a brief paragraph describing what your package does:

EOmaps is a python package to visualize and analyze geographical datasets.

It is intended to simplify the process of geospatial data visualization and to provide a straight forward way to turn the maps into interactive widgets for data analysis.

EOmaps is based on matplotlib and cartopy and extends cartopy's capabilities with the following features

• Multi-layer capabilities (compare/combine/overlay multiple layers)
• North-arrows, scalebars, gridlines on arbitrary projections, ...
• A PyQt5 GUI widget that can be used to quickly fetch webmaps, switch layers, check data-values etc.
• Capabilities to visualize datasets as ellipses, rectangles, geodesic circles, voronoi diagrams, contour plots ...
• Integration with datashader to visualize extremely large datasets
• ...and many more features...

It is extensively documented, unit-tested, citable via a zenodo doi and installable via conda or pip (however using pip is discouraged since dependencies like GDAL and PYPROJ can be difficult to install, especially on windows)

Community Partnerships

We partner with communities to support peer review with an additional layer of checks that satisfy community requirements. If your package fits into an existing community please check below:

• [ ] Pangeo
  • [ ] My package adheres to the Pangeo standards listed in the pyOpenSci peer review guidebook

Scope

• Please indicate which category or categories. Check out our package scope page to learn more about our scope. (If you are unsure of which category you fit, we suggest you make a pre-submission inquiry):

  • [ ] Data retrieval
  • [ ] Data extraction
  • [ ] Data processing/munging
  • [ ] Data deposition
  • [ ] Data validation and testing
  • [x] Data visualization
  • [ ] Workflow automation
  • [ ] Citation management and bibliometrics
  • [ ] Scientific software wrappers
  • [ ] Database interoperability

Domain Specific & Community Partnerships

- [x] Geospatial
- [ ] Education
- [ ] Pangeo
- [ ] Unsure/Other (explain below)

• Explain how and why the package falls under these categories (briefly, 1-2 sentences). Please note any areas you are unsure of:

EOmaps can be used to visualize geospatial datasets provided in any projection supported by PyProj.

I am unsure if Pangeo is applicable or not (I have no experience with the pangeo community so far)

• Who is the target audience and what are the scientific applications of this package?

The target audience are scientists and researchers working with geospatial datasets. EOmaps can be used to quilkly visualize datasets, compare multiple datasets with each other or compare maps to an extensive list of open access webmap services.

In addition to the interactive capabilities, maps created with EOmaps can be exported as high-resolution images or vector-graphics to create publication-ready plots.

Since EOmaps is based on matplotlib, maps can be connected to ordinary matplotlib axes to analyze multi-dimensional (e.g. timeseries) data.

It also has great potential to be used in education to teach about projections, distortions, spatial resolution, rasterization of data etc.

• Are there other Python packages that accomplish similar things? If so, how does yours differ?

EOmaps is based on cartopy. While cartopy provides similar functionalities in terms of data visualization, EOmaps greatly extends these capabilities (especially for large datasets), adds multi-layer support, a basic GUI, easy-access to webmaps, and many more features.

There exist other packages that focus on interactive geo-data visualization, but to my knowledge none that focusses on local use in pure python.

• folium (wrapper for javascript-library leaflet)

• geemap (wrapper for google-earth-engine)

• geoviews - provides an api for matplotlib, but it is a much more high-level plotting library than EOmaps

• Any other questions or issues we should be aware of:

P.S. Have feedback/comments about our review process? Leave a comment here

[NickleDave]

Hi @raphaelquast and welcome to pyOpenSci. Thank you for opening this detailed presubmission issue.

EOmaps is definitely in scope for pyOpenSci.
To be extra sure I discussed with our executive director @lwasser, and she agreed this dataviz package is in scope under the description in our guide here: https://www.pyopensci.org/software-peer-review/about/package-scope.html#what-if-my-package-seems-like-its-category-or-domain-is-out-of-scope

Just to make sure you see it, the checklist we start reviews with is here: https://www.pyopensci.org/software-peer-review/our-process/review-timeline.html#step-0-optional-author-submits-pre-submission-inquiry I have already done most of the initial checks and do not expect those to be an issue.

Please proceed with a full submission, and be sure to reference this issue by number when you do.

[raphaelquast]

@NickleDave Thank you very much for your quick response. ... and I am glad to hear that EOmaps fits into the scope of pyOpenSci!

I had a look at the checklist and I agree that most points should already be fulfilled. (I'll try to add a contributing.md file in the next minor release and implement an issue template as soon as possible)

I'll proceed with a proper submission and I'm very much looking forward to your insights and comments on the package!

[NickleDave]

I had a look at the checklist and I agree that most points should already be fulfilled. (I'll try to add a contributing.md file in the next minor release and implement an issue template as soon as possible)

Great, yes we will need those before we can start the review.

I'll proceed with a proper submission and I'm very much looking forward to your insights and comments on the package!

Excellent, I saw you did so. We are looking for an editor now. And we're looking forward to the review, thanks!

[raphaelquast]

I just put this here for reference... I've added all missing points so the checklist should now be complete!

• CONTRIBUTING.md file is now added (here) and will be part of the upcoming release (EOmaps v7.1.2)
• Issue templates for "bug reports" and "feature requests" are implemented