Information Conversion .


20 views
Uploaded on:
Description
2/15/2012
Transcripts
Slide 1

Information Conversion POEC 6382 Applied GIS Software

Slide 2

Conversion Commands From Interchg record organize • To Interchange document arrange import – send out From Shapefile • To Shapefile shapearc – arcshape From Census data • To Census information tigerarc – arctiger tigertool From another GIS • To another GIS dlgarc (.dlg) – arcdlg dxfarc (.dxf) – arcdxf igdsarc (.dgn) – arcigds igesarc (.ige) – arciges etakarc ( From DBASE to INFO • To DBASE from INFO dbaseinfo – infodbase There are numerous others—go to ArcDoc under "Information Conversion"for points of interest POEC 6382 Applied GIS Software

Slide 3

Arc Interchange File Format Interchange File Format (postfix .e00) allows simple transportation to another stage running Arc/INFO. A trade document contains all scope data and proper INFO record data in a settled length, ASCII design. Can move an exchange document, and in addition download it from the web. Send out - changes over a scope, document or other bolstered informational collection to exchange record organize Arc: trade cover urban communities urban areas (prefix just, postfix will be included) Will change over a scope named urban areas to a fare document, cities.e00 IMPORT - reproduce the scope, document or other upheld informational index from a sent out exchange record. Bend: import cover urban areas urban communities changes over an exchange document cities.e00 to a scope named urban communities The utility IMPORT71 which accompanies ArcView can likewise be utilized to change over .e00 records to inclusions, so you don\'t need to have ArcInfo to utilize .e00 POEC 6382 Applied GIS Software

Slide 4

COVERAGE TO SHAPE ARCSHAPE - composes include credits or INFO records to another shape information document ARCSHAPE <in_cover> <in_feature_class> <out_shape_file> SHAPEARC - composes shapefile spatial and ascribe data to an ARC/INFO scope. shapearc <in_shape_file> <out_cover> {out_subclass} Problems with polygons - Shape polygon elements are changed over into REGIONS in light of the fact that "there is no real way to safeguard that polygon shape highlights don\'t cover" (i.e., shape documents don\'t have topology). On the off chance that polygon topology is required, give an out_subclass name so that your properties will be put away in the district subclass table which will be named: <out_cover>.pat{out_subclass}. At that point the REGIONPOLY summon is utilized to reproduce the polygons. POEC 6382 Applied GIS Software

Slide 5

A Note on Regions An approach to speak to more perplexing components The islands of Hawai (numerous polygons) as one district House, carport, horse shelter building impressions at one address as one locale States of US as 50 districts, each with their provinces as inside polygons (external limit is then the same for states and its fringe regions) Overlapping territories, for example, untamed life living spaces covering with land utilize sorts Regions are taken care of as a unique "element class" (or subclass), similarly as circular segments, polygons, and so forth are highlight classes There are around 25 orders for making and preparing areas! Since shape documents are not completely topological, ArcInfo does not know whether polygons cover, hence it makes areas while changing over shapefiles with polygons to inclusions REGIONPOLY is the summon which changes over districts into polygons POEC 6382 Applied GIS Software

Slide 6

REGIONPOLY changes over a locales subclass into a polygon scope and makes an INFO table containing covering district data. makes the polygon scope by playing out a REGIONCLEAN on the locale scope to kill superfluous polygons. RESELECT is then used to choose just those polygons related with the locale subclass. DROPFEATURES is utilized to drop locale subclasses from the out_cover. In the event that the <in_cover> does not have name focuses, CREATELABELS is utilized to add name focuses to the <out_cover>. REGIONPOLY includes some additional fields (subclass, subclass#, rings_ok, rings_nok) to your .pat. To dispose of these utilization DROPITEM. REGIONPOLY <in_cover> <out_cover> <in_subclass> {out_table} POEC 6382 Applied GIS Software

Slide 7

Steps for SHAPEARC with polygons Example for shape record named TRACTS.shp (a shape document with this name containing enumeration tracts for Plano is in the p:\p6382\ex4 envelope) SHAPEARC <in_shape_file> <out_cover> {out_subclass} arc: SHAPEARC tracts class arc: LC (rundown of inclusions ought to incorporate TRACTS) arc: DIR INFO (take note of that there is no tracts.pat, yet there is a tracts.pat class CLEAN <in_cover> {out_cover} {dangle_length} {fuzzy_tolerance} { POLY | LINE} (this will reproduce the polygons) arc: CLEAN tracts tractsC .01 poly (dependably give cleaned adaptation another name) arc: DIR INFO (now have a .pat record) arc: ITEMS tracts.pat (notwithstanding, no property information) REGIONPOLY <in_cover> <out_cover> <in_subclass> {out_table} arc: REGIONPOLY statesc state class (class.tbl contains data about the old districts) arc: ITEMS tracts.pat (now have trait information, yet additional garbage factors) DROPITEM <in_info_file> <out_info_file> {item … item} (this is discretionary) arc: DROPITEM state.pat subclass# rings_ok rings_nok arc: ITEMS tracts.pat (now have recently the information things we needed) (Note: ArcToolbox and ArcCatalog changes join the greater part of the above strides) POEC 6382 Applied GIS Software

Slide 8

Conversion Commands - Tiger/LINE TIGERARC - changes over from Census TIGER/Line documents to Arc/INFO organize ARCTIGER - changes over from Arc/INFO into TIGER/Line format TIGERTOOL - runs the TIGERARC charge and after that procedures the yield by consolidating zone point components and line highlights into one coordinated polygon scope. POEC 6382 Applied GIS Software

Slide 9

CONVERSION FROM OTHER GIS dlgarc - Converts from USGS Digital Line Graph (DLG) configuration to Arc/INFO arrange arcdlg - Converts from Arc/INFO to DLG dxfarc - Converts Autocad DXF (computerized trade organization) to Arc/INFO dxfinfo - Describes the substance of a DXF record arcdxf - Converts from Arc/INFO to DXF organize igdsarc - Converts from Intergraph\'s Interactive Graphics Design Software (IGDS) and MicroStation Design configuration to Arc/INFO. - these records have a .dgn expansion igdsinfo - Describes substance of IGDS document arcigds - Converts from Arc/INFO to IGDS igesarc - Converts from Initial Graphics Exchange Specification (IGES) to Arc/INFO arciges - Converts from Arc/INFO to IGES etakarc - Converts from Etak MapBase record to Arc/Info There are numerous others—go to ArcDoc under "Information Conversion"for points of interest POEC 6382 Applied GIS Software

Slide 10

Conversion from Other GIS (e.g .dxf) LAYERS DXF arrange documents, for instance, may have up to 999 "layers" of vector information. This is run of the mill of CAD records. Utilize the summon dxfinfo (for .dxf) or igdsinfo ( for .dgn) to get rundown of layers shapefiles and inclusions regularly contain just a single kind of information—for instance, boulevards, railways, and hydrologic elements would each be a different scope However, it is conceivable to store numerous line and point includes in a solitary scope, utilizing a thing field (dxf-layer) to separate the layers. For the most part, while changing over CAD records, (for example, .dxf), you have two options: Convert all layers to one scope and utilize a thing variable to separate them (utilize the $REST choice; the thing dxf-layer will separate the layers) Convert every layer to its own scope, by either Create one scope as above and after that reselect on dxf-layer to re-make isolate ones Use discourse in dxfarc (or ArcToolbox wizard) to change over every layer to separate inclusions POEC 6382 Applied GIS Software

Slide 11

Conversion from Other GIS (e.g. .dxf) (contd.) ATTRIBUTE DATA Some changed over inclusions (for instance, those from dxf and dgn positions) have INFO documents containing properties for the scope that are not naturally joined to the scope. These INFO documents can be seen with Arc: dir data order. The qualities are put away in <cover>.acode INFO petition for highlight class circular segment <cover>.pcode INFO petition for highlight class poly <cover>.xcode INFO petition for highlight class point. Utilize the JOINITEM charge to join the INFO record to the cover, utilizing <cover>- id as the <relate_item> Note that TIGERTOOL and the change wizards in ArcToolbox do the joinitem for you POEC 6382 Applied GIS Software

Slide 12

AutoCAD .dxf Example Key83.dxf, the document to be changed over, is in p:\poec6382\ex4  &watch dxfarc.wat (valuable for review yield from dxfinfo beneath) Display the dxf document—take note of the numerous layers Arc: ap Arcplot: mape dxf key83.dxf Arcplot: dxf key83.dxf Arcplot: quit Display information about dxf record layers—once more, note the mutiple layers Arcplot: dxfinfo key83.dxf (gives data about the dxf layers— does not incognito to INFO) Convert Arc: Dxfarc key83.dxf Enter the first layer and choices: $rest (changes over all layers) View Results arc: dir information key83.acode (curve highlights) key83.xcode (point highlights—content comment for this situation) Note: no .aat or .pat document) POEC 6382 Applied GIS Software

Slide 13

AutoCAD .dxf Example (contd) Join Attribute information bend: manufacture key83 lines Arc: dir data (there is currently an .aat record.) Arc: things key83.aat (in any case, no trait information in .aat record) Arc: list key83.acode (this is the place the property information is - - take note of the dxf-layer variable which distinguishes the layer - - utilize dxf-layer to part into independent inclusions circular segment: joinitem key83.aat key83.acode key83.aat key83-id (adds credit information to .aat file)  Separate o

Recommended
View more...