阅读:6868回复:23
关于*.E00格式数据的属性字段值的问题
<P>*.E00格式数据的属性字段个数有时和字段值的个数不相等,可见下例,有AREA、PERIMETER 、region# 、region-ID、CODE五个字段,可是对应的字段值却只有4列,也就是少了region#和region-ID中的一个字段的值,这是何解? </P>
<P>region.PAT XX 5 5 30 911<BR>AREA 8-1 14-1 18 5 60-1 -1 -1-1 1-<BR>PERIMETER 8-1 94-1 18 5 60-1 -1 -1-1 2-<BR>region# 4-1 174-1 5-1 50-1 -1 -1-1 3-<BR>region-ID 4-1 214-1 5-1 50-1 -1 -1-1 4-<BR>CODE 6-1 254-1 6-1 20-1 -1 -1-1 5-<BR> 4.25016993999714030e+02 8.44438372437667230e+01 1 0141101<BR> 1.58659174867090770e+02 5.36975600173641820e+01 2 0141161<BR> 3.84837713999906550e+02 7.96368014029537790e+01 3 0141101<BR> 3.58104437999892980e+02 7.63858382160677820e+01 4 0141101</P> <P> 。。。。。。。 。。。。。。。</P> <P> 6.57636000000056810e+01 3.34293680284682890e+01 910 0141161<BR> 7.54623999993782490e+01 3.74090222359493650e+01 911 0141200</P> <P>找到的E00格式数据的说明,都没有对此作解释,不得其解,请各位高手多多指点啊!</P> |
|
1楼#
发布于:2005-11-05 09:07
<P>哭,怎么没有人理我?呜呜呜</P>
|
|
2楼#
发布于:2005-11-07 12:34
<P>你找到的数据格式说明是这个吗:http://avce00.maptools.org/e00compr/index.html</P>
|
|
|
3楼#
发布于:2005-11-07 15:38
<P>我无法访问到这个网页。</P>
<P>我有一些e00的数据,打开后都有发现实际字段值的个数小于相应字段说明的字段个数,这个问题的原因是什么?仍在郁闷中。。。</P> <P>如果您知道,恳求指点迷津。</P><br> [此贴子已经被作者于2005-11-7 15:40:00编辑过]
|
|
4楼#
发布于:2005-11-07 15:39
<P>上面的地址里有比较详细的读写转换eoo数据的类</P>
<P>在这里贴出,希望你能下载到.</P> <H2>A Library to Read/Write Compressed E00 Files</H2> <P>E00Compr is an <a href="http://opensource.org/" target="_blank" >Open Source</A> (i.e. Free!) ANSI-C library to compress and uncompress Arc/Info Export (E00) files. <P>The C library can be easily plugged into existing E00 translators to add support for compressed E00 files simply by replacing the existing translator's read/write function by the E00ReadNextLine() and E00WriteNextLine() functions provided by the library. See the <a href="http://avce00.maptools.org/e00compr/e00compr.html" target="_blank" >library documentation</A> for all the details. <P>For those who do not need a library but simply want to convert some files, the package includes the <a href="http://avce00.maptools.org/e00compr/e00compr.html#e00conv" target="_blank" >"E00CONV" conversion program</A> that allows you to convert a E00 file to and from any compression level (NONE, PARTIAL or FULL). <P>The latest version of the library is version 1.0.0 from September 17, 2005. <P> <UL> <LI><a href="http://avce00.maptools.org/e00compr/e00compr.html" target="_blank" >E00Compr documentation</A> <br> <LI><a href="http://avce00.maptools.org/e00compr/HISTORY.TXT" target="_blank" >HISTORY.TXT</A> - revision history <p> <LI><a href="http://avce00.maptools.org/dl/e00compr-1.0.0.tar.gz" target="_blank" >e00compr-1.0.0.tar.gz</A> (or <a href="http://avce00.maptools.org/dl/e00compr-1.0.0.zip" target="_blank" >e00compr-1.0.0.zip</A>): The latest version of the package, including source code and documentation. <p> <LI><a href="http://avce00.maptools.org/e00compr/e00conv.exe" target="_blank" >E00CONV.EXE</A>: A precompiled version of the <a href="http://avce00.maptools.org/e00compr/e00compr.html#e00conv" target="_blank" >"E00CONV conversion program</A> for WIN32 (DOS executable under Windows 95/98/NT) </LI></UL> <P>See als <P> <UL> <LI><a href="http://avce00.maptools.org/avce00/index.html" target="_blank" >AVCE00</A> - The C library that makes Arc/Info (binary) vector coverages appear as ASCII E00 files! <p> <LI><a href="http://avce00.maptools.org/gistrans_links.html" target="_blank" >Other GIS translators and utilities</A>, format information, etc. </LI></UL> <P>Comments, suggestions (and bug reports of course!) are always welcome... please keep in mind that I may not have time to respond to all Emails (but I'll do my best). </P> |
|
|
5楼#
发布于:2005-11-07 15:43
<P>真是不错的地方,先谢谢您,我去看看</P>
<P><img src="images/post/smile/dvbbs/em02.gif" /> </P> |
|
6楼#
发布于:2005-11-07 15:49
希望有结果到这里发布下成果和经验,这个问题还是大家比较需要的:)
|
|
|
7楼#
发布于:2005-11-07 16:08
<P>我看了一下那个网站,那里只说了怎么读写的方法,但是涉及到内核数据如何读取的问题,却略了。</P>
<P>嗯,如果问题解决了,一定过来说明的。</P> [此贴子已经被作者于2005-11-7 16:17:52编辑过]
|
|
8楼#
发布于:2005-11-07 16:33
<P>这个是以前看过的一个格式说明,发上做参考</P>
<P>下载地址:</P> <P><a href="attachment/2005-11/200511716371527846.txt">2005-11/200511716371527846.txt</a></P> <P> ANALYSIS</P> <P> OF</P> <P> ARC EXPORT FILE FORMAT<br> <br> FOR</P> <P> ARC/INFO (REV 6.1.1)</P><br><br><br><br><br> <P><br> TABLE OF CONTENTS</P> <P>1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . 1</P> <P>2 OVERALL ORGANIZATION. . . . . . . . . . . . . . . . . . . 2</P> <P>3 ARC FILE FORMATS. . . . . . . . . . . . . . . . . . . . . 3<br> 3.1 ARC. . . . . . . . . . . . . . . . . . . . . . . . . 4<br> 3.2 CNT. . . . . . . . . . . . . . . . . . . . . . . . . 6<br> 3.3 LAB. . . . . . . . . . . . . . . . . . . . . . . . . 7<br> 3.4 LOG. . . . . . . . . . . . . . . . . . . . . . . . . 8<br> 3.5 PAL. . . . . . . . . . . . . . . . . . . . . . . . . 9<br> 3.6 PRJ. . . . . . . . . . . . . . . . . . . . . . . . . 11<br> 3.7 SIN. . . . . . . . . . . . . . . . . . . . . . . . . 12<br> 3.8 TOL. . . . . . . . . . . . . . . . . . . . . . . . . 13</P> <P>4 INFO FILE FORMATS . . . . . . . . . . . . . . . . . . . . 14<br> 4.1 .AAT . . . . . . . . . . . . . . . . . . . . . . . . 15<br> 4.2 .ACODE . . . . . . . . . . . . . . . . . . . . . . . 16<br> 4.3 .BND . . . . . . . . . . . . . . . . . . . . . . . . 17<br> 4.4 .PAT . . . . . . . . . . . . . . . . . . . . . . . . 18<br> 4.5 .PCODE . . . . . . . . . . . . . . . . . . . . . . . 19<br> 4.6 .TIC . . . . . . . . . . . . . . . . . . . . . . . . 20</P> <P>5 CONCLUSION. . . . . . . . . . . . . . . . . . . . . . . . 21</P> <P>APPENDIX A: SAMPLE EXPORT FILE BEFORE TOPOLOGY. . . . . . . . 22</P> <P>APPENDIX B: SAMPLE EXPORT FILE AFTER POLYGON TOPOLOGY . . . . 24</P> <P>APPENDIX C: SAMPLE EXPORT FILE AFTER LINE TOPOLOGY. . . . . . 27</P> <P>APPENDIX D: SAMPLE EXPORT FILE FOR POINT COVERAGE . . . . . . 30</P> <P>APPENDIX E: SAMPLE EXPORT FILE FOR SINGLE-PRECISION<br> COVERAGE. . . . . . . . . . . . . . . . . . . . . . . . . 35</P> <P>APPENDIX F: SAMPLE EXPORT FILE FOR DOUBLE-PRECISION<br> COVERAGE. . . . . . . . . . . . . . . . . . . . . . . . . 37<br>1 INTRODUCTION</P> <P><br>Note: ESRI considers the export/import file format to be<br>proprietary. As a consequence, the identified format can only<br>constitute a "best guess" and must always be considered as<br>tentative and subject to revision, as more is learned.</P> <P>It appears that all ARC/INFO files except user-created lookup<br>tables are exported, including .ACODE and .PCODE.<br>2 OVERALL ORGANIZATION</P> <P>The export file begins with a line with three fields.</P> <P> 1- an initial 'EXP'<br> 2- what appears to be a constant of '0'<br> 3- the pathname for the creation of the export file</P> <P>The export file ends with a line beginning 'EOS'.</P> <P>The ARC files are included first, in alphabetical order except<br>for the SIN, LOG, and PRJ files which occur last. Then the INFO<br>files are included in alphabetical order.</P> <P>The beginning of each ARC file is indicated by the file name (a<br>three-character identifier) followed by ' 2' for single-<br>precision or ' 3' for double-precision. Single-precision<br>carries 8 digits, and double-precision carries 15 digits.</P> <P>Each ARC file ends with a line of seven numbers beginning with a<br>-1 and followed by six zeros, except the SIN, LOG, and PRJ files<br>which end in 'EOX', 'EOL', and 'EOP', respectively. The LAB file<br>uses a slight variation of this -1 ending line (see below). The<br>format for each ARC file is specific to that type of file. These<br>formats are covered below.</P> <P>The beginning of the INFO file section is indicated by 'IFO 2',<br>and its end is indicated by 'EOI'. The INFO files each begin with<br>the file name. For example, the polygon attribute table would be<br>'STDFIG24C.PAT' on a line by itself. The format is the same for<br>every INFO file. This format is given below.<br>3 ARC FILE FORMATS</P> <P>Formats will be given for the most common ARC files:</P> <P> ARC<br> CNT<br> LAB<br> LOG<br> PAL<br> PAR<br> PRJ<br> SIN<br> TOL</P><br> [此贴子已经被作者于2005-11-7 16:37:41编辑过]
|
|
|
9楼#
发布于:2005-11-07 16:33
<P>3.1 ARC</P>
<P>The ARC (arc coordinates and topology) file consists of repeating<BR>sets of arc information. The first line of each set has seven<BR>numbers:</P> <P> 1. coverage#<BR> 2. coverage-ID<BR> 3. from node<BR> 4. to node<BR> 5. left polygon<BR> 6. right polygon<BR> 7. number of coordinates</P> <P>The subsequent lines of a set are the coordinates with two x-y<BR>pairs per line, if the coverage is single-precision. If there<BR>are an odd number of coordinates, the last line will have only<BR>one x-y pair. Double-precision puts one coordinate pair on each<BR>line.</P> <P>An example of an actual ARC section follows:</P> <P>ARC 2<BR> 1 2 2 1 1 2 2<BR> 3.4029994E+05 4.1001998E+06 3.4009988E+05 4.1002000E+06<BR> 2 3 3 2 3 2 2<BR> 3.4050000E+05 4.1001998E+06 3.4029994E+05 4.1001998E+06<BR> 3 1 1 4 1 2 4<BR> 3.4009988E+05 4.1002000E+06 3.4040006E+05 4.1003995E+06<BR> 3.4090012E+05 4.1002000E+06 3.4070003E+05 4.1001995E+06<BR> 4 4 4 3 4 2 2<BR> 3.4070003E+05 4.1001995E+06 3.4050000E+05 4.1001998E+06<BR> 5 6 3 4 4 3 3<BR> 3.4050000E+05 4.1001998E+06 3.4059997E+05 4.1001002E+06<BR> 3.4070003E+05 4.1001995E+06<BR> 6 7 4 5 1 3 3<BR> 3.4070003E+05 4.1001995E+06 3.4079997E+05 4.1000002E+06<BR> 3.4019978E+05 4.1000000E+06<BR> 7 5 5 2 1 3 2<BR> 3.4019978E+05 4.1000000E+06 3.4029994E+05 4.1001998E+06<BR> -1 0 0 0 0 0 0</P> <P>An example of a double-precision ARC section follows:</P> <P>ARC 3<BR> 1 0 0 0 0 0 7<BR> 3.40200000000000E+05 4.10000000000000E+06<BR> 3.40300000000000E+05 4.10020000000000E+06<BR> 3.40500000000000E+05 4.10020000000000E+06<BR> 3.40600000000000E+05 4.10010000000000E+06<BR> 3.40700000000000E+05 4.10020000000000E+06<BR> 3.40800000000000E+05 4.10000000000000E+06<BR> 3.40200000000000E+05 4.10000000000000E+06<BR> 2 0 0 0 0 0 4<BR> 3.40100000000000E+05 4.10020000000000E+06<BR> 3.40400000000000E+05 4.10040000000000E+06<BR> 3.40900000000000E+05 4.10020000000000E+06<BR> 3.40100000000000E+05 4.10020000000000E+06<BR> -1 0 0 0 0 0 0<BR></P> |
|
|
上一页
下一页