.. include :: substitutions.txt Introduction ===================== |GC| is a |J| component that let you easily embed beautiful |GM| or |OLM| into your |J| website. Standard |J| articles, can be bound to |GCIs| - which consist in geographic features such as *POINTs*, *LINEs* and *POLYGONs* - and the resulting maps can be shown in the article page and/or in one or more overview maps. A single |GCI| can be represented by more than one geographic type: so that you can have simultaneously a set of POINTS, some POLYGONS and some LINES for a single |J| article. |GCIs| on the map are grouped by |GCLs|, graphic appearance of |GCIs| can be fully customized defining styles attributes in the |GCLs| configuration panel. |GC| was created as a sort of *Geographic Index* to |J| articles, the earliest versions had a tight binding between |J| articles and the geometric features that |GC| was going to show on its maps. Suggestion from the users made |GC| subsequently evolve to cover more general use cases, it is now possible to create |GCIs| which are completely unbound from existing |J| articles. The new Access Control List (ACL) features introduced by |J| 1.6 are now fully supported by |GC| allowing a fine grained control over the front-end and back-end user access to the different operations available in the software. |GCIs| are also language-aware: they can optionally make use of the same |J| language support system recently introduced for |J| core articles. .. _requirements: Requirements ------------ |GC| requirements are the same as |J| 1.7.x. .. warning:: *simplexml* PHP extension is required by |GC|, this extension is a standard extension and is normally installed by default. In a few rare cases, we've found this extension was missing, if in doubt, ask to your system administrator or ISP to install this extension. Key features ------------ What makes this component unique among other mapping tools in the |J| galaxy is probably the level of assistance (this is really what people pays for), its ease of use, its configurability and and its Import/Export functions. Import/Export ............. Input functions allows you to import tracks from a *GPX* file or directly draw into a map window within your browser, all your data will also be readily available in *KML* format. Place your maps everywhere .......................... With the |GC| core output you can place your |GC| maps in one or more pages choosing one of the available :ref:`map_renderers`. Using :ref:`plugins` you can also place customized :ref:`tag_maps` everywhere in an article or get the map inserted automatically in all articles where a linked |GCI| exists. Styles & more ............. From the control panel interface you can configure the appearance in details: for each |GCL|, you can style: * Line color * Line width * Polygon line color * Polygon fill color * Polygon line transparency * Polygon fill transparency * Point icon * Point icon size (|OLM|, |OLWM| and KML only: not supported in the embedded |GM|) Of course you can configure several aspects of the main map appearance: * |TOC| (TOC) type (hidden, list, select) * TOC position (left, top, right, bottom) * TOC and main map width (onyl useful for TOC position left and right) * Which layers should be activated at start (none, all, selected) * Map dimensions * KML icon (hide or show) |OL| based maps (|OLM| and |OLWM|) supports more styling attributes: * Labels for features (you can choose, font, color and transparency) * Clustering for points (|OLWM| only: points which are closer than 20px at the current visualisation scale are grouped) * Selection style: selected items (when the user clicks on an item) are styled differently Geocoding ......... :ref:`geocoding` allows the user to enter an address in a form field and get either redirected to a page of your site containing a |GC| map or get the existing map in the page (if any) centered and zoomed on the address coordinates. This module is quite flexible and allows some nice tricks. Map types --------- |GC| can produce different kind of maps, allowing a broad range of use cases. Overview maps ............. An :ref:`Overview Map` can be used as a *geographic index* to your |J| contents (articles or other |J| elements), this kind of map is typically used as a primary or secondary home page to show how website's contents are positioned on the globe. Automatic maps .............. An :ref:`automatic map` is generated by a |J| :ref:`content_plugin` which automatically adds a map to an article's page if the article has an associated |GCI|. Tag maps ........ Tags maps are the most flexible type of map: they are inserted by a |J| :ref:`content_plugin` which replaces the `{geocontent}` string when found in an article's body. Tags maps can be configured in depth to show or not to show the |TOC| or certain layers. Map renderers ------------- Available map types can be shown using different :ref:`map_renderers`. |GC| renderers have both a different appearance and different configuration options. .. _glossary: Small glossary --------------- Just a few terms used in this manual and their meaning: * |GCL|: layers are groups of geometric features (|GCI|, see below), they also hold all informations concerning the appearance (colors, transparency, line width etc.) of the |GCI| * |GCI|: these are the geometric features which share the same balloon text (if any), the same hyperlink (if any) or the same link to a |J| article (if any), |GCI| can also be ''complex'' in the sense that |GC| does not pose any limitation on the number or geometric type (POINT, LINE or POLYGON) of the individual geometric entities you place in a |GCI| * |TOC|: a list of layers with associated controls to switch visualisation on or off and optionally a small globe icon to download layer's contents in the KML format. * **Front-end**: the public side of |J|, the |J| administration control panel is also known as *back-end*.