geospatial-data

The gdal/swig/python/samples/ogr_layer_algebra.py should be promoted to an official Python script

Steps:

• move it to gdal/swig/python/scripts
• create a new test script for it in autotest/pyscripts/test_ogr_layer_algebra.py
• write a documentation page in doc/source/programs/ogr_layer_algebra (and link it to the index)

Is there a way to know when the imagery was collected? I assume sometime in the daylight hours, and probably recently(?) but I have no way of knowing by looking at the output and the associated image.

Can that output be put in the CLI output or some other metadata file that gets associated with the LC####### directory?

This is a ToDo-Issue.

Following events should be added:

• while moving the hintMarker a event should be fired like move or change. For example, while drawing the rectangle, the current bounds / latlngs can be useful. see #1072
• While moveing / editing the coords of a layer, we can send a coordsmove event. Edit, Drag, Rotation, ...
• Enabledrag & disabledrag in Dragging.js

As shown in screenshot below.

Source: https://geocompr.robinlovelace.net/read-write.html#iovec

In episode _episodes_rmd/12-time-series-raster.Rmd

There is a big chunk of code that can probably be made to look nicer via dplyr:

# Plot RGB data for Julian day 133
 RGB_133 <- stack("data/NEON-DS-Landsat-NDVI/HARV/2011/RGB/133_HARV_landRGB.tif")
 RGB_133_df <- raster::as.data.frame(RGB_133, xy = TRUE)
 quantiles = c(0.02, 0.98)
 r <- quantile(RGB_133_df$X133_HARV_landRGB.1, q

Expected behavior and actual behavior

Cropping any raster with any GeoVector should work. Instead, if the GeoVector is bigger than the world, an error is raised.

simple_world.geojson.zip

Steps to reproduce the probl

It'd be great if by default geospatial plots did not truncate axis ticks.

In the meantime, there is an easy one liner to change a setting to display axis ticks without truncation: plt.ticklabel_format(style="plain")

I only found out about this later

Lines L315:L325 in Lesson 5 advocate for subsetting columns without comma notation:

head(gapminder[3])

I'd argue that for clarity sake, we should change this to always use comma notation:

head(gapminder[,3]

See #86

It would be very useful to create a template for the schedule of a geospatial workshop to be used in the workshop website. This schedule should be added to this file: https://github.com/carpentries/workshop-template/blob/gh-pages/_includes/dc/schedule.html