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

Exporting shape file from a SpatiaLite table produces very large file size #24252

Closed
qgib opened this issue Mar 11, 2017 · 9 comments
Closed
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers

Comments

@qgib
Copy link
Contributor

qgib commented Mar 11, 2017

Author Name: Reinhard Reiterer (Reinhard Reiterer)
Original Redmine Issue: 16342
Affected QGIS version: 2.18.4
Redmine category:data_provider/spatialite


To reproduce this issue please import a shape file in a SpatiaLite table and export the table as a shape file again. The new shape file is more than twice as large as the original shape file!


@qgib
Copy link
Contributor Author

qgib commented Mar 11, 2017

Author Name: Reinhard Reiterer (Reinhard Reiterer)


  • 10833 was configured as 16342.m4v

@qgib
Copy link
Contributor Author

qgib commented Mar 13, 2017

Author Name: Saber Razmjooei (@saberraz)


Hi Reinhard,

What version of gdal are you using? I can't reproduce the problem with QGIS 2.18.4 (not from a ppa but built against latest gdal) in Ubuntu.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Mar 13, 2017

Author Name: Saber Razmjooei (@saberraz)


  • category_id was configured as Data Provider/SpatiaLite

@qgib
Copy link
Contributor Author

qgib commented Mar 14, 2017

Author Name: Reinhard Reiterer (Reinhard Reiterer)


Hi Saber,

the QGIS 'About' dialog says 'Compiled against GDAL/OGR 1.11.3':

image

I noticed this issue on Ubuntu 16.04 LTS and Windows 7.


  • 10841 was configured as qgis_2_18_4_about

@qgib
Copy link
Contributor Author

qgib commented Mar 14, 2017

Author Name: Reinhard Reiterer (Reinhard Reiterer)


Sample shape files (EPSG: 31259, Encoding: Windows-1252):

http://www.bev.gv.at/pls/portal/docs/PAGE/BEV_PORTAL_CONTENT_ALLGEMEIN/0200_PRODUKTE/UNENTGELTLICHE_PRODUKTE_DES_BEV/VGD-Oesterreich_gen_50.zip

@qgib
Copy link
Contributor Author

qgib commented Mar 17, 2017

Author Name: Saber Razmjooei (@saberraz)


I can confirm the issue.

Using ogr2ogr the file size is 28 MB. But QGIS save as function output is 47 MB!


  • status_id was changed from Feedback to Open

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Mar 7, 2018

Author Name: Nino Formica (Nino Formica)


Tested with GIS 2.18.17 and QGIS 3.0.0 (both GDAL/OGR 2.2.3): confirm the issue.
Sample shapefile VGD-Oesterreich_gen_50 originally has .dbf size 3.8 MB; after import in SpatiaLite and re-export as shapefile it becomes 32 MB !

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2019

Author Name: Giovanni Manghi (@gioman)


End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.


  • resolution was changed from to end of life
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Mar 9, 2019
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers labels 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! Data Provider Related to specific vector, raster or mesh data providers
Projects
None yet
Development

No branches or pull requests

1 participant