Orbit Composite Resource

An Orbit Composite Resource (*.ocr) uses index to access a set of resources and present these to Orbit as a single read-only resource.
The set of resources can be a defined (fix list) or can be undefined (all files within a folder).

An OCR can combine multiple resources from any supported datatype.

All combined resources should have the same coordinate system. The CRS doesn't need to be defined for each individual resource.
All combined resource files should be available in the same directory of the ocr file or any subdirectory of this “root” directory.

Every resource combined by the composite resource will appear as a different Model.

An Orbit Composite Resource :

• is an easy way to access multiple files that should belong together (e.g. multiple tiles of a grid).
• is useful for accessing files that can be modified outside the user's domain. When opening an OCR, Orbit will read all files from disc, making sure the latest saved changes are presented to the user.
• there is no limit on the number of resources that can be combined in one OCR, but be wise.
  Every single resource from the OCR needs to be stored in memory.
  When combining a lot of files from the same datatype that will not be updated in future one OVT for vector data or one OMI for image or raster data is advised.

A defined OCR can be assembled using an Orbit standalone.
All datasets in an opened workspace can be saved to an OCR, via the Main Toolbar > Workspace > Save Workspace as OCR…

To modify the Model-usernames of an OCR, one needs to adjust the dataset Resource Description file (*.ord).
If not present, an ORD-file may be created automatically by assigning a coordinate reference system.

Example code in text-editor

<?xml version="1.0" encoding="UTF-8"?>
<Content>
    <ResourceList>
        <Resource>
            <Location>map1.shp</Location>
            <ResourceDriver>com.eurotronics.orbitx.driver.shape.ShapeDriver</ResourceDriver>
        </Resource>
        <Resource>
            <Location>map2.ovf</Location>
            <ResourceDriver>com.eurotronics.orbitx.driver.shape.ShapeDriver</ResourceDriver>
        </Resource>
        <Resource>
            <Location>ortho.omi</Location>
            <ResourceDriver>com.eurotronics.orbitx.driver.geoimage.GeoImageDriver</ResourceDriver>
        </Resource>
    </ResourceList>
</Content>

A undefined OCR can only be assembled using a text editor, e.g. notepath. For more information contact the Orbit support team (support at orbitgis dot com).

Example code in text-editor

<?xml version="1.0" encoding="UTF-8"?>
<Content>
    <ResourceList>
        <ResourceFilter>
            <FileNameFilter>folder\*.ovf</FileNameFilter>
            <SubFolders>false</SubFolders>
        </ResourceFilter>
    </ResourceList>
</Content>

An Orbit Composite Resource can be accompanied by a Orbit Resource Description file (*.ord) or a projection file (*.prj) having the same name to define the coordinate reference system.

The Object Composite Resource can be accompanied by an Orbit Legend file (*.olg) to define the legend or presentation of the resource in Orbit.
If no legend file is available for the composite resource, the legend files of the composing resources will be used.
When creating a legend file for a composite resource, Orbit will start from the according dataset legends.