> I'm going off at a bit of a tangent here so I thought I'd send this off > list. I agree ESRI Arc/Info can be a killer > but some things can be done to minimise stuff. We have what we call a > spectrum of functionality going from simple map imaging on a web page > through ArcView to full Arc/Info and we strive to drive tasks towards the > simple end reducing the scale of all sorts of problems . In our world we > also find that often the great majority of the GIS data is only > needed to be > read so we have this all widely available and catalogued on the network > leaving only the data being actively work with on the local machines.
Nigel, thanks for the comments. Yes, I'm sure there is things we could do to minimize Arc/Info headaches. Our biggest problem is that we don't keep data long enough to really build a good structure. We are a consulting company and work with a variety of data structures. I think the biggest problem we run into isn't errors over then net, it's the speed issue. We have serveral simulation models and amls that take forever to run over the network. Actually, I have an aml that you might find interesting. We created an aml to perform arc-arc interections. For example, I can take two arc covers and intersect them creating a point cover who's attribute table is a combination of both arc covers... regards, Greg Zartman -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
