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 tools only output .shp fileset instead of GPX or other format #19826

Closed
qgib opened this issue Nov 4, 2014 · 13 comments
Closed

Processing tools only output .shp fileset instead of GPX or other format #19826

qgib opened this issue Nov 4, 2014 · 13 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms

Comments

@qgib
Copy link
Contributor

qgib commented Nov 4, 2014

Author Name: Howard Frederick (@simbamangu)
Original Redmine Issue: 11561
Affected QGIS version: 2.6.0
Redmine category:processing/gdal


The processing tools will only produce a shapfile set instead of GPX, KML or SQLITE format. When GPX is selected as an output, this error appears:

Oooops! The following output layers could not be open
Subunits: .../Flightplanning/Routes/su_RuahaC-3s-1.gpx
The above files could not be opened, which probably indicates that they were not correctly produced by the executed algorithm

In the output directory, there is a set of su_RuahaC-3s-1.gpx.shp, *.gpx.dbf, etc. files, or *.kml.shp, etc. in the case of trying a KML output.

Selecting a temporary file output produces no error, creating a shapefile in a temporary directory.

Tested on MacOS X 10.9, QGIS 2.4 and 2.6, and got the same problem with trying to output GPX, KML and SQLITE.

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Giovanni Manghi (@gioman)


Hi Howard,

are you referring to the "Convert format" tool?

I just tested here on Linux and Windows and when outputting a temporary layer the result is in the expected format, not a shapefile.

In case of choosing to output a non temporary result then it still works ok. However there is an annoying aspect: after choosing the format you want to output in the "destination format" dropdown, the use must choose also the same format after clicking "save to file" when is asked to choose a name/place where to save the output.

Not sure if/how we can fix this, but anyway seems more an annoyance rather then a serious bug.

PS
To test I used the point layer you attached yesterday in the other gpx related ticket, and got gpx files as output.


  • status_id was changed from Open to Feedback
  • category_id was configured as Processing/GDAL

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Giovanni Manghi (@gioman)


ps
also tested kml and sqlite, same as above.

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Paolo Cavallini (@pcav)


Yes, this is one of the many improvements of the new Processing. Perhaps you have an old version masking to recent one?

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Giovanni Manghi (@gioman)


Paolo Cavallini wrote:

Yes, this is one of the many improvements of the new Processing. Perhaps you have an old version masking to recent one?

do you refer to the necessity to choose twice the output format?

I certainly do not have an old processing installation masking the most recent one, and this (small) problem still there.

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Howard Frederick (@simbamangu)


Paolo Cavallini wrote:

Yes, this is one of the many improvements of the new Processing. Perhaps you have an old version masking to recent one?

My Processing version shows as 2.2.0-2.

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Paolo Cavallini (@pcav)


That's it. Please remove it, and use the stock one (2.6).

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Howard Frederick (@simbamangu)


Paolo Cavallini wrote:

That's it. Please remove it, and use the stock one (2.6).

Right - have done an 'rm -rf ~/.qgis2/python/plugins', reinstalled QGIS from the package installer - now I have Processing 2.6 indicated.

However - same symptoms! Asking for .GPX produces *.GPX.shp, etc.

@qgib
Copy link
Contributor Author

qgib commented Nov 5, 2014

Author Name: Giovanni Manghi (@gioman)


Howard Frederick wrote:

Paolo Cavallini wrote:

That's it. Please remove it, and use the stock one (2.6).

Right - have done an 'rm -rf ~/.qgis2/python/plugins', reinstalled QGIS from the package installer - now I have Processing 2.6 indicated.

However - same symptoms! Asking for .GPX produces *.GPX.shp, etc.

if any, here it creates a .shp.gpx file when outputting to a temp file, but outputting not to a temp file then the result is a .gpx file.

Maybe is a OsX thing, I tested on Linux and Windows.

@qgib
Copy link
Contributor Author

qgib commented Nov 6, 2014

Author Name: Howard Frederick (@simbamangu)


Maybe is a OsX thing, I tested on Linux and Windows.

Perhaps - will try to test this on another Mac tomorrow, definitely still an issue here.

@qgib
Copy link
Contributor Author

qgib commented Nov 7, 2014

Author Name: Giovanni Manghi (@gioman)


Howard Frederick wrote:

Maybe is a OsX thing, I tested on Linux and Windows.

Perhaps - will try to test this on another Mac tomorrow, definitely still an issue here.

maybe better try a Windows or Linux installation and see if there are differences.

@qgib
Copy link
Contributor Author

qgib commented Jan 15, 2015

Author Name: Howard Frederick (@simbamangu)


No longer an issue on QGIS 2.6.1, OS X.

Select GPX as output correctly creates .GPX instead of .gpx.shp fileset.


  • status_id was changed from Feedback to Closed

@qgib
Copy link
Contributor Author

qgib commented Jun 5, 2015

Author Name: Bernd Vogelgesang (Bernd Vogelgesang)


On Linux Mint, trying to save as SQLITE still produces a .sqlite.shp file.
GPX seems to work.

QGIS 2.8.2, Processing 2.9.3

Ah, just saw: when trying to create a test.sqlite, the filename in the input field gets constructed as test.sqlit <- e missing! Thats why its created as test.sqlit.shp. Adding an e to the file extension produces an sqlite file.


  • status_id was changed from Closed to Reopened

@qgib
Copy link
Contributor Author

qgib commented Jun 6, 2015

Author Name: Giovanni Manghi (@gioman)


Bernd Vogelgesang wrote:

On Linux Mint, trying to save as SQLITE still produces a .sqlite.shp file.
GPX seems to work.

QGIS 2.8.2, Processing 2.9.3

Ah, just saw: when trying to create a test.sqlite, the filename in the input field gets constructed as test.sqlit <- e missing! Thats why its created as test.sqlit.shp. Adding an e to the file extension produces an sqlite file.

see #18696


  • resolution was changed from to not reproducable
  • status_id was changed from Reopened to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms labels May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Processing Relating to QGIS Processing framework or individual Processing algorithms
Projects
None yet
Development

No branches or pull requests

1 participant