gsrao456 wrote: > Hi All > > Apologies if this has been already discussed in the past. > > I am a new member of this group. I have just started > using MITAB. > > Actually when we try to convert a surpac string file with large > coordinates (1e7), the coordinates are set to a default value of > 1000000. Is this a bug in mitab library, if yes is there any > workaround to come across this problem. >
Not really a bug, but a "feature" of the TAB format. TAB datasets store the object coordinates in the file using integers. The overall bounds of the dataset are scaled to fit in the integer range of +/-1000000000 (+/-1e9). If you don't explicitly provide bounds then MITAB tries to use some default value depending on the dataset's coordsys. You are likely hitting that limit because the default bounds for the coordsys that you chose are not large enough for the range of coordinates of your data. You'll have to explicitly specify bounds that are large enough for your data at the time that you create the dataset, if you use the C API, then see mitab_c_create()'s north, south, east, west args: http://mitab.maptools.org/mitab-docs/mitab__capi_8cpp.html#a12 Daniel -- Daniel Morissette http://www.mapgears.com/ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/mitab/ <*> 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/
