neteler
November 4, 2024, 10:41pm
1
Hi devs,
we are past the planned release date for the upcoming 8.4.1 release.
Remaining for the 8.4.1 milestone are (currently) 10 open pull
requests (PRs) that still need to be tested, reviewed or moved:
https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.4.1
This is the 8.4.1 milestone (open issues and pull requests):
Let's review what should be in 8.4.1 and what should be postponed.
Opinions (or actions on the PRs) are welcome.
Best,
Markus
--
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page
Markus and Devs.
Until db.in.ogr is updated along the lines of #4593 , I would like to add (or have someone add) info to the manual to tell users to simply add
gdal_doo=AUTODETECT_TYPE=YES
to enable csv input to be parsed correctly, automatically. Users can still use a csvt file if they want to have more detailed and direct control over how data columns are read. But this workaround will work well for most users.
Michael
Michael Barton
On Nov 4, 2024, at 3:54 PM, Markus Neteler via OSGeo Discourse noreply@discourse.osgeo.org wrote:
Hi devs,
we are past the planned release date for the upcoming 8.4.1 release.
Remaining for the 8.4.1 milestone are (currently) 10 open pull
requests (PRs) that still need to be tested, reviewed or moved:
https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.4.1
This is the 8.4.1 milestone (open issues and pull requests):
GitHub
GRASS GIS - free and open-source geospatial processing engine - 8.4.1 Milestone · OSGeo/grass
Let’s review what should be in 8.4.1 and what should be postponed.
Opinions (or actions on the PRs) are welcome.
Best,
Markus
–
Markus Neteler, PhD
https://www.mundialis.de - company
https://grass.osgeo.org - FOSS
https://neteler.org - freelancing & blog
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here .