OpenAtlas » OpenAtlas Discovery

The icons in the network could be configured together with those on the map. To improve the usability of this configuration, we will wait for the release of Nuxt Studio: https://content.nuxt.com/blog/studio-module-alpha

Thank you for your message on Mattermost. I will transfer this conversation to the ticket because of traceability.

So do I understand you correctly? You would like to have another key for all related type IDs for each entity? So an entry will look like this:

{
  "id": 59711,
  "label": "Grave 203",
  "systemClass": "feature",
  "relations": [
    50505
  ],
  "typeIds": [
    12345,
    24515,
    5222452,
    12332,
    436,
    352,
    63
  ]
}

I think this is doable, but it will definitely have an impact on performance. How much, I cannot say, but I will add an additional parameter that these typeIds are optional.

Is this what you thought of?

My question is, what do you do if multiple IDs have an icon attached? And if you think of only taking the standard type ID, then the issue arise, that Actors don't have a standard ID and therefore the example with Jesus doesn't work.

#2744 is closed and available in develop branch.

It is now always included, since it has no performance issue.