Feature Request: Conditional color based on fields values

[ImagoXV]

Hello @androidseb

Thank you very much for your awesome work on mapmarker !

For sure I took the premium version ;)

I've had an idea for some time, that is the possibility to change the color of the POI icon based on the value of some of its fields.

For example, the POI has a boolean field. When setting the color there is the option to set a conditional color based on this boolean value, so the user would set two color values. This principle could be declined for multiple choices as well.
You could even imagine the app to let the user chose the colors of each value during fields creation.
So the user could trigger a conditional color mode of the POI icon and the app would just ask on which field the user wants to base the color scale (which would have been already defined by the user).

Such feature could allow some very cool graphical and color based analysis of lots of POI for data-driven decision process.

I'm not yet familiar with javascript, but maybe I could help.

Thanks again

I wish you the best

Arthur.

[androidseb]

Hello @ImagoXV, thank you for proposing the idea.

Like many ideas I've seen flowing recently, this might be achievable via workflows: #70

If I understand what you're asking, you would like to be able to configure some automation that updates a POI's color based on the value of specific custom fields? I'm not sure what you mean by "conditional color", do you mean a separate color "override" field, which could be blank in which case the base color of the POI would be used, or are you talking about editing the POI's color automatically when a certain custom field is edited to a certain value?

[androidseb]

Interesting!

I think I understand a little better what you're trying to achieve, workflows might not solve this use case directly, because what you're looking for is more of a dynamic value for the POI's color.

I've had similar feedback from other users requesting for the color or icon being dynamic based on the time of the day compared to a custom date field, for example, a delivery driver might want urgent deliveries for which the delivery window is closing to show in a brighter color than other deliveries. Or in your case, you might want to color trees that haven't been watered / harvested in a different color.

To be honest, I haven't quite wrapped my head around how I would address these kinds of use cases, the dynamic color / icon feature sounds similar but still separate from workflows.

In the scope of workflows, what you could maybe achieve would be:

• Trigger: when a POI gets edited
• Action:
  • If "field value" = "0", then assign color 0
  • If "field value" = "1", then assign color 1
  • etc.

But it isn't quite what you're asking for initially, but it would cover your use case, right?

---

By the way, regarding your use case specifically, I feel like you can kind of achieve what you want today with sub folders, which I see you're already using.

Under "arbres/oliviers", you could add a set of folders, each with their own color, like so:

• arbres/oliviers/sans réponse
• arbres/oliviers/0
• arbres/oliviers/1
• arbres/oliviers/2
• arbres/oliviers/3
• arbres/oliviers/4

Then you could use the top folder selection button at the top as your "multi-choice". When a POI is switched to a folder, you get a prompt to update its color/icon automatically. Also, since modifying a folder's color prompts you to automatically update the color / icon of all POIs inside it, it might be somewhat maintainable.

I'm aware that's not exactly what you're asking for, but it might be an interesting workaround in the current state of the app.

---

I have some questions for you:

1. Would the description of your use case in the scope of workflows work for you? (essentially an automation auto-editing the color on POI edit, no "color override" with base color concept)
2. In theory, if there was a dynamic color feature, what would you expect if there are multiple "color affecting" custom fields? If you change more than one of those fields, which one should prevail?

[ImagoXV]

Hi Seb, thanks for your answer

Your gut is right, changing each tree for a subfolder with associated color is doable, but not on the long run. Especially as my number of tree is rising

I could make it work with the workflows I guess, but again, as you identified, not exactly what would be needed for long term survez. It would work better for one-shot actions I imagine

Your second question is interesting.
In the first idea about these dynamic color, I was imagining something rather linear.

When you edit your folder/sub-folder and click on the color, it could propose the classic color scale alongside a "Conditional" option. When you click that one, it could propose to map color based on the values of boolean and multiple choices. To avoid errors, colors could be set automatically when creating a boolean (black/white) and when making a multiple choice (random?).

But where you question becomes cool, is that it implies interactions between the fields which could affect the value and/or icon !

I feel that's out of the scope ! ;)

I do not imagine any priority between the fields colors. They would just be set by the user to meet its need on the spot (or on duration)

Thanks for your time !

Arthur

[androidseb]

Thanks for the ideas. At this time I need to start with implementing a first version of workflow, that will help me think about these use cases a little more as I go. At the moment I don't have a good response about how I would include this kind of dynamic color in the app without complicating the UI and adding extra options to most custom field editor views. Let's talk about this more once workflows have progressed in the app, by then maybe you'll find your use case works fine with auto-edits, or maybe we'll see more options as workflows start to work in the app.

[ImagoXV]

Thanks for the answer and thanks for the chitchat

I'll dig into the workflowswhen I'll have some time

I wish you the best

Arthur

[androidseb]

Just to be clear, I yet have to build workflows. I'm hoping to do it this year.