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

[BUG]: Geopackage reader: For Geopackages containing a boolean field, the value 'true' is read as '1' #1223

Open
JohannaOtt opened this issue Jul 4, 2024 · 1 comment
Labels
bug confirmed Issue has been confirmed

Comments

@JohannaOtt
Copy link
Contributor

JohannaOtt commented Jul 4, 2024

Describe the bug
When importing a geopackage file containing a boolean field with true values, the values are read as 1

To Reproduce
Steps to reproduce the behavior:

  1. Go to Import source schema and import the attached geopackage as schema
  2. Go to Import source data and import the geopackage as source data
  3. Rightclick on BoolField in the Schema Explorer and open the Properties
  4. Chose the section Occurring values
  5. Click the refresh button and the occurring values - it is 1

testExportFlo.zip

Expected behavior
I would expect the occurring value to be true as this is the value I assigned to the field when creating the geopackage file with hale»studio.

Additional context
I am using Version 5.1.0. release
Build 202402261605
Revision 883baf4

When loading the data to QGIS, the value is true as expected which is why the error must be in the Geopackage reader, not the writer.

@JohannaOtt JohannaOtt added the bug label Jul 4, 2024
@JohannaOtt JohannaOtt changed the title [BUG]: For Geopackage containing a boolean field, the value 'true' is read as '1' [BUG]: Geopackage reader: For Geopackages containing a boolean field, the value 'true' is read as '1' Jul 4, 2024
Copy link

github-actions bot commented Sep 3, 2024

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 3, 2024
@florianesser florianesser added confirmed Issue has been confirmed and removed stale labels Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed Issue has been confirmed
Projects
None yet
Development

No branches or pull requests

2 participants