RE: MI Converting Non-Earth N & E to a proper Projection N & E
Hi David There is a great tool that does that automatically on as many files you want (as well TAB) called "coordination". Look up: www.greatcircle.co.nz. Best regards Flavio *** REPLY SEPARATOR *** On 04.09.2000 at 17:18 David Booth wrote: >Hi Steve, > >The way to fix this problem is to export your non-earth table to mif/mid, >which preserves the coordinate values. Edit the header of the mif file and >replace the coordsys... line with the correct one for your projection, then >re-import the table. > >As you've found, using Save As with the correct projection doesn't work in >the case of NEM tables. > >Hope you haven't got too many to do - I ended up automating the procedure in >mapbasic after the first few hundred tables! > >- >David Booth >Senior GIS Officer >Merseyside Information Service > >> -Original Message- >> From:Steve McCrone [SMTP:[EMAIL PROTECTED]] >> Sent: 04 September 2000 08:12 >> To: [EMAIL PROTECTED] >> Subject: MI Converting Non-Earth N & E to a proper Projection N & E >> >> Hello Mappers: >> I have some vector (say polylines) data that was saved using: >> >> Non-Earth m, Bounds -10, -10, 10, 100. >> This was done since the PRJ file did not contain the appropriate >> projection parameters. >> >> The coordinates of the nodes of the plines are grid coordinates in the >> Rectified Skew Orthomorphic (RSO) projection. Therefore, when the user >> clicks the mouse on a feature, the correct E & N is displayed. >> >> The appropriate RSO projection parameters have been added to the PRJ file >> and now I wish to convert all of the existing data (in Non-Earth) to RSO. >> >> When I simply change the projection to RSO the data gets all messed up. I >> am able to write some Map Basic code that programmatically extracts the E >> & N from each node and stores them into an ASCII file. I then import these >> coordinates into MI and generate lines from the points. I also could write >> some MB code to create the new tables. >> >> Is there a simpler way of doing this? Perhaps without getting into MB >> programming at all. I am working in MapInfo 5.0 and MapBasic 4.1.2. >> >> Thanks >> >> >-- >To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put >"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED] xx Announcing the ultimate JavaScript Mapping Solution xx !!! Neapoljs: Live on http://www.mapserver.ch - Mit freundlichen Gruessen / Kind Regards Flavio Hendry- mailto:[EMAIL PROTECTED] TYDAC AG - http://www.tydac.ch Geographic Information Solutions Buristrasse 23 -- CH-3006 Bern Tel +41 (0)31 368 0180 - Fax +41 (0)31 368 1860 - MAPINFO Strategic Partner - PCI Reseller - FME Distributor - -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI Converting Non-Earth N & E to a proper Projection N & E
Hi My question was: > Hello Mappers: I have some vector (say polylines) data that was saved>using: Non-Earth m, Bounds -10, -10, 10,>100. This was done since the PRJ file did not contain the>appropriate projection parameters. & N is displayed. The appropriate RSO>projection parameters have been added to the PRJ file and now I wish to>convert all of the existing data (in Non-Earth) to RSO. & N from each node>and stores them into an ASCII file. I then import these coordinates into>MI and generate lines from the points. I also could write some MB code to>create the new tables. Is there a simpler way of doing this? Perhaps>without getting into MB programming at all. I am working in MapInfo 5.0>and MapBasic 4.1.2. Thanks The solution is: Save the file out as a MIF, and then edit the MIF header. Add the correctprojection parameters to the header. Then read the MIF back into MI.
Re: MI Converting Non-Earth N & E to a proper Projection N & E
> Steve McCrone wrote: > > Hello Mappers: > > I have some vector (say polylines) data that was saved using: > > Non-Earth m, Bounds -10, -10, 10, 100. > This was done since the PRJ file did not contain the appropriate > projection parameters. Hi Steve! Forget it, and find the original data and start over. With such a large Bounds, chances are that your original coordinates have been rounded off beyond recognition. The size of your coverage is 50 times the circumference of the globe, and the moon orbit would probably fit within it. And 'Save Copy As...' will NEVER work with nonearth data to earth data. Regards, Mats.E -- ::: :Email/ [EMAIL PROTECTED] ICQ#9517386 : :-: :Mail/ GISKRAFT, Mats Elfstroem, Vaepplingv 21, SE-227 38 LUND, SWEDEN: :Phones: +46 46 145959, +46 70 595 3935 : ::: -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
RE: MI Converting Non-Earth N & E to a proper Projection N & E
Hi Steve, The way to fix this problem is to export your non-earth table to mif/mid, which preserves the coordinate values. Edit the header of the mif file and replace the coordsys... line with the correct one for your projection, then re-import the table. As you've found, using Save As with the correct projection doesn't work in the case of NEM tables. Hope you haven't got too many to do - I ended up automating the procedure in mapbasic after the first few hundred tables! - David Booth Senior GIS Officer Merseyside Information Service > -Original Message- > From: Steve McCrone [SMTP:[EMAIL PROTECTED]] > Sent: 04 September 2000 08:12 > To: [EMAIL PROTECTED] > Subject: MI Converting Non-Earth N & E to a proper Projection N & E > > Hello Mappers: > I have some vector (say polylines) data that was saved using: > > Non-Earth m, Bounds -10, -10, 10, 100. > This was done since the PRJ file did not contain the appropriate > projection parameters. > > The coordinates of the nodes of the plines are grid coordinates in the > Rectified Skew Orthomorphic (RSO) projection. Therefore, when the user > clicks the mouse on a feature, the correct E & N is displayed. > > The appropriate RSO projection parameters have been added to the PRJ file > and now I wish to convert all of the existing data (in Non-Earth) to RSO. > > When I simply change the projection to RSO the data gets all messed up. I > am able to write some Map Basic code that programmatically extracts the E > & N from each node and stores them into an ASCII file. I then import these > coordinates into MI and generate lines from the points. I also could write > some MB code to create the new tables. > > Is there a simpler way of doing this? Perhaps without getting into MB > programming at all. I am working in MapInfo 5.0 and MapBasic 4.1.2. > > Thanks > > -- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
MI Converting Non-Earth N & E to a proper Projection N & E
Hello Mappers: I have some vector (say polylines) data that was saved using: Non-Earth m, Bounds -10, -10, 10, 100. This was done since the PRJ file did not contain the appropriate projection parameters. The coordinates of the nodes of the plines are grid coordinates in the Rectified Skew Orthomorphic (RSO) projection. Therefore, when the user clicks the mouse on a feature, the correct E & N is displayed. The appropriate RSO projection parameters have been added to the PRJ file and now I wish to convert all of the existing data (in Non-Earth) to RSO. When I simply change the projection to RSO the data gets all messed up. I am able to write some Map Basic code that programmatically extracts the E & N from each node and stores them into an ASCII file. I then import these coordinates into MI and generate lines from the points. I also could write some MB code to create the new tables. Is there a simpler way of doing this? Perhaps without getting into MB programming at all. I am working in MapInfo 5.0 and MapBasic 4.1.2. Thanks
