• Installation guide
• Service-application-interface

Add a fixed div on the bottom of the form ad insert a clone of the "Reset all" and "Search" button group

Develop a login system according to Milko's Service

The menus on the right and the text juxtapose when the side of the window in not big, the text could be moved on top of the menus so that they do not mix.

Create these functions in Cypher class:

• send_to_service()
• decrypt_message()

and finish to develop these functions:

• encrypt_message()
• export_key_to_server()

Try searching for Elevation, set a range from 6000 to 7400, then try looking at map.
The map is frozen and you cannot do anything.
This might be because the cluster default zoom is greater than the map's maximum zoom: this should be checked.

Service

• matchTagsByLabel's response must returns also the number of markers that will be displayed on relative map (@milko)

Interface

• Change panel's colour if markers are more than 10k (class panel-danger) or disable buttons if markers are 0
• Add a cloud on "Show on map" button with this text: Too many points (xxx) , reduce your selection.

The map window of node details has 2 problems:

1. Cannot close
2. Info tooltips not opens

The log type variables are better constants instead of defines.

class Cypher {
        const E = "error";
        const W = "warn";
        const I = "info";
        const D = "debug";
        const T = "trace";

      ...

and then call with:

$this->log(self::E, "message");

Add a text "help-block" on the bottom of each input with the indication of the return button is disabled for this form

The function $.add_geojson_cluster has the Service query for load marker's tooltip contents that cause map crash:

markers.on("click", function(m) {
        var objp = {};
        objp.storage_group = "results";
        objp[kAPI_REQUEST_OPERATION] = kAPI_OP_GET_UNIT;
        objp.parameters = {};
        objp.parameters[kAPI_REQUEST_LANGUAGE] = lang;
        objp.parameters[kAPI_REQUEST_PARAMETERS] = {};
        objp.parameters[kAPI_REQUEST_PARAMETERS][kAPI_PARAM_LOG_REQUEST] = "true";
        objp.parameters[kAPI_REQUEST_PARAMETERS][kAPI_PARAM_ID] = m.layer.feature.properties.id;
        objp.parameters[kAPI_REQUEST_PARAMETERS][kAPI_PARAM_DATA] = kAPI_RESULT_ENUM_DATA_FORMAT;
        objp.parameters[kAPI_REQUEST_PARAMETERS][kAPI_PARAM_DOMAIN] = m.layer.feature.properties.domain;
        $.ask_to_service(objp, function(marker_content) {
                $.each(marker_content.results, function(domain, rows) {
                        //$("#marker_content").find(".modal-title").html(rows[7].name + " " + domain);
                        $("#marker_content").find(".modal-body").html($.parse_row_content(rows));
                });
                $("#marker_content").modal("show");
                $("#marker_content a.text-info").popover({container: "body", placement: "auto", html: "true", trigger: "hover"});
        });
});

http://influxdb.com/ 👍

When user remove or reset forms, next researches produces invalid enums and/or summary data aren't displayed properly.
Perhaps the cause is on the local storage (on form check)

The map selection should be divided as follows:

A. Empty base maps

B. Labelled base maps

C. Labels

D. Environmental layers

To be decided.

E. Climate layers

The level column represents the default level.

Level 0 represents the background, levels larger than zero represent the foreground. If the library represents this in the inverse order, just look at this text upside-down.

All maps in layer groups A and B share a single level, 0, which represents the background. Whenever a map is selected, the current contents of the level are replaced by the new one.

Layer groups A, B and C have static levels, which means that their order cannot change.

Layer groups D and E have dynamic levels, which means that the user may re-arrange them to change their background/foreground order. The preferred way would be to allow dragging the selected elements to indicate the order.

Elements in map layer E which share the same default level are to be considered variations of the same layer: for instance, Clouds and Clouds (enhanced) represent the same layer, except that they are two variations of the same theme, this means that when their order is changed, both elements will share the new level.

Whenever a map from layer A is selected, all other layers are enabled; when an element of layer B is selected, layer group C is disabled.

The default layer map is Esri.WorldImagery.

All layer group elements with a maximum zoom level lower than the current zoom level should be disabled; this means that maps become enabled as the used reduces the zoom level.

The developing of map tools must be completed.

On the interface

• Add marker (function exists but no integrated on map)
• Add tooltip (function exists but no integrated on map)
• Measure distances (not working perfectly)

The following features must be added to the login form:

• A way to restore password
• A description for the invitation policy
• A link for require an invitation

Need a Service that includes all main constants and returns an object.
This Service will be called by an asynchronous reques and then stored in user's local cache.

As showned below, when the map is displayed there's no way to know what markers are going to show.
Find a solution to "summarise" what is displayed.

Map functionalities

Layers

• Layers management
• Drag and drop layers position

Tools

• Distance measurement
• Show position on click
• Add Marker

Treeselect popover cannot ever open

The map window of node details has 2 problems:

1. Cannot close
2. Info tooltips not opens

• Token for admins (allows operation directly via API)
• Manage local RSA key (renew) for allow communications with remote service server
• Caching system (mem_cached)

Integrate the advanced admin template to site

Create a simple markdown blog using https://github.com/Dynalon/mdwiki

Currently measurements is shown on left panel.
Show measurements on the bottom-center text

in raw data details, urls might be converted to links.
Do not forget to add target="_blank" as html attribute.

Create a system to auto-manage marker colours and then let the user to choose its own preferred (on each marker and on a group of markers)