Open qgib opened 10 years ago
Author Name: Giovanni Manghi (@gioman)
very nice idea!
Author Name: Werner Macho (Werner Macho)
Very nice idea
The most annoying thing for me is that you cannot "save as" a layer within an already existing spatialite database .. Probably this will address that issue as well.
And probably take a look at alexander bruys QConsolidate plugin as well :)
Author Name: Richard Duivenvoorde (@rduivenvoorde)
I think it is a good plan to streamline the 'saveas' functions more to work for other data types.
But isn't this the beginning of ETL tool like FME? With all it's options like:
I'm not sure if this will work out in a dialog format like this, and I'm not sure if all this should be part of QGIS. To be able to create something like the bottom (some buttons to save as this or that), also needs one or more extra dialogs.
So do not get me wrong, it is a great idea: a gui for ogr2ogr ( like FME is ;-) ), but I'm wondering if we should stitch this all into QGIS. It would be nice to base it on QGIS-core, but make it modular or so?
Good idea to pull discussion to this place.
Author Name: Nathan Woodrow (@NathanW2)
Richard Duivenvoorde wrote:
I think it is a good plan to streamline the 'saveas' functions more to work for other data types.
But isn't this the beginning of ETL tool like FME? With all it's options like:
The toolbox is more ETL then this, this is just making the Save As dialog better and the targets then is just to remove the need to change settings all the time.
- being able to reproject stuff
Save as already does this.
- being able to transform / remove /add attributes
Not in scope for this tool. This should be done using a query on the layer, then exporting the query. One tool for one job.
- add filters (spatial and non spatial)
Not in scope for this tool. Use a query, export that.
- add other outputs, and maybe previews
All formats would be supported, there is no others. What previews?
- etc
`
I'm not sure if this will work out in a dialog format like this, and I'm not sure if all this should be part of QGIS. To be able to create something like the bottom (some buttons to save as this or that), also needs one or more extra dialogs.
Not at all, there is a Save as Target which just takes the config you have set and saves it. No extra stuff needed.
So do not get me wrong, it is a great idea: a gui for ogr2ogr ( like FME is ;-) ), but I'm wondering if we should stitch this all into QGIS. It would be nice to base it on QGIS-core, but make it modular or so?
It would be a widget in gui and core stuff in core so it can be reused. I would also plan to make a standalone (python app) that does it outside of QGIS.
Good idea to pull discussion to this place.
Author Name: Anita Graser (@anitagraser)
+1 for getting rid of as many modal dialogs as possible.
My other first reaction was: There's a layer list right to a layer list ...
I don't share Richard's concerns about this getting too ETL tool like. It's an improved "Save as" interface.
One question concerning exporting multiple layers at once: How would the workflow be to export multiple layers to e.g. Shapefile? How are the filenames picked/generated?
Author Name: Nathan Woodrow (@NathanW2)
Anita Graser wrote:
+1 for getting rid of as many modal dialogs as possible.
My other first reaction was: There's a layer list right to a layer list ...
Yes that is a good point, both might not be needed, it would just be a matter of playing with it.
One question concerning exporting multiple layers at once: How would the workflow be to export multiple layers to e.g. Shapefile? How are the filenames picked/generated?
The plan was to have some of kind of config options something like: ask, match, or something like that. I haven't fleshed it that out yet, but it should be flexible.
Author Name: Vincent chourmo (Vincent chourmo)
If this is the only way to save a file, it is an horrible idea. QGIS must use the standard / platform way to save files. It gives a lot of benefits for the platform. For instance, on a mac, you have folders, per file tagging and virtual folders, access to several cloud based storage (on the next version)... More importantly, it makes QGIS a good platform citizen, improves consistency and helps discovery for the end user. Ways exists to implement parameters in the save dialog, or with a previous/after dialog.
It may be a good idea to have a batch conversion interface, in QGIS Browser for instance.
Author Name: Nathan Woodrow (@NathanW2)
Vincent chourmo wrote:
If this is the only way to save a file, it is an horrible idea. QGIS must use the standard / platform way to save files. It gives a lot of benefits for the platform. For instance, on a mac, you have folders, per file tagging and virtual folders, access to several cloud based storage (on the next version)... More importantly, it makes QGIS a good platform citizen, improves consistency and helps discovery for the end user. Ways exists to implement parameters in the save dialog, or with a previous/after dialog.
It may be a good idea to have a batch conversion interface, in QGIS Browser for instance.
Just to be clear this doesn't change how the old Save As.. works. You can still pick pick a folder and Save As.. like normal. I have only just seen that my mockup is missing the folder input, which of course only makes sense for file based formats. I will update the screen shot.
Author Name: Giovanni Manghi (@gioman)
Author Name: Nathan Woodrow (@NathanW2) Original Redmine Issue: 10454
Redmine category:gui Assignee: Nathan Woodrow
This is a mockup of a new UI I am thinking of for exporting layers, single or multi. Opening a ticket here for more feedback and so I don't forgot the idea like I normally do ;)
Currently the main issues I have with current Save/Export method are:
Other issue I have, which are related to 3), are:
QGIS has strong data format support and import and exporting should be a lot cleaner.
So here is the mock up idea.
New tab (can close) in the main area, with Map in the other (you will see why later)