Access nominatim via osmdata and drop nominatimlite

[cforgaci]

This commit replaces nominatimlite::geo_lite_sf() with osmdata::getbb(). The former creates an issue with the workshop website deployment (error when calling nominatimlite::geo_lite_sf()) and adds a dependency that might not be needed.

@ClementineCttn, to me, it looks like getbb() leads to the same results, but maybe you tested this on other cities and it does not always work. It would be great if we could stick to getbb() from a deployment perspective. Let me know if you agree by responding to this PR.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/r-geospatial-urban/compare/md-outputs..md-outputs-PR-31

The following changes were observed in the rendered markdown documents:

 18-import-and-visualise-osm-data.md | 11 ++---------
 md5sum.txt                          |  2 +-
 2 files changed, 3 insertions(+), 10 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2024-05-17 16:10:00 +0000