explorist_g wrote: > > > Helo, > > First of all, great work:D. > I need some help. I'm using ogr2ogr for converting from Geodatabase to > MapInfo. The issue that I have is that I can't get coordinate system > right. Original coordsys is like this: > > PROJCS["Bosnien_Zone_6", > GEOGCS["GCS_Hermannskogel", > DATUM["D_Hermannskogel", > SPHEROID["Bessel_1841",6377397.155,299.1528128]], > PRIMEM["Greenwich",0.0], > UNIT["Degree",0.017453292519943295]], > PROJECTION["Transverse_Mercator"], > PARAMETER["False_Easting",6500000.0], > PARAMETER["False_Northing",0.0], > PARAMETER["Central_Meridian",18.0], > PARAMETER["Scale_Factor",0.9999], > PARAMETER["Latitude_Of_Origin",0.0], > UNIT["Meter",1.0]] > > I know that MI drivers can't recognize this projection so I'm using > this to convert: > ogr2ogr.exe -f "MapInfo file" -dsco FORMAT=MIF -a_srs BiH6.prj > converted database.mdb > where BiH6.prj contains above parameters. > > But still in output MIF file I get: > CoordSys Earth Projection 8, 104, "m", 18, 0, 0.9999, 6500000, 0 > instead of: > CoordSys Earth Projection 8, 9999, 10, 472.8677, 187.8769, 544.7084, > -5.76198422, -5.3222842, 12.80666941, 1.54517287, 0, "m", 18, 0, > 0.9999, 6500000, 0 > > So is anybody can tell me how to correct this? Can I add this new > parameters somewhere in code?(editing source isn't problem). How to > tell MI drivers to use this new parameters?. > > Thank you in advance.
Faruk, What you want can be accomplished by using the "MIF datum" hack for MITAB. Use this wkt: PROJCS["Bosnien_Zone_6", GEOGCS["GCS_Hermannskogel", DATUM["MIF 9999,10,472.8677,187.8769,544.7084,-5.76198422,-5.3222842,12.80666941", SPHEROID["Bessel_1841",6377397.155,299.1528128]], PRIMEM["Greenwich",0.0], UNIT["Degree",0.017453292519943295]], PROJECTION["Transverse_Mercator"], PARAMETER["False_Easting",6500000.0], PARAMETER["False_Northing",0.0], PARAMETER["Central_Meridian",18.0], PARAMETER["Scale_Factor",0.9999], PARAMETER["Latitude_Of_Origin",0.0], UNIT["Meter",1.0]] Note the carefully formatted DATUM name with the ellipsoid number and datum shift parameters. Currently if the datum name is not in the list of recognised names (in mitab_spatialref.cpp) it is just assuming WGS84. It *ought* to check for TOWGS84 parameters in the WKT and if found it should construct the 999 or 9999 style coordsys info itself. I'd appreciate it if you could file an mitab bug on this issue assigned to me (including my notes in the previous paragraph). Best regards, -- ---------------------------------------+-------------------------------------- I set the clouds in motion - turn up | Frank Warmerdam, [EMAIL PROTECTED] light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush | President OSGeo, http://osgeo.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/mitab/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/mitab/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
