Skip to content
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

941 review gis chapter #942

Merged
merged 10 commits into from
Mar 24, 2023
Merged

941 review gis chapter #942

merged 10 commits into from
Mar 24, 2023

Conversation

Robinlovelace
Copy link
Collaborator

No description provided.

@Robinlovelace Robinlovelace linked an issue Mar 24, 2023 that may be closed by this pull request
10-gis.Rmd Outdated
You *can* interact with QGIS\index{QGIS}, SAGA\index{SAGA}, GRASS\index{GRASS} and gvSIG from system terminals and embedded CLIs\index{command-line interface}, but 'pointing and clicking' is the norm.
This means many GIS\index{GIS} users miss out on the advantages of the command-line according to Gary Sherman, creator of QGIS\index{QGIS} [@sherman_desktop_2008]:
A defining feature of [interpreted](https://en.wikipedia.org/wiki/Interpreter_(computing)) languages with an interactive console --- technically a read-eval-print loop (REPL) --- such as R is the way you interact with them:
rather than relaying on a pointing and clicking on different parts of a screen, you type commands into the console and hit `Enter` each time you want a command to be executed.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you mean: rather than relying on pointing and clicking?
I would also change the end of the sentence to: each time you want to execute a command.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

In other words, R is typically controlled by a command-line interface (CLI)\index{command-line interface}.

CLIs are not unique to R: most early computing environments relied on a command line 'shell' and it was only after the invention and widespread adoption of the computer mouse in the 1990s that graphical user interfaces (GUIs)\index{graphical user interface} became common.
GRASS the longest-standing continuously-developed open source GIS\index{GIS} software, for example, relied on its command-line interface before it gained a GUI [@landa_new_2008].
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, they celebrate their 40th anniversary this year in Prague which is amazing!!

10-gis.Rmd Outdated
- Has a 'shallow' learning curve meaning geographic data can be explored and visualized without hours of learning a new language
- Provides excellent support for 'digitizing' (creating new vector datasets), including trace, snap and topological tools^[
The **mapedit** package allows the quick editing of a few spatial features but not professional, large-scale cartographic digitizing.
'CLI vs GUI' debate does not have to be adverserial: both have advantages.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 'CLI vs GUI' debate

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

10-gis.Rmd Outdated
'CLI vs GUI' debate does not have to be adverserial: both have advantages.
Which is most appropriate depends on a range of factors including the task (with drawing new features being well-suited to GUIs), the level of reproducibility desired, and the user's skillset.
GRASS is a good example of GIS software that is primarily based on a CLI but which also has a prominent GUI.
Likewise, while R is focussed on its CLI, IDEs such as RStudio provide a GUI for improving accessibility.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we use "focused" throughout the book since it is the AE spelling.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorted now.

Copy link
Collaborator

@jannes-m jannes-m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @Robinlovelace, excellent rewrite!

@Robinlovelace
Copy link
Collaborator Author

Thanks Jannes, great comments! Crazy thing, in Codespaces I can see your comments inline:

image

@Robinlovelace Robinlovelace merged commit 8afab30 into main Mar 24, 2023
@Robinlovelace Robinlovelace deleted the 941-review-gis-chapter branch March 24, 2023 22:42
@jannes-m
Copy link
Collaborator

Wow, one day I have to try codespace as well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Review GIS chapter
2 participants