ACarlotti's Comments
| Changeset | When | Comment |
|---|---|---|
| 89384422 | over 5 years ago | I've reverted this in changeset/90029800.
|
| 89919652 | over 5 years ago | I've returned this to highway=secondary in changeset/89919652, because I think that is much more appropriate. I wouldn't object to this being changed to secondary_link, and/or the reverse direction being changed to a matching classification. |
| 89753104 | over 5 years ago | Reverted in 90028115 |
| 89919652 | over 5 years ago | I think "normal" in that sentence means "not a _link". The example given in the footnote showed a highway link using a pre-existing unclassified road to join onto a secondary road. The portion of the unclassified road involved was then tagged as a secondary road. (Both roads were changed from secondary to tertiary a couple of months ago, but the same principle still holds). |
| 89919652 | over 5 years ago | I think that statement is relating to the case of a simple link with no intermediate junctions, with the instruction being to not choose an arbitrary division point.
If this is considered to be a pre-existing street, then the wiki would say that 'highway=secondary' is correct. On the other hand, if this isn't a pre-existing street, but the A1307 were a motorway, then the wiki would say 'highway=secondary_link' is correct. I think the reality falls into neither case, so there isn't explicit guidance for this situation, but I don't think the classification should decrease if the classification of the A1307 were raised to a motorway. So, to conclude, I'd say that either 'highway=secondary' or 'highway=secondary_link' is correct; I think I now favour the latter slightly more. |
| 89919652 | over 5 years ago | I think 'secondary' is probably best (though without the ref). (I'm basing this partly upon the various wiki pages for highway links). |
| 89579256 | over 5 years ago | I still don't think that works. Using "highway=construction" and "access" tags is ambiguous, and I would normally interpret this to be indicating the access arrangements once the road is open. I had a look at instances of this tagging elsewhere, and it looks like my interpretation is the most common one in the areas I found. If you want to indicate that the access is temporarily restricted, then I would just add appropriate access tags. Your changes also broke Graphopper's cycle routing. I've mostly reverted your changes (in changeset/89936254) because I still think the tagging is wrong (and routing was visibly broken). It might be possible to improve the accuracy of the tags at each end of Histon Road, but the way you tried doing it doesn't quite work. Personally I'd favour just leaving it tagged as open because the short stretch of inaccuracy doesn't affect anywhere that someone would actually want to drive to or from. |
| 89936254 | over 5 years ago | Oops, I failed to add a comment.
|
| 89919652 | over 5 years ago | I disagree. And even if they should be the same, I think 'unclassified' is the wrong tag for the northbound sign, since it's main role is as a slip road from a motorway onto a secondary road. |
| 89753104 | over 5 years ago | I think there is a bus stop here. I don't know if there is a physical sign here, but route 606 (previously 206) to Impington Village College runs along this road northbound in the morning (on schooldays). |
| 89579256 | over 5 years ago | I looked at that page but failed to see the schedule completion date above the table. The table itself gives estimated end dates of Spring 2021 for Phase B+C and Summer 2021 for Phase D. |
| 89579951 | over 5 years ago | I suspected so. Thanks! |
| 89579256 | over 5 years ago | I think there are issues with most of the changes in this changeset.
I think this best thing to do with this changeset is to revert it entirely, and then perhaps add more accurate tags to the bits of Histon Road that are temporarily oneway. |
| 89579951 | over 5 years ago | Why did you edit relation/1016554 in this changeset? |
| 89384422 | over 5 years ago | Can you explain why you have made this change? As far as I can tell, the existing tags were more accurate.
|
| 89363793 | over 5 years ago | I believe so - I remember seeing the 'end of shared pedestrian/cycle area' sign just round the corner on Fendon Road (south) a few days ago. I don't know how far they extend. |
| 88881139 | over 5 years ago | I'm not entirely sure what you mean. It isn't usually possible to delete or amend existing changesets (once they are closed), so the way to fix mistakes is to create a new changeset with the corrections. I think I've corrected Tom Scully Motors; if there are any other mistakes that I've missed, than I suggest you fix them yourself (in a new changeset). |
| 89352063 | over 5 years ago | I think you've added an excessive number of nodes in this changeset (and the other one in the same location). Most of the nodes you've added change the position of the way by less than 1m (and almost all by less than 2m), and some affect the alignment by less than 10cm (compared to straight lines ignoring those nodes). GPS traces won't be accurate to less than 1m, and imagery often isn't that accurate either - it can be distorted in various ways. It is also rarely possible (and never sensible) to try to identify the centreline of a road accurately to a precision of less than 10cm. |
| 89107522 | over 5 years ago | You should also add addr:street tags when tagging address (assuming the street name is part of the address - see addr=* for more details).
|
| 89109287 | over 5 years ago | These are not housenumbers, so should not be tagged with addr:housenumber. I think this needs to reverted. (The added data seems to just be duplicating existing data, sometimes even duplicating the name of a different building.)
|