A different notification radius for each location
chris.calo says:
It's silly to use the same location radius for all locations. I want to be notified of tasks to do at home when I'm actually at home, so that radius should be 1/4 mile (or less, honestly). On the other hand, when I fly to SF, I should be notified of SF tasks when I'm anywhere in the vicinity of the city. That radius might be 10 or 50 miles. It makes no sense to have the same radius for all locations.
An even better solution would be to understand the granularity of a location, and therefore, its approximate size. Treat locations as areas, not points. Cities are huge, countries are even bigger, addresses are tiny, and neighborhoods and ZIP codes are a little bit bigger.
An even better solution would be to understand the granularity of a location, and therefore, its approximate size. Treat locations as areas, not points. Cities are huge, countries are even bigger, addresses are tiny, and neighborhoods and ZIP codes are a little bit bigger.
aaron.fuleki says:
I'd love to see this feature too, Chris. I find that my daily locations all have a radius of a mile or less (usually walking distance). However, I have several weekly locations that are farther away, many of which could use a 10-20 mile radius (e.g., Sunday drive to the big city).
When I fly I often would like something even larger, as you suggest. Just last weekend I flew to Chicago, completely forgetting to take something back for a friend I ended up bumping into. I don't expect RTM to be sentient, but a bigger radius around Chicago would have brought that up when I was packing the night before.
I found several help forum posts about this, so clearly others would like it too.
Having built some location-aware and/or GIS-related apps in my day, I'd think simple radius estimations would be the only sane way to implement location-specific radii. Even a square would work; you could cache the boundaries, greatly simplifying the math to calculate whether your current location falls within said square. Even a mobile device could run through hundres of location squares quite quickly. The Google Maps API has an example implementation of a bounding box algorithm, if I recall correctly.
When I fly I often would like something even larger, as you suggest. Just last weekend I flew to Chicago, completely forgetting to take something back for a friend I ended up bumping into. I don't expect RTM to be sentient, but a bigger radius around Chicago would have brought that up when I was packing the night before.
I found several help forum posts about this, so clearly others would like it too.
Having built some location-aware and/or GIS-related apps in my day, I'd think simple radius estimations would be the only sane way to implement location-specific radii. Even a square would work; you could cache the boundaries, greatly simplifying the math to calculate whether your current location falls within said square. Even a mobile device could run through hundres of location squares quite quickly. The Google Maps API has an example implementation of a bounding box algorithm, if I recall correctly.
(closed account) says:
The Android Locale app does a good job of this.
Log in
to post a reply.