Closed GoogleCodeExporter closed 9 years ago
It looks like I have a problem with my routes.txt file, but I can't seem to
identify
what it is.
Thanks.
Original comment by greg.god...@jocogov.org
on 20 Jun 2008 at 8:05
Thanks for the report. I'm pretty sure you can work around this problem by
adding a
route_long_name column to routes.txt (even if the value for it is the empty
string on
every row). I am writing a fix which will get into the next release. Let me
know if
the work around helps.
Original comment by tom.brow...@gmail.com
on 28 Jun 2008 at 2:17
Also, utf-8 errors in route_long_name can trigger this bug.
Original comment by tom.brow...@gmail.com
on 30 Jun 2008 at 6:57
It looks like the error may have been due to the UTF version of the files.
My DB extract (SQL Server 2005 & Win XP client) was creating UTF-16 files. I
was
looking for a conversion tool when I discovered that COPY with the "a" switch
(a as
in ASCII), generates a file that passes as UTF-8.
Thanks,
Original comment by greg.god...@jocogov.org
on 30 Jun 2008 at 9:52
The validator should read UTF-16, generate an error and otherwise process it
normally. If you send me the file I can work out what went wrong with the utf-16
handling.
Original comment by tom.brow...@gmail.com
on 30 Jun 2008 at 9:56
No bother. We're good now. I am getting good validation now, and I'm not sure
we
could reproduce the files that caused the error message.
Thanks!
Original comment by greg.god...@jocogov.org
on 30 Jun 2008 at 10:06
Fix for route_long_name = None (stack trace that opened this issue) is fixed in
trunk
and will be in next release. If someone reproduces the utf16 problem please
open a
new issue.
Original comment by tom.brow...@gmail.com
on 30 Jun 2008 at 10:46
Original comment by bdfer...@google.com
on 26 Sep 2014 at 4:35
Original issue reported on code.google.com by
greg.god...@jocogov.org
on 20 Jun 2008 at 7:11