Maptitude - http://research.umbc.edu/~roswell/maptitude.html
Besides the other suggestions, you will want to modify the table (Dataview >
Modify Table) to change all of the integer field types to 4 byte integers.
Otherwise, when the program adds up each field it will return garbage data
if/when the value exceeds the ability of the 1 and 2 byte datafields to hold
it (I know this through experience).
Note that the only real number definitions in the census block group map
fields seem to be AREA, "Land Area", "Water Area", "Lowmod %", "% in
Sample", "Med Rent % of HH Inc", "HU Mtg Own Costs: %inc", and "HU n/Mtg Own
Cost: %inc" Perhaps changing these to integers will solve your problem?
Jim
kbyrnes wrote:
> Maptitude - http://research.umbc.edu/~roswell/maptitude.html
>
> I'm working with a state-wide data file of block group data involving
> approx. 3,400 BGs. I have tagged all the BGs with another geographic
> code and am attempting to aggregate BG data for the new tagged geography
> (e.g. 26 regional watershed polygons). Whether I choose a user-defined
> aggregation method or accept the default aggregation type, I get the
> same result....a fatal "floating point error" which crashes the system.
> I assume this may be the result of calculating averages where the
> attempted arithmetic involves a division by zero. Does anyone have a
> suggestion of a solution/work-around, etc? I only really care about
> aggregating population counts or projections for selected older cohorts
> to get a feel for the older demographics of each watershed.
>
> Any suggestions from more-informed Maptitude users would be appreciated.
>
> Kevin Byrnes, Demographer
> Va. Dept. for the Aging
>
______________________________________________________________________
To unsubscribe, write to [EMAIL PROTECTED]
