Maptitude - http://research.umbc.edu/~roswell/maptitude.html Mike: We usually do a lot of import from Shape here, and to round off your success, I can recommend to export as lines (Tools, Line/Area conversion) and then back again from lines into polygons, then all the duplicates segments will be removed by Maptitude (am I correct Peter?). If the original file is too wrong, we get better results while exporting to another format (in that case use just Tools, Export) different from the one that has the offending objects (almost always the cause of the error is bad topology, not required by ArcView; try ArcInfo, or AtlasGIS). Then, if you have attributes, you will have to export the Geocodification separately, as centroids, and then built it up again using Fill, Tag in the dataview. You can use one of the above steps to export or import in the correct projection/coordinate system as well. Good luck! Reinaldo Michael Powell wrote: > Maptitude - http://research.umbc.edu/~roswell/maptitude.html > > Peter: > Thanks for your response. You were right (as usual). > By "un-checking" the box the shapefile was > successfully imported. Of course, I fouled up the > projection so the city is now in no-where land and is > 10 times its correct size, but that's my problem. > Thanks for your help. > > Mike > --- "Peter H. Van Demark" <[EMAIL PROTECTED]> wrote: > > Maptitude - > > http://research.umbc.edu/~roswell/maptitude.html > > > > Mike: > > > > >Recently I tried to open/import ArcView shapefiles > > in > > >Maptitude 4.1. Some of the files opened (and > > >converted to .dbd) fine, but two larger ones > > returned > > >an error message and could not be opened. FYI, one > > of > > >the shapefiles had about 225,000 records and 75 > > >fields. The file size was about 19 megs. Has > > anyone > > >had a similar experience, could it be due to the > > size > > >of the files, and is there a way to fix the > > problem? > > > > Were they areas? If so, the default is to build > > topology. By removing the > > check from the Eliminate duplicate boundary lines > > box, the areas will be > > imported as polygons, which requires far less > > processing and memory. There > > will only be a few things that you cannot do with a > > non-topological .DBD > > file, such as merging by value. > > > > Peter > > > > > ---------------------------------------------------------------- > > Peter Van Demark > > Director of GIS Products and Training Phone: > > 617-527-4700 > > Caliper Corporation Fax: > > 617-527-5113 > > 1172 Beacon Street E-mail: > > [EMAIL PROTECTED] > > Newton MA 02461-9926 Web site: > > http://www.caliper.com > > > > > > > ______________________________________________________________________ > > To unsubscribe, write to > [EMAIL PROTECTED] > > __________________________________________________ > Do You Yahoo!? > Get email at your own domain with Yahoo! Mail. > http://personal.mail.yahoo.com/?.refer=text > > ______________________________________________________________________ > To unsubscribe, write to [EMAIL PROTECTED] ______________________________________________________________________ To unsubscribe, write to [EMAIL PROTECTED]
begin:vcard n:P�rez Machado;Reinaldo Paul x-mozilla-html:FALSE url:www.igasageo.com.br org:IGASA Geoprocessamento Ltda. version:2.1 email;internet:[EMAIL PROTECTED] title:Director President adr;quoted-printable:;;Rua Marqu=EAs de Itu 70, Conj. 41=0D=0AVila Buarque;S�o Paulo;SP;01223-000;Brasil x-mozilla-cpt:;-16512 fn:Reinaldo Paul P�rez Machado end:vcard
