Skip to content
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

[gdal_contour] argparser #9739

Merged
merged 5 commits into from
Apr 24, 2024
Merged

[gdal_contour] argparser #9739

merged 5 commits into from
Apr 24, 2024

Conversation

elpaso
Copy link
Collaborator

@elpaso elpaso commented Apr 24, 2024

Uses the new argparser for the gdalcontour options.

elpaso added 2 commits April 24, 2024 13:24
Uses the new argparser for the gdalcontour options.
@elpaso elpaso force-pushed the gdalcontour-argparser branch from ad54b38 to 2cb0219 Compare April 24, 2024 11:24
@rouault
Copy link
Member

rouault commented Apr 24, 2024

When the PR is ready, can you separate the changes in gdalargumentparser.h/cpp in a separate initial commit?

@elpaso
Copy link
Collaborator Author

elpaso commented Apr 24, 2024

When the PR is ready, can you separate the changes in gdalargumentparser.h/cpp in a separate initial commit?

I can remove the changes completely and put them in a separate PR, I'm not using them here, I just though they were right in case one wanted to further modify the arg.

@coveralls
Copy link
Collaborator

Coverage Status

coverage: 69.062% (+0.006%) from 69.056%
when pulling 39e258e on elpaso:gdalcontour-argparser
into d14f23c on OSGeo:master.

@rouault rouault added this to the 3.10.0 milestone Apr 24, 2024
@rouault rouault merged commit 40884e8 into OSGeo:master Apr 24, 2024
31 of 32 checks passed
@elpaso elpaso deleted the gdalcontour-argparser branch April 26, 2024 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants