Timeline for PostGIS import error
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2023 at 16:21 | comment | added | Sergey47 | Vince, but it works with other files. I have converted these files to QGIS, and they are displayed correctly there | |
| Mar 9, 2023 at 16:11 | comment | added | Vince | If the codepage file claims UTF-8, but it isn't, the file may not be usable. It's not nice to lie to ETL software. | |
| Mar 9, 2023 at 15:43 | comment | added | robin loche |
Have you tried SELECT convert(name, 'LATIN1', 'UTF8') from my_table ?
|
|
| Mar 9, 2023 at 15:26 | comment | added | Sergey47 | UTF 8 is written in cpg files. But dbf has a different encoding and in the case of small files, it converts to UTF 8, if a file with a large number of lines, it gives the error that it described earlier | |
| Mar 9, 2023 at 13:08 | history | answered | robin loche | CC BY-SA 4.0 |