Thank you one and all for solving my "Splits" on polygons problem and informing me on the form of Zip Code data. I am aware of the "99" suffix on Census Tracts that represent ships with live aboard crews, but I hadn't thought of Zip Codes as anything but polygons. Alas, there are many, many points which are, as many have said, Post Offices. Tim Rood -----Original Message----- From: Spencer Simpson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 19, 2001 12:32 PM To: Rood, Timothy; Mapinfo Mailing List Subject: Re: MI-L Slits on and by polygons "Timothy Rood" <[EMAIL PROTECTED]> wrote: > I'm getting one of those MI messages that doesn't seem to fit the > circumstances when I try to split a polygon soils layer with a polygon zip > code layer to derive a soils by zip code map. The message I get is "Cannot > split, erase or overlay with point or text objects." That may be the best MI > can do, but it doesn't make sense to me. Is this, perhaps, big file > limitation that cause MI to choke on this kind of operation? Are you sure that the zip code layer is ALL region objects? Since many ZIP codes are valid oonly at a post office, some entries in ZIP code databases will be points. MapInfo allows tables to contain a mixture of object types, and so some of its ZIP code products will be a mixture of point and region objects. To find out if there are records that aren't regions, select the rows from your ZIP code table where str$(obj)<>"Region" If any rows are selected, you need to make a new table that has only the region objects. Select the rows where str$(obj)="Region" and use "File -> Save Copy As..." to save them off to their own table. HTH Spencer _______________________________________________________________________ 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.
