diff options
-rw-r--r-- | doc/book-enea-edge-getting-started/doc/submaps.xml | 52 |
1 files changed, 28 insertions, 24 deletions
diff --git a/doc/book-enea-edge-getting-started/doc/submaps.xml b/doc/book-enea-edge-getting-started/doc/submaps.xml index 54923a5..84bbda6 100644 --- a/doc/book-enea-edge-getting-started/doc/submaps.xml +++ b/doc/book-enea-edge-getting-started/doc/submaps.xml | |||
@@ -1,5 +1,5 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | 1 | <?xml version="1.0" encoding="UTF-8"?> |
2 | <chapter id="maps"> | 2 | <chapter condition="hidden" id="maps"> |
3 | <title>Maps</title> | 3 | <title>Maps</title> |
4 | 4 | ||
5 | <section id="submaps"> | 5 | <section id="submaps"> |
@@ -355,9 +355,10 @@ | |||
355 | <section id="tileserver"> | 355 | <section id="tileserver"> |
356 | <title>Tile Server Map</title> | 356 | <title>Tile Server Map</title> |
357 | 357 | ||
358 | <para>The Enea Edge Management application has the capacity to render a map from a tile | 358 | <para>The Enea Edge Management application has the capacity to render a |
359 | server. Each uCPE device can have a set location and will be automatically | 359 | map from a tile server. Each uCPE device can have a set location and will |
360 | placed on the tile server map at its exact location.</para> | 360 | be automatically placed on the tile server map at its exact |
361 | location.</para> | ||
361 | 362 | ||
362 | <section id="tileserver_config"> | 363 | <section id="tileserver_config"> |
363 | <title>Tile Server Configuration</title> | 364 | <title>Tile Server Configuration</title> |
@@ -403,8 +404,8 @@ | |||
403 | <row> | 404 | <row> |
404 | <entry>TileJSON URL</entry> | 405 | <entry>TileJSON URL</entry> |
405 | 406 | ||
406 | <entry>The URL of the TileJSON configuration file. Leave it | 407 | <entry>The URL of the TileJSON configuration file. Leave it |
407 | blank if the tile server used does not support json | 408 | blank if the tile server used does not support json |
408 | configuration files.</entry> | 409 | configuration files.</entry> |
409 | </row> | 410 | </row> |
410 | 411 | ||
@@ -427,12 +428,13 @@ | |||
427 | 428 | ||
428 | <note> | 429 | <note> |
429 | <para>The Browser Cross-Origin Resource Sharing (CORS) policy prevents | 430 | <para>The Browser Cross-Origin Resource Sharing (CORS) policy prevents |
430 | requests from HTTPS to an external HTTP. This means that if the default | 431 | requests from HTTPS to an external HTTP. This means that if the |
431 | HTTPS configuration is used for the Enea Edge Management application, | 432 | default HTTPS configuration is used for the Enea Edge Management |
432 | the application will not be able to reach a tile server that is | 433 | application, the application will not be able to reach a tile server |
433 | accessible only through HTTP. In this case a proxy can be installed that | 434 | that is accessible only through HTTP. In this case a proxy can be |
434 | provides a gateway for HTTPS calls to HTTP. Optionally, HTTP web access | 435 | installed that provides a gateway for HTTPS calls to HTTP. Optionally, |
435 | can be used for accessing the Enea Edge Management application.</para> | 436 | HTTP web access can be used for accessing the Enea Edge Management |
437 | application.</para> | ||
436 | </note> | 438 | </note> |
437 | </section> | 439 | </section> |
438 | 440 | ||
@@ -463,9 +465,10 @@ | |||
463 | 465 | ||
464 | <listitem> | 466 | <listitem> |
465 | <para>In the <emphasis role="bold">Create View</emphasis> window, | 467 | <para>In the <emphasis role="bold">Create View</emphasis> window, |
466 | set a name for the TileServer view, select <literal>tileserver</literal> | 468 | set a name for the TileServer view, select |
467 | in the <emphasis role="bold">Map Type</emphasis> drop-down menu and place the | 469 | <literal>tileserver</literal> in the <emphasis role="bold">Map |
468 | admin user in the right-hand side list-box.</para> | 470 | Type</emphasis> drop-down menu and place the admin user in the |
471 | right-hand side list-box.</para> | ||
469 | </listitem> | 472 | </listitem> |
470 | 473 | ||
471 | <listitem> | 474 | <listitem> |
@@ -561,16 +564,16 @@ | |||
561 | 564 | ||
562 | <listitem> | 565 | <listitem> |
563 | <para>If the <emphasis role="bold">Override device | 566 | <para>If the <emphasis role="bold">Override device |
564 | location</emphasis> checkbox is left unchecked, the device will be placed at | 567 | location</emphasis> checkbox is left unchecked, the device will be |
565 | the coordinates previously set in the <emphasis | 568 | placed at the coordinates previously set in the <emphasis |
566 | role="bold">Location</emphasis> tab.</para> | 569 | role="bold">Location</emphasis> tab.</para> |
567 | </listitem> | 570 | </listitem> |
568 | 571 | ||
569 | <listitem> | 572 | <listitem> |
570 | <para>If the <emphasis role="bold">Override device | 573 | <para>If the <emphasis role="bold">Override device |
571 | location</emphasis> checkbox is checked, the coordinates set on the device | 574 | location</emphasis> checkbox is checked, the coordinates set on the |
572 | previously will be ignored, and the device will be placed at the cursor's | 575 | device previously will be ignored, and the device will be placed at |
573 | position.</para> | 576 | the cursor's position.</para> |
574 | 577 | ||
575 | <note> | 578 | <note> |
576 | <para>Checking the <emphasis role="bold">Override device | 579 | <para>Checking the <emphasis role="bold">Override device |
@@ -583,8 +586,8 @@ | |||
583 | <para>A device already placed on the map can be dragged and dropped | 586 | <para>A device already placed on the map can be dragged and dropped |
584 | inside the map. Coordinates will not be changed.</para> | 587 | inside the map. Coordinates will not be changed.</para> |
585 | 588 | ||
586 | <para>If two or more uCPE devices are too close together on the map, and | 589 | <para>If two or more uCPE devices are too close together on the map, and |
587 | the current zoom level cannot accommodate all their icons, a cluster | 590 | the current zoom level cannot accommodate all their icons, a cluster |
588 | will be shown. The cluster is represented by a large circle that | 591 | will be shown. The cluster is represented by a large circle that |
589 | displays a number representing the number of devices it contains. The | 592 | displays a number representing the number of devices it contains. The |
590 | color of the cluster changes according to the alarms of the devices in | 593 | color of the cluster changes according to the alarms of the devices in |
@@ -594,7 +597,8 @@ | |||
594 | elements can be distinguished. When hovering over the cluster, a window | 597 | elements can be distinguished. When hovering over the cluster, a window |
595 | with information about the cluster will be available. It will contain | 598 | with information about the cluster will be available. It will contain |
596 | the number of the devices in the cluster, as well as their status. The | 599 | the number of the devices in the cluster, as well as their status. The |
597 | Devices link will open a drop-down menu that contains all the devices.</para> | 600 | Devices link will open a drop-down menu that contains all the |
601 | devices.</para> | ||
598 | </section> | 602 | </section> |
599 | </section> | 603 | </section> |
600 | </chapter> \ No newline at end of file | 604 | </chapter> \ No newline at end of file |