I usually map these with a bare node - you could also use crossing=unmarked. I honestly don’t think a new tag is necessary.
I usually map these with a bare node - you could also use crossing=unmarked. I honestly don’t think a new tag is necessary.
Oh wow, big tech single-handedly curing my internet addiction! Love it!
OnlyOffice has a usable client for mobile. And it’s FOSS.
I absolutely love CyclOSM. It’s great for bike commuting, as it differentiates between separated cycle paths and cycle lanes, shows one-way streets that allow opposite bicycle traffic, good/bad surface quality, 20 and 30 km/h streets and bike stands.
OSM has much better coverage in Europe as more volunteers contibute. I heard it’s not that great in the US.
I love your style of writing :) I’ll bookmark your site in my gemini browser. I also think the post fits as it’s urbanism- and community-related.
I prefer to map them separately. For paths going along the road I use highway=footway
+ footway=sidewalk
, for separate paths just highway=footway
. You can also add sidewalk=separate
to the road, so that routing software knows to prefer the separately mapped sidewalk to just using the road.
crypt.ee is a great alternative, which is extremely well designed. Included in the subscribtion is an online document editor for personal notes and documents. Everything fully encrypted of course & works across all platforms.
That’s definitely not normal. The rendering can be a bit slow, but everything else shold be usable. Unless you have a low-range phone. If that is the case, I can recommend Organic Maps, which are much less resource-intensive.