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

[Processing] GRASS Support multiple vector output file formats #5726

Closed
wants to merge 1 commit into from
Closed

[Processing] GRASS Support multiple vector output file formats #5726

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Nov 25, 2017

Description

Add multiple vector output file formats with v.out.ogr:

  • Supported output formats are based on Processing GdalUtils...
  • ...which have been improved to support vector file formats discovering.
  • 2 output options have been added: dsco and lco for v.out.ogr.
  • v.external isn't the default import method (v.in.ogr used, thanks to @neteler).

New formats:
processinggrassoutputvectorformats

OGR output options:
processinggrassoutputvectoroptions

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

  • Commit messages are descriptive and explain the rationale for changes
  • Commits which fix bugs include fixes #11111 in the commit message next to the description
  • Commits which add new features are tagged with [FEATURE] in the commit message
  • Commits which change the UI or existing user workflows are tagged with [needs-docs] in the commit message and containt sufficient information in the commit message to be documented
  • I have read the QGIS Coding Standards and this PR complies with them
  • This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
  • New unit tests have been added for core changes
  • I have run the scripts/prepare-commit.sh script before each commit

@nirvn
Copy link
Contributor

nirvn commented Nov 26, 2017

Nice

@nirvn
Copy link
Contributor

nirvn commented Nov 26, 2017

For consistency, maybe place geopackage and shape file formats on top, followed by an alphabetical list of additional formats? That's what we now do elsewhere.

@neteler
Copy link
Contributor

neteler commented Nov 29, 2017

Nice, it is very important to avoid v.external being the default import method in favor of v.in.ogr (which got improved again in GRASS GIS 7.4.0)

@ghost ghost mentioned this pull request Jan 7, 2018
8 tasks
Copy link
Contributor

@alexbruy alexbruy left a comment

Choose a reason for hiding this comment

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

Looks good to me.

@@ -193,6 +223,48 @@ def getSupportedOutputRasterExtensions():
allexts.append(ext)
return allexts

@staticmethod
def getSupportedVectors():
Copy link
Contributor

Choose a reason for hiding this comment

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

Same as above. If I'm not wrong QgsVectorFileWriter already has methods for getting such information

vector = False
raster = False
# Is it an OGR driver?
if (gdal.DCAP_VECTOR in metadata
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe better to rely on the core API here, e.g. supportedFiltersAndFormats() and other methods of the QgsRasterFileWriter class?

@alexbruy
Copy link
Contributor

@medspx can you rebase? I will be happy to merge it after this

@alexbruy
Copy link
Contributor

Superseded by #6996

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants