.. raw:: html

    <style> .red {color:red} </style>

.. role:: red


=========================
What's New in Version 3.2
=========================

These are the main new features of the most recent Pathfinder release, the 3.2 version:

* :ref:`Cost calculation models <costs_3_2>`
* :ref:`Identify and edit feature attributes <attrib_3_2>`
* :ref:`Pylon report <pylon_report_3_2>`
* :ref:`Pathfinder Explore algorithm (beta) <ga_3_2>`
* :ref:`Hybrid planning and tunneling <combined_3_2>`
* :ref:`New geoproceses <geoprocesses_3_2>`
* :ref:`New resistance map palette <RM_palette_3_2>`
* :ref:`Improved pylon spotting <pylon_spotting_3_2>`
* :ref:`StreetView tool <streetview_3_2>`
* :ref:`Presentation view <simpleview_3_2>`
* :ref:`Export intermediate points <interpoints_3_2>`
* :ref:`German language interface <german_3_2>`

Previous releases:

* :doc:`What's new in Pathfinder 3.1 <whatsNew3.1>`


.. _costs_3_2:

Cost calculation models
=======================

A cost calculation model estimates the monetary cost of building or operating the infrastructure defined by a route. In previous Pathfinder versions, there was only one predefined cost calculation model and detailed parameters. The unit costs per layer had to be set up in the administration tool. 

In the new release:

* **Múltiple cost estimation models** are supported for each scenario. In the :ref:`scenario settings <cost_models>`, the user can select which calculation models to apply when paths are calculated or refreshed. 

  Depending on your company settings, some custom cost estimation models may be available. Check with Gilytics if you need specific cost calculation models.

  .. image:: ./images/costModels.jpg
    :align: center

|

* **Cost model configuration**. Cost models use *global parameters*, accessible through the cost model Settings button in the scenario settings:

  .. image:: ./images/costModelsConfig.jpg
    :align: center

  The cost models can also use *per-layer unit costs*, which are specified in the *properties panel* of each layer:

  .. image:: ./images/costModelsLayerConfig.jpg
    :align: center

|

* **Cost estimation table**. The :ref:`cost estimation table <path_cost>` can be open from the *Results/Path Cost* menu option or by clicking on the cost numbers in the Paths section of the Results panel. The cost model can now be selected in this report dialog:

  .. image:: ./images/costPanel.jpg
    :align: center

|

* **Cost reporting**. Finally, also the :ref:`printed report <print_report>` has been expanded to include estimated costs in the project summary section and the scenario section, where cost tables for all cost estimation models are provided:

  .. image:: ./images/costReportSummary.jpg
    :align: center

|

  .. image:: ./images/costReportTables.jpg
    :align: center


.. _attrib_3_2:

Identify and edit feature attributes
====================================

With Pathfinder 3.1, the option to :ref:`filter data based on attribute values <layer_settings>` was introduced. This means the attributes of geographic elements are important to classify the input data into layers and, therefore, set different resistance values.

To :ref:`identify the attributes <identify_attrs>` of objects in a specific layer, use the Identify icon in that layer's settings panel:

.. image:: ./images/identifyAttrib.jpg
  :align: center

The cursor will change into a blue dot. Click on an object of the selected layer:

.. image:: ./images/identifyCursor.jpg
  :align: center

After clicking, if one or more features are found in the selected location, their IDs and attributes will be shown in the Identify dialog:

.. image:: ./images/identifyAttrDlg.jpg
  :align: center

The features values can then be **edited** for uploaded and WFS layers, but not for OpenStreetMap layers. Type the value you want and then click *Enter*. When you do so and the change is performed, a green checkbox will appear next to it.

.. image:: ./images/identifyEdit.jpg
  :align: center

.. note::

  Attribute editing has important consequences:

  * The affected layers must be :ref:`processed <layer_preprocess>` again so the attribute change takes effect in the elements included in the layer. Also, the resistance map and other results must also be recalculated.

  * Attribute value changes affect the :ref:`base dataset <base_dataset_project_layers>` from which layers in different project may take their data, so all the projects using the modified data will change if their layers are reprocessed. This may be specially dangerous when editing WFS layers. A lot of projects and users may depend on the service data, so be careful with these changes and notify affected users.


.. _pylon_report_3_2:

Pylon report
============

Following customers' requests, Pathfinder 3.2 introduces a new :ref:`report <pylon_report>` to display a table of all the pylons or points created for each path, with their location and other properties.

.. image:: ./images/pylonReportMenu.jpg
  :align: center

|

.. image:: ./images/pylonReportDlg.jpg
  :align: center

As with other charts and reports, it can be **exported** to a CSV fle.

This table is also available in the :ref:`printed report <print_report>` for each scenario:

.. image:: ./images/pylonReport.jpg
  :align: center


.. _ga_3_2:

Pathfinder Explore algorithm (beta)
===================================

As part of our research program into :ref:`routing algorithms <algorithm_selection>`, Pathfinder 3.2 includes a new Pathfinder Explore algorithm which can be used like the standard routing algorithms, and also to solve specific problems like combined overhead-tunnel routing (see below). 

.. image:: ./images/exploreAlgo.jpg
  :align: center

Some advantages of this algorithm are:

* Small **memory footprint** and great performance with large areas.

* Generation of many **alternative routes**. By default this number is six, but in some cases (see the Tunneling geoprocess) can be configured.

* Extensible with complex geometric and multi-map **constraints**. Because the resistance evaluation (cost function) is clearly separated from the algorithm engine, the Explore algorithm can be extended to take into account specific geometric criteria (e.g. slope limits or advanced crossings constraints) and to use multiple resistance maps as input, describing alternate costs for different technologies used, so the most appropriate can be chosen for each route segment.

Compare the results of the Fast, Pylon Spotting and Explore algorithms.


.. image:: ./images/corridorsAndPaths.jpg
  :align: center


You are welcome to try this new routing method and give us your feedback.


.. _combined_3_2:

Hybrid planning and tunneling
=============================

More and more, combining multiple infrastructure modes or technologies to plan a single route is becoming an important requirement. For instance, it maybe necessary to find an optimal powerline path combining overhead and underground (earth cable) sections.

A new :ref:`hybrid planning geoprocess <routing_geoprocesses>` has been developed to address this routing problem. Its requirements are:

* The area where underground cables are preferred, the *critical area*, must be defined in a project layer.

* One scenario must define the *overhead constraints*, but in such a way that the overhead line crosses the critical area. This section will be then substituted by an underground route.

* The second scenario (subscenario) must define the *underground cable constraints*.

* The Start point must be located outside the critical area. The End point can be either in or out this area.

This image shows an example of results with a blue overhead section and a green underground section. Critical areas are displayed in a transparent red:

.. image:: ./images/hybridRouting.jpg
  :align: center

Similarly, in some countries it is important to combine conventional powerlines with tunnel segments. Again, a new :ref:`tunnel planning geoprocess <routing_geoprocesses>` has been implemented to do so by using a custom :ref:`Pathfinder Explore algorithm <ga_3_2>`.

This geoprocess uses *three different scenarios*, one for the conventional technology (typically overhead), a second one with the constraints defining the tunnel sections (usually should have a smaller resistance/cost than overhead for a high elevation, surface protected areas, type of geology, etc.), and a third scenario defining the cost of locating the tunnel entrance (usually must be away from populated areas, but not too far from transportation networks).

The geoprocess includes tunnel-specific constraints like maximum and minimum slope, and a maximum and minimum length for the tunnel sections.

.. image:: ./images/tunnelGeoprocess.jpg
  :align: center

The results can be displayed in the 2D and 3D views, where the tunnel sections are marked with dashed lines.

.. image:: ./images/tunnelView2D.jpg
  :align: center

|

.. image:: ./images/tunnelView3D.jpg
  :align: center

This video shows how to use the geoprocess to get combined routes with tunnels:

.. raw:: html

   <div style="text-align:center">
   <iframe width="560" height="315" src="https://www.youtube.com/embed/aamqJMoR8yc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
   </div>


.. _geoprocesses_3_2:

New geoprocesses
================

As with the :ref:`viewshed calculation <raster_geoprocesses>` processes in 3.1, Pathfinder 3.2 also adds new geoprocesses to our :doc:`geoprocessing toolbox <runGeoprocesses>`.


Path resistance
---------------

In addition to the :ref:`resistance profile chart <resistance_profile>`, this :ref:`geoprocess <path_resistance>` provides statistics about the total value and the variation of the resistance (taken from the resistance map) along the selected path. It is a convenient way to compare the "cost" of the paths calculated with similar constraints. It is also useful to estimate the resistance of a path in a different scenario from the one used to calculate it.

Note that the resistance values reported here will not include the angle cost and other constraints applied in advanced algorithms.

The path and the scenario are selected as input:

.. image:: ./images/geoprocResistance.jpg
  :align: center

The Results tab will show a button to download the table with the stats:

.. image:: ./images/geoprocResistanceOut1.jpg
  :align: center

|

.. image:: ./images/geoprocResistanceOut2.jpg
  :align: center


Ridge detection
---------------

Pathfinder creates automatically a digital elevation model (DEM) for the project area. This DEM can be used in some geoprocesses like the :ref:`Ridge and Hilltop Detection <ridge_detection>`:

.. image:: ./images/geoprocRidges.jpg
  :align: center

As a result, we obtain separate layers with the ridge lines and hilltop points, which we can download or add as a layer to the project:

.. image:: ./images/geoprocRidgesOut2.jpg
  :align: center


Once these results are added to the project, we can use them to apply further constraints on the route calculation, for instance, to avoid ridges and hilltops.


Clustering / generalization
---------------------------

Another new geoprocess can be used to :ref:`group together elements into larger shapes <clustering>`, for instance, find building groups to define larger shapes representing populated areas.

The geoprocess has some parameters to specify the amount of objects to include in each group and the maximum separation distance in a group.

.. image:: ./images/geoprocCluster.jpg
  :align: center

|

.. image:: ./images/geoprocClusterOut.jpg
  :align: center


Corridor extraction and coverage
--------------------------------

Pathfinder includes now a geoprocess to :ref:`extract a subcorridor from the corridor map <subcorridor>` (or from any other raster), the area closest to a selected optimal path.

.. image:: ./images/geoproc_subcorridor_result.jpg
  :align: center

On the other hand, we can also :ref:`calculate the area <corridor_coverage>` covered by the subcorridor on selected layers, visually as well as quantitatively in a table:

.. image:: ./images/geoproc_area_coverage.jpg
   :align: center

|

.. image:: ./images/geoproc_area_table.jpg
   :align: center


Number of Intersections
-----------------------

In some cases, it is important to know how many times the candidate routes cross certain layers (railways, protected areas, etc.), since this may incurr in additional costs or restrictions.

This :ref:`geoprocess <layer_intersections>` provides the number of intersections between selected paths and layers:

.. image:: ./images/geoproc_numintersect.jpg
   :align: center

After running the geoprocess, we get a *table* in CSV format, showing how many times each path intersects each of the selected layers:

.. image:: ./images/geoproc_numintersect_result.jpg
   :align: center


.. _RM_palette_3_2:

New resistance map palette
==========================

The :ref:`resistance map <resistance_map>` provides valuable visual feedback on how the scenario constraints are applied into resistances.

In the 3.2 version, the color palette used to display the resistance map has been improved to offer better contrast between the low and high values.

This is how a resistance map might look with the 3.1 palette:

.. image:: ./images/rmPaletteOld.jpg
  :align: center

And this is how it looks with the new 3.2 palette:

.. image:: ./images/rmPaletteNew.jpg
  :align: center


.. _pylon_spotting_3_2:

Improved pylon spotting
=======================

The new advanced :ref:`routing algorithms with pylons spotting <pylon_spotting>`, introduced in Pathfinder 3.0, have been optimized to support larger area sizes and resolutions.

In addition, a new :ref:`corridor map <corridor_map>` calculation has been implemented, to be consistent with this advanced algorithm.

Compare the corridor map corresponding to the Fast and Pylon Spotting algorithms:

.. image:: ./images/corridors.jpg
  :align: center

The pylong spotting corridor may be discontinuous in some areas, since it shows only locations where pylon placement is favorable:

.. image:: ./images/pylonSpotCorridorDetail.jpg
  :align: center


.. _streetview_3_2:

StreetView tool
===============

Sometimes it is convenient to check the situation on the ground to verify the constraints provided by the data sources. Some elements like existing lines, buildings, etc. might be different than we expected, or we might need to check their type or precise location.

The Street View by Google comes in handy to do these quick checks. Just click on a street or road where StreetView is available (unfortunately, the available areas are not displayed).

.. image:: ./images/streetViewMenu.jpg
  :align: center

|

.. image:: ./images/streetView.jpg
  :align: center

This tools works in both the 2D and 3D views.


.. _simpleview_3_2:

Presentation view
=================

This new option in the :ref:`View menu <map_view>` can be used to simplify the project viewer interface for public presentation purposes.

.. image:: ./images/presentation.jpg
  :align: center

Its effect is to hide some user interface elements like the right panel, menus and layer resistance information.

Touch-based interaction in Pathfinder has also been improved to ease the use of this kind of displays.

.. image:: ./images/presentationView.jpg
  :align: center

To exit this mode, press the key combination *<Ctrl> + <Alt> + <Shift> + P*.


.. _interpoints_3_2:

Export intermediate points
==========================

In version 3.2, the scenario intermediate points are also :ref:`exported <export_data>` in shape format together with the rest of the scenario.

.. image:: ./images/exportIntermPts.jpg
  :align: center


.. _german_3_2:

German interface
================

The user interface in Pathfinder version 3.2 is available in German, and it can be selected from the user profile:

.. image:: ./images/german.jpg
  :align: center