gdaltips

My "Mastering #GDAL Tools" course is now available on YouTube! This course is the result of my 20 years of experience processing large volumes of imagery and building data pipelines. Check out the playlist at youtube.com/playlist?list=… . More in the thread below (1/n)

GDAL 3.6.1 is released: lists.osgeo.org/pipermail/gdal… . Users of 3.6.0 *should* migrate to 3.6.1 to avoid a potential corruption of the spatial index of GeoPackage files generated by 3.6.0

You have a look at this great tutorial about @gdalorg tools courses.spatialthoughts.com/gdal-tools.html Put together by @spatialthoughts Ujaval Gandhi

.@MappingGIS En este artículo te presentamos las 30 aplicaciones #GIS #OpenSource que debes de conocer mappinggis.com/2022/07/aplica…

Big push for the #MapServer !

You can also reach to feature of certain index using standard @Python list indexing

@wrenoud @doublebyte @howardbutler @JachymCepicky @STACspec @petegadomski @GdalOrg Is this the future?!

Hey @STACspec curious folks! @petegadomski is adding STAC output of the @GdalOrg `gdalinfo -json` command #issuecomment-1234287651" target="_blank" rel="nofollow noopener">github.com/OSGeo/gdal/pul… which was an idea hatched at #FOSS4G2022 because good things happen when people meet in person 🙂

GDAL 3.5.2 release candidate available for your testing: lists.osgeo.org/pipermail/gdal…

oh ... outputdir/output-file-{X}-{Y}.gpkg is better ogr2ogr will not create just files in the output directory sorry for that

Just needed to cut big vector dataset into smaller chunks. With some 🐍 code and dirty ogr2ogr call from the subprocess module, you can put together several ogr2ogr -clipsrc 0 0 100 100 output_dir input_file.gpkg -nlt MULTILINESTRING Change the -clipsrc values and repeat

You can also loop through all features using simple `for` loop. #fiona converts input featurs in to the @GeoJSON structure, so accessing it's properties is easy feature["properties"]["name"]

@STACspec was resonating during #FOSS4G2022 a lot! Great to see @gdalorg to support it more!

The data source behaves like list of features. You need just number of features? Simply use `len()` function

All important datasource attributes are stored in `meta` attributes - including name, file name, coordinate reference system and attribute schema. (used along with json.dumps( ...., indent=4) for better readability)

I love the way, #fiona is done: you just `fiona.open()` the dataset and can use the code block to close it automatically. if you `dir()` the data source, you can see all the object attributes. with fiona.open("dataset.gpkg") as ds: print(dir(ds))

Big thanks for promoting @python and #geospatial 🐍🗺️

State of PDAL talk from FOSS4G2022 - Slides: tinyurl.com/pdal2022

Slides of "State of GDAL" talk given last week at #FOSS4G2022 available at download.osgeo.org/gdal/presentat…

You can use @gdalorg @python bindings, but writing code using #GDAL is like writing C++ code using pythonish syntax - not very python. But there is #fiona library for basic vector file manipulation. pip install fiona docs: fiona.readthedocs.io/en/stable/ file: file.io/kab3EwQOQ88R