It doesn't help that there are multiple ways to map sidewalks in OSM (as a property of the roads themselves, or as standalone paths parallel to the roads).

I got pretty into OSM for a while and that's definitely the thing that eventually put me off... So much stuff has multiple ways to be mapped, and it gets confusing/overwhelming. I understand that OSM has a very malleable data model, and that definitely has many benefits, especially for niche/edge cases. But I do wish the community had arrived at a settled convention for at least the most basic stuff, like the aforementioned sidewalks.

▲

maxerickson 4 hours ago | parent | next [-]

There's usually a reasonably clear consensus within a region or country.

That's less true for niche stuff (vs stuff where two different ideas are in wide use), but there probably isn't all that much of it either.

One way to approach it is to not worry too much about it, consistency can come later.

	▲	rafabulsing 4 hours ago \| parent [-]
		That's true, but the very feeling that I might be inputting things in a way that might have to be updated later kinda drained my motivation. I do understand that even if does get replaced eventually, it still was useful for a while, and probably served as the basis for whatever came after. But still. For whatever reason, in my brain, it just diminished whatever psychological reward I got from adding information to OSM, which is a shame.

▲

nradov 3 hours ago | parent | prev [-]

At least in urban areas I've seen it's almost always better to define the sidewalks separately. The routing for pedestrians is often significantly different than for vehicles. This matters when the data is fed into Strava or Garmin for running routes.