You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I think it is more logical to include the area rather than the source dataset in the alert email. If you have set a few alerts, it is in fact nog very clear anymore which ones you want to look at. Area is the most important to a manager. Alternatively, both could be included of course. Lat/Lon is in fact also totally uninformative so perhaps these 2 columns can go and we use area instead there?
The text was updated successfully, but these errors were encountered:
In email there is a section called "Alert details" where the area is mentioned. An example follows here below for one of my alerts. Maybe you refers to the table with the occs examples? Mentioning the area has not really sense as it could be "Belgium" if no more specific area is selected. Moreover, it will be a redundant information as this info is already present as I mentioned before. Notice also that the details shown in the example table are the same as the ones shown in the table mode of the web application. In my opinion we shouldn't change it as lat lon are always present while municipality (just to mention the field which would make more sense) is not always filled in.
Hi, I think it is more logical to include the area rather than the source dataset in the alert email. If you have set a few alerts, it is in fact nog very clear anymore which ones you want to look at. Area is the most important to a manager. Alternatively, both could be included of course. Lat/Lon is in fact also totally uninformative so perhaps these 2 columns can go and we use area instead there?
The text was updated successfully, but these errors were encountered: