• The Rules Checker application in this release does not check all the business rules listed in the latest Business Rules document. Please read doc/Application_Documentation.txt for the list of supported rules checked in this release. The Rules Checker application will be extended in future releases to cover the remaining business rules.
• The Level 0 Read API's inheritance mechanism for <Colors> and <Rendering Properties> is incomplete. If an inherited <Color> or <Rendering Properties> object conflicts with a more "recent" object, the conflicting inherited object is completely overridden, rather than being deconflicted if possible. Consequently, the inherited information is correct, but incomplete for these cases.
• The SE_EXACT_SEARCH option for search bounds is not available.
• LSR <Models> can only be instanced into the following types of spatial reference frames.
• geodetic (2D or 3D)
• projected spatial reference frames (e.g., Mercator)
• augmented projected spatial reference frames (e.g., Augmented Mercator (3D))
• compatible LSR spatial reference frames
• Browser - Because this application uses X, you must install X on your win32 platform in order to compile and/or run this application. In addition, problems with Browser have been observed in displaying objects with many components (components numbering in the tens of thousands). This is thought to be due to the underlying X Motif implementation's usage of (relatively) small signed rather than large unsigned numbers to allow lots of widgets to be hooked up.
• S1000-to-SEDRIS conversion caveats.
• S1000 data must first be converted into STF files before being read on any platform other than Irix (Silicon Graphics) or Sun. S1000 data cannot be read directly on other platforms, because S1000 does not support them. (This is a limitation of S1000 itself; its libraries are not supported for Win32, Linux, AIX, etc.).
• Does not distinguish damaged states for S1000 models, since S1000 has not always used a consistent naming scheme to identify models containing state information. Consequently, the "damaged" and "healthy" versions of a model will become two separate <Models> in SEDRIS.
• Database features/models that depict treelines, fences, or wire obstacles are tagged with "treeline" codes. The only way to distinguish them at this time is by checking their textures.
• The Model Viewer application does not run on SunOS 5.7.
• The Model Viewer application processes only polygonal <Primitive Geometry>; other primitives, e.g. <Lines> and <Points>, are currently omitted. A further ramification of this limitation is that a <Model> containing only a <Feature Model> without a <Geometry Model> will not be processed at all.

If you have any questions or comments regarding this release, please contact: help@sedris.org.