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

Not all Features in Personal GDB layer showing up in QGIS 1.8 #15632

Closed
qgib opened this issue Sep 18, 2012 · 3 comments
Closed

Not all Features in Personal GDB layer showing up in QGIS 1.8 #15632

qgib opened this issue Sep 18, 2012 · 3 comments
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 Sep 18, 2012

Author Name: rmercer - (rmercer -)
Original Redmine Issue: 6368
Affected QGIS version: master
Redmine category:data_provider/ogr


I have a point layer stored in an ESRI Personal GDB. The layer contains 431 features. When I load this layer into QGIS, it only shows the first 180 records in the layer. If you look at the properties in the layer, it shows the count of 431 features.
This layer was copied out of an ESRI File GDB. When you load the same layer from the File GDB into QGIS, all 431 features show up and are accessible in the attribute table.

Based on input from GIS.stackexchange, I did some research into the features in the layer. It turns out that feature 181, and a few features further down in the list, have invalid geometry. I tried running @ogrinfo -al datasource@ and it only returns the first 180 records. That is, it loads records until it hits the first record with an error in the spatial data. As a test, I tried running @ogrinfo datasource layer -where "OBJECTID=183"@, which is the next valid point. It correctly listed the data for that record. This indicates that it is able to read the subsequent, valid, records but not all of them in a row.

So, the long and short is that loading the same layer, with the same spatial data issues, has different results if it is stored in a File GDB or a Personal GDB. The File GDB will load all the features in the layer, regardless of whether they display or not. The Personal GDB layer will load records until a record is reached that has an error in the spatial data, at which point it stops.

I am not sure which would be better from a data standpoint.

Which is better:

  1. Have QGIS continue to stop at a spatial data error and simply bring up an error message to notify you of the reason not all records were loaded.
  2. Load all records regardless of errors, like current behavior with File GDB, and then raise notification that some records have errors in their spatial data.

Here is the question from gis.stackexchange.com for reference. It has screenshots and additional detail:
"Why can't I see all records in my personal GDB in QGIS?":http://gis.stackexchange.com/questions/33528/why-cant-i-see-all-records-in-my-personal-gdb-in-qgis

@qgib
Copy link
Contributor Author

qgib commented Jun 21, 2014

Author Name: Jürgen Fischer (@jef-n)


  • category_id was configured as Data Provider/OGR

@qgib
Copy link
Contributor Author

qgib commented Jun 21, 2014

Author Name: Giovanni Manghi (@gioman)


please test with the latest qgis release available and/or attach sample data.


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Oct 11, 2014

Author Name: Giovanni Manghi (@gioman)


closing for lack of feedback, please reopen if necessary.


  • resolution was changed from to worksforme
  • status_id was changed from Feedback to Closed

@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 24, 2019
@qgib qgib closed this as completed May 24, 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