worldmap | Experiments with world choropleth map using Leaflet

The .html method on D3 selections first deletes anything that's already inside those elements before setting the new contents. Thus, to initiate an element's base HTML content with .html, be sure to call it first before adding anything else to the element, and also do not call .html later on, or risk it overwriting anything that was added to it.

You're close. You've got a number of issues though.

You're including the d3-tip library, but you're not making real use of it at all. Because of this, it's adding to the confusion. You have your own

Your "mouseover" event fails to add the country SVG element for two reasons:

First, because you're selecting the #tipDiv element which never appears since it's part of the d3-tip code that doesn't get used. To fix this, I think you want to select the div.tooltip element instead. Since you already have the 'tooltip' variable set to this, you don't need d3.select; you can simply do:

If you want the right column to dynamically have the same height as the left column, then you probably thinking use some JS or JQuery help.

See the snippet below:

The variable i is changing. You do not call formatter function until later, at which point i already points to the last element of the for loop. If you could call the formatter straight after it finishes the first element and before it continues to the second, you would get AA. What you need to do is bind i['tag'] to a parameter of the lambda - tag=i["tag"] so that the value itself will be saved.

If you add your markers to a named layer, you can use the clear command to remove all markers in one go.

e.g.

I found my answer after looking through more of the documentation. I should have been using context.self. So my Init case looks like:

There is no best way to do anything*. It's what works best for you.

From what I understand you want to make a dynamic 2D arrays to hold your char of world map. You have a lot of options to do this. You can have a worldMap class nothing wrong with that. If you want dynamic 2D arrays just make functions out of this kind of logic.

After giving it some more thought, I finally came up with a solution that "somehow works". I'm not too satisfied with it as it still takes a lot of time and heavily depends on not too many events in the database.

The events are loaded into memory, therefore accessing the database only once. The distance calculation is done for every point to any point, whether it might be within range or not, this will need some more tweeking, but I'll manage that.

If any of you have another thought on how to improve this, please inform me here.

So, there are 2 things that come to my mind when I saw your compose file.

1. Do I need to change the config path?
2. Where is my custom .ini file?

When running a container with an official image (as grafana/grafana), we cannot change the config without feeding it from the outside. So you should specify it in your compose file as a "volume".

For comma rendering numbers, I use prettyNum from base R, also comma function is available in scales package.