-
-
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
Importing Data into a QGIS Created File Based Geodatabase #51435
Comments
Aaaand I inadvertently used the wrong github account to file this. Yay. |
@rjhale1971, it seems the file cannot be downloaded. Could you please attach it (or, better, the layer with only one sample feature) directly to this issue report? |
Atached. I went ahead and moved the data into a Geopackage - the problem is the same. Create a new File Based Geodatabase and drag and drop the Centerlines Table into it and the data shifts one column to the left. Hopefully this helps - and thanks again. |
Issue confirmed using QGIS 3.28 on Windows. It only occurs dragging and dropping the layer to an Esri File Geodatabase using the browser, while it doesn't occur exporting the layer to an ESRI File Geodatabase layer. |
Thanks! That also made me realize I'm missing an export to ESRI FileGDB on Linux - but not on windows. I'm guessing that's a symptom of running this through Conda. I'll send them an bug report. |
You rock! |
What is the bug or the crash?
When importing data into File Based Geodatabse (created in QGIS) the attributes shift one column to the left.
In the screenshot all the data should be in the column to the right.
Steps to reproduce the issue
Example:
Versions
3.28.2 On Fedora (using the conda installer) and Windows 10
Supported QGIS version
New profile
Additional context
There is no problem with editing. The only problem seems to be importing this into a new file geodatabase. I can save it out to geopackage and I'm fine. I tried a ESRI File Based Geodatabase -> Geopackage -> QGIS Produced File Based Geodatbase and it still shifted the data one column to the left. .
The text was updated successfully, but these errors were encountered: