-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review #2
Review #2
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
@@ -38,6 +38,9 @@ | |||
"\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line #4. study_poly = Polygon(zip(lon_points, lat_points))
Then here we would have:
tudy_poly = Polygon(study_bbox_coordinates)
Reply via ReviewNB
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edited to correspond to new construction of bbox coordinates
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closing conversation, resolved
@@ -38,6 +38,9 @@ | |||
"\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The paths are not correct (also in the text above). We should have
general-exploration-landcover_io
instead of
general-exploration-landcover
Reply via ReviewNB
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry this was my bad. I changed the name of the project folder to general-exploration-landcover_io
without veryfing where else it's used. I'll sort this issue out as part of pending task for the editor. Thanks @annefou
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, fixed now see commit 9ab8466. For reproducibility, I'd suggest to use os.path.join
to call the existing notebook_folder
variable. For instance, change lcxr.to_netcdf("general-exploration-landcover/MT-study-area.nc")
to lcxr.to_netcdf(os.path.join(notebook_folder,"MT-study-area.nc"))
. How does it sound @jamesdamillington? Same for other cells using notebook_folder
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I agree @acocac, os.path.join
is better. I have edited in the code and in the markdown.
I have also added decode_coords="all"
to the xarray.open_dataset
call to ensure CRS info is read back in correctly which it wasn't previously.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closing conversation, resolved
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:33Z To match the format of the other notebooks’ headings (see examples in the Exploration theme), I would suggest: 1. Adding the mention of the dataset used (Impact Observatory) in the ‘Purpose’ section 2. Renaming the ‘Dataset description’ section ‘Sensor description’ and detail the characteristics of the Impact Observatory dataset 3. Renaming the ‘Dataset’ section ‘Dataset originator/creator’ 4. Adding a section ‘Dataset reference and documentation’ (e.g. using this document) 5. Adding a note on the creative license jamesdamillington commented on 2022-09-09T11:22:11Z Thanks for these useful suggestions. I have added information as suggested (although I am not sure 'Sensor description' is entirely appropriate as really the content describes datasets/products derived from sensors). For dataset reference and documentation I have added a peer review paper in addition to the technical document highlighted. acocac commented on 2022-09-20T09:54:46Z @jamesdamillington you're right dataset is the correct term for your notebook. We'll change it during the typesetting process if that's ok for you.
TODO in the typesetting (post-print) stage |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:34Z Line #5. km2deg = 1.0 / 111 I am not sure but it would maybe help clarify this part if a comment on where the number '111' comes from is added (e.g. 1 deg corresponds to approximately 111 m at the equator) jamesdamillington commented on 2022-09-09T12:19:24Z Yes, good idea. I have added this comment (with 111 km) acocac commented on 2022-09-21T16:30:14Z closing conversation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:35Z Here, I would maybe suggest adding a line interpreting this graph (e.g. 'we can see the whole study area represented by the red rectangle is included in the datasets queried represented by the blue rectangles') jamesdamillington commented on 2022-09-09T12:19:32Z Yes, I agree this would be useful. I have also added text prior to this to explain each dataset is for a tile of the earth's surface. acocac commented on 2022-09-21T16:33:27Z closing conversation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:36Z Just a thought: maybe it could be nice to duplicate the graphs that have been produced below for pixel counts for 'estimated area' as well using the 300 m res? jamesdamillington commented on 2022-09-10T09:20:23Z This is a good point, in that it is likely more intuitive to work in area rather than pixel counts. Duplicating the graphs seemed repetitive so instead I have changed the original graph to have units of area. acocac commented on 2022-09-21T16:35:02Z closing conversation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:36Z Same here as in 3: it might be interesting to add the visualisation in terms of area? jamesdamillington commented on 2022-09-10T09:20:31Z I have changed the sankey to show the transitions as units of area rather than cell counts. In the subsequent table, I now show both cell counts and area acocac commented on 2022-09-21T16:36:13Z closing conversation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:37Z
jamesdamillington commented on 2022-09-09T12:19:43Z Thanks, I have made these edits. NHomer-Edi commented on 2022-09-21T16:34:29Z closing conversation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:38Z Line #14. axes.set_xlabel('x [metre]'), axes.set_ylabel('y [metre]') To add labels for axes? jamesdamillington commented on 2022-09-09T12:19:48Z Thanks. I have added these labels NHomer-Edi commented on 2022-09-21T16:35:13Z closing converstation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:39Z Line #13. sa_munis_xr = xr.DataArray(data=sa_munis_r, name='Municipality code' Suggestion to understand the colorbar in the next plot better jamesdamillington commented on 2022-09-09T12:19:52Z Thanks, I have added this NHomer-Edi commented on 2022-09-21T16:35:41Z closing converstation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:40Z Line #18. ax[ix].set_xlabel('x [metre]'), ax[ix].set_ylabel('y [metre]') To add labels for axes? jamesdamillington commented on 2022-09-09T12:19:56Z Thanks. I have added these labels NHomer-Edi commented on 2022-09-21T16:36:00Z closing converstation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:40Z Line #18. ax[ix].set_xlabel('x [metre]'), ax[ix].set_ylabel('y [metre]')
To add labels for axes? jamesdamillington commented on 2022-09-09T12:20:00Z Thanks. I have added these labels NHomer-Edi commented on 2022-09-21T16:36:19Z closing converstation, resolved |
View / edit / reply to this conversation on ReviewNB aedebus commented on 2022-08-24T17:52:41Z Details of the dataset version to add here in 'Dataset' jamesdamillington commented on 2022-09-10T09:29:51Z Thanks, this is now added aedebus commented on 2022-09-19T14:46:13Z There is a small typo here with an extra " acocac commented on 2022-09-20T10:18:48Z TODO in the typesetting stage. |
cm-template-review-checklist)= Review Checklist Template:::{note} Review Checklist : First review, @aedebus, 24-08-2022Code of conduct
General checks
Reproducibility
Pedagogy
Ethical
Other Requirements
AOB |
@aedebus thanks for the first review 👍 Can you confirm if it is ready for its revision from the author @jamesdamillington? |
@annefou, a friendly reminder that the deadline for first reviews is Thursday, September 8th. Where possible can you also use the suggested checklist template and confirm when your review is ready. Thank you 🙏 |
@acocac @jamesdamillington I can confirm my review is ready for revision ✅ |
I am working on it. |
View / edit / reply to this conversation on ReviewNB annefou commented on 2022-09-01T09:30:26Z Line #7. bbox=study_bbox
study_bbox is not defined anymore. We should have:
bbox=study_poly.bounds jamesdamillington commented on 2022-09-09T12:20:17Z Yes, thanks I have fixed this and elsewhere NHomer-Edi commented on 2022-09-21T16:30:57Z closing conversation, resolved |
Thanks, this is now added View entire conversation on ReviewNB |
@acocac I think I have now responded to all reviewer comments in review round 1 |
@jamesdamillington thanks for going through each of reviewers comments! Please @annefou @aedebus can you confirm if you're happy with all replies to your suggestions/comments. Feel free to reply each comment and/or update the checklist accordingly. |
I am happy with the updated notebook. I think it is great and on my side ready to be merged. Thanks. |
There is a small typo here with an extra " View entire conversation on ReviewNB |
@jamesdamillington Thank you for implementing the changes. I have noticed a small typo and commented accordingly, but everything looks good to me otherwise. @acocac I can confirm that other than this minor detail, it looks ready to be merged from my end too. |
jamesdamillington you're right dataset is the correct term for your notebook. We'll change it during the typesetting process if that's ok for you. View entire conversation on ReviewNB |
@annefou this is an error in ReviewNB, the version in Binder only has a single colormap plotted. View entire conversation on ReviewNB |
TODO in the typesetting stage. View entire conversation on ReviewNB |
@annefou thanks for recommending to merge the notebook and move to the post-print stage. |
@aedebus thanks for confirming all is ok! The minor typos will be addressed in the post-print stage. |
Great! Thanks all. Do I need to do anything now? |
@jamesdamillington. You don't need to anything now. The notebook is good to go -- thanks to you and reviewers! Next steps:
|
closing conversation, resolved View entire conversation on ReviewNB |
6 similar comments
closing conversation, resolved View entire conversation on ReviewNB |
closing conversation, resolved View entire conversation on ReviewNB |
closing conversation, resolved View entire conversation on ReviewNB |
closing conversation, resolved View entire conversation on ReviewNB |
closing conversation, resolved View entire conversation on ReviewNB |
closing conversation, resolved View entire conversation on ReviewNB |
closing converstation, resolved View entire conversation on ReviewNB |
closing conversation, resolved View entire conversation on ReviewNB |
1 similar comment
closing conversation, resolved View entire conversation on ReviewNB |
closing converstation, resolved View entire conversation on ReviewNB |
1 similar comment
closing converstation, resolved View entire conversation on ReviewNB |
closing conversation, resolved View entire conversation on ReviewNB |
closing converstation, resolved View entire conversation on ReviewNB |
Notebook Review: Issue#99
Notebook Name: Exploring Land Cover Data (Impact Observatory)
Submitting Author: @jamesdamillington
Reviewers: @annefou @aedebus
Moderators: @acocac @NHomer-Edi
Pull Request: PR#110
Reviewer instructions & questions
@annefou @aedebus, please carry out your review in this PR by using the checklist template below (available for copy and paste here).
Any questions, concerns or suggestions regarding the review process contact the editor.
✨ Please start on your review when you are able, and be sure to complete your review within the next four weeks, thank you! ✨
Review Checklist
Code of conduct
General checks
Reproducibility
Pedagogy
Ethical
Other Requirements
AOB
Please use the ReviewNB to submit your reviews on the notebook. ReviewNB is a third-party plugin in GitHub for displaying Jupyter Notebook content.
In addition to ReviewNB, we suggest to explore or run the notebook in: