My company conducts real estate market feasibility, primarily for
multifamily development and we are trying to establish a system to use GPS
to do our apartment maps using MapInfo and Access. We have established a
process to get lat/lons from the handheld GPS directly into Access, which we
use for our apartment analysis and data aggregation. Because the Access DB
is so large, we would prefer not to have our GIS specialist not work
directly with this large database, but rather a subset of the data
specifically for each project we use. In Access, the lat/lons are defined
as Number, Double, with 10 decimal places.
Our database programmer has designed an export procedure, but we have two
problems:
1) if he exports it as a comma delimited file for import into MapInfo, the
lat/lons are imported as a character field, so our GIS specialist has to
save a copy of the file, open the copy and then change the field type using
Table--Maintenance in order to generate the points.
2) if he exports it from Access as an Excel file, Excel seems to natively
recognize the fields with only 2 decimal places, despite the definition in
Access. Even if we change the number format to 10 decimal places in Access,
when we import this table into MapInfo, MI truncates the lat/lons to three
decimal places, and even then in a seemingly random manner (sometimes there
are only 2 decimal places).
Our goal is to pushbutton this as much as possible so that all our GIS
specialist has to do is open the file in MI and generate the points. What
are we doing wrong here?
Greg Grant
Webmaster/Utility Infielder
The Danter Company: National leaders in real estate research
http://www.danter.com
_______________________________________________________________________
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, send e-mail to [EMAIL PROTECTED] and
put "unsubscribe MapInfo-L" in the message body.
