For documentation on the current version, please check Knowledge Base.
Orbit Legend
| Name | Orbit Legend File |
| Acronym | OLG |
| File Extension | *.olg |
OLG stands for Orbit Legend File. This is an extension file that can accompany any spatial storage format.
Features
An orbit legend defines values for rendering parameters.
For each rendering parameter a default value can be specified. In OrbitGIS terms such a set of default values is called the “Basic Appearance” of a model. Depending on the spatial type of the model the rendering parameters may differ.
Rendering parameters can be directly linked to the value of a specific attribute of each individual object.
A more advanced feature of the Orbit Legend system is defining a model-level classification on one attribute and then defining rendering parameters for each of the classification groups. That way individual objects will be rendered according to which classification group they belong to. Multiple classifications can be made within one model, as long as the rendering parameters defined for the classification group are not used in another classification. Classification is available for models of any spatial type.
Label rendering is available for models of any spatial type.
Piechart rendering is a special rendering style rendering a pie in the middle of each object in the model. Pie slices can be determined by listing a number of attributes. That way the size of each slice is directly linked to the attribute value of each individual object.
Another approach is to create an object-level classification on one attribute. A color and label can be assigned to each classification group. That way the size of each Pie slice is defined by looking at the size of the classification group for the individual object. Using an object-level classification is only useful when an object has multiple attribute sets. Piechart rendering is available for models of any spatial type.
More information about the Orbit Legend tools : Dataset Legend Editor
OrbitGIS
Generally a OLG file is stored on the same location and has the same name as the dataset itself. However, if no such “sibling” legend file is found, OrbitGIS will automatically generate a default legend. Saving an unsaved legend (save button) will result in a legendfile on the same location and with te same name as the dataset itself. It is not necessary to define the location and name to the file.
It is possible to store a legend file as a different name or on a different location. This option is common in the following cases :
| One dataset with more legendfiles. | This is used for datasets which maintain a lot of information. That information can be displayed on the map by defining a legend. Because it is a lot of information (f.e. lots of attributes), it will be represented by several legends. In such case a legendfile with the same name as the dataset is mostly a basic legend. Legendfiles with different names are legends that represent spatial information on a specific way such as classification, labels and/or Pie Charts. Tip: Give a meaningful name to the legendfiles. Do not choose e.g. floods1.olg, floods2.olg but choose floods_riskareas.olg, floods_floodedareas.olg, floods_compareyear.olg Give a description for each legendfile - floods_riskareas.olg : Highlights all the risk areas for floods - floods_floodedareas : Highlights the flooded areas - floods_compareyear : Visualises pie charts that compare the data of several years |
|---|---|
| One legendfile for more datasets. | This is used for datasets who are similar to each other. This means having exactly the same model(s) and attributes, but the content is different. Define the legend once and apply it for all other datasets. For example datasets that vary in time (floods_2010, floods_2011, floods_2012,…) or in space (floods_alabama, floods_mississippi) . One legend is used: floods.olg |
The EOS Server
General information about the eos server is available on the page: Orbit EOS Console
Information about the managing of resources (datasets) with the EOS server is available on the page: Resources > Datasets > Dataset Setup
The EOS server is the GIS data server for your organisation or enterprise, either local, corporate wide or for internet/intranet use. The EOS Server also manages the resources (datasets) that are connected to Orbit GIS.
The EOS Console will automatically recognize the legend file that is stored on the same location and with the same name as the dataset. It is not necessary to define it.
When another name or location is used, the legend file must be defined.
| One dataset with more legendfiles. | One dataset can be set as many resources if each resource is linked to another legend. |
|---|---|
| One legendfile for more datasets. | Link one legend to more resources. |
Legend and Models
Models refer as layers in Orbit GIS and have their own graphical appearance. As datasets can have several models, for each model within the dataset a legend can be defined. Depending on the spatial type of the model (f.e. points, lines, areas or images) the parameters for the legend editing are different.
