General principles
From Geoikia-english
Contents |
Introduction
You can arrange the setting of the Geoide Viewer with the Geoide Author. Before the Geoide Author to work, it is advisable to learn some basic principles. These general principles are explained below.
What is a Geoide Application
An application consists of a Context (collection of digital maps) and a Viewer configuration (Gui-config) or Lay-out of the Geoide Viewer. A context can be linked to multiple viewer configurations. It is therefore possible for the Geoide Viewer to focus on different target groups, which maps are the same, but which functionality and layout can be adjusted to different groups of users. Within a context a print functionality, search functions and report references (search the map) can be used.
Hierarchy
The Geoide Author uses a certain hierarchy. This is visualized in its tabs and a tree:
Tab: Contexts
At the highest level are the contexts. Each context consists of maps and layers. Layers can be grouped by group respectively. Each map can be equipped with search functions, report templates and print references.
Tab Servers: This indicates what services are available for retrieving map information.
Tab Viewer Configurations: Here the layout of the viewer is made. A context can use multiple viewer configurations.
Tab Admin: The actual removal of items from the database can be done via this menu.
Remove and discard
The Geoide Author works with lists and references. This has the following consequences for the user:
- If an item from the tree is removed then the reference to that item will be removed. The item itself remains in the Geoide Author and can be found in the lists and remains available to the user. When deleting an item, a dialog opens in which the user is asked whether the item itself should be removed from the database. Exception is the removal of a context. This item will be removed without warning. The underlying maps, layers etc. however remain present within the Geoide Author. The actual removal of data from the database can also be done through the tab Admin.
- When an item is added the Geoide Author will add the item to the list and a reference to the item will be created (Reference is based on the location in the tree where the user added the item).
- When an item is copied the original will be used as basis and used for the new item. The new item will have a new unique name. When copying a layer, the reference to the service where the layer is retrieved is also copied. This means that in the Geoide Author different layers with differnet names may exist but with the same source. A copy includes only the item itself and not the underlying items. For example, if a map is copied, the map’s properties are also copied, but not the underlying layers.
Configure once and multiple use in context and/or maps
The configurable items (maps, layers, group layers, added inputs, Report Templates and Print References) may be used in multiple context/maps simultaneously. Changes applied to an item apply to all places the item has been used. You can also copy an item and reuse the item. A copied item behaves as a new item.
Scope (public/private)
It is possible to hide items for others. This is indicated by the "scope". If the scope is "private", then other users cannot see this item (layer, layer group, etc..). If the scope is "public", then other users can see and use it. However, the configured item cannot be changed by others. A component assigned as "public" cannot be assigned again as "private". However, the item "owner" can still change the item. Users are not automatically notified when the owner has modified the item.
Save Changes to the server
All changes made via the Author are only stored on the server after clicking on the Save button at the bottom of the Author screen. If changes are not stored yet, then you can undo the changes by pressing the 'Refresh' button of your browser.
> Main Page > Background Information > General principles
