-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
2.2 GB GeoJson file crashes qgis #21016
Comments
Author Name: Giovanni Manghi (@gioman)
|
Author Name: baditaflorin - (baditaflorin -) Giovanni Manghi wrote:
Here is the dropbox link https://www.dropbox.com/s/vdf439xeibk6ndy/tmpw9cnuy_lines.zip?dl=0 |
Author Name: Giovanni Manghi (@gioman) it does crash qgis (that starts eating up memory while trying to open the file), but it does also crash ogrinfo.
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Sandro Santilli (@strk) Should up/downstream resolved tickets not be closed ? |
Author Name: Sandro Santilli (@strk) Closing, filed upstream: https://trac.osgeo.org/gdal/ticket/6540
|
Author Name: Jukka Rahkonen (Jukka Rahkonen) The original file has 612173 lines so I made a short five row version as an attachment. Ogrinfo follows. I would say that GDAL should not crash of jam but the file itself is lunatic to be used with Simple Feature based GIS system. Because GeoJSON does not have schema GDAL must parse the whole file once for finding all the attributes. In this sample of 5 features there are 207 attributes (tags). ogrinfo short.geojson -al -so Layer name: OGRGeoJSON
|
Author Name: baditaflorin - (baditaflorin -)
Original Redmine Issue: 12935
Affected QGIS version: master
Redmine category:data_provider/ogr
I am not sure if the file is complete, is was downloaded via QuickOSM plugin, but not sure if it completed.
The idea is that it should not crash and it's crashing in such a way that not even a mini-dump is provided
https://www.dropbox.com/s/vdf439xeibk6ndy/tmpw9cnuy_lines.zip?dl=0
Related issue(s): #21011 (relates)
Redmine related issue(s): 12929
The text was updated successfully, but these errors were encountered: