decimal points

932 views
Skip to first unread message

Hankins, Michael D.

unread,
May 29, 2009, 4:18:23 PM5/29/09
to mapi...@googlegroups.com
I spent weeks geocoding records for my company. MapMarker Plus 9.2 goes
out five and six decimal places on the tables I geocoded. I open the
same table in MapInfo 9.0 and it truncates it to 4 decimal places, even
though the column is listed as float. Have I lost the values out to six
decimals or is MapInfo just hiding them? I export to text file and it
is only 4 decimal there too. Any help or suggestions would be
appreciated.

Michael Hankins
Actuarial Services Analyst
COUNTRY(r) Financial

Tony Pilkington

unread,
May 30, 2009, 1:51:03 AM5/30/09
to mapi...@googlegroups.com
The values are still held as 'floats' and so have lost no value. Try
altering the type to decimal (12,6).

David R Sherrod

unread,
May 30, 2009, 1:32:37 PM5/30/09
to mapi...@googlegroups.com
Michael, Tony is correct.  MapInfo doesn't bother its browser window with all the details, so it clips the values for viewing purposes only.  Nothing is lost from FLOAT, but on export the text file contains nothing more than what is seen in the browser window.

This is a sporadic issue for me, too, because I commonly need to gather info from a map and then take it to the field with me, hard-copy style.  Example: perhaps I need to find a benchmark that I set in a terrain undergoing rapid landscape changes.  If I can get within ten meters, using handheld GPS, I can always sniff the benchmark or recognize the detritus from the installation.

If you want to preserve decimal places, then TABLE-->Table Structure-->Maintenance, and within that pulldown you can reformat the columns. (I'm not in M.I. right now, so the actual pulldown sequence may differ from my memory.) In Tony's example, the 12 is column width, which accounts for the decimal places but also for the decimal point, the integral values for lat-long, and the minus sign (depending on where you're working, geographically).  Thus (12,6) is a handy coding.  If your data is gathered originally by handheld GPS, then you needn't show precision greater than 3 decimal places, although 4 always makes a person feel better.  Most of us try to preserve the precision of original data, regardless.

Anecdotally, when printing for field visits, I modify tables to create columns for metric coordinates. My boots have a better grasp of meters than decimal degrees for distance to travel.

Dave Sherrod
-----------------------------------------

-----mapi...@googlegroups.com wrote: -----

To: <mapi...@googlegroups.com>
From: "Tony Pilkington" <a.j.pil...@talk21.com>
Sent by: mapi...@googlegroups.com
Date: 05/29/2009 10:51PM
Subject: [MI-L] Re: decimal points

Hankins, Michael D.

unread,
Jun 1, 2009, 8:22:48 AM6/1/09
to mapi...@googlegroups.com

Thank you Tony and David.  Changing from float to decimal will be a snap compared to re-running everything. 

 

Mike

 


Reply all
Reply to author
Forward
0 new messages