Related to what Steve states below, the map can visually appear to line up,
but your spatial analysis queries will be wrong. I have seen situations
where you place a point inside of a polygon, but a Contains query insists it
is not actually in the polygon. After much swearing, I put all of the
displayed layers in the same projection and the query worked.
If you are not careful about your projections, this can bite you
unexpectedly.
- Brad
> -----Original Message-----
> From: Steve Wallace [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 31, 2000 9:11 AM
> To: Spencer Simpson; Mapinfo Mailing List
> Subject: Re: MI How does MapInfo handles muliple Projections in the
> same window?
>
>
> ----- Original Message -----
> From: "Spencer Simpson" <[EMAIL PROTECTED]>
> To: "Mapinfo Mailing List" <[EMAIL PROTECTED]>
> Sent: Thursday, August 31, 2000 11:21 AM
> Subject: Re: MI How does MapInfo handles muliple Projections in the same
> window?
>
>
> ... [snip]
>
> > There is one other consideration: The datum transformation the MapInfo
> uses
> > most of the time is simple and (relatively) fast, but fairly inaccurate.
> If
> > your layers are in projections based upon different datums, they might
> not
> > line up *perfectly*. You will have to decide if you can live with the
> > inaccuracy.
>
> Spencer is right here (of course!), and don't forget that they also may
> not
> line up right if you have data with different bounds clauses.
>
> Steve Wallace
> Vice President, Operations
> Florida Farm Bureau Insurance Co's
>
> ----------------------------------------------------------------------
> To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
> "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
