Known Limitations
.
This is a synopsis of the known limitations in the SEDRIS SDK Release 3.1.


  • The initial SEDRIS SDK Release 3.1 will not have the following SRM functions implemented:
    • GCS coordinate validation
    • UTM coordinate validation
    • Horizontal datum transformations
    .
  • The GC to LTP vector conversion doesn't work properly.
  • .
  • The SE_GetErrorDescription() function is not fully implemented and it will, in most cases, return a null pointer (no error message).
  • .
  • Once a GMI is placed in an environment with a specific SRF (the SRF of the environment root object), then it can no longer be consumed to a different SRF using the automatic conversion. If another SRF is needed for those objects, first the users have to extract the objects in their "native" SRF, and then perform necessary conversions.
  • .
  • The Rules Checker application in this release does not check all the DRM Constraints. Please read doc/ToolsAndUtilities.htm for the list of DRM Constraints checked in this release. This application will be extended in subsequent releases to cover the remaining DRM Constraints.
  • .
  • The Read API's inheritance mechanism for <Colours> and <Rendering Properties> is incomplete. If an inherited <Colour> 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 implemented.
  • .
  • An LSR <Models> can only be instanced into the following types of spatial reference frames:
    • geodetic (2D or 3D)
    • any projected spatial reference frame (e.g., Mercator)
    • any augmented projected spatial reference frame (e.g., Augmented Mercator (3D))
    • compatible LSR spatial reference frames
    .
  • 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.


Return to: Top of this Page
Last updated: May 30, 2002