|
Mar 2019
10:41am, 6 Mar 2019
26,969 posts
|
DocMoye
I agree with above
Could it be possible to have a choice when you mark something as inaccessible you have a choice of permanent or 90 days ?
|
|
Mar 2019
10:43am, 6 Mar 2019
4,165 posts
|
Fragile Do Not Bend
Maybe inaccessible-ness needs to be account specific, after all it only really matters to the person who’s home circle it is and irrelevant to anyone passing through.
And a flag for unusual activity (e.g with greater than X number of inaccessible points) to pick up the odd person taking the piss.
|
|
Mar 2019
11:07am, 6 Mar 2019
368 posts
|
JCB
Good idea FDNB, though the flag thing may not work since choosing a new home circle could cause a flurry of marking being needed.
Don’t forget swimming! 🤣
I mark the bay area near me as inaccessible since I won’t be using foot, bike travel to get to those spots, and there aren’t many landmarks to go by... for the one time I did swim there. Hot air balloon travel anyone? 🙃
I agree that a tool to mark inaccessible/accessible would be useful. It’s not a frequent occurrence generally but the status of a point can change.
Time limits may sometimes be roughly known or not at all. Including that information might be useful though perhaps not necessary if you can mark/unmark accessibility. Or as an adjunct when marking/unmarking it could be specified with ‘for today’, ‘for a week’, ‘for a month’, ‘for three months’, ‘for six months’, ‘for a year’, ‘forever’. Not sure if that adds too much complexity...
What to do when different people are marking/unmarking a spot? In ‘free’ territory (where no one has their circle) then the conflict might be resolved by defaulting to accessible since it’s less of an imposition to have a point marked that way. Effectively all unowned territory cannot be marked as inaccessible. Flowers could then be created for any one actually going through the point. For ‘singly owned’ territory (one person has their circle there, call it one ‘circlee’) then that person’s vote for the point sticks. For ‘multiply owned’ territory (more than one person has their circle there) then it could default to inaccessible. No goodies/baddies show up but shouldn’t be a big deal. Marking it as accessible would require a majority of the ‘circlees’ selecting that. So a point can be marked inaccessible when: - it’s in your circle and no one else’s, or - a vote for marking it inaccessible if you and other people have it in home circle.
A point can be marked accessible when: - it’s in your circle and no one else’s, or - a vote for marking it accessible if you and other people have it in home circle.
If it’s in no one’s home circle then no changes are allowed.
If you really feel the need to change a point not in anyone’s circle then temporarily changing your home circle to that area will enable you to do that (unless and until someone else has the same idea)!
This doesn’t completely rule out issues with multiple bikers against one runner, for instance, or one person has access that’s not general.
Just some of my musings on it. 😄
|
|
Mar 2019
8:54am, 7 Mar 2019
2,956 posts
|
R4R
some interesting musings, but like synge said in an earlier post, it can all get a bit complicated to solve what is a simple problem
maybe a simple solution would be the ability to see inaccessible points - maybe not usually visible, but selectable via a tick box - and if a point has become accessible again because of house-building, then you have the option to make it accessible again
I say simple - it would be simple to use, but not necessarily simple for Fetch to code
|
|
Mar 2019
9:25am, 7 Mar 2019
1,435 posts
|
CumbriAndy
This could be even simpler.
Every point on the map currently defaults to accessible - they can only be marked as inaccessible when a marker is placed and flagged by a user. Which leads my simple mind to believe that each point is essentially either 'on' or 'off'. All we are lacking is a simple means to turn them back 'on' again. The route mapping already knows which points we travel through - it seems a relatively simple concept for the route mapping to confirm that any point that has been travelled across is 'on', resetting as necessary. No need for any user input at all.
This carries the same caveat as R4R's point - I have no idea what this means in terms of changes to coding.
|
|
Mar 2019
9:37am, 7 Mar 2019
2,998 posts
|
StuH
Which I think is what I was saying, but maybe not have cycling reset the points.
Likewise, I have no idea how feasible any of it is from a coding aspect.
|
|
Mar 2019
9:39am, 7 Mar 2019
2,957 posts
|
R4R
morning CA - that's exactly what I suggested (8:37pm on Tuesday) but some people objected to the automatic-ness of it - some suggesting that if a runner/walker marked a point on a busy A-road as inaccessible because it was dangerous to get to, then they didn't want a cyclist making it accessible again.
I suppose the same applies to any such point - when I move my home point to the Lake District several times a year I will mark points in lakes/meres/waters as inaccessible although to an open-water swimmer they are fair game
|
|
Mar 2019
9:42am, 7 Mar 2019
3,088 posts
|
Fizz :-)
How about inaccessible points can only be within the home circle of the person that marked them? So if you wanted to clear your inaccessibles, you move your home point?
|
|
Mar 2019
9:43am, 7 Mar 2019
3,089 posts
|
Fizz :-)
(oh, that's basically what JCB said)
|
|
Mar 2019
9:46am, 7 Mar 2019
21,406 posts
|
fetcheveryone
That's what I'm thinking too - there are a few coding hurdles to overcome in order to make that happen, but it's on the cards.
|