The SEDRIS Data Representation Model
APPENDIX A - Classes
Image Anchor

Class Name: Image Anchor

Superclass - <SEDRIS Abstract Base>

Subclasses

This DRM class is concrete and has no subclasses.

Definition

An instance of this DRM class specifies where the given <Image> instance is located in the specified SRF.

An <Image Anchor> instance is used in one of two ways:

  1. As a component of an <Image> component of an <Image Library> instance.

    In this case, the <Image> instance is not tied to a particular <Feature Representation> instance or <Geometry Representation> instance. The <Location> components of the <Image Anchor> instance specify the positions of the corners of the <Image> instance in the specified SRF.

    NOTE 1  If two georeferenced <Image> instances are to be placed exactly next to each other by means of <Image Anchor> components, the <Location> components of those <Image Anchor> instances are exactly the same along the common edge.

  2. As a component of an <Image Mapping Function> instance.

    In this case, the <Image Anchor> instance defines how the associated <Image> instance is to be applied to the DRM object having the <Image Mapping Function> instance as a component. The srf_context_info of the <Image Anchor> instance shall match that of the context in which the <Image Mapping Function> instance is being applied.

    <Image Anchor> instances are used to support spherical and cylindrical image projections for <Image Mapping Function> instances. By specifying anchor points that are not in the same plane, non-orthogonal projection becomes possible.

    NOTE 2  When an image mapping is applied to many <Polygon> instances using a single <Image Mapping Function> instance, a continuous image results when displayed.

Primary Page in DRM Diagram:

Secondary Pages in DRM Diagram:

This class appears on only one page of the DRM class diagram.

Example

  1. A producer has a geospecific texture that has been derived from overhead photography and rectified. It is used to drape over a terrain surface and is represented as an <Image> instance with an <Image Anchor> component.

  2. If a producer has a georeferenced <Image> instance that is to be explicitly applied to one or more terrain <Polygon> instances, the mapping of the image data to the <Polygon> instances is defined by an <Image Mapping Function> component of each <Polygon> instance that has an <Image Anchor> component and an association to the appropriate <Image> instance.

FAQs

Is it necessary to specify an SRF for every <Image> component of an <Image Library> instance?

No. An <Image> instance is not required to specify an <Image Anchor> component, and in fact, an <Image> instance utilizes its optional relationship with <Image Anchor> only when the texture is geospecific.

Consequently, since an SRF is specified for an <Image> instance only if an <Image Anchor> component is present, only geospecific textures require specification of an SRF.

In a given <Image Library> instance, are all geospecific <Image> components required to specify the same SRF? If so, why not store the SRF specification within the <Image Library> instance rather than in <Image Anchor> components for individual <Image> instances?

Although all geospecific textures in an <Image Library> instance may specify the same SRF, this is not a requirement for data providers, nor can it be relied upon by consumers. Consequently, each geospecific <Image> may specify an independent SRF.

Furthermore, many data providers generate <Image> instances that are not geospecific and thus do not require the specification of an SRF. Adding SRF information as a field of <Image Library> would require all data providers to specify SRFs for all <Image Library> instances, even those to which SRFs were not applicable.

Can the SRF specified for a geospecific <Image> instance differ from those specified for the <Environment Root> components of the <Transmittal Root> instance of its native transmittal, and if so, why?

A geospecific <Image> instance is not required to specify the same SRF as that of any of the <Environment Root> instances that may be present in its native transmittal. It is perfectly possible for a transmittal to contain multiple <Environment Root> instances, each with its own SRF, or to have an <Image Library> instance and no <Environment Root> instances whatsoever.

How can a data provider transmit an <Image> instance and its associated warping?

<Image Anchor> instances only provide for a simple method of <Image> warping. It is assumed that for more complex forms of warping (e.g., "rubber sheeting", ortho-rectification) the <Image> instance will be warped by the data provider and transmitted in the final state.

Constraints

Composed of (two-way)

Component of (two-way)

Inherited Field Elements

This class has no inherited field elements.

Field Elements

SE_SRF_Context_Info

srf_context_info;

2


Notes

Composed of Notes


Location

The three <Location> components of an <Image Anchor> instance are interpreted as the locations of corners of the given <Image> instance, not those of the centre of the texels in the corners of the <Image> instance.

When an <Image Anchor> instance is interpreted as a component of an <Image> instance or as a component of an <Image Mapping Function> instance specifying a planar projection, the <Location> components of the <Image Anchor> instance are interpreted as follows.

  1. The first <Location> component specifies the location to which the lower left corner of the <Image> instance is mapped.

  2. The second <Location> component specifies the location to which the upper left corner of the <Image> instance is mapped.

  3. The third <Location> component specifies the location to which the upper right corner of the <Image> instance is mapped.

When an <Image Anchor> instance is interpreted as a component of an <Image Mapping Function> instance that specifies a non-planar projection, the <Location> components of the <Image Anchor> instance are interpreted as follows.

  1. For a cylindrical projection, the first <Location> component specifies the centre of the cylinder. The second specifies a point at the centre of the top of the cylinder, thus indicating direction. The third <Location> component specifies the alignment of the cylinder by specifying a point on the surface of the cylinder.

  2. For a spherical projection, the first <Location> component specifies the centre of the sphere. The second specifies the point at the north pole of the sphere, thus indicating direction. The third <Location> component specifies a point on the equator of the sphere.

Fields Notes

srf_context_info

The srf_context_info field specifies the SRF within which the <Image Anchor> instance is defined.


Prev: Image. Next: Image Library. Up:Index.