Gillingham (Dorset) & Gillingham (Kent) duplicated
(Thought I had posted this earlier, apologies if this is a duplicate)
The places Gillingham in Dorset and Gillingham in Kent are both listed as Gillingham. This means, for instance, that if I try to create a new route for Gilsha (Gillingham to Shaftesbury, in Dorset), it gives me as the start point Gillingham in Kent. It would be quite a long walk!
I suggest that the places be renamed as Gillingham (Kent) and Gillingham (Dorset).
Would that be possible please?
Thanks
-
I agree with there being two different names. There are two places called Ashford. In slow ways Ashford in Kent is called Ashford whilst Ashford in Surrey is called Ashford (Spelthorne). I think Ashford (Surrey) would be better.
I wonder if it would be possible in slow ways to call up an alphabetic list of all the names of the slow ways nodes.
0 -
Hi there,
I think both Gillingham and Ashford have both been sorted now. When you search for them from the main page. Please do keep letting us know though if other issues with same place name but different location come up?
Best wishes,
Cristie0 -
Hi Cristie, thanks for looking into this. Unfortunately Gillingham is not sorted, Gillingham (Dorset) still sends me to Gillingham (Kent) instead. As I had also reported this as a bug, I've updated the bug report (347) with more detail.
Martin
0 -
It appears to work as follows:
If I give an ambiguous place name it gives a list of the multiple options.
Below this it gives a list of Slow Ways places and then routes.
However these are places and routes associated with the top name in the multiple options list.
It doesn't attempt to list any slow ways places related to names below the first in the multiple options list.
Here are a few ambiguous names where the first listed is not the most obvious:
Narborough (not Leicestershire)
and Enfield, Ilford, Stratford and Sutton (not Greater London)
Tony
0 -
Hi Martin,
Apologies, I was looking at a different page and you're absolutely right. When you select the place Gillingham, Dorset it shows the southern part of the UK with two sets of Slow Ways. I'll pass it on and flag up the ticket.
Tony, I'm not certain about how the search works but will pass your comments on also, they're really valuable to us so we can find and fix the bugs.
Best wishes,
Cristie0 -
Hi Cristie or anyone,
Is there any progress on fixing this? Just to reiterate the problem, if you try to reference Gillingham in Dorset, it takes you to Gillingham in Kent. The effect of this is that:
1. It isn't possible to create a place review for Gillingham (Dorset)
2. It isn't possible to create a new route starting or finishing in Gillingham (Dorset)
3. Because of this, Slow Ways has a credibility problem in our area of North Dorset.Gillingham (Dorset) is a Walkers are Welcome town, but we aren't able to promote Slow Ways until this is resolved.
Don't want to seem negative, but could you at least give an indication that the problem is understood and a timescale for resolution?
Thanks
Martin
0 -
If you go to the home page and input Gillingham it says Multiple Matches and gives you the option to click on Gillingham, North Dorset. If you do this it shows routes etc. for this location.
0 -
Yes,it shows nearby Slow Ways Gillingham - Mere, Stalbridge - Gillingham, and Wincanton - Gillingham, which are local to me, and Gillingham - Hucking, which is in Kent.
Then, for example, you choose Gillingham - Mere (Gilmer) and suggest a new route. That specifies a start point at Grid ref TQ7751068340, which is Gillingham in Kent.
And having clicked on Gillingham, North Dorset after the Multiple Matches it gives lists Slow Way places Gillingham (Dorset), Mere (Wiltshire) and Shaftesbury (Dorset). If you then select Gillingham (Dorset), it takes you to Gillingham (Kent).
Not good.
0 -
I see this is now fixed. Thank you.
0 -
That's great news, I'm so glad it's fixed. It was to do with data pulling in from elsewhere which must have now been updated.
Thank you for your patience.
Best wishes,
Cristie0 -
Hi Cristie. I don't think the multple Gillinghams problem was fully resolved after all.
When I look at settlement page for G in Kent it is as expected except the map which shows both pink line clusters. If I try to open the G in Dorset settlement from that map it just flicked back to G in Kent.
If I go to home page search, choose Dorset option (is only in top set of choices, other lists are for Kent only) it then goes to a similar G in D page wit only the expected G in D choices this time, this works I guess but could be off putting for potential Dorset reviewers. And te disinentive would be compounded by the map not showing anything. It's just empty and white with the buttons atthe top right.
Please forgive spelling etc the autocorrect Zendesk bug is happening again!
I found another one a bit like this recently but didn't report it. Ive forgotten if it still important or is this a change that is going to be made wholesale later with a database chnge or update? If the latter then obiously pease ignore this.
0 -
Hi Daisy,
Interesting the Gillinghams. Thanks for letting us know there are still things to work out.I'll let my tech colleagues know and see what can be done. I know originally the data was pulling from somewhere we couldn't influence but that was fixed and so maybe it's something we've tweaked recently.
Yes please. Do say via the help desk when you spot these things as it's so helpful for us to then look into.
Best wishes,
Cristie0
Please sign in to leave a comment.
Comments
12 comments