geospatial-data
Here are 214 public repositories matching this topic...
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?
In the event payload the return type of layer is `L.Layer? so it needs to be casted to the Layer-Type.
layer.on('pm:edit', (e) => {
if(e.shape === 'Polygon'){
(e.layer as Polygon).getLatLngs();
}
});
I think following should work too: (But not tested)
layer.on('pm:edit', (e) => {
if(e.layer instanceof L.Polygon){
(e.layer as Polygon).getLatLngs();
}
It would be great to mention this in the relevant chapter: https://github.com/walkerke/crsuggest
Specifically it would fit perfectly here: https://geocompr.robinlovelace.net/reproj-geo-data.html#which-crs-to-use
Heads-up @walkerke, awesome package, let me know if you've any comments/suggestions on describing the package and thanks for developing it!
-
Updated
Sep 13, 2021 - Python
-
Updated
Dec 3, 2021 - HTML
-
Updated
Nov 8, 2019 - Jupyter Notebook
-
Updated
Dec 22, 2021
-
Updated
Jul 25, 2019 - Jupyter Notebook
-
Updated
Nov 16, 2021 - TypeScript
-
Updated
Dec 16, 2021 - Java
-
Updated
Dec 24, 2021 - Python
-
Updated
Feb 19, 2021 - Jupyter Notebook
-
Updated
Dec 22, 2021 - Java
-
Updated
Dec 21, 2021 - Julia
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
-
Updated
Aug 31, 2019
-
Updated
Nov 15, 2019 - C
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.
Steps to reproduce the probl
-
Updated
Jan 21, 2020 - Jupyter Notebook
-
Updated
Sep 23, 2021 - Python
-
Updated
Mar 10, 2021
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
-
Updated
Jun 10, 2021 - JavaScript
-
Updated
Dec 23, 2021 - Jupyter Notebook
-
Updated
Dec 6, 2021 - Python
Linux .deb installer
Investigate how to build a .deb installer.
Improve this page
Add a description, image, and links to the geospatial-data topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the geospatial-data topic, visit your repo's landing page and select "manage topics."

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