For what it's worth, in case it helps you figure out any similar expressions, this is one that I'm using right now, and it's been working just fine in my web map:
var Due1 = Date($feature.Followup1);
var Due2 = Date($feature.Followup2);
if(IsEmpty($feature.Followup2)){
if(DateDiff(Today(), Due1, 'days')>=0){
var TimeColour = 'Yellow';
}
else {
var TimeColour = 'Blue'
}
}
else if(DateDiff(Today(), Due2, 'days')>=0){
var TimeColour = 'Red';
}
else {
var TimeColour = 'Yellow'
}
if($feature.Override != 'None'){
var Colour = $feature.Override;
}
else if(IsEmpty($feature.Abated)){
var Colour = TimeColour;
}
else {
var Colour = 'Green';
}
return $feature.Category + Colour
Workflow:
A code violation is recorded, and a due date is set. If the violation is not abated in that timeframe, another warning is given and a second due date is set. A citation is issued if there's still no resolution by that date. Due dates can be adjusted as needed depending on the situation.
Need:
Newly recorded violations show up on the map as blue. After they pass the first due date, they turn yellow. After they pass the second due date, they turn red. Once abated, they turn green.
Arcade explanation:
- If there's no second due date set yet, then it checks if today is before or after the first due date, setting the colour to blue (normal) or yellow (past due).
- Otherwise, if a second due date is set, it checks if today is before or after that deadline, setting the colour to yellow (past due) or red (outstanding).
- These expressions set one variable, TimeColour.
- Then it checks if there's a status override. If there is, the colour is set to that override, ignoring the above variable.
- Otherwise, it checks if there's an abatement date recorded (the violation has been resolved). If not, then the symbol colour is set to the above TimeColour variable. If there is, the colour is set to green.
- Lastly, in addition to the colour that was calculated out, the expression returns the violation category as well. The overall result is 20 possible combinations (5 categories, each with 4 possible colours).
This can probably be simplified (I could start with the check for the override, for example), but it should give you an idea of a more elaborate setup of date-based arcade expressions, should you decide to get a little fancy.
Happy coding!
