<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1479" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=662534921-02022005>I've been using
ogr2ogr for some time (Windows binary from OpenEV_FW) to convert the entire
TIGER line data from the census into workable MapInfo TAB street
layers. Something we recently noticed is that our resulting streets in
California are off by a about 1/10th of a mile. Nothing terrible,
but enough to make them unusable for our purposes. I went to check my
old files to see if the problem is new, but I found it in the files I was
creating about two years ago. I've done very little work in California, so
I've never noticed it before.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=662534921-02022005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=662534921-02022005>I started to think
this was a projection issue. So, I started checking other states
throughout the country. I've not checked them all, but all the other
states I have checked are absolutely dead on. This includes states from
all corners (Washington, New York, Florida) and in the middle of the country
(Missouri, Illinois). But California appears to be the only one that is
incorrect. This also appears to affect all of California, and isn't
isolated to one small part.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=662534921-02022005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=662534921-02022005>As a control, I've
used several of our internal data layers that I'm quite confident in, and the
Microsoft Terraserver WMS layer. Terraserver makes it really easy to see
when streets are off.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=662534921-02022005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=662534921-02022005>Another oddity is
that this effect is lessened if the layer is loaded into MapServer (versus
MapInfo), I'm guessing since MapServer uses OGR. The data is still out of
place in MapServer, but not quite as much. We've tested the data in
multiple versions of MapInfo just to be sure that wasn't part of the
problem.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=662534921-02022005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=662534921-02022005>Any ideas on why
this would happen? I'm using the basic command line options for
ogr2ogr.</SPAN></FONT></DIV></BODY></HTML>