Maptitude - http://research.umbc.edu/~roswell/maptitude.html
The evidence seems quite clear, Maptitude absolutely rocks with large
databases, but I'll add my two cents worth (three cents Canadian, oh well).
I work with postal code databases covering western Canada, total of 200,000
points (each point representing a Canadian six-digit postal code). I join
large census datasets to each point for market analysis in Maptitude, and
the program handles all I throw at it in what I consider to be very
acceptable execution times given the large amount of processing being done.
I'm using a AMD K6-2 333 machine, so nothing special on the hardware end
either.
I'm sure glad I found out about Maptitude (quite by accident), I wonder why
it doesn't have a higher profile than it does considering the amazingly
extensive features and data built into the package for the money. Thanks so
much, Caliper!
Murray Rice
Altavision Geographics
[EMAIL PROTECTED]
----- Original Message -----
From: "Health Maps" <[EMAIL PROTECTED]>
To: "Maptitude" <[EMAIL PROTECTED]>
Sent: Wednesday, February 07, 2001 4:00 PM
Subject: RE: [Maptitude] Maptitude vs. ArcView & mapinfo
> Maptitude - http://research.umbc.edu/~roswell/maptitude.html
>
> I have millions of death records for several NW states (points) and other
> layers of parcels, census blocks, rather large attribute databases with
> hundreds of variables, and I run these on a modest Pentium III. I have had
> no problem. I did try to do this in AV and its not possible. Too slow,
limit
> of 255 variables in the attribute data, etc.
>
> Richard Hoskins
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> GMT -8
>
>
> -----Original Message-----
> From: Carl Chance [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 07, 2001 12:51 PM
> To: Maptitude
> Subject: Re: [Maptitude] Maptitude vs. ArcView & mapinfo
>
>
> Maptitude - http://research.umbc.edu/~roswell/maptitude.html
>
> At 01:25 PM 2/7/01 +0000, you wrote:
> >Maptitude - http://research.umbc.edu/~roswell/maptitude.html
> >
> >Carl.
> >
> >I am interested about the limits to which Mapt can be pushed. I am about
> to
> >start
> >a large project, involving some 150000 parcels. In the last 5 years I
have
> >preferred maptitude over other GIS, and I would like to use it for this
> >project.
> >However, I do not know how well Maptitude would perform with such a large
> >database.
> >
> >In your experience, after digitizing the parcels, how did Mapt perform in
> >managing
> >(displaying, laoding, quetying) the database?
> >
> >Maybe the people at Caliper could provide some comments about actual
> >applications
> >of Mapt (or other of tbeir products) with large databases.
> >
______________________________________________________________________
To unsubscribe, write to [EMAIL PROTECTED]
