Udarian,

So this is the problem with leaving it as designated and why I made the edit and believe it should be as I edited. On many cycling platforms, to generate cycling routes, a the platform relies on data from OSM to generate a route. I previously created a route that included the footpath at issue. When I was riding I came across the issue we are discussing where I wanted to get on the path but the path is within a complex that is guarded by a gate. Thus access to this area is private, not designated. The reason for that is the term designated as it's defined in the link I sent you refers to cycle paths, like for example the pathway along US1 for cyclists known as the Underline. That is a "designated" foot/cycle path as no heavy motor vehicles are permitted on that path.

The example we are discussing, is a pathway that is private. The only people allowed into that complex are people authorized, thus it's essentially private and the whole thing, including the roads should be tagged as that. You'll notice on the regular roads where cars drive in that area that the roads are marked as private. If the roads where the cars drive in that private complex are marked as private, then it follows that a pathway there must also be marked as private.

In your response you mention "It is designated because from what I can tell it is a pedestrian and foot path," however, have you been to the location to verify this? I encourage you to go there and speak to the guard the same way I did to ask if the pathway is "designated" for public access who cycle or walk on there, or if the pathway is actually private. This is no different than marking a pathway on a military base as private, and not designated because designated implies certain road users of the public can access it if they walk or bike on it.

Do you potentially have another solution? I'm all ears as to how to figure this out with you to ensure that the pathway is correctly marked.