Hello everyone,
I have been using Dawarich for about a week now, and I’m loving it so far. Tracking with the IOS app in connection with Apple Shortcuts works great.
About two days ago, I added Places manually, because even though I accepted suggestions, Places were never created. But I still won’t receive suggestions for the places or the areas I defined, but rather for the street name of the place where my defined place is.
Is this intended behaviour, or am I doing something wrong?
For areas, visits should be suggested with no issues, places aren’t working the same as areas though, for them first a visit is being detected and then a possible place name is being inferred, so that depends on clusters of your points
So currently should we use areas or places to track visits? I found areas work much better if I can set a large radius, but places have much better icons and everything. From an end user’s perspective, I would just like to give my places radii. I like using the ability to hide places too, which I can’t do with areas.
I’d say go with whatever serves you best, but I can say for sure that areas will receive geofencing in the future, while places may not
I have a similar question on the use case for Areas vs Places? what was the original intent?
they seem very similar but the major distinctions I see are that areas you can set the radius of inclusion while places have tagging …. am I missing anything else?
when do you personally make something an Area vs when do you make it a place? is there any further distinction between the 2? Are they eventually going to be combined being as they are so similar? whats the best to use as far as future-proofing?
thanks in advanced, just want to make sure im using the software in the way it was intended to avoid unforeseen consequences!
Areas were introduced a lot earler than places but their purpose is pretty much the same, to track visits. It’s possible they will be merged later on