Ka-Boom! Palladian 2.5

@qqilihq , sure, I’ll email you within 48 hours - currently fixing a major hurdle.

Update: Thanks @qqilihq for the trial/test version you emailed. For the OAuth, I can see that that variables can now takeover the fields.

As for the Map Viewer, I did a comprehensive test and here’s what I found:

  1. It works as you described in the email. That’s a good start!
  2. Here’s a screenshot of the result:

  1. If you have more time in the future, maybe you could take a look at why the labels did not appear on the map. Here’s how I configured the node to show that I have assigned the label column appropriately:


Here’s an image to show you the importance of the labeling for the case where the geographical region covered is very wide:

As you can see, for wide coverage, annotations would definitely help the users make sense of the map if the location names are seen. If you can also go further than that, for a dense map as shown here, it would make sense for the coordinates to be of different colors according to pre-assigned categories, with smaller teardrop sizes, and for the location names (label) to appear as map legends to avoid overcrowding of labels. But that’s just my opinion :grin:

  1. As for the Tile Provider, I prefer the OSM as shown above. It works okay. But some of the other providers either gave me errors, or a non-workable image:

Here’s for Stamen:

Here’s for Apple:

But I don’t personally use these two tile providers, since the OSM tile alternative works for me and is my preferred option.

All in all, thanks for the work in this! Really appreciate it. :+1:

  1. For the labels to show, you’ll need to use the Labels renderer
  2. You can also assign colors and apply different sizes (for the “Teardrop” and “Circle” style) to the labels

This can be achieved by putting size and color manager nodes before the Map Viewer:

As I think that these are probably less-obvious functionalities, I’ve put together an example workflow which will scrape a list of of European cities from a Wikipedia table and visualize these as shown above. I’ve shared it on my NodePit Space:

Hope this helps!


Oh wow I’ll definitely look into this tomorrow! At first glance that looks awesome!

1 Like

@qqilihq Thank you, I tried it on a dummy component and it works!

Hope to see it in the next official release ! :grin:

P.S. Is there a way to convert coordinates to their respective states/region automatically without prior info? (Kinda the reverse function of the Palladian geocoder nodes)

1 Like

Currently not yet (easily), but it’s in fact already a todo on our agenda :slight_smile:


Alrighty, good to know! :+1:

Hi @badger101

You may have a look at the following workflow:

which is using on top of the Palladian geocoder nodes, a “street to GPS location dictionary” file called “allCountries.txt” that can be downloaded from GeoNames as a zipped file.

One may use this dictionary in the two senses (coordinates to street and the other way round). Although it is far from being the perfect solution because it doesn’t contain all the streets of the world, it may let you start implementing your own workflow based on this file while waiting for the future Palladian geocoder plugin release including this feature. You might implement from it a workflow that looks for the nearest GPS coordinates in the dictionary and returns the state/region as desired.

Hope it helps :wink:


1 Like

Thanks @aworker , I’ll have a go at using the RLL node in a few hours. It sounds like it’ll do the job. Do you think it covers worldwide?

1 Like

My pleasure @badger101. The GeoNames dictionary is global with more than 12 million addresses from all over the world, although I cannot say how much that really covers worldwide.