grass
grass copied to clipboard
OSGeo
GRASS GIS - free and open-source geospatial processing engine
**Describe the bug** g.gui.timeline doesn't display anything, originally reported by @chaedri **To Reproduce** t.create output=test semantictype=mean title=title description=desc t.register -i input=test maps=elev_lid792_1m@PERMANENT,elev_state_500m@PERMANENT start=2000-01-01 increment="1 month" g.gui.timeline test ``` Traceback (most...
The temporal neighbourhood modifier states `The format is strds[t,r,c], where t is the temporal offset, r is the row offset and c is the column offset` but never explicitly states...
This seems to solve issue #3420
Another bug coming from using global variables in r.horizon. Reported by a user, can be reproduced with https://www.datigeo-piem-download.it/static/regp01/DTM5_ICE/RIPRESA_AEREA_ICE_2009_2011_DTM-SDO_CTR_FOGLI50-172-EPSG32632-TIF.zip: ``` r.horizon elevation=DTM5_172 direction=0 step=1 coordinates=350089,4979561 -d file=horizon.csv ``` The bug is...
This PR addresses https://github.com/OSGeo/grass/issues/3105. It implements a new `plot_point()` function that uses the internal `state` in `dense_line.c`. Calling `G_plot_point()` with `-d` flag causes a segfault because the static `state` in...
https://github.com/OSGeo/grass/blob/656add71cfc681c352ae2a23ec1d7c29b37c958f/raster/r.latlong/main.c#L3 `r.latlong` uses grid cell edges (west, north), not centers, at least when using it in `EPSG:4326` projection. This seems like a bug. If it isn't a bug, it seems...
**To Reproduce** Steps to reproduce the behavior: 1. Run `g.proj -w` as a command line utility or using Python: `gs.start_command + gs.communicate` / `gs.read_command`. 2. Run the same command but...
**Describe the bug** When processing the vector map one of backend commands (seems to be v.reclass) change the database table name to map_somenumbersandchars (example map_ef0691c223f2_631@PERMANENT), after that following command (v.extract)...
**Describe the bug** The target to build `libgrass_gis.8.4.so` is allowed to run even without `libgrass_datetime.8.4.so` built yet. Probably all the other core libraries too, but I found a seed for...
The issue is reproduceable, reason unknown. At the moment just taking a note, will look into this at some point later. ``` #0 0x0000000000000000 in ?? () #1 0x00007ffff7ede221 in...
