Hi Greg,
Curious why you believe this border road is clearly not open to the public? This photo is taken about 200km south on the border: https://media.gettyimages.com/photos/indian-villageswomen-along-her-son-cross-the-road-at-the-near-border-picture-id618590050
The road layout at this (and many other points) osm.org/#map=17/25.51274/88.78252 suggests to me that the road is open to the public. There is no sign on satellite photos of any gates or barriers at the two junctions visible at that location. The following location also has roads running from the settlement out to the west and south east which strongly suggests the border road is used for transport: osm.org/#map=17/25.36119/88.84355

The following articles show photos of the public using the Indian Bangladesh border road elsewhere (locations unknown) https://www.gqindia.com/content/india-bangladesh-border-journey/
https://www.thestar.com/news/world/2013/04/01/hundreds_of_bangladeshis_getting_killed_at_border_with_india.html

There are also numerous gates to fields dotted along the length of the road, which would appear to be used by farmers to access fields between the fence and the actual border. There would be no way for these farmers to access many of these gates without moving along the border road.

Generally speaking I'd be a little hesitant to tag many km of road with access tags unless I was certain! :)

Best regards,

David

Oh, and there was a problem with erosion following storms in 2014, which has now been addressed, perhaps that was the cause of the closed notice?

The County Council had confirmed by email that the footpath from Penally level crossing, past the firing range, across the golf course to the beach is currently open and passable, and isn't closed during use of the firing range. I'll mark it as open.

when the rifle range is in use, I mean!

Hi, the path you marked as closed from Penally to the beach is (I believe) a public footpath that crosses a rifle range, and is temporarily closed when the path is in use. Your edit suggests it is permanently closed. Do you happen to know which is the case please? Thanks!

Oops, wrong description left on changeset - actually some details in Penally from (old) local knowledge and Bing.

This isn't a railway, it's the border fence and accompanying road. See this photo for a similar section of border fence: https://media.gqindia.com/wp-content/uploads/2016/12/GQindia-Border-866x487.jpg

This is not a railroad/railway. It is a border fence and road. It looks like this: https://media.gqindia.com/wp-content/uploads/2016/12/GQindia-Border-866x487.jpg I have already fixed part of this, but not all of it!

or rather passing_place

Good spot. Perhaps it was meant to be highway=passing place? There's a bug in the version of iD I was using where the text cursor jumps from the value box back to the key box after typing one or two characters. Could have resulted from that.

If it looks like a passing place feel free to correct - I'm on my mobile so can't deal with it too easily.

Thanks,

David

I'll remove the railway tag - having looked at it, it does look a bit like a railway but there are sharp corners in places which show it cannot be. The line is a fence. There is also the border road running immediately next to the fence which needs mapping. I may get a chance to start on this.

Hi Aubry1, if you change highway=track to highway=bridleway and it's a UK public bridleway, please would you add bicycle=yes and foot=yes as otherwise you are breaking routing for bicycles and possibly hiking too. It might also be good to add physical=track as otherwise you are removing info that may be useful to people such as disability adapted bicycles, tricycles, off road wheelchairs etc.
My recommendation would be to leave it as highway=track and add:
designation=public_bridleway
foot=yes
bicycle=yes
horse=designated
This carries the maximum useful information and works with all routing engines, although it doesn't render as a green dashed line on the default Mapnik render, (though this should be a secondary consideration really)
up to you how you tag ultimately of course! :)
Many thanks!

Thanks, yes, I think the tagging I used was very old. I've edited now - does that look better?

Think I've got what you mean now - you mean when looking at the map, or a map background in an editor? I deleted the duplicates from this changeset previously. They aren't showing up in the opencyclemap at some zoom levels because the renderer layer because that hasn't been udpated from the underlying data yet. Please see the other changeset that I've commented on this afternoon for one where I haven't fixed the underlying data.
When editing, rely on the data in the editor, not on a background map layer, which may be out of date at high zoom levels. I never use map backgrounds for editing but prefer to use satellite photos as that also helps see what's really on the ground.

I'm not sure what you mean by "The Standard layer does not show every track, but the Cycle Map layer does." - can you clarify which layers you are talking about? Thanks :)

Very weird!! I will see if I can reproduce it! Glad we found the issue, anyway!

I'll stop looking now :)

also way/509026287 and way/509026287

also way/509026288 duplicates a path and doesn't link to correct point on western end. I note someone has mapped a stile next to this path (presumably should be on it) - can you double check it's a bridleway please?

also bridleway way/509026289