OpenStreetMap logo OpenStreetMap

Changeset When Comment
175037602 26 days ago

I reverted this changset

changeset/175038462

175037313 26 days ago

I reverted this changset

changeset/175038462

175037207 26 days ago

I reverted this changset

changeset/175038462

174436292 about 1 month ago

HI've reverted this revert. I'm making contact with the Data Working Group about this subject.

174123340 about 1 month ago

The designated UK square blue sign "cyclists dismount" does NOT have the same meaning as the OSM tag bicycle=dismount

The sign is only an advisory, which by itself effectively lets you know that you may continue riding. Historically used to show it was legal to ride, but the upcoming highway had an adverse condition that could not be improved. (low height, narrow, poor visibilty).
I repeat, it did not mean "must not ride." It advised you of an issue.

It also was allowed, confusingly, to be used where a cycle way ended, but a pedestrain way continued. The intent to draw attention to an actual prohabition on cycling that is not clearly marked. (eg Pedestrian Zone).

The meaning has been updated. The original intent of advising of adverse conditions has been removed. It may only have been advise, but advising disabled people to walk breaks UK disability laws. The adverse conditions should now be signed to show the specific issue (eg Low Height (2m)). It is now only to be used together with other signs to confirm "No Cycling" exists at locations where it may not be apparent.

Now things get complex. In the situation your discussing. It is clear the intent is that the Cycle Track ends and you're not to ride over the foot bridge. But there appears no prohabition on cycling over that foot bridge.

Although we commonly say that "cycling on a pavement" is illegal in the UK. That is wrong. The prohabition is for vehicles, and objects with wheels, or animals, being taken onto a "footway" that is part of a road, but forms a lane in the road seperate from the carriegeway. (There is a legal difference between footway, footpath, and walk way). The bridge is seperate from the road, and therefore a footpath. Since it is a legislative Footpath and not a legislative Footway, there is no prohabition on non-motorised vehicles. A Traffic Order would be needed, and signed with a No Cycling sign at both ends of the bridge.

In my experience the Highways Authority can't be bothered with creating a Traffic Order, and has chosen to acheive their aim by misleading with the advisory Cyclists Dismount sign. Putting up this advice sign does not require a Traffic Order with associated cost.

There may be no prohabition of cycling over that bridge, but I would accept the intent of the sign and make the bridge bicycle=no.

174204545 about 1 month ago

Using areas mapped by sec147 in or around Exeter misleads.

Cranbrook is unusual as it's can be described as a personal project of one person

Taunton ? Thats nowhere near Exeter, it's in a differenct county. If I added data there I would respect the local mapping.

174204545 about 1 month ago

My changes are done not as part of a personal quest, they are done to bring the mapping in line with the regional practice for adding addresses.

The vast majority of the changes are to to addresses added by a one person. Sec147. Edits that appear to be from an automated import, and which involved moving some nodes to polygons.

I strongly agree that we should discuss issues, but this comes back to being a local issue. The dominant practice used by local mappers is to add addresses to nodes. (I don't include sec147 as a local mapper).

I will be going ahead with the changes, but making the changesets cover a much smaller area, and specifically concentrating on the areas where sec147 added addresses.

If you wish to raise the issue in the discussion forum, go ahead. I'm happy to discuss this there,

174204545 about 1 month ago

I did not make ~10,000 changes in an edit, and the edits are not "automated/mechanical" with regard to how this is meant in OSM, or the intent.

The mapping practice does follow local style. I'm not imposing this across the county so it does not need discussion.

The polygons with addresses in our area were mostly added by sec147. Sec147 edits appear automated and have the type of issues that lead to the rules on automated edits, and imports.

But.... looking at my changesets I do feel they are too large and should have been broken up into smaller changesets.

I'm not going to revert your reverts, but I am going to go back and once again move, with regard to local style, addresses to nodes. They will be done in much smaller areas /. changesets.
They are not with OSM intent, "scripted" or "mechanical".
I will also, once gain, fix some of the issues created by sec147. Others will fix in seperate edits, or by visiting some specfic locations.

174204545 about 1 month ago

Hi Joe-w. Exeter and East Devon area has always been dominated by mapping addressees as nodes, usually within the building. Done primarily by areas three main mappers. Myself, Guy, and Wilpin.

I personally didn’t bother with address for several years, and initially added them to buildings. When I started adding addresses in Topsham, it became obvious addressed buildings were nearly always wrong, or an assumption. From experience I found it was nearly always not possible to verify there was only one address is associated with a building. Then accepted the local style of adding address to nodes removed that issue."

The addresses added to buildings in our area are primarily from a user called sec147 in 2022.
His edits were questionable and appeared automated. He bulk added a large amount of addresses to polygons, often containing errors, and other issues.
His edits involved deleting address nodes, usually created by myself, Guy or Wilpin, and moving the data to polygons.

The link you give does not state or imply what I did was wrong? It also appears to be the creation of a single person? As is common in OSM, there is no clear rule

My edits were done to bring addressing into line with local mapping styles, with the next stage to find and fix errors created by sec147.

I see you've reverted my address edits. I wish you'd waited for me to respond first. You've done this by stating my edits are "undiscussed automated edits". My edits were not automated edits and clearly do not meet the common definition of that. I'll be a bit cheeky and state your reverts are undiscussed automated edits?

166004173 about 2 months ago

phodgking, we are allowed to use Ordnance Survey maps if they have the appropriate licence. There are two available as background layers in the iD editor used to make this edit.

"Ordnance Survey map" is commonly is used to refer to the Explorer & Landranger maps that can not be used for OSM mapping. If that's the case then the this changeset needs to be fixed.

172019682 3 months ago

I believe this should be discussed on the UK forum
https://community.openstreetmap.org/c/communities/uk/86

My, initial, late night thoughts.
1) The data does not belong in a relation, but as a tag related to use of Hotel
2) Data does povide information on a relevent function, or use, of an amenity
3) Terms used seem misleading (slang) and reasonable to consider a perjorative. Official, neutral, terms must be used

So I'd suggest a tag (innitial thoughts)
hotel:use=accommodation_centre

But....
4) Debate must be had on whether this data could cause harm, and if so withheld from OSM. Need to think on that one a bit more. It's definatly a discussion for the UK forum, and not a changeset comment.

171408641 4 months ago

I believe this group of changesets by The Vyne needs reverting. They all imply a lack of understanding of tag defintions and are likely wrong. The original tagging was done by the National Trust team and should be considered authoritive, if their work is changed there needs to be a clear explenation in the changeset comment.

171223363 4 months ago

This type of problem has been discussed on the UK section of the OSM Community Forum. I've linked to the post I made because it has a few links. The discussion went off-topic.

https://community.openstreetmap.org/t/marking-a-prow-as-a-bad-idea/113487/6

170268872 4 months ago

Hi Fgjgdrou,

In this changeset, and changesest 170268926 you have deleted a large number of address nodes, then attached the address to an adjacent & surrounding building.

In Exeter, and the surrounding areas the default way of adding an address is to create a node inside the assumed related building just back from the entrance door, then add the address to the node. (commonly exception for seperate business buildings eg supermarkets). What we may map from outside appearence as seperate buildings, commonly have walls knocked through to combine addresses.

I feel you simply shouldn't have made these changes, and ask that you revert them to meet the local style.

You have also appear to have done something that appears to be a bigger problem. You state your source for new addresses in "interpolation". We simply can't do that in the Exeter region, and I'd argue it's bad practice in most places. Can you remove the addresses that were from "interpolation".

Thanks,

Jass

119213269 5 months ago

Pink Duck, there would need to be evidence for the way being privately owned and "no Cycling ".

119213269 5 months ago

This way appears to be "footpath" and not pavement/footway. Therefore pedal cycles are allowed to use it (no prohobition). If Peter Sil has observed cyclists commonly using this footpath then I'd think it would be reasonable to add bicycle=yes.

169231443 5 months ago

Hi Blaster88,

I reverted this changeset in changeset/169312444.
changeset/169312444

The changeset had dragged a highway node affecting a major road. I aslo saw the changeset had added foot=no to the main road. I've looked and can see you've added foot=no to several major roads in the area. The use of foot=no on major roads has been discused several times amongst the UK Community. The concensus is that foot=no must not be added. Although it is clearly not meant to travel along these roads, the foot=no implies a prohobition. There is no prohibition so foot=no should no be used. In fact it appears pedestrains have a legal right to use the road.

It's felt that end users should deduce the road should not be used by pedestrians by taking into account facts such as speed limit and road type.

169312444 5 months ago

Revert of changeset/169231443 which dragged a node, and had added foot=no to busy road (no ban for pedestrains)

changeset/169231443

165611883 5 months ago

Yes, and you've reminded me that I've got to update it. Water started flowing into the quarry to the east, and land to west was washed into quarry.

At time I mapped it the area was flooded but receding, so didn't add water. The water is still there and being fed by a flow from the west, so I'll l add water later. The quarry is now a large lake.

167432073 6 months ago

If you look on Bing Streetside you can see there Trenham Avenue joins Tyefields by crossing the footway of Tyefields. There is a give way before the footway. An example of an OSM continous crossing?

https://www.bing.com/maps?&cp=51.575797~0.515389&lvl=19.83&dir=213.16301&pi=-25.197578&style=x&v=2&sV=2&form=S00027

access=no is rarely correct. It means the road exists but there is not access along it, for anything. That means no private access, and pedestrian access.