EVOLUTION-MANAGER
Edit File: index.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/> <meta http-equiv="X-UA-Compatible" content="IE=9"/> <meta name="generator" content="Doxygen 1.8.5"/> <title>ISO8211Lib: ISO8211Lib</title> <link href="tabs.css" rel="stylesheet" type="text/css"/> <script type="text/javascript" src="jquery.js"></script> <script type="text/javascript" src="dynsections.js"></script> <link href="doxygen.css" rel="stylesheet" type="text/css" /> </head> <body> <div id="top"><!-- do not remove this div, it is closed by doxygen! --> <div id="titlearea"> <table cellspacing="0" cellpadding="0"> <tbody> <tr style="height: 56px;"> <td style="padding-left: 0.5em;"> <div id="projectname">ISO8211Lib </div> </td> </tr> </tbody> </table> </div> <!-- end header part --> <!-- Generated by Doxygen 1.8.5 --> <div id="navrow1" class="tabs"> <ul class="tablist"> <li class="current"><a href="index.html"><span>Main Page</span></a></li> <li><a href="pages.html"><span>Related Pages</span></a></li> <li><a href="annotated.html"><span>Classes</span></a></li> <li><a href="files.html"><span>Files</span></a></li> </ul> </div> </div><!-- top --> <div class="header"> <div class="headertitle"> <div class="title">ISO8211Lib </div> </div> </div><!--header--> <div class="contents"> <div class="textblock"><h2>Introduction</h2> <p>ISO8211Lib is intended to be a simple reader for ISO/IEC 8211 formatted files, particularly those that are part of SDTS and S-57 datasets. It consists of open source, easy to compile and integrate C++ code.</p> <h2>ISO 8211 Background</h2> <p>The <a href="http://py-iso8211.sourceforge.net/tibbs/faq.html">ISO 8211 FAQ</a> has some good background on ISO 8211 formatted files. I will briefly introduce it here, with reference to the library classes representing the components.</p> <p>An 8211 file (<a class="el" href="classDDFModule.html">DDFModule</a>) consists of a series of logical records. The first record is special, and is called the DDR (Data Description Record). It basically contains definitions of all the data objects (fields or <a class="el" href="classDDFFieldDefn.html">DDFFieldDefn</a> objects) that can occur on the following data records.</p> <p>The remainder of the records are known as DRs (data records - <a class="el" href="classDDFRecord.html">DDFRecord</a>). They each contain one or more field (<a class="el" href="classDDFField.html">DDFField</a>) instances. What fields appear on what records is not defined by ISO 8211, though more specific requirements may be implied by a particular data standard such as SDTS or S-57.</p> <p>Each field instance has a name, and consists of a series of subfields. A given field always has the same subfields in each field instance, and these subfields are defined in the DDR (<a class="el" href="classDDFSubfieldDefn.html">DDFSubfieldDefn</a>), in association with their field definition (<a class="el" href="classDDFFieldDefn.html">DDFFieldDefn</a>). A field may appear 0, 1, or many times in a DR. </p> <p>Each subfield has a name, format (from the <a class="el" href="classDDFSubfieldDefn.html">DDFSubfieldDefn</a>) and actual subfield data for a particular DR. Some fields contain an <em>array</em> of their group of subfields. For instance a <em>coordinate field</em> may have X and Y subfields, and they may repeat many times within one coordinate field indicating a series of points.</p> <p><em>This would be a real good place for a UML diagram of ISO 8211, and the corresponding library classes!</em></p> <h2>Development Information</h2> <p>The <b><a class="el" href="iso8211_8h_source.html">iso8211.h</a></b> contains the definitions for all public ISO8211Lib classes, enumerations and other services.</p> <p>To establish access to an ISO 8211 dataset, instantiate a <a class="el" href="classDDFModule.html">DDFModule</a> object, and then use the <a class="el" href="classDDFModule.html#af4ffa6d8f0d6f06221b94ff8082adf43">DDFModule::Open()</a> method. This will read the DDR, and establish all the <a class="el" href="classDDFFieldDefn.html">DDFFieldDefn</a>, and <a class="el" href="classDDFSubfieldDefn.html">DDFSubfieldDefn</a> objects which can be queried off the <a class="el" href="classDDFModule.html">DDFModule</a>.</p> <p>The use <a class="el" href="classDDFModule.html#a2922aa33316aec6a3d4781b77e531eae">DDFModule::ReadRecord()</a> to fetch data records (<a class="el" href="classDDFRecord.html">DDFRecord</a>). When a record is read, a list of field objects (<a class="el" href="classDDFField.html">DDFField</a>) on that record are created. They can be queried with various <a class="el" href="classDDFRecord.html">DDFRecord</a> methods.</p> <p>Data pointers for individual subfields of a <a class="el" href="classDDFField.html">DDFField</a> can be fetched with <a class="el" href="classDDFField.html#a405aaacb344f388c2dcdaac03ea697aa">DDFField::GetSubfieldData()</a>. The interpreted value can then be extracted with the appropriate one of DDFSubfieldDefn::ExtractIntValue(), DDFSubfieldDefn::ExtractStringValue(), or DDFSubfieldDefn::ExtractFloatValue(). Note that there is no object instantiated for individual subfields of a <a class="el" href="classDDFField.html">DDFField</a>. Instead the application extracts a pointer to the subfields raw data, and then uses the <a class="el" href="classDDFSubfieldDefn.html">DDFSubfieldDefn</a> for that subfield to extract a usable value from the raw data.</p> <p>Once the end of the file has been encountered (<a class="el" href="classDDFModule.html#a2922aa33316aec6a3d4781b77e531eae">DDFModule::ReadRecord()</a> returns NULL), the <a class="el" href="classDDFModule.html">DDFModule</a> should be deleted, which will close the file, and cleanup all records, definitions and related objects.</p> <h3>Class APIs</h3> <ul> <li> <a class="el" href="classDDFModule.html">DDFModule</a> class. </li> <li> <a class="el" href="classDDFFieldDefn.html">DDFFieldDefn</a> class. </li> <li> <a class="el" href="classDDFSubfieldDefn.html">DDFSubfieldDefn</a> class. </li> <li> <a class="el" href="classDDFRecord.html">DDFRecord</a> class. </li> <li> <a class="el" href="classDDFField.html">DDFField</a> class. </li> </ul> <p>A complete <a href="example.html">Example Reader</a> should clarify simple use of ISO8211Lib.</p> <h2>Related Information</h2> <ul> <li> <p class="startli">The ISO 8211 standard can be ordered through <a href="http://www.iso.ch/">ISO</a>. It cost me about $200CDN.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">The <a href="http://user.icx.net/~brooks/iso8211.html">ISO/IEC 8211/DDFS Home Page</a> contains tutorials and some code by Dr. Alfred A. Brooks, one of the originators of the 8211 standard.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">The <a href="http://py-iso8211.sourceforge.net/tibbs/iso8211.html">ISO/IEC 8211 Home Page</a> has some python code for parsing 8211 files, and some other useful background.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">The <a href="http://mcmcweb.er.usgs.gov/sdts/sdtsxx/index.html">SDTS++</a> library from the USGS includes support for ISO 8211. It doesn't include some of the 1994 additions to ISO 8211, but it is sufficient for SDTS, and quite elegantly done. Also supports writing ISO 8211 files.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">The USGS also has an older <a href="ftp://sdts.er.usgs.gov/pub/sdts/software/fips123/">FIPS123</a> library which supports the older profile of ISO 8211 (to some extent).</p> <p></p> <p class="endli"></p> </li> </ul> <h2>Licensing</h2> <p>This library is offered as <a href="http://www.opensource.org">Open Source</a>. In particular, it is offered under the X Consortium license which doesn't attempt to impose any copyleft, or credit requirements on users of the code.</p> <p>The precise license text is:</p> <p><em> Copyright (c) 1999, Frank Warmerdam </em></p> <p><em> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: </em></p> <p><em> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </em></p> <p><em> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. </em></p> <p><em> </em></p> <h2>Building the Source</h2> <ol> <li> <p class="startli">First, fetch the source. The most recent source should be accessible at an url such as <a href="http://home.gdal.org/projects/iso8211/iso8211lib-1.4.zip">http://home.gdal.org/projects/iso8211/iso8211lib-1.4.zip</a>.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">Untar the source.</p> <p><code> % unzip iso8211lib-1.4.zip </code></p> <p class="endli"></p> </li> <li> <p class="startli">On unix you can now type ``configure'' to establish configuration options.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">On unix you can now type make to build libiso8211.a, and the sample mainline 8211view.</p> <p></p> <p class="endli"></p> </li> </ol> <p>Windows developers will have to create their own makefile/project but can base it on the very simple Makefile.in provided. As well, you would need to copy cpl_config.h.in to cpl_config.h, and modify as needed. The default will likely work OK, but may result in some compiler warnings. Let me know if you are having difficulties, and I will prepare a VC++ makefile.</p> <h2>Author and Acknowledgements</h2> <p>The primary author of ISO8211Lib is <a href="http://pobox.com/~warmerdam">Frank Warmerdam</a>, and I can be reached at <a href="#" onclick="location.href='mai'+'lto:'+'war'+'me'+'rda'+'m@'+'pob'+'ox'+'.co'+'m'; return false;">warmerdam@pobox.com</a>. I am eager to receive bug reports, and also open to praise or suggestions.</p> <p>I would like to thank:</p> <ul> <li> <p class="startli"><a href="http://www.safe.com/">Safe Software</a> who funded development of this library, and agreed for it to be Open Source.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">Mark Colletti, a primary author of SDTS++ from which I derived most of what I know about ISO 8211 and who was very supportive, answering a variety of questions.</p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">Tony J Ibbs, author of the ISO/IEC 8211 home page who answered a number of questions, and collected a variety of very useful information. </p> <p></p> <p class="endli"></p> </li> <li> <p class="startli">Rodney Jenson, for a detailed bug report related to repeating variable length fields (from S-57).</p> <p></p> <p class="endli"></p> </li> </ul> <p>I would also like to dedicate this library to the memory of Sol Katz. Sol released a variety of SDTS (and hence ISO8211) translators, at substantial personal effort, to the GIS community along with the many other generous contributions he made to the community. His example has been an inspiration to me, and I hope similar efforts on my part will contribute to his memory.</p> </div></div><!-- contents --> <!-- start footer part --> <hr class="footer"/><address class="footer"><small> Generated by  <a href="http://www.doxygen.org/index.html"> <img class="footer" src="doxygen.png" alt="doxygen"/> </a> 1.8.5 </small></address> </body> </html>