Title: Message
Hi Craig,

It really isn't the table's projection that's of interest when doing "create points". You can (and should) set the right projection for the X/Y values when running the function, regardless of the table's projection. Pro will reproject the data as needed when storing it in the table.

What version of Pro are you using ? If 8.0 or later, you can set your session's default projection, which will then be pre-chosen.

The reason your previous procedure worked, is that Pro (at least before 8.0, introduced in 5.x I think) has a built-in "short-circuit", that makes opening a mapper set the session projection to whatever the mapper's is, and a new mapper with just one table will use that table's projection. If you forget to open a mapper when opening your table, the previous session projection will prevail.


Best regards / Med venlig hilsen
Lars I. Nielsen
GisPro


Craig Westell wrote:
I'm wanting to bring together spatial data recorded by a variety of sources in a variety of mapping datums. When I've had to do this in the past I've simply written a new table for each datum set before importing into a workspace and updating to a new table in my preferred datum (GDA94). It seems a bit long winded. So this is my question: Is it possible to set mapinfo up to recognise the original datum (i imagine from a datum field) and convert accordingly rather than having to 'Create Points' manually? Would I be better off setting up a remote database and do the conversions outside MI before importing? Has anyone had a similar problem to work through?
 
many thanks
craig

_______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l


_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l

Reply via email to