|
阅读：2082回复：2
[求助]有人提供一下e00文件详细说明！
本人近来在搞e00文件，想知道详细的文件说明，有没有人给俺提供一份说明？
|
|
|
|
1楼#
发布于：2005-01-27 12:51
<P>俺找到了一份，顺便发上来，共享</P><P>Arc/Info E00 FormatArc/Info Export (E00) Format Analysis
Original Author: Unknown Last Update: 2000-02-24, Daniel Morissette, <a href="mailtdanmo@videotron.ca" target="_blank" >danmo@videotron.ca</A> This is an updated version of the (world famous) "ANALYSIS OF ARC EXPORT FILE FORMAT FOR ARC/INFO (REV 6.1.1)" that has been around for quite a while. It was impossible to find the author of the original document, but a copy of the original can be downloaded from: <a href="http://www.geocities.com/~vmushinskiy/fformats/files/e00.txt" target="_blank" >http://www.geocities.com/~vmushinskiy/fformats/files/e00.txt</A> </P><P>TABLE OF CONTENTS 1. Introduction 2. Overall Organization 3. ARC File Formats 3.1 ARC 3.2 CNT 3.3 LAB 3.4 LOG 3.5 PAL 3.6 PRJ 3.7 SIN 3.8 TOL 3.9 TXT - Annotations 3.10 TX6/TX7 - Annotations 3.11 RXP 3.12 RPL 4. INFO File Formats 4.1 .AAT 4.2 .ACODE 4.3 .BND 4.4 .PAT 4.5 .PCODE 4.6 .TIC 5. Conclusion APPENDIX A: Sample Export File Before Topology APPENDIX B: Sample Export File After Polygon Topology APPENDIX C: Sample Export File After Line Topology APPENDIX D: Sample Export File for Point Coverage APPENDIX E: Sample Export File for Single-Precision Coverage APPENDIX F: Sample Export File for Double-Precision 1. INTRODUCTION Note: ESRI considers the export/import file format to be proprietary. As a consequence, the identified format can only constitute a "best guess" and must always be considered as tentative and subject to revision, as more is learned. It appears that all ARC/INFO files except user-created lookup tables are exported, including .ACODE and .PCODE. 2. OVERALL ORGANIZATION The export file begins with a line with three fields. 1- an initial 'EXP' 2- what appears to be a constant of '0' for uncompressed files, and 1 for compressed files (FULL or PARTIAL). 3- the pathname for the creation of the export file The export file ends with a line beginning 'EOS'. The ARC files are included first, in the following order (note that all these sections are not always present): ARC CNT LAB PAL PAR TOL TXT, TX6, TX7, ... SIN LOG PRJ RXP RPL Then the INFO files are included in alphabetical order (???not sure???). (There does not seem to be any real rule for the ordering of the INFO files, it probably depends on the version of Arc/Info that was used to generate the file. For instance, the .BND table sometimes comes first, but it also happens to come last with the .TIC...) The beginning of each ARC file is indicated by the file name (a three-character identifier) followed by ' 2' for single- precision or ' 3' for double-precision. Floating point values carry 8 digits (ex: -1.0000000E+02) in single-precision coverages, and 15 digits (ex: -1.19299887000023E+02) in double-precision coverages. However, there has to be an exception(!): double-precision floating point values inside INFO tables carry 18 digits (ex: -5.70000000000000000E+01). Each ARC file ends with a line of seven numbers beginning with a -1 and followed by six zeros, except the SIN, LOG, and PRJ files which end in 'EOX', 'EOL', and 'EOP', respectively. The LAB file uses a slight variation of this -1 ending line (see below). The format for each ARC file is specific to that type of file. These formats are covered below. TX6, TX7, RXP and RPL sections start with the usual "TX6 2", etc. line, and end with "JABBERWOCKY". These sections are divided in sub-sections (called "subclasses" in Arc/Info), each sub-section starts with a line with the name of the subclass, and end with the same "-1 0 0 0 0 0 0" line as the other ARC files (except for RXP sub-sections, which end with "-1 0" only). The beginning of the INFO file section is indicated by 'IFO 2', and its end is indicated by 'EOI'. The INFO files each begin with the file name. For example, the polygon attribute table would be 'STDFIG24C.PAT' on a line by itself. The format is the same for every INFO file. This format is given below. 3. ARC FILE FORMATS Formats will be given for the most common ARC files: ARC CNT LAB PAL PAR TOL TXT, TX6, TX7, ... SIN LOG PRJ RXP RPL 3.1 ARC The ARC (arc coordinates and topology) file consists of repeating sets of arc information. The first line of each set has seven numbers: 1. coverage# 2. coverage-ID 3. from node 4. to node 5. left polygon 6. right polygon 7. number of coordinates The subsequent lines of a set are the coordinates with two x-y pairs per line, if the coverage is single-precision. If there are an odd number of coordinates, the last line will have only one x-y pair. Double-precision puts one coordinate pair on each line. An example of an actual ARC section follows: ARC 2 1 2 2 1 1 2 2 3.4029994E+05 4.1001998E+06 3.4009988E+05 4.1002000E+06 2 3 3 2 3 2 2 3.4050000E+05 4.1001998E+06 3.4029994E+05 4.1001998E+06 3 1 1 4 1 2 4 3.4009988E+05 4.1002000E+06 3.4040006E+05 4.1003995E+06 3.4090012E+05 4.1002000E+06 3.4070003E+05 4.1001995E+06 4 4 4 3 4 2 2 3.4070003E+05 4.1001995E+06 3.4050000E+05 4.1001998E+06 5 6 3 4 4 3 3 3.4050000E+05 4.1001998E+06 3.4059997E+05 4.1001002E+06 3.4070003E+05 4.1001995E+06 6 7 4 5 1 3 3 3.4070003E+05 4.1001995E+06 3.4079997E+05 4.1000002E+06 3.4019978E+05 4.1000000E+06 7 5 5 2 1 3 2 3.4019978E+05 4.1000000E+06 3.4029994E+05 4.1001998E+06 -1 0 0 0 0 0 0 An example of a double-precision ARC section follows: ARC 3 1 0 0 0 0 0 7 3.40200000000000E+05 4.10000000000000E+06 3.40300000000000E+05 4.10020000000000E+06 3.40500000000000E+05 4.10020000000000E+06 3.40600000000000E+05 4.10010000000000E+06 3.40700000000000E+05 4.10020000000000E+06 3.40800000000000E+05 4.10000000000000E+06 3.40200000000000E+05 4.10000000000000E+06 2 0 0 0 0 0 4 3.40100000000000E+05 4.10020000000000E+06 3.40400000000000E+05 4.10040000000000E+06 3.40900000000000E+05 4.10020000000000E+06 3.40100000000000E+05 4.10020000000000E+06 -1 0 0 0 0 0 0 3.2 CNT The CNT (Polygon Centroid Coordinates) file contains the centroid of each polygon in the coverage. It has sets of centroid information with an initial coordinate line and, if there are labels, the label ids will follow, with up to 8 label ids per line. The coordinate line has three fields: 1- number of labels in polygon 2- centroid x 3- centroid y An example of an actual CNT section follows: CNT 2 0 3.4048516E+05 4.1001702E+06 1 3.4046691E+05 4.1002662E+06 1 1 3.4048875E+05 4.1000852E+06 2 0 3.4060000E+05 4.1001665E+06 -1 0 0 0 0 0 0 The following example shows centroids with more than one label attached to them: </P><P>CNT 2 0-1.1930000E+02 4.9150002E+01 1-1.1934029E+02 4.9169064E+01 1 13-1.1927331E+02 4.9168560E+01 2 3 4 5 6 7 8 9 10 11 12 13 14 1-1.1921005E+02 4.9199642E+01 15 -1 0 0 0 0 0 0 3.3 LAB The LAB (Label Points) section consists of repeating sets of label point information. The first line of each set has four numbers: 1. coverage-ID: Label User ID 2. Polygon ID: System ID of the polygon which encloses the label (or 0 in a point coverage) 3. x coordinate 4. y coordinate The second and final line of the set gives the label box window. This information is marked as marked as obsolete in the SDL documentation. It currently contains repetitions of the x and y coordinates. Note that the LAB section ends with a different '-1' line than the other files. An example of an actual LAB section follows: LAB 2 1 2 3.4046650E+05 4.1002668E+06 3.4046650E+05 4.1002668E+06 3.4046650E+05 4.1002668E+06 2 3 3.4048869E+05 4.1000852E+06 3.4048869E+05 4.1000852E+06 3.4048869E+05 4.1000852E+06 -1 0 0.0000000E+00 0.0000000E+00 An example of a double-precision LAB section follows: LAB 3 1 2 3.40500000000000E+05 4.10006225000000E+06 3.40500000000000E+05 4.10006225000000E+06 3.40500000000000E+05 4.10006225000000E+06 2 3 3.40468812500000E+05 4.10026225000000E+06 3.40468812500000E+05 4.10026225000000E+06 3.40468812500000E+05 4.10026225000000E+06 -1 0 0.00000000000000E+00 0.00000000000000E+00 Labels are usually linked to the .PAT (Point or Polygon Attribute Table) file and the way LAB entries relate to .PAT records depends on the type of coverage. In a POINT COVERAGE, the polygon ID in each label entry will always be 0 and in this case there would be a 1 to 1 relationship between the LAB entries and the .PAT records. I.E. Label#1 would correspond to .PAT record#1, etc... In a POLYGON COVERAGE, labels are attached to polygons (PAL section) and their centroids, (CNT section), which are all linked to the .PAT table. In this case, the second value in a LAB entry is the associated polygon ID and can also be used as the 1-based record index in the .PAT table. Also note that in a polygon coverage, there can be 0, 1 or more labels attached to each polygon. So we cannot assume that there is always a 1 to 1 relationship between labels and polygons. Here is a portion of a E00 LAB section and the associated .PAT file: LAB 2 3027 2-1.5342091E+02 5.7450005E+01 -1.5342091E+02 5.7450005E+01-1.5342091E+02 5.7450005E+01 3063 3 1.0056972E+01 5.7236324E+01 1.0056972E+01 5.7236324E+01 1.0056972E+01 5.7236324E+01 12092 4-1.6142227E+02 5.5626617E+01 -1.6142227E+02 5.5626617E+01-1.6142227E+02 5.5626617E+01 12091 5-1.6280910E+02 5.5155094E+01 -1.6280910E+02 5.5155094E+01-1.6280910E+02 5.5155094E+01 12090 6-1.6383534E+02 5.4822258E+01 -1.6383534E+02 5.4822258E+01-1.6383534E+02 5.4822258E+01 3680 7-1.3228665E+02 5.3464508E+01 -1.3228665E+02 5.3464508E+01-1.3228665E+02 5.3464508E+01 ... ... COUNTRY.PAT XX 4 4 16 270 AREA 4-1 14-1 12 3 60-1 -1 -1-1 1- PERIMETER 4-1 54-1 12 3 60-1 -1 -1-1 2- COUNTRY# 4-1 94-1 5-1 50-1 -1 -1-1 3- COUNTRY-ID 4-1 134-1 5-1 50-1 -1 -1-1 4- -2.1156395E+04 5.6565942E+03 1 0 9.2814314E-01 5.3587232E+00 2 3027 8.4326690E-01 5.9903331E+00 3 3063 6.9115734E-01 4.9834957E+00 4 12092 1.0414843E-01 1.2769473E+00 5 12091 5.7765609E-01 4.0451255E+00 6 12090 ... ... </P> |
|
|
|
2楼#
发布于：2005-01-27 12:59
我今天不能上传了，我明天再把文档传上来吧，上面的仅仅是一部分。
|
|
|