- Notifications
You must be signed in to change notification settings - Fork 36
Description
Submitting Author: Raphael Quast (@raphaelquast)
All current maintainers: @raphaelquast
Package Name: EOmaps
One-Line Description of Package: EOmaps is a python package to visualize, analyze and compare geographical datasets.
Repository Link: https://github.com/raphaelquast/EOmaps
Version submitted: 7.3
Editor: @banesullivan
Reviewer 1: @yeelauren
Reviewer 2: @jhkennedy
Archive:
Version accepted: 8.0.2
Date accepted (month/day/year): 03/14/2024
Code of Conduct & Commitment to Maintain Package
- I agree to abide by pyOpenSci's Code of Conduct during the review process and in maintaining my package after should it be accepted.
- I have read and will commit to package maintenance after the review as per the pyOpenSci Policies Guidelines.
Description
EOmaps is a python package to visualize, analyze and compare 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
- A flexible API to quickly turn the maps into fully customizable interactive data-analysis widgets
- ...and many more features...
It is extensively documented, unit-tested, citable via a zenodo 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)
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
- Data visualization1
- Workflow automation
- Citation management and bibliometrics
- Scientific software wrappers
- Database interoperability
Domain Specific & Community Partnerships
- [x] Geospatial - [ ] Education - [ ] Pangeo
Community Partnerships
If your package is associated with an
existing community please check below:
- Pangeo
- My package adheres to the Pangeo standards listed in the pyOpenSci peer review guidebook
-
For all submissions, explain how the and why the package falls under the categories you indicated above. In your explanation, please address the following points (briefly, 1-2 sentences for each):
-
Who is the target audience and what are scientific applications of this package?
The target audience for EOmaps are scientists and researchers working with geospatial datasets.
EOmaps can be used to quilkly visualize structured (or unstructured) geo-spatial datasets, compare multiple datasets with each other or compare maps to an extensive list of open access webmap services. Since EOmaps is based on matplotlib, the created maps can also be connected to ordinary matplotlib axes to analyze multi-dimensional (e.g. timeseries) data.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.
Finally, I believe that EOmaps also has great potential to be used in education to teach about projections, distortions, spatial resolution, rasterization of data, the subtleties of big-data visualization etc.
-
Are there other Python packages that accomplish the same thing? 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)
-
If you made a pre-submission enquiry, please paste the link to the corresponding issue, forum post, or other discussion, or
@tag
the editor you contacted:
-
Technical checks
For details about the pyOpenSci packaging requirements, see our packaging guide. Confirm each of the following by checking the box. This package:
- does not violate the Terms of Service of any service it interacts with.
- uses an OSI approved license.
- contains a README with instructions for installing the development version.
- includes documentation with examples for all functions.
- contains a tutorial with examples of its essential functions and uses.
- has a test suite.
- has continuous integration setup, such as GitHub Actions CircleCI, and/or others.
Publication Options
- Do you wish to automatically submit to the Journal of Open Source Software? If so:
JOSS Checks
- The package has an obvious research application according to JOSS's definition in their submission requirements. Be aware that completing the pyOpenSci review process does not guarantee acceptance to JOSS. Be sure to read their submission requirements (linked above) if you are interested in submitting to JOSS.
- The package is not a "minor utility" as defined by JOSS's submission requirements: "Minor ‘utility’ packages, including ‘thin’ API clients, are not acceptable." pyOpenSci welcomes these packages under "Data Retrieval", but JOSS has slightly different criteria.
- The package contains a
paper.md
matching JOSS's requirements with a high-level description in the package root or ininst/
. - The package is deposited in a long-term repository with the DOI:
Note: JOSS accepts our review as theirs. You will NOT need to go through another full review. JOSS will only review your paper.md file. Be sure to link to this pyOpenSci issue when a JOSS issue is opened for your package. Also be sure to tell the JOSS editor that this is a pyOpenSci reviewed package once you reach this step.
Are you OK with Reviewers Submitting Issues and/or pull requests to your Repo Directly?
This option will allow reviewers to open smaller issues that can then be linked to PR's rather than submitting a more dense text based review. It will also allow you to demonstrate addressing the issue via PR links.
- Yes I am OK with reviewers submitting requested changes as issues to my repo. Reviewers will then link to the issues in their submitted review.
Confirm each of the following by checking the box.
- I have read the author guide.
- I expect to maintain this package for at least 2 years and can help find a replacement for the maintainer (team) if needed.
Please fill out our survey
- Last but not least please fill out our pre-review survey. This helps us track
submission and improve our peer review process. We will also ask our reviewers
and editors to fill this out.
P.S. Have feedback/comments about our review process? Leave a comment here
Editor and Review Templates
The editor template can be found here.
The review template can be found here.
Footnotes
-
Please fill out a pre-submission inquiry before submitting a data visualization package. ↩
Metadata
Metadata
Assignees
Labels
Type
Projects
Status