0day

joined 9 months ago
[โ€“] 0day@programming.dev 4 points 1 week ago

I would have expected the comments to be pretty dry and to the point. Thos eare some interesting stats. ๐Ÿคฃ

[โ€“] 0day@programming.dev 2 points 1 week ago

access=* is where m* mind went too. After checking the wiki, I was reminded that is for legal access.

[โ€“] 0day@programming.dev 2 points 1 week ago

Looks like you got it figured out. Setting it to track did the job. If you're still getting routed on something other than osm.org (e.g. a phone app), you may need to change your router settings.

[โ€“] 0day@programming.dev 1 points 5 months ago

You could pipe it to less.

somecommand | less

Or if you want only the beginning or end of output, use head or tail.

[โ€“] 0day@programming.dev 1 points 8 months ago

Like when everyone "went green"

[โ€“] 0day@programming.dev 1 points 8 months ago

Interesting. I just found this instruction. I'm guessing you already did too. (Source)

For speed limits depending on the way direction, see maxspeed:forward=*.

So I would say, map that section of road with forward/backward speeds. Also, the signs should be independent nodes.

The position of the actual speed limit signs can be added as nodes beside the road/railway/waterway
[โ€“] 0day@programming.dev 14 points 8 months ago

Good commit messages always help me find the bugs I introduced.

[โ€“] 0day@programming.dev 1 points 8 months ago

I live in a different state, not close to you. A similar thing would happen a lot when I lived in the big city. People would hit their brakes or slow down toward the end of a ramp, while merging. A few times I had people come to a stop at the end of an on ramp.

So you would be reaching the speed of traffic, looking left for your spot to merge in to moving traffic. When you look straight ahead again, you end up slamming on your breaks because the person in font of you is slowing to a creep. Meanwhile traffic on the interstate is ripping by and now you have to try to merge.