Skip to content

Add 'gdal raster polygonize' (port of gdal_polygonize.py) #12122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Apr 16, 2025

Conversation

rouault
Copy link
Member

@rouault rouault commented Apr 10, 2025

No description provided.

@rouault rouault added enhancement funded through GSP Work funded through the GDAL Sponsorship Program gdal_cli Anything related to the new 3.11 "gdal" CLI frontend labels Apr 10, 2025
@rouault rouault added this to the 3.11.0 milestone Apr 10, 2025
@rouault rouault force-pushed the gdal_raster_polygonize branch from 4f85c45 to 3dcbaaa Compare April 10, 2025 17:15
@rouault rouault force-pushed the gdal_raster_polygonize branch from 3dcbaaa to 0b43d4f Compare April 10, 2025 19:32

.. option:: -l, --nln, --layer <LAYER>

Provides a name for the output vector layer. Defaults to "polygonize".
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider exposing gdal_polygonize options -mask and -nomask (as --ignore-mask)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could do this in a follow-up

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider exposing gdal_polygonize options -mask and -nomask (as --ignore-mask)

I deliberately didn't expose them as they seemed a bit too specialized to me, at least at that stage. There are many other algorithms where the user can't provide an "external" mask and I'm not sure why polygonize would be an exception

@rouault rouault force-pushed the gdal_raster_polygonize branch from 0b43d4f to 2b1746f Compare April 16, 2025 16:11
@rouault rouault force-pushed the gdal_raster_polygonize branch from 2b1746f to caf5ae4 Compare April 16, 2025 16:41
@rouault rouault merged commit 087abc6 into OSGeo:master Apr 16, 2025
8 of 35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement funded through GSP Work funded through the GDAL Sponsorship Program gdal_cli Anything related to the new 3.11 "gdal" CLI frontend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants