Conduct a feature review in an attempt to list the features of the current site as accurately as possible.

We'd use this to discuss future developments and also to guide our efforts to write a more thorough test suite...

Zoom recentres itself instantly when using mouse wheel on homepage

When I edit a toilet it tends to overwrite previous contributors, so it say 'Gaillyk, Gaillyk' for example instead of ''Gaillyk, liz sugden'.

So that we don't get so many loos at the RCA

FIREFOX

• Styling of More info on Firefox eg St. Andrews.
• No scroll on Nearest Toilets selection

User was on Chrome desktop

Went to https://gbptm-unity.herokuapp.com. Logged in however was not asked of location whereabouts

Also happened on IE11

"Hi!
The 5 nearest toilets are listed below. Click more info to find out about each toilet's features.

You can set preferences to highlight toilets that meet your specific needs".

Text is misleading, User expected to see these loos on the map or for loo's that didn't match preferences to not appear.

We'll move the area lookup into the report creation...

Steps to reproduce:

1. Go to http://greatbritishpublictoiletmap.rca.ac.uk/loos/54c2347a2ec4abe957b83a91

2. Click on JSON (Column, left hand side, 2/3 of the way down...)

3. Expected: JSON displayed, Actual: Map displayed?

Baby-changing stat is showing majority as 'no' and very few are 'unknown'.
Could this data from when the field was incorrectly made a boolean and any edit was defaulting to 'no'?

The baby-changing column in the 'By Area' statistics of the Explorer is showing # of baby-changing for all toilet reports when it should just show the 'active' toilet reports.

Hopefully the headline stats also use 'active' toilets, not 'all' for baby-changing, accessible, public/restricted...?

• Map didn't load when selecting full size icon

Part of - #202

And think about how we'd use it to make a desktop management and data explorer app for GBPTM

We start work on that in August ;-)

@marxian @Hoolean

Some feedback from a user who is not particularly tech savvy and is/maybe dyslexic, using an iPad Air on safari browser

• Landscape - Only shows first nearest toilet, user didn't know they could scroll
• User didn't read info, looked at map then struggled to work out where they were
• Do I log in?
• How do I know where I am?
• How do know how many toilets work? - User selected a toilet which had a big queue. Needed to find another quickly. What's the quickest route?
• Individual toilet selection. Didn't understand the logic of going from map with many toilets to an individual selection
• I'm not familiar with the area. Directions to toilet
• Make map more user friendly
• Map didn't load when selecting full size icon #204
• User didn't know what the symbols meant on the map. Thought the "find me" icon was for directions
• User walked with the iPad expecting the map to highlight the route
• User couldn't find Norwich Market toilets on map
• User works with drug users and commented on this in relation to public toilets and drug users
• User runs https://www.map.uk.net/get-help/gender/ and requested that Non-gender specific details are added as an option for the Facilities list

The geolookup works, but the 🔍 button does nothing. You have to press enter.

We use the same component for add/edit, and it works, but it renders the same headings/rubric in both modes.

I suggest a mode prop we can pass in from index.js

Android - User sees a black screen after selecting favicon

A black screen earlier today

Editing

• Add Sanitary/condoms/vending machine information

Could be a partial cause of #191

Try to add a loo, see the alert box with "Align the crosshair with where you believe the loo to be."

Try to see a crosshair. Fail

Despite the existence of a showCrosshair prop on the LooMap class I can't see any code which this prop would actually activate.

replicate:

load the site
move the map away from your geolocation
hit "Add a toilet"
see the report screen load
note that the map has reverted to your current geolocation

A variant of this behaviour in current production has resulted in a lot of loos being added in the wrong place.

Hello - Did you add this in the end? I can't spot it. I'm submitting the final data/story to the ODI on Monday for them to consider do if we can include it there's not much time left.

Donations page link isn't working - goes to RCA Intranet log-in page?

Take a look at the single example in https://github.com/neontribe/gbptm/blob/develop/test/api/api.js#L15

The process of trying to update existing reports on a specific location from the same user is over-complicated.

Instead we should:

• Not do this
• deduplicate the array of contributors on the loo instead.

Set accessibility preference and then visit: https://gbptm-stage.herokuapp.com/loos/5789d80d6e9caa1000117f49

We still need a tool which removes all the loos and reports submitted in bulk, leaving only those submitted by individuals.

Then we 'd import reports and regenerate all the loos.

Leaving the Attended/Baby-changing/Automatic/Radar fields on 'Don't know' when adding a new toilet defaults to No.

Not possible to change a field from Yes/No back to Don't know.

Nearest Toilets text needs styling.

Looks like another z-index problem like the crosshair.

This manifests in the single loo maps in the list: packages/ui/src/components/LooListItem.jsL44

Please consider tidying up the GBPTM repos so we only have those for the current version open, and they are public.

IE11 - Page not loading when user selects more info from the nearest toilets option

"Hi Gail

There's a bug in the map in that if you choose 'other' in the opening hours, it doesn't save it but just reverts to unknown.

Hope all is well

Phillip."

Problem

At present, metres are converted into radians before being passed to Mongo's $geoNear.

We don't really want to represent our distance as radians while providing an interface that uses metres, however, as the amount of metres a radian represents in longitude varies greatly at different latitudes. Our simple conversion method doesn't take this into account and so the results returned are misleading.

As we use $geoNear with a radius to do our bounding box queries too, using the same method of conversion, searches within a bounding box of coordinates are also affected.

Suggested Remedy

Do we want to be using metres for toilet range searches in our API?

• For nearby toilets, almost definitely, as this represents how accessible toilets are for a user far better than coordinates could. Mongo has support for metre radii, which we should try and use here.
• For coordinate bounds, it is more complicated. We should see how this could be used on the front-end before fixing this implementation but, to fix this, either:
  • The approach for nearby toilets could be used as previously (and clipped to the bounding box, which is not done at the moment, although this is a separate issue) or
  • Simple numerical conditions could be tested against the toilet's coordinates (greater than / less than) to eliminate toilets outside the bounds, assuming they are rectangular, which is not checked for at present)

Android device Samsung Galaxy J5

When user searches for a place the keyboard blocks the results and user cannot select the correct place.

We currently depend on the opening_hours module to check if loos are open at the time of viewing.

It adds at least 200K (uncompressed) to our payload.

Given that our app allows the use of precisely 5 opening hours variants we can probably slim this down a lot with an implementation of our own.

Unexpected Behaviour

GET /api/loos/near/0/52?limit=5 gives 4 loos.
GET /api/loos/near/0/52?limit=100, with the same default radius, gives 96 loos. This shows that the previous request should have provided 5 loos instead of 4.

Suspected Cause

The limit parameter is applied before inactive loos are filtered out.

Suggested Remedy

The $geoNear query must be first in the aggregation, so a fix is not as simple as changing the order.

We should consider the function of the limit parameter, as it is currently been worked around in our front end by being given an arbitrarily large value instead of being useful.

Perhaps it makes more sense to limit the radius of the search instead of the quantity of results, as this would pertain to how the endpoint is actually used better.

I mean 5/5 just like that?

Working on it

• Search doesn't give breakdown of all Street names eg Southwell Road. Beach Road v The Street
  

• IE11 Toilet pin doesn't fire?
• Toilet preferences doesn't seem to do anything eg Gurney Road toilets doesn't have baby changing but appears on map after making preference.
• Map centre dot might get confused for a loo?
• Where does initial data come from
• Styling of More info on Firefox eg St. Andrews.
• Updating credentials ?

Expected Behaviour

In Add Mode, the user is either not allowed to zoom at all or can zoom as normal.

Actual Behaviour

On finishing a zoom, the user is immediately and disconcertingly returned to their previous zoom level, although not always in the same location.