EarthPy: Software Submission for Review

[lwasser]

Submitting Author: Leah Wasser (@lwasser)
All current maintainers: (@lwasser, @nkorinek, @mbjoseph, @joemcglinchy, @jlpalomino)
Package Name: earthpy
One-Line Description of Package: A package built to support working with spatial data using open source python
Repository Link: https://github.com/earthlab/earthpy
Version submitted: 0.7
Editor: @luizirber
Reviewer 1: @HaoZeke
Reviewer 2: @sgillies
Archive:
JOSS DOI:
Version accepted: v 0.7.5
Date accepted (month/day/year): 11/06/2019

---

• Paste the full DESCRIPTION file inside a code block below:

Python is a generic programming language designed to support many different applications. Because of this, many commonly performed spatial tasks for science including plotting and working with spatial data take many steps of code. EarthPy takes advantage of functionality developed for raster data (rasterio) and vector data (geopandas) and simplifies the code needed to :

    Stack raster bands from data such as Landsat into an easy to use numpy array
    Work with masks to set bad pixels such a those covered by clouds and cloud-shadows to NA (mask_pixels())
    Plot rgb (color), color infrared and other 3 band combination images (plot_rgb())
    View histograms of sets of raster
    Create discrete (categorical) legends

EarthPy also has an io module that allows users to

    Quickly access pre-created datasubsets used in the earth-analytics courses hosted on www.earthdatascience.org
    Download other datasets that they may want to use in their workflows.

Scope

• Please indicate which category or categories this package falls under:
  • Data retrieval
  • Data extraction
  • Data munging
  • Data deposition
  • Reproducibility
  • Geospatial
  • Education
  • Data visualization*

* Please fill out a pre-submission inquiry before submitting a data visualization package. For more info, see this section of our guidebook.

• Explain how the and why the package falls under these categories (briefly, 1-2 sentences):
  This package wraps around rasterio and geopandas to make working with geospatial data easier.

• Who is the target audience and what are scientific applications of this package?
  The target audience is people working with different types of raster and vector data in python. There are many operations that are often repeated by users that require a lot of code. This package simplifies these operations so users can quickly explore their data.

• Are there other Python packages that accomplish the same thing? If so, how does yours differ?
  Not that we know of! this is why we created this package.

• 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.
• has an OSI approved license
• contains a README with instructions for installing the development version.
• includes documentation with examples for all functions.
• contains a vignette with examples of its essential functions and uses.
• has a test suite.
• has continuous integration, such as Travis CI, AppVeyor, 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 in inst/.
• The package is deposited in a long-term repository with the DOI:

Note: Do not submit your package separately to JOSS

Code of conduct

• I agree to abide by pyOpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

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

NOTE: I am actually not sure what research application means according to Joss!! may followup with Arfon on this.

[lwasser]

@luizirber as the editor for this package, will you please ping the reviewers and give them a 3 week deadline to perform the review?

[luizirber]

Editor checks:

• Fit: The package meets criteria for fit and overlap.
• Automated tests: Package has a testing suite and is tested via Travis-CI or another CI service.
  • Travis and AppVeyor
• License: The package has an OSI accepted license
  • yes, BSD 3-Clause
• Repository: The repository link resolves correctly
• Archive (JOSS only, may be post-review): The repository DOI resolves correctly
• Version (JOSS only, may be post-review): Does the release version given match the GitHub release (v1.0.0)?

---

Editor comments

---

Reviewer: @HaoZeke
Reviewer: @sgillies
Due date: 2019-10-25

[luizirber]

@lwasser I don't have permission to change labels in this issue, but ready for review (past editor checks and reviewer assignment)

[lwasser]

@luizirber !! i Just made you an admin for this repo so you should have permissions now. Please let me know if you don't!! And thank you for letting me know and for being willing to serve as an editor!!

[luizirber]

Hi @kysolvik and @carsonfarmer! Anything I can do to help you with your reviews? Next steps are:

• Post this template in a comment here: https://www.pyopensci.org/dev_guide/appendices/templates#review-template
• Follow the template and https://www.pyopensci.org/dev_guide/peer_review/reviewer_guide.html for you review.

[lwasser]

our docs are building again too - yay! they were down due to a RTD issue. thank you @luizirber

[lwasser]

hey guys @carsonfarmer @luizirber -- wanted to followup on here. @kysolvik pointed out that there is a potential conflict of interest here given Kylen has worked for me and i'm not sure if that would apply with @carsonfarmer as well given we were both a part of earth lab for some time. we may need to reassign reviewers. @luizirber i tried to ping you on slack but am not sure if you saw it! just want to ensure this review moves forward given we definitely need to swap out atleast one reviewer!! i was wondering if @leouieda could do it instead of @kysolvik and kylen could do one of martin's submissions as one idea. but very open to thoughts.