Add node worldmap in explorer

[Neylix]

Description

Working on issue #225

Implement first task :

• Create an algorithm to transform a geographical patch into a x/y coordinates
• Create the JavaScript component to display it on the node explorer

I noticed that some coordinates cannot compute a geo patch. For exemple when longitude is equal to -45, sdc and tdc are equal to 1 or -1 and then are not in range for the index_patch function

Test are just on 4 geo patch, but I tested all and it works fine (cannot test all in geo_patch_test cause compute_patch is private)

I'll work soon on second task to add map on the explorer, I think to use Leaflet to display the map

[ghost]

For the UI, what do you think of:

• https://echarts.apache.org/examples/en/editor.html?c=effectScatter-bmap
• https://telemetry.polkadot.io/#map/0x91b171bb158e2d3848fa23a9f1c25182fb8e20313b2c1eb49219da7a70ce90c3
• https://solanabeach.io/

Something more graphical should be great.
But however, thanks for the contribution 👍

[Neylix]

Thanks for reply !

Using echarts is a good idea as it is already imported and used in telemetry.

However using points on the map is not interesting because the range of coordinates is to large. Here the worldmap with all ranges displayed :

So we cannot have precise point on the map, unless if we get the exact coordinates from nodes instead of getting a range using geo patch.

In all case, I think that displaying the range is a good idea as it is an important variable for the ARCH consensus.

What do you think about getting node exact coordinates and grouping them with a range of +-1 and so have good precision to diplay them as a point on the map like in your exemple ?

[ghost]

Hello.
Thanks for the changes and the proposals.
In fact GeoPatch are designed with sub levels of details.
So each patch have 3 digits.
Each digit corresponds to a subdivision of 16 squares.
Example: 012, it will be located on the first square, then inside it will go in the second nested square and finally it will to the third nested square of the latter.
This way we have some precision but without giving too much information.

Also if there are too many points we can aggregate or if for UI clarity it will not render nicely, we can keep two digits and show popup with the number of nodes inside.

[Neylix]

Hi !

Correct me if I'm wrong but I think that each digit do not subdivise by 16 the possible range, the first one yes, but the 2 others only subdivise by 4 :
Depending on real coordinates, the first digit can be all possiblities (from 0 to F)
Then, due to function resolve_with_sign() the second digit must have f_i and s_i with the same sign as the original coordinates so it let open only 4 possiblities.
For exemple if first digit is "0" so f_i positive and s_i negative, second digit must have same sign so it remain only "0", "1", "4", "5".
It's same thing for the third digit.

So with that said, we can have only 256 geo patch (16 * 4 * 4).
I tested this with "brute force" method (calculate all coordinates possiblities incrementing by 0.5) and the result is 256 unique geo patch

If I'm right, the final subdivision looks like the map I presented in my last comment (16 by 16 subdivisions)

[ghost]

Hi !

Correct me if I'm wrong but I think that each digit do not subdivise by 16 the possible range, the first one yes, but the 2 others only subdivise by 4 : Depending on real coordinates, the first digit can be all possiblities (from 0 to F) Then, due to function resolve_with_sign() the second digit must have f_i and s_i with the same sign as the original coordinates so it let open only 4 possiblities. For exemple if first digit is "0" so f_i positive and s_i negative, second digit must have same sign so it remain only "0", "1", "4", "5". It's same thing for the third digit.

So with that said, we can have only 256 geo patch (16 * 4 * 4). I tested this with "brute force" method (calculate all coordinates possiblities incrementing by 0.5) and the result is 256 unique geo patch

If I'm right, the final subdivision looks like the map I presented in my last comment (16 by 16 subdivisions)

Hello.
If I'm remember well, normally it should be 16x16 squares at least for the two first digits, and probably also for the third.
@I-Archer-Zero Can you confirm ?
If so, we would have to change the coordinates to geo patch algorithm.

[Neylix]

Hi @samuel-uniris @I-Archer-Zero
Do you have an update on this subject ?
Is there a need to rework on geo patch algorithm ?

[ghost]

Related to #253

[Neylix]

How to test :

• Testing data sent from Phoenix Live is done in worldmap_live_test.ex
• Testing maps updates in real time : run docker-compose up node 1 go on explorer worldmap view and then run other node containers
• Testing multiple nodes display without running hundred of container : update worldmap_live.ex file and replace P2P.available_nodes() by your own datas (can create a loop to randomly generates Nodes data)