Bug #87074 | MySQL Workbench and OGR2OGR | ||
---|---|---|---|
Submitted: | 14 Jul 2017 15:29 | Modified: | 4 Jun 2020 19:31 |
Reporter: | Joaquim Seixas | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 6.3.9 64 bits | OS: | Windows (10) |
Assigned to: | CPU Architecture: | Any | |
Tags: | MySQL Workbench, OGR2OGR |
[14 Jul 2017 15:29]
Joaquim Seixas
[14 Jul 2017 20:52]
MySQL Verification Team
Thank you for the bug report. Are you able to attach screen-shots of the issue (use the tab Files for). Thanks in advance.
[15 Jul 2017 9:08]
Joaquim Seixas
MySQL Workbench ogr2ogr 1
Attachment: MySQL OGR2OGR 1.png (image/png, text), 200.90 KiB.
[15 Jul 2017 9:09]
Joaquim Seixas
MySQL Workbench ogr2ogr 2
Attachment: MySQL OGR2OGR 2.png (image/png, text), 153.92 KiB.
[16 Jul 2017 6:17]
MySQL Verification Team
Thank you for the feedback! Verified as described with WB 6.3.9 on Win7. Thanks, Umesh
[4 Jun 2020 19:31]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Workbench 8.0.21 release, and here's the proposed changelog entry from the documentation team: Although the installation and file path were valid, MySQL Workbench was unable to find the ogr2ogr and ogrinfo files when loading spatial data. Thank you for the bug report.