Pink Duck's Comments
| Changeset | When | Comment |
|---|---|---|
| 126006197 | Are they really concrete asphalt though laid with hot-rolling machine? Non-road traffic is often bitmac (bitumous McAddam). |
|
| 116595587 | Seems to be a partly mistaken edit, was opening_hours="24/7 closed" previously. Moving to description loses that programmatic comprehension. |
|
| 125817813 | Defra statement: “We will repeal the 2026 cut-off date for recording historic rights of way, as set out in the Countryside and Rights of Way Act 2000, to allow more time for paths to be identified and added to the public rights of way network, as well as providing the ‘right to apply’ for landowners to divert or extinguish rights of way in certain circumstances. These measures, along with accompanying guidance, will be implemented as soon as reasonably practical.” |
|
| 125817813 | Have you actually walked rights-of-way often? It seems doubtful if so that you wouldn't have encountered situations where the definitive map right of way route was blocked by buildings, walls, fencing etc and an alternate route provided by farmer, with notice publicising the fact somewhere nearby from council. In those cases, the footpath may get signed private, where the ground truth is that you'll get argued/shot at by disgruntled farmer and berated for following the outdated right of way route. Some even go through the middle of new build (as in 1980s) plots/homes. |
|
| 125817813 | The definitive map and public rights of way are very much an outdated legal basis, with use-it-or-lose-it review upcoming and causing much fuss. |
|
| 125817813 | In some cases you removed the access=private where a previous survey states “they've put a private sign up” |
|
| 125817813 | Where highway=path, but I note a lot of your changed cases are highway=footway, tagged as primarily pedestrian traffic already. |
|
| 125817813 | Taking access=private off now means all types of vehicle may travel, whereas in reality only designated pedestrian per the RoW is legally required. In reality, in some cases the land owners still reject even that. |
|
| 125817813 | That seems very unhelpful. Public footpaths do cross private land. That they do does not make the land public, only the route of the public footpath itself. Hence foot=designated overriding access=private. |
|
| 116056278 | Pavements are usually surfaced with bitmac (bitumous McAddam), not concrete asphalt. surface=paved is fine for the user agents to understand suitability. Could always use surface=bitmac or surface=bituminous. |
|
| 119538371 | Tarmac is the company name, tarmac with a lowercase has been used by some to mean the material associated with the company (often bitmac from paving-sized jobs). I just don't see the value gain from switching from 'paved' to something technically incorrect. It would be better to remain generically known as, well, not un-paved. |
|
| 119538371 | Shouldn't StreetComplete just simplify the choice to unpaved/paved? There’s already a specific value paving_stones. surface=*
The value 'tarmac' might be a better fit, though only 268 uses in taginfo. It just bugs me, since it isn’t asphalt. |
|
| 119538371 | Isn't paved value closer to BitMac (bitumous McAddam) as used on pavements than asphalt? (as in hot-rolled road surfacing) |
|
| 87228634 | Some pandemic confusion there it seems, as the farm butcher signage appeared there at the time. I've corrected things up. |
|
| 93879389 | A technical point, but surface=paved more accurately describes BitMac (Bitumous McAddam) as often used by pavements, than asphalt often used in roads. |
|
| 119360648 | It would be good if when adding cyclepaths that are shared pavements that you use tag combination: highway=path,surface=*,foot=designated,bicycle=designated,segregated=no,path=sidewalk - instead of highway=cycleway. Those sections of route aren't primarily for cyclists, rather cyclists have been given the right to use the pavement. |
|
| 33998268 | It was 7 years ago. It looks to have expanded into the adjacent building number since, now 62-64 in addressing. The postal city possibly originally wrong, have corrected to Lowestoft. |
|
| 123250055 | Perhaps remove path=right, path:surface=grass etc. tags from adjacent road way when explicitly mapping. |
|
| 122804234 | operator="UK Power Networks" too? |
|
| 121368696 | Not Cawston on review, actually Corpusty and Saxthorpe area. |