|
Hi Tim
The parameters for the projection are held in the
header of the MAP file.
As mentioned before I do not know MITAB, but I
would imagine there is a function to read the projection for any particular
table. If there is not Uffe has really good documentation at his website on the
content of the MAP file so you could read the parameters directly
yourself.
The overhead of conversion is not a problem with
regard to render times. Bear in mind you are not reprojecting the whole file,
only what you render, and the time to transform a node is much smaller than the
time to read the data off the disc or storage card. Ideally though the OSTN02
"look up" table wants to be loaded into memory once, so that it is constanly
used from memory. Even if it isn't you'll probably find the Operating System
will cache it, giving the same effect.
You can see from MapInfo that the "on the fly"
transformation will not be a problem. MapInfo is continually doing this as the
contents of all its MAP files are actually in integers, and need to be
multiplied by a "step size" which are the widths and heights of the Bounds
clause divided by 2 GB to get floating point values. Its doing even more when
different layers are in different base projections or even just different Bounds
clauses.
Regards
Bob
__._,_.___ YAHOO! GROUPS LINKS
__,_._,___ |
Title: Message
- [mitab] Locating features in a particular area scumhampton
- Re: [mitab] Locating features in a particular area Daniel Morissette
- Re: [mitab] Locating features in a particular area Bob Young
- RE: [mitab] Locating features in a particular area Tim Smith
- Re: [mitab] Locating features in a particular a... Daniel Morissette
- RE: [mitab] Locating features in a particular area Tim Smith
- RE: [mitab] Locating features in a particular area Tim Smith
- Re: [mitab] Locating features in a particular a... Bob Young
- RE: [mitab] Locating features in a particular area Tim Smith
