i couldnt understand why the problem is seen with map info only and not with arcview as we are using the same coordinate system information in both the cases. I think NAD27 datum is causing the problem.
we are using this in our export code written in VB:
Private m_fmeSessionObj As FMEOSession
m_fmeSessionObj.coordSysManager.defineCoordSys fmestraryCSParms, m_sFMECSName
Here the fmestraryCSParms is FMEOStringArray that contains the coordinate information such as the projection algorithm and map datum which we give asinput to the defineCoordSys method on fmesession object which will return the coordinate system name - 'm_sFMECSName'
And further when we create the FME writer object to write the features to output file format, we do the following:
'create writer
Set m_fmeWriterObj = m_fmeSessionObj.createWriter(sDestFormat, fmestraryUserDirAry)
'Set the writer parameters
Set fmestraryWriterPara = m_fmeSessionObj.createStringArray
'append the coordinate system info obtained from the defineCoordSys method used earlier on fmesession object as a key value pair to the stringarray
fmestraryWriterPara.Append "COORDINATE_SYSTEM"
fmestraryWriterPara.Append m_sFMECSName
'finally open the writer and use it for writing to targed format
m_fmeWriterObj.Open sDestDataset, fmestraryWriterPara
Considering this as the code that we are using, i would like to know why this is failing for NAD27 datum only and that to for map info format only.. is this a bug in FME? or are we missing to initialize any specific attribute for mapinfo format? Please clarify??
