andrew_r_blake wrote: > > It would appear MITab is quite happy to quickly use the spatial indexes > generated by MapInfo, but is unable to generate optimal spatial indexes > itself. >
You got it there: MITAB can read the spatial index no problem, but the current implementation doesn't always generate a balanced spatial index (tree)... actually it doesn't contain any smarts to keep the tree balanced, which results in the behaviors that you noticed. There may even be some TODO comments in the code to that effect. > > Is the problem likely to be in MITab or OGR ? > It's in MITAB. Daniel -- Daniel Morissette http://www.mapgears.com/ ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/dkFolB/TM --------------------------------------------------------------------~-> 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/
