|
阅读：4293回复：19
[求助]请问e00是什么文件阿？
各位大虾请问e00是什么文件格式？有什么软件打开？
|
|
|
1楼#
发布于：2004-06-15 10:08
<FONT size=2><FONT color=#cc0033>E00</FONT> 是ESRI 的一
种过渡<FONT color=#cc0033>文件格式</FONT></FONT> |
|
|
2楼#
发布于：2004-06-17 18:56
<P>文本格式的,可以直接看.</P>
|
|
|
3楼#
发布于：2004-06-18 09:13
你看看ARCGIS就知道了
|
|
|
4楼#
发布于：2004-06-18 16:36
<DIV>E00是ESRI的一中交换格式，其导出是有两种，一种为非压缩格式，用写字板即可打开，为文本文件，另一种为压缩格式，打开后为乱码。</DIV>
|
|
|
5楼#
发布于：2004-06-21 11:23
E00 在ARCINFO， ARCVIEW， ERADS IMAGINE 中可以直接读去，MAPGIS， MAPINFO ，PCI 中好象也提供了转化工具
|
|
|
6楼#
发布于：2004-06-29 22:46
<P>E00文件格式：</P><CENTER><H1>Arc/Info Export (E00) Format Analysis</H1></CENTER><P><CENTER>Original Author: Unknown
Last Update: 2000-02-24, <I>Daniel Morissette, <a href="mailtdanmo@videotron.ca" target="_blank" >danmo@videotron.ca</A></I></CENTER><P>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: <P><CENTER><a href="http://www.geocities.com/~vmushinskiy/fformats/files/e00.txt" target="_blank" >http://www.geocities.com/~vmushinskiy/fformats/files/e00.txt</A> </CENTER><P><HR width="50%"><P><P><H2>TABLE OF CONTENTS</H2><P><UL><LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#INTRO" target="_blank" >1. Introduction</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#OVERALL" target="_blank" >2. Overall Organization</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#ARC_FILES" target="_blank" >3. ARC File Formats</A> <UL><LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#ARC" target="_blank" >3.1 ARC</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#CNT" target="_blank" >3.2 CNT</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#LAB" target="_blank" >3.3 LAB</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#LOG" target="_blank" >3.4 LOG</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#PAL" target="_blank" >3.5 PAL</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#PRJ" target="_blank" >3.6 PRJ</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#SIN" target="_blank" >3.7 SIN</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#TOL" target="_blank" >3.8 TOL</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#TXT" target="_blank" >3.9 TXT - Annotations</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#TX6" target="_blank" >3.10 TX6/TX7 - Annotations</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#RXP" target="_blank" >3.11 RXP</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#RPL" target="_blank" >3.12 RPL</A> </LI></UL><LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#INFO_FILES" target="_blank" >4. INFO File Formats</A> <UL><LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#AAT" target="_blank" >4.1 .AAT</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#ACODE" target="_blank" >4.2 .ACODE</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#BND" target="_blank" >4.3 .BND</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#PAT" target="_blank" >4.4 .PAT</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#PCODE" target="_blank" >4.5 .PCODE</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#TIC" target="_blank" >4.6 .TIC</A> </LI></UL><LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#CONCLUSION" target="_blank" >5. Conclusion</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#APP_A" target="_blank" >APPENDIX A: Sample Export File Before Topology</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#APP_B" target="_blank" >APPENDIX B: Sample Export File After Polygon Topology</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#APP_C" target="_blank" >APPENDIX C: Sample Export File After Line Topology</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#APP_D" target="_blank" >APPENDIX D: Sample Export File for Point Coverage</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#APP_E" target="_blank" >APPENDIX E: Sample Export File for Single-Precision Coverage</A> <LI><a href="http://pages.infinit.net/danmo/e00/docs/v7_e00_cover.html#APP_F" target="_blank" >APPENDIX F: Sample Export File for Double-Precision</A> </LI></UL><P><H2><A>1. INTRODUCTION</A></H2><P>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. <P>It appears that all ARC/INFO files except user-created lookup tables are exported, including .ACODE and .PCODE. <P><H2><A>2. OVERALL ORGANIZATION</A></H2><P>The export file begins with a line with three fields. <P><UL><LI>1- an initial 'EXP' <LI>2- what appears to be a constant of '0' for uncompressed files, and 1 for compressed files (FULL or PARTIAL). <LI>3- the pathname for the creation of the export file </LI></UL><P>The export file ends with a line beginning 'EOS'. <P>The ARC files are included first, in the following order (note that all these sections are not always present): <UL><LI>ARC <LI>CNT <LI>LAB <LI>PAL <LI>PAR <LI>TOL <LI>TXT, TX6, TX7, ... <LI>SIN <LI>LOG <LI>PRJ <LI>RXP <LI>RPL </LI></UL><P>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...) </P><P>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). <P>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. <P>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). <P>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. </P> |
|
|
|
7楼#
发布于：2004-06-29 22:47
<H2><A>3. ARC FILE FORMATS</A></H2><P>Formats will be given for the most common ARC files: <P><UL><LI>ARC <LI>CNT <LI>LAB <LI>PAL <LI>PAR <LI>TOL <LI>TXT, TX6, TX7, ... <LI>SIN <LI>LOG <LI>PRJ <LI>RXP <LI>RPL </LI></UL><P><H3><A>3.1 ARC</A></H3><P>The ARC (arc coordinates and topology) file consists of repeating sets of arc information. The first line of each set has seven numbers: <P><UL><LI>1. coverage# <LI>2. coverage-ID <LI>3. from node <LI>4. to node <LI>5. left polygon <LI>6. right polygon <LI>7. number of coordinates </LI></UL><P>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. <P>An example of an actual ARC section follows: <P><UL><PRE>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</PRE></UL><P>An example of a double-precision ARC section follows: <P><UL><PRE>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</PRE></UL><P><H3><A>3.2 CNT</A></H3><P>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. <P>The coordinate line has three fields: <P><UL><LI>1- number of labels in polygon <LI>2- centroid x <LI>3- centroid y </LI></UL><P>An example of an actual CNT section follows: <P><UL><PRE>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</PRE></UL><P>The following example shows centroids with more than one label attached to them: <P><UL><PRE>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</PRE></UL><P><H3><A>3.3 LAB</A></H3><P>The LAB (Label Points) section consists of repeating sets of label point information. The first line of each set has four numbers: <P><UL><LI>1. coverage-ID: Label User ID <LI>2. Polygon ID: System ID of the polygon which encloses the label (or 0 in a point coverage) <LI>3. x coordinate <LI>4. y coordinate </LI></UL><P>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. <P>Note that the LAB section ends with a different '-1' line than the other files. <P>An example of an actual LAB section follows: <P><UL><PRE>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</PRE></UL><P>An example of a double-precision LAB section follows: <P><UL><PRE>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</PRE></UL><P>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. <P>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... <P>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. <P>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. <P>Here is a portion of a E00 LAB section and the associated .PAT file: <UL><PRE>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 270AREA 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......</PRE></UL><P><P><H3><A>3.4 LOG</A></H3><P>The LOG (Coverage History) file contains a free form set of lines of indeterminate number which are separated by lines which begins with a tilde, "~". <P>ARC records many commands and their resource impacts in this file. The standard ARC format for writing in the LOG has nine fields: <P><UL><LI>Year (I4) <LI>Month (I2) <LI>Day (I2) <LI>Hours (I2) <LI>Minutes (I2) <LI>Connect Time in minutes (I4) <LI>CPU Time in seconds (I6) <LI>I/O Time in seconds (I6) <LI>Command line (A100) </LI></UL><P>However, any information can be added to the LOG file in free- form format. <P>An example of an actual LOG section follows: <P><UL><PRE>LOG 219940118 849 0 3 35export cover landli stdfigc none~19940118 850 0 7 190clean landli landlicp # # poly~EOL</PRE></UL>
|
|
|
|
8楼#
发布于：2004-06-29 22:48
<H3><A>3.5 PAL</A></H3><P>The PAL (Polygon Topology) file consists of repeating sets of polygon information. For single-precision, the first line of each set has five numbers: <P><UL><LI>1. number of arcs in polygon <LI>2. x min of polygon <LI>3. y min of polygon <LI>4. x max of polygon <LI>5. y max of polygon </LI></UL><P>The subsequent lines of a set give information on the arcs which comprise the polygon. There are three numbers per arc with information for two arcs per line. <P><UL><LI>1. Arc_Id (negative if reversed) <LI>2. From_Node_Id (if arc is reversed, then this is the arc's To_Node_Id) <LI>3. Adjacent_Polygon_Id (Id of the polygon that shares this arc with the current polygon) </LI></UL><P>The first polygon given is the universal polygon. <P>"The PAL file contains the polygon topology for a coverage and min-max boxes for the polygons. For each polygon in a coverage the PAL file has a (usually) clockwise list of the arcs, nodes that comprise the polygons, as well as the adjacent polygons, and a min-max box. To keep a continuous list, 'virtual' arcs with arc# of 0 are used to connect to holes (thus forming donuts), which are connected in counter-clockwise order. The PAL file is a random access, variable record length file, with the length dependent on the number of arcs surrounding the polygon (1 to 10000). <P>The arc# in the PAL file is the record number of that arc within the coverage's ARC file, the node# is the same as the node# in the arc file at the appropriate end, and the polygon# is the record number of that polygon within the coverage's PAL file. The PAL file record number for a polygon is the same as the PAT file record number and the CNT file record number." SDL documentation, July 1989, p. 24. <P>An example of an actual PAL section follows: <P><UL><PRE>PAL 2 5 3.4009988E+05 4.1000000E+06 3.4090012E+05 4.1003995E+06 0 0 0 -1 1 2 -7 2 3 -6 5 3 -3 4 2 4 3.4009988E+05 4.1001995E+06 3.4090012E+05 4.1003995E+06 1 2 1 3 1 1 4 4 4 2 3 3 4 3.4019978E+05 4.1000000E+06 3.4079997E+05 4.1001998E+06 -2 2 2 5 3 4 6 4 1 7 5 1 2 3.4050000E+05 4.1001002E+06 3.4070003E+05 4.1001998E+06 -4 3 2 -5 4 3 -1 0 0 0 0 0 0</PRE></UL><P>An example of a double precision PAL section follows: <P><UL><PRE>PAL 3 375-1.80000000000000E+02-9.00000000000000E+01 1.80000000000000E+02 8.35960388183594E+01 0 0 0 304 401 242 0 0 0 -305 399 241......... 2-1.80000000000000E+02 6.43997573852539E+01-1.69628768920898E+02 6.89338989257812E+01 -332 428 1 -333 424 1 1-7.70438766479492E+01 6.72657470703125E+01-7.49158401489258E+01 6.83600692749023E+01 -329 253 1 7-1.80000000000000E+02-9.00000000000000E+01 1.80000000000000E+02-6.32283134460449E+01 579 389 1 584 390 1 583 394 1 585 395 1 586 396 1 -588 430 1 587 429 1 -1 0 0 0 0 0 0 0.00000000000000E+00 0.00000000000000E+00</PRE></UL><P>Note that the last line of the section (-1 plus 6 zeros) is followed by an extra line. IMHO, this line does not really belong there, but it has to be taken into account when reading the E00 file!!! <P><H3><A>3.6 PRJ</A></H3><P>The PRJ (Projection Parameters) file consists of a set of projection keywords and values including a set of parameters following the keyword "Parameters". <P>This file needs further research for specific keywords and parameters for the projections supported by ADS and MOSS. <P>An example of an actual PRJ section follows: <P><UL><PRE>PRJ 2Projection UTM~Zone 13~Datum NAD27~Zunits NO~Units METERS~Spheroid CLARKE1866~Xshift 0.0000000000~Yshift 0.0000000000~Parameters~EOP</PRE></UL><P><H3><A>3.7 SIN</A></H3><P>Spatial Index <P>It usually is comprised of a single line with the value "EOX". <P>An example of an actual SIN section follows: <P><UL><PRE>SIN 2EOX</PRE></UL><P><H3><A>3.8 TOL</A></H3><P>This consists of ten lines with a tolerance type, a tolerance status, and a tolerance value on each line. The tolerance types are: <P><UL><LI>1. fuzzy <LI>2. generalize (unused) <LI>3. node match (unused) <LI>4. dangle <LI>5. tic match <LI>6. undefined <LI>7. undefined <LI>8. undefined <LI>9. undefined <LI>10. undefined </LI></UL><P>The tolerance status "is set to 1 if the tolerance is verified (been applied to operations of the coverage) and to 2 if the tolerance is not verified (been set by the TOLERANCE command, but not yet used in processing)." <P>An example of an actual TOL section follows: <P><UL><PRE>TOL 2 1 1 8.1813842E-01 2 2 0.0000000E+00 3 2 0.0000000E+00 4 1 0.0000000E+00 5 2 0.0000000E+00 6 2 8.0025000E+00 7 2 8.0025000E-01 8 2 8.0025000E-01 9 2 8.0025000E-01 10 2 8.0025000E-01 -1 0 0 0 0 0 0</PRE></UL><P>An example of a double-precision TOL section follows: <P><UL><PRE>TOL 3 1 2 8.00000000000000E-02 2 2 0.00000000000000E+00 3 2 0.00000000000000E+00 4 2 0.00000000000000E+00 5 2 0.00000000000000E+00 6 2 8.00000000000000E+00 7 2 8.00000000000000E-01 8 2 8.00000000000000E-01 9 2 8.00000000000000E-01 10 2 8.00000000000000E-01 -1 0 0 0 0 0 0</PRE></UL><P>Note that this section does not always contain ten lines, as we can see in the following example: <P><UL><PRE>TOL 2 1 1 2.0000000E+00 4 2 0.0000000E-01 -1 0 0 0 0 0 0</PRE></UL><P><H3><A>3.9 TXT - Annotations</A></H3><P>A TXT section starts with "TXT 2" or "TXT 3" and ends with the usual "-1 0 0 0 0 0 0" line. <P>Here is an example of an <B>empty TXT section</B>... (not very useful, I know, but it at least confirms that empty TXT sections can exist!): <P><UL><PRE>TXT 2 -1 0 0 0 0 0 0</PRE></UL><P>Here is a double-precision TXT section: <P><UL><PRE>TXT 3 1 1 0 21 2 5.92753812500000E+05 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 6.09405200000000E+06 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 8.00000000000000E+01-1.0000000E+02AB 1 1 0 21 3 5.98056937500000E+05 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 6.08779850000000E+06 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 8.00000000000000E+01-1.0000000E+02ABC -1 0 0 0 0 0 0</PRE></UL><P>And this is an entry from a single-precision TXT: <P><UL><PRE>TXT 2 0 2 0 0 6 5.8053578E+05 5.8293578E+05 0.0000000E+00 0.0000000E+00 2.1061998E+06 2.1061998E+06 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 5.0000000E+02-1.0000000E+02ABCDEF -1 0 0 0 0 0 0</PRE></UL><P><UL><LI>The first line of each entry contains 5 values: <P><OL><LI>LEVEL <LI>num_vertices1: for the line along which the text is drawn. <LI>num_vertices2: for the text arrow. If this value is negative then <LI>SYMBOL (Text Font) <LI>Number of chars. in text string </LI></OL>
<LI>Then we have 15 floating point values (when unused, these values default to 0.0000E+00): <UL><LI>Values 1 to 4 are the X coordinates of the line along which the text should be drawn (unused vertices are set to 0.000E+00) <LI>Values 5 to 8 are the Y coordinates for this same line. <LI>Values 9 to 11 are the X coordinates for the text arrow <LI>Values 12 to 14 are the Y coordinates for the text arrow <LI>The 15th value is probably the height??? </LI></UL><p><LI>Then the next line (line 5 for single, line 7 for double-prec.) contains an unknown value... in most cases, it is a value of -1.0000000E+02, but it is different sometimes. An important thing to note about this value is that it is always in single-precision format, even inside double-precision coverages. <p><LI>And the the text string follows. Like the rest of the E00 file, the text string will be split in 80 characters lines if the annotation is longer than 80 chars. One should look at the string length parameter to know how many lines of text string to expect. </LI></UL><P><P><H3><A>3.10 TX6/TX7 - Annotations</A></H3><P>TX6/TX7 sections start with "TX6 2", etc. and end with a line with the word "JABBERWOCKY". They can contain several sub-sections (subclasses), each sub-section start with a line with the subclass name and ends with a "-1 0 0 0 0 0 0" line. The main (and only?) difference between TX6 and TX7 sections is that the first line of each entry in a TX7 section has one more value (8 values instead of 7). <P>Here is one entry from a single-precision TX7 section: <P><UL><PRE> 89 1 3 2 2 0 10 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0-1.0000000E+02 5.0997402E-04 0.0000000E+00 0.0000000E+00-1.1926495E+02 5.0306187E+01-1.1926391E+02 5.0306408E+01-1.1926808E+02 5.0305916E+01-1.1926808E+02 5.0305916E+01-1.1926457E+02 5.0305916E+01AB DEFGHIJ</PRE></UL><P><UL><LI>The first line contains 8 values: <P><OL><LI>USER-ID <LI>LEVEL <LI>num_vertices1: for the line along which the text is drawn. <LI>num_vertices2: for the text arrow. If this value is negative then the arrow is reversed. <LI>SYMBOL (Text Font) <LI>??? Always 0 <LI>Number of chars. in text string <LI>??? Always 0, this value is not present in a TX6 </LI></OL><p><LI>Then we have 2 sets of 20 integer values, (3 lines each): <UL><LI>The first value of the first set is the text justification (See note below). <LI>The first value of the second set seems to always be 1 ??? <LI>The 38 other values seem to be always 0. </LI></UL><p><LI>Then line 8 contains an unknown value... in most cases, it is a value of -1.0000000E+02, but it is different sometimes. An important thing to note about this value is that it is always in single-precision format, even inside double-precision coverages. <p><LI>And line 9 contains 3 values... the 1st one is probably the text height??? <p><LI>Followed by (num_vertices1 + num_vertices2) pairs of coordinates. <p><LI>And the the text string follows. Like the rest of the E00 file, the text string will be split in 80 characters lines if the annotation is longer than 80 chars. One should look at the string length parameter to know how many lines of text string to expect. </LI></UL><P><B>Note about text justification:</B> <BLOCKQUOTE>If you look at the image <a href="http://pages.infinit.net/danmo/e00/docs/e00_textjust.gif" target="_blank" >e00_textjust.gif</A>, the red line indicates the line defined by the coordinates of the text feature. The blue dot is the point of the line to which the text is aligned, and the black number is the actual text. Justifications (1,2,3) place text above the line, (4,5,6) place it centered on the line, and (7,8,9) place the text below the line. Horizontally, (1,4,7) left-align the text to the first coordinate of the text line, (2,5,8) center-align the text to the midpoint of the text line, and (3,6,9) right-align the text to the last coordinate of the line. </BLOCKQUOTE><P>A TX6 section in a double-precision coverage: <P><UL><PRE>TX6 3STREETS 1 1 2 0 5 0 7 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0-1.0000000E+02 6.00000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 4.47348339990000E+06 5.33074571997000E+06 4.47348339990000E+06 5.33074571997000E+06ABCDEFG 2 1 3 0 5 0 18 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0-1.0000000E+02 3.50000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 4.47347279980000E+06 5.33087457983000E+06 4.47347279980000E+06 5.33087457983000E+06 4.47351938175583E+06 5.33083216377889E+06ABCDEFGHI JKLMNOPQ -1 0 0 0 0 0 0DESC 497 2 2 0 1 0 10 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0-1.0000000E+02 2.50000000000000E+00 0.00000000000000E+00 0.00000000000000E+00 4.47363686987000E+06 5.33098710986000E+06 4.47363686987000E+06 5.33098710986000E+06ABCDEFGHIJ -1 0 0 0 0 0 0JABBERWOCKY</PRE></UL><P><H3><A>3.11 RXP - Specific to Regions</A></H3><P>RXP sections are specific to region coverages. They contains sub-sections, corresponding to the region subclasses. As for the other sections of this type, it ends with a "JABBERWOCKY" line. <P>The RXP section seems to connect the region ids for each subclass to the polygons (from the PAL section) that are part of each region. The first column would be the region IDs, and the second column the corresponding PAL polygon IDs... <P>The format is quite simple: <P><UL><PRE>RXP 2NAME1 1 159 -1 0OTHER_NAME 1 214 1 216 1 217 1 218 1 222 1 226 1 227 -1 0LAST_NAME 1 28 1 31 1 36 1 47 1 48 -1 0JABBERWOCKY</PRE></UL><P><H3><A>3.12 RPL - Specific to Regions</A></H3><P>RPL sections are also specific to region coverages. The RPL section contains one or more subsections (called subclasses in Arc/Info)... like for all other section types that contain subclasses, it ends with a JABBERWOCKY line. Each region subclass is in the exact same format as a PAL section, the difference is that each entry in a RPL subclass seems to contain the list of arcs that define a region and not a single polygon. <P>Here is an example of a single-precision RPL section: <P><UL><PRE>RPL 2NAME1 8 7.0712538E+05 6.1982350E+06 7.3062950E+05 6.2321335E+06 677 548 0 -671 543 0 -670 542 0 632 513 0 631 510 0 -660 504 0 -686 535 0 -676 547 0 -1 0 0 0 0 0 0OTHER_NAME 20 3.0415478E+05 5.9847795E+06 3.6067356E+05 6.0342510E+06 -876 709 0 -877 706 0 0 0 0 913 731 0 886 715 0 879 711 0 -881 707 0 -883 712 0 -912 713 0 -919 730 0 -920 735 0 0 0 0 -935 745 0 -936 746 0 -931 738 0 -934 744 0 0 0 0 -928 741 0 -929 742 0 -927 740 0 -1 0 0 0 0 0 0LAST_NAME 215 3.1433966E+05 6.0253455E+06 6.7686263E+05 6.5089305E+06 112 89 0 0 0 0 115 85 0 114 91 0 104 76 0 0 0 0 169 103 0 168 139 0...... -1 0 0 0 0 0 0JABBERWOCKY</PRE></UL> |
|
|
|
9楼#
发布于：2004-06-29 22:48
<H2><A>4. INFO FILE FORMATS</A></H2><P>INFO files follow the same format: <P><OL><LI>name of the info file and summary information <LI>definitions for each of the attributes <LI>actual data values </LI></OL><P>The name line consists of six fields: <P><I>Note: the values inside brackets are the start-end position of the field in the line.</I> <P><OL><LI>(0-31) name of the INFO file <LI>(32-33) external flag: "XX" indicates an external table (stored in the coverage directory) and " " indicates an internal table (stored in the info directory). <LI>(34-37) number of attributes in a record (valid attributes only) <LI>(38-41) number of attributes total, including deleted ones (deleted attributes have an index of -1) <LI>(42-45) length of data record <LI>(46-55) number of data records </LI></OL><P>The definitions for each attribtue consist of eight fields: <P><OL><LI>(0-15) name of attribute <LI>(16-18) attribute size in its internal (binary) representation <LI>(19-20) appears to be constant of '-1' <LI>(21-24) start position of attribute in the binary data records <LI>(25-25) appears to be constant of '4' <LI>(26-27) appears to be constant of '-1' <LI>(28-31) attribute output format width (see below for discussion) <LI>(32-33) attribute output format precision <LI>(34-36) type of attribute (see below for discussion) <LI>(37-38) appears to be constant of '-1' <LI>(39-42) appears to be constant of ' -1' <LI>(43-46) appears to be constant of ' -1' <LI>(47-48) appears to be constant of '-1' <LI>(49-64) Alternate field name (almost always blank) <LI>(65-69) attribute index (sequential identifier starting at 1, value of -1 for deleted attributes which should be ignored) </LI></OL><P>The output format field is handled differently for numeric and character attributes. Numeric attributes give the output width followed by a space then the number of decimal positions. Character attributes give the output width followed by a constant of '-1'. <P>The type of the attribute is specified by the following codes: <P><PRE> 10-1 (D) Date (stored as 8 bytes, display width must be either 8 chars (12/31/99) or 10 chars (12/31/1999) ) 20-1 (C) Character string 30-1 (I) Integer with fixed number of digits (1 byte storage per digit) 40-1 (N) Numeric value with decimals and fixed number of digits (using 1 byte storage per digit in memory) 50-1 (B) Binary integer (2 or 4 bytes) 60-1 (F) Binary float (4 or 8 bytes, depends on coverage precision)</PRE><P>Here is the form that each data type takes in the data records of an E00 INFO table: <P><PRE> 10 (D) 8 characters 20 (C) Nbr of chars = attribute size (field 2 in attr. def. line). 30 (I) Nbr of chars = attribute size (field 2 in attr. def. line), value is right-justified 40 (N) stored as single prec. floats = 14 chars, ex: "-1.7735416E+00" (Uses 1 byte storage per digit internally, but always stored as single precision floats in both single and double precision E00 tables.) 50 (B) 32 bits integer = 11 chars total, right-justified 16 bits integer = 6 chars total, right-justified 60 (F) single prec. = 14 chars total, ex: "-1.7735416E+00" double prec. = 24 chars total, ex: "-2.60358875000000000E+05"</PRE><P>Note that it is possible to have 4 bytes binary floats inside double-precision tables, or to have 8 bytes binary floats inside single-precision tables. The representation used for the Binary float values inside the E00 table data records is on 14 chars for 4 byte floats, and 24 chars for 8 byte floats, independently of the precision of the coverage. (eg. 4 bytes floats would use 14 chars (-1.7735416E+00) even inside a double-precision table, and 8 byte floats will always use 24 chars, even inside single-precision tables). <P>Formats will be given for the most common INFO files: <P><UL><LI>.AAT <LI>.ACODE <LI>.BND <LI>.PAT <LI>.PCODE <LI>.TIC </LI></UL><P><H3><A>4.1 .AAT</A></H3><P>The .AAT (Arc Attribute Table) contains seven fields whose attribute names are self-explanatory. However, additional attributes may be added as desired, after the -ID attribute. <P>An example of an actual .AAT section follows: <P><UL><PRE>LANDLICL.AAT XX 7 7 28 7FNODE# 4-1 14-1 5-1 50-1 -1 -1-1 1-TNODE# 4-1 54-1 5-1 50-1 -1 -1-1 2-LPOLY# 4-1 94-1 5-1 50-1 -1 -1-1 3-RPOLY# 4-1 134-1 5-1 50-1 -1 -1-1 4-LENGTH 4-1 174-1 12 3 60-1 -1 -1-1 5-LANDLICL# 4-1 214-1 5-1 50-1 -1 -1-1 6-LANDLICL-ID 4-1 254-1 5-1 50-1 -1 -1-1 7- 2 1 0 0 2.0006265E+02 1 2 3 2 0 0 2.0006250E+02 2 3 1 4 0 0 1.0989176E+03 3 1 4 3 0 0 2.0003140E+02 4 4 3 4 0 0 2.8198248E+02 5 6 4 5 0 0 8.2309576E+02 6 7 5 2 0 0 2.2345322E+02 7 5</PRE></UL><P><H3><A>4.2 .ACODE</A></H3><P>The .ACODE (Arc Lookup Table) contains seven fields whose attribute names are the same (except the -ID) as that in the ADS files documentation. However, additional attributes should be able to be be added as desired, after the LABEL attribute. <P>An example of an actual .ACODE section follows: <P><UL><PRE>LANDLICP.ACODE 8 8 80 7LANDLICP-ID 4-1 14-1 8-1 50-1 -1 -1-1 1-XLABEL 4-1 54-1 8 2 60-1 -1 -1-1 2-YLABEL 4-1 94-1 8 2 60-1 -1 -1-1 3-SIZE 4-1 134-1 8 2 60-1 -1 -1-1 4-ANGLE 4-1 174-1 8 2 60-1 -1 -1-1 5-SZLBL 4-1 214-1 4-1 50-1 -1 -1-1 6-IFONTF 4-1 254-1 4-1 50-1 -1 -1-1 7-LABEL 52-1 294-1 52-1 20-1 -1 -1-1 8- 1 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0 0 2 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0 0 3 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0 0 4 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0 0 5 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0 0 6 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0 0 7 0.0000000E+00 0.0000000E+00 0.0000000E+00 0.0000000E+00 0 0</PRE></UL><P><H3><A>4.3 .BND</A></H3><P>The .BND (Coverage Min/Max Coordinates) table contains four fields whose attribute names are self-explanatory. <P>An example of an actual .BND section follows: <P><UL><PRE>LANDLICP.BND XX 4 4 16 1XMIN 4-1 14-1 12 3 60-1 -1 -1-1 1-YMIN 4-1 54-1 12 3 60-1 -1 -1-1 2-XMAX 4-1 94-1 12 3 60-1 -1 -1-1 3-YMAX 4-1 134-1 12 3 60-1 -1 -1-1 4- 3.4009988E+05 4.1000000E+06 3.4090012E+05 4.1003995E+06</PRE></UL><P>An example of a double-precision .BND section follows: <P><UL><PRE>STDFIG11CPX.BND XX 4 4 32 1XMIN 8-1 14-1 18 5 60-1 -1 -1-1 1-YMIN 8-1 94-1 18 5 60-1 -1 -1-1 2-XMAX 8-1 174-1 18 5 60-1 -1 -1-1 3-YMAX 8-1 254-1 18 5 60-1 -1 -1-1 4- 3.40100000000000000E+05 4.10000000000000000E+06 3.40900000000000000E+054.10040000000000000E+06</PRE></UL><P><H3><A>4.4 .PAT</A></H3><P>The .PAT (Polygon or Point Attribute Table) contains four fields whose attribute names are self-explanatory. However, additional attributes may be added as desired, after the -ID attribute. <P>An example of an actual .PAT section follows: <P><UL><PRE>LANDLICP.PAT XX 4 4 16 4AREA 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-LANDLICP# 4-1 94-1 5-1 50-1 -1 -1-1 3-LANDLICP-ID 4-1 134-1 5-1 50-1 -1 -1-1 4--1.7982806E+05 2.3455293E+03 1 0 8.0025000E+04 1.6990741E+03 2 1 8.9864000E+04 1.5285940E+03 3 2 9.9390586E+03 4.8201389E+02 4 0</PRE></UL><P>An example of a double-precision .PAT section follows: <P><UL><PRE>STDFIG11CPX.PAT XX 5 5 54 3AREA 8-1 14-1 18 5 60-1 -1 -1-1 1-PERIMETER 8-1 94-1 18 5 60-1 -1 -1-1 2-STDFIG11CPX# 4-1 174-1 5-1 50-1 -1 -1-1 3-STDFIG11CPX-ID 4-1 214-1 5-1 50-1 -1 -1-1 4-DATA 30-1 254-1 30-1 20-1 -1 -1-1 5--1.70000000000000000E+05 0.00000000000000000E+00 1 0 9.00000000000000000E+04 1.53005627441406250E+03 2 1SMALL 8.00000000000000000E+04 1.69907165527343750E+03 3 2LARGE</PRE></UL><P><H3><A>4.5 .PCODE</A></H3><P>The .PCODE (Polygon Lookup Table) contains eight fields whose attribute names are the same (except the -ID) as that in the ADS files documentation. However, additional attributes should be able to be be added as desired, after the LABEL attribute. <P>An example of an actual .PCODE section follows: <P><UL><PRE>LANDLICP.PCODE 8 8 80 2LANDLICP-ID 4-1 14-1 8-1 50-1 -1 -1-1 1-XLABEL 4-1 54-1 8 2 60-1 -1 -1-1 2-YLABEL 4-1 94-1 8 2 60-1 -1 -1-1 3-SIZE 4-1 134-1 8 2 60-1 -1 -1-1 4-ANGLE 4-1 174-1 8 2 60-1 -1 -1-1 5-SZLBL 4-1 214-1 4-1 50-1 -1 -1-1 6-IFONTF 4-1 254-1 4-1 50-1 -1 -1-1 7-LABEL 52-1 294-1 52-1 20-1 -1 -1-1 8- 1 1.6050000E+00 1.4490000E+00 7.0000000E-02 0.0000000E+00 5 0LARGE 2 1.6470000E+00 1.1520000E+00 7.0000000E-02 0.0000000E+00 5 0SMALL</PRE></UL><P><H3><A>4.6 .TIC</A></H3><P>The .TIC (Tic Coordinates) table contains three fields whose attribute names are self-explanatory. <P>An example of an actual .TIC section follows: <P><UL><PRE>LANDLICP.TIC XX 3 3 12 4IDTIC 4-1 14-1 5-1 50-1 -1 -1-1 1-XTIC 4-1 54-1 12 3 60-1 -1 -1-1 2-YTIC 4-1 94-1 12 3 60-1 -1 -1-1 3- 1 3.4009244E+05 4.1000002E+06 2 3.4010028E+05 4.1004150E+06 3 3.4090753E+05 4.1003998E+06 4 3.4089972E+05 4.0999850E+06</PRE></UL><P>An example of a double-precision .TIC section follows: <P><UL><PRE>STDFIG11CPX.TIC XX 3 3 20 4IDTIC 4-1 14-1 5-1 50-1 -1 -1-1 1-XTIC 8-1 54-1 18 5 60-1 -1 -1-1 2-YTIC 8-1 134-1 18 5 60-1 -1 -1-1 3- 1 3.40900000000000000E+05 4.10000000000000000E+06 4 3.40900000000000000E+05 4.10040000000000000E+06 2 3.40100000000000000E+05 4.10000000000000000E+06 3 3.40100000000000000E+05 4.10040000000000000E+06</PRE></UL><P><H2><A>5. CONCLUSION</A></H2><P>The content and format of the ARC EXPORT file seems to be straightforward in most cases. The remaining areas of uncertainty include: <P><UL><LI>the meaning of the 'SIN 2' section <LI>the precise format of the PRJ file for different projections <LI>possible variation in the '-1' suffixes of INFO definitions </LI></UL><P>However, none of these appears to be that serious, and the indicated formats should be used to identify any errors or limitations. <P>Because this information was derived from limited experimentation, it should be considered as tentative and subject to revision at any time. <P><HR width="50%">
|
|
|
上一页
下一页