[mapserver-users] TIGER OGR on Windows doesn't work with backslash in paths
Martin, Daniel
DMartin@erac.com
Wed, 19 Jun 2002 17:05:47 -0500
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------=_NextPartTM-000-77b3d447-83cf-11d6-9830-00508bcfddcb
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C217DD.775DEA50"
------_=_NextPart_001_01C217DD.775DEA50
Content-Type: text/plain;
charset="iso-8859-1"
After struggling with using TIGER line data through OGR within the Windows
binary version 3.6, I finally figured out something that is probably worth
getting into the mailing archives - just in case someone else is searching
for the solution.
On Windows, paths in .map files can happily use the \ backslash, including
the paths of other OGR types such as MapInfo TAB. However, OGR for TIGER
line doesn't work unless you use strictly / foreslashes in your paths. Pure
trial and error landed me with that conclusion. Perhaps it is a bug, or
perhaps it is by design. Either way it's the way it is.
Although, as the documentation warns, TIGER data is so terribly slow it's
nearly useless. Speaking of which, if anyone knows a good converter for
TIGER to MapInfo that supports the 2000 Census data, please let me know.
Even if it doesn't support the extra year 2000 files, it may work for my
needs.
Thanks,
Dan Martin
------_=_NextPart_001_01C217DD.775DEA50
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4613.1700" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=024094921-19062002><FONT face=Arial size=2>After struggling
with using TIGER line data through OGR within the Windows binary
version 3.6, I finally figured out something that is probably worth getting
into the mailing archives - just in case someone else is searching for the
solution.</FONT></SPAN></DIV>
<DIV><SPAN class=024094921-19062002><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=024094921-19062002><FONT face=Arial size=2>On Windows, paths in
.map files can happily use the \ backslash, including the paths of other
OGR types such as MapInfo TAB. However, OGR for TIGER line doesn't
work unless you use strictly / foreslashes in your paths. Pure trial and
error landed me with that conclusion. Perhaps it is a bug, or perhaps it
is by design. Either way it's the way it is.</FONT></SPAN></DIV>
<DIV><SPAN class=024094921-19062002><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=024094921-19062002><FONT face=Arial size=2>Although, as the
documentation warns, TIGER data is so terribly slow it's nearly
useless. Speaking of which, if anyone knows a good converter for
TIGER to MapInfo that supports the 2000 Census data, please let me
know. Even if it doesn't support the extra year 2000 files, it may work
for my needs.</FONT></SPAN></DIV>
<DIV><SPAN class=024094921-19062002><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=024094921-19062002><FONT face=Arial
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=024094921-19062002><FONT face=Arial size=2>Dan
Martin</FONT></SPAN></DIV></BODY></HTML>
------_=_NextPart_001_01C217DD.775DEA50--
------=_NextPartTM-000-77b3d447-83cf-11d6-9830-00508bcfddcb--