-
Share away, the more views the better.
I think the majority are existing one way streets. Those roads are a bit narrower than average but for most streets in the area you couldn't have two cars passing each other without a gap in the parked cars. I'm not sure how congested the parking is round there, streetview doesn't seem to show it as any worse than other places nearby so I'm not sure of the basis of keeping them in.
-
As I said, you don't have to worry about drivers going in opposite directions in filtered areas if you do it right. If you end up with one street that's the principal way in, you can create a couple of passing spaces. Either way it'll work. The reason why drivers get into fisticuffs that eventually lead to one-way streets being adopted is because they're in a hurry to get somewhere while treating the street or area as a way to that somewhere else, not as a destination. If it's just people going a couple of dozen metres into a filtered cell, all that urgency dissipates and people will happily reverse a bit in the rare cases when conflict will occur.
As posted by @aggi in the TfL thread:
https://www.haringey.gov.uk/parking-roads-and-travel/travel/transport-strategy/low-traffic-neighbourhoods-haringey/low-traffic-neighbourhoods-public-consultation
I'm afraid these are all about as bad as attempts at filtering can ever get. Firstly, in well-filtered areas you don't need one-way streets. Yes, even if streets with a line of car-parking on each side only allow one functional vehicle lane between them. There are very few exceptions to that rule. In fact, one of the main justifications for filtering is that it enables removal of one-way streets, but here (especially in Bruce Grove West) they're leaving them all in, probably to not get people worried about damage to their parked cars. Most proposed filters are in completely the wrong places, e.g. the 'Enfield trial filters' in Bounds Green Area A, which are on the borough boundary, where they most assuredly shouldn't be.
I'm obviously aware that the borough operates under constraints, but this is not a good way to filter, especially if you're going to impose them as schemes out for consultation like this.