[PRE REVIEW]: EOWater: A Google Earth Engine-based efficient water monitoring tool

[editorialbot]

Submitting author: @ShiruiH (Shirui Hao)
Repository: https://github.com/ShiruiH/EOWater
Branch with paper.md (empty if default branch):
Version: v0
Editor: Pending
Reviewers: Pending
Managing EiC: Kristen Thyng

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/10250bd8f2fb9ce6b83d1b36aaab55ae"><img src="https://joss.theoj.org/papers/10250bd8f2fb9ce6b83d1b36aaab55ae/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/10250bd8f2fb9ce6b83d1b36aaab55ae/status.svg)](https://joss.theoj.org/papers/10250bd8f2fb9ce6b83d1b36aaab55ae)

Author instructions

Thanks for submitting your paper to JOSS @ShiruiH. Currently, there isn't a JOSS editor assigned to your paper.

@ShiruiH if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.

Editor instructions

The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:

@editorialbot commands

[editorialbot]

Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

✅ OK DOIs

- 10.1016/j.envsoft.2021.105095 is OK
- 10.3390/rs13183681 is OK
- 10.1038/s41598-022-17074-6 is OK
- 10.1080/01431160600589179 is OK
- 10.1109/TSMC.1979.4310076 is OK
- 10.1007/s10584-013-0853-x is OK
- 10.1016/j.envsoft.2024.106257 is OK
- 10.1016/j.rse.2017.06.031 is OK

🟡 SKIP DOIs

- None

❌ MISSING DOIs

- None

❌ INVALID DOIs

- None

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.98  T=0.58 s (46.4 files/s, 396308.0 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
CSV                              6              0              0         171005
HTML                             1           7470              0          19931
JavaScript                       7            238            237            710
Jupyter Notebook                 5              0          28963            604
Python                           2            140            137            449
Markdown                         2            110              0            230
JSON                             2              0              0            130
TeX                              1              7              0             85
YAML                             1              1              4             35
-------------------------------------------------------------------------------
SUM:                            27           7966          29341         193179
-------------------------------------------------------------------------------

Commit count by author:

    46	Kilian Vos
    42	Shirui Hao
     6	Shirui

[editorialbot]

Paper file info:

📄 Wordcount for paper.md is 2243

✅ The paper includes a Statement of need section

[editorialbot]

License info:

🟡 License found: GNU General Public License v3.0 (Check here for OSI approval)

[editorialbot]

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

[editorialbot]

Five most similar historical JOSS papers:

Geodata-Harvester: A Python package to jumpstart geospatial data extraction and analysis
Submitting author: @sebhaan
Handling editor: @hugoledoux (Active)
Reviewers: @lukasbeuster, @martibosch
Similarity score: 0.6782

WDPM: the Wetland DEM Ponding Model
Submitting author: @KevinShook
Handling editor: @kbarnhart (Retired)
Reviewers: @r-barnes, @awickert, @KCallaghan
Similarity score: 0.6757

GeoClimate: a Geospatial processing toolbox for environmental and climate studies
Submitting author: @ebocher
Handling editor: @elbeejay (Active)
Reviewers: @abhishekvp, @omshinde, @arbennett
Similarity score: 0.6662

pyveg: A Python package for analysing the time evolution of patterned vegetation using Google Earth Engine
Submitting author: @samvanstroud
Handling editor: @usethedata (Retired)
Reviewers: @arbennett, @usethedata
Similarity score: 0.6530

rgee: An R package for interacting with Google Earth Engine
Submitting author: @csaybar
Handling editor: @hugoledoux (Active)
Reviewers: @appelmar, @gena, @jhollist
Similarity score: 0.6495

⚠️ Note to editors: If these papers look like they might be a good match, click through to the review issue for that paper and invite one or more of the authors before considering asking the reviewers of these papers to review again for JOSS.

[kthyng]

Hi @ShiruiH and thanks for your submission! I am looking for some specific items to make sure your submission fits our requirements at a high level (not at the more detailed review level) before moving on to finding an editor or putting this on our waitlist if no relevant editors are available. I'll comment over time as I have a chance to go through them:

• OSI-approved license
• Installation instructions
• Documentation exists at all
• Tests of some sort
• Check paper (make sure compiles, read through, check for length 250-1000 words)
• Substantial scholarly effort
• Clear research application

In the meantime, please take a look at the comments above ⬆️ from the editorialbot to address any DOI, license, or paper issues if you're able (there may not be any), or suggest reviewers. For reviewers, please suggest 5 reviewers from the database listed above or your own (non-conflicted) extended network. Their github handles are most useful to receive but please don't use "@" to reference them since it will prematurely ping them.

[kthyng]

@ShiruiH 👋

• Do you have docs besides the readme?
• Is something stopping you from releasing this on PyPI or conda-forge?
• How do you or would a user verify your code is working correctly?

Thanks!