Component administration

Component options


Proxyhost

Path to the proxy host script, eg : "/cgi-bin/proxy.cgi?url=".
If left empty, no proxy host script will be used.

Url of the print service

Url of the mapfish-print service, eg : http://localhost/print-servlet/pdf/
If this URL is not defined, the Print tool will be automatically disabled.

Url of the method print

Url of the print method.
If not set, it will be deducted from the print service URL like this :
[print service url]print.pdf

Url of the method create

Url of the create method.
If not set, it will be deducted from the print service URL like this :
[print service url]create.json

Joomla inherited properties

  • Permissions

Layer groups


Layer groups are used to gather layers by theme/subject in the map viewer.

Properties :

  • Name : visible denomination of the group in the layers tree
  • Alias : internal denomination of the group in the map viewer.
    The alias 'background' is a reserved word used by the viewer to identify the background layer group (typically, a background layer group contains exclusive base layers).
    As background group is defined by context and is not an intrinsic property of a group, the used of this alias is protected.
  • is default open : initial opening status of the group

Joomla inherited properties

  • Access level
  • Status
  • Permissions

Layer


Properties :

  • Name : initial layer name in the layer tree, overwrite with the value from the capabilities of the service
  • Alias : internal denomination
  • Overlay Groups : group to which the layer belongs to
  • Service : physical or virtual service from which the layer is issued
  • Authentication : optional user/password fields in case of the selected service requires authentication
  • Layer : layer name as defined in the service. Button at the right of this combobox executes a GetCapabilities on the selected service and populates with layer names this element
  • Tiled : layer tiled state
  • Default visible : initial layer visibility
  • Opacity : initial layer opacity
  • Metadata link : url to a web page. If defined, the layer tree node will be rendered as a link.
  • To add as an OpenLayers layer
    Adding a layer to the viewer is done by using high-level libraries options (OpenGeo SDK and GeoExt).
    However, this option allow to define a layer directly with the low-level librarie OpenLayers.
    This can be usefull when :
    - some specific parameters are not handle by the high-level libraries
    - the layer to add is a WMTS which does not have a high-level libraries handler
The following properties are used to build the OpenLayers layer, in combination with the previous generic properties :
  • WMTS
  • Style : One of the advertised layer styles. Must be provided.
  • Matrix Set : One of the advertised matrix set identifiers. Must be provided.
  • Options : All the key/value pairs (comma separated) to add in the 'config' object to send to the layer constructor
new OpenLayers.Layer.WMTS (config)

eg :
format:"image/png",
> dimensions:[],
> requestEncoding: "KVP",
> matrixIds:[
> {identifier:"0",scaleDenominator:559082264.02,matrixWidth:1,matrixHeight:1,tileWidth:256,tileHeight:256,topLeftCorner:{lon:-20037508.34,lat:20037508.34 }},
> {identifier:"1",scaleDenominator:279541132.01,matrixWidth:2,matrixHeight:2,tileWidth:256,tileHeight:256,topLeftCorner:{lon:-20037508.34,lat:20037508.34 }},
> {identifier:"2",scaleDenominator:139770566.00,matrixWidth:4,matrixHeight:4,tileWidth:256,tileHeight:256,topLeftCorner:{lon:-20037508.34,lat:20037508.34 }},
> {identifier:"3",scaleDenominator:698852830.03,matrixWidth:8,matrixHeight:8,tileWidth:256,tileHeight:256,topLeftCorner:{lon:-20037508.34,lat:20037508.34 }}
> ]

NB : To allow a WMTS layer with a KVP request Encoding to be print with MapFish Print, the matrixIds param must be provided with all the properties present in the previous example.

  • WMS/WMS-C
  • Style : One of the advertised layer styles. Must be provided.
  • Options : All the key/value pairs (comma separated) to add in the 'options' object to send to the layer constructor
new OpenLayers.Layer.WMS (name, url, params, options)

eg :
resolutions: [1056.633663,528.3168317,264.1584158,132.0792079,66.03960396,26.41584158, 13.229166668, 6.614583334, 2.645833334],
> attribution:'<a href="http://www.provider.org/" target="_blank"><img src="http://provder.org/logo.gif"></a>
> <a href="http://www.provider.org/terms.pdf" alt="TOS" title="TOS" target="_blank">Terms of Service</a>

Joomla inherited properties

  • Access level
  • Status
  • Permissions

Context


Properties :

  • Name : page title
  • Alias : internal identifier
  • Url : URL to view the context (with the default Joomla! template. To go further on integrated context in Joomla!, see Defining Context Links)
  • Background group : group to use as background group. This means that layers of this group will be used as base layers in the map.
  • Overlay Groups : groups to use as overlay group.
  • Default adding group : the layer adding with the "Add layer" tool will be here. If not set, the first overlay group will be used for that purpose.
  • Service : available services in this context. This list must contain all the services delivering the layers belonging to the selected groups (background and overlay).
    This list can contain additional services available for adding layer with the "Add layer" tool.
  • Default service type : when using a Proxyhost (see System_environment), you can dynamically add services in the viewer. The type of those services must be set here. Only one type by context.
  • Srs : System reference system of the map, eg : EPSG:900913
  • Unit : Unit of the map.
  • Center coordinates : Center coordinates, in the previous srs, of the map, eg : -900, 5350000
  • Max resolution : max resolution of the map, eg : 156543
  • Max extent : max extent, in the previous srs, of the map, eg : -1100000,4600000,989115,6216470
  • Root node text : optional text to overwrite the layer tree root node text. Default value is empty.
  • Map title : Title of the document to print
  • Abstract : Abstract of the document to print
  • Tools : list of the tools available in the context. No dependencies between each other.

Joomla inherited properties

  • Access level
  • Status
  • Permissions

Joomla inherited properties description


Each item defined in the EasySDI Map component inherits of these 3 standard Joomla! properties :

Access level

From : http://docs.joomla.org/ACL_Tutorial_for_Joomla_1.6

Controlling What Users Can See

The setup for controlling what users can see is done as follows:

  1. Create the different User Groups required for the site. Each Group can be thought of as a role that a user will have for the site. Keep in mind that one User can be a member of one or more Groups. If desired, groups can have parent groups. In this case, they automatically inherit the Access Levels of the parent group.
  2. Create the set of Access Levels required for the site. This could be a small number or a large number depending on the number of different groups and how many categories of items there are. Assign each Access Level to one or more of the User Groups created in step 1.
  3. Assign each item to be viewed to one Access Level. Items include content items (articles, contacts, and so on), menu items, and modules.

Any time a user is about to view an item on a Joomla page, the the program checks whether the user has access to the item, as follows:

  1. Creates a list of all the Access Levels that the User has access to, based on all Groups that the User belongs to. Also, if a group has a parent group, access levels for the parent group are also included in the list.
  2. Checks whether the Access Level for the item (article, module, menu item, and so on) is on that list. If yes, then the item is displayed to the user. If no, then the item is not displayed.
  3. Note that Access Levels are set separately for each Group and are not inherited from a group's parent group.

Access level checkin for map items is detailled in Loading a context

Permissions

From : http://docs.joomla.org/ACL_Tutorial_for_Joomla_1.6

Controlling What Users Can Do

The system for setting up what users can do -- what actions they can take on a given item -- is set up with the Permissions tab of Global Configuration and the Permissions tab of the Options screen of each component. Permissions can also be set up at the Category level for core components and at the Article level for articles.

Note that this set up is independent of the setup for viewing.

When a user wants to initiate a specific action against a component item (for example, edit an article), the system checks the permission for this combination of user, item, and action. If it is allowed, then the user can proceed. Otherwise, the action is not allowed.

Status

An item can have one of the following status :
- published
- unpublished
- archived
- trashed

Only published items can be accessible on the site by users.
Other status are handle by administrators and allow them to manage life cyle of the items.

The usual life cycle of item in Joomla! is:

  1. unpublished : Item is editing/reviewing by an administrator and is not visible in the site.
  2. published : Item is made available for the site. Users could see it according to their access level.
  3. archived : Item are no more visible.
  4. trashed : Item is place in the trash. It still exists and can be retrieved