Axiangel
commented
2 years ago I have the same general usage as you describe above. And while i don't have the need for nested fences (atleast i don't think i do) i think making geofences "genral" instead of instance dependant is a great idea. My three instances share most geofences already and any change here must be made on all three. ;-/
Would be really nice if we could create geofences based on other geofences. This would be typically useful for quests scanning. I usually let each area be scanned by their own workers as a first scanning round and then create a big area which covers all areas as a second scan round so all workers from all areas are covering missing stops.
At the moment if I change an area I have to reflect this changes on the "missing" area as well. Having nested geofences would cover that.
Additionnally it would be even better if this could work accross instance (e.g. create a geofence on instance 1 that is made up of geofences from instances 1, 2 and 3).