When adding a direction using the up/down arrow values go negative.

[sekerob]

Had this a number of times being flagged on the issue report, which is dating from before the 5 degrees step change i.e. when direction incremented/decremented by 10 degrees. The simplest reproducible test is to enter direction=0, then using the down, the value goes -5. The OSMI issue report flags this as a suspect value. Going from 355 to 5 and back effectively turns 355 to -5 too.

O/T WishListed: Fantastic would be if 1) holding the up/down in/decrementing rolls on rather that clicking multiple times to get to a desired beam alignment. 2) Outstanding would be if one could grab the beam and drag it around.

thanks for reading.

[quincylvania]

Welcome, @sekerob. Is this causing problems for any actual data consumers? 355° and -5° are equivalent for the direction a stationary object is facing.

Outstanding would be if one could grab the beam and drag it around.

I'd consider this a separate issue…

[sekerob]

Thanks for your comment and probably no, a data consumer will likely know that all numbers are an offset to 0, due north. Unfortunately hitting false-positive or ignore does not resolve... few weeks later the same issue pops up again. Anyway, thought if greater than 360, subtract 360 and if less than zero, add 360 would cure the issue. Hardly expect an editor doing a full circle twice.
cheers

[Jeinzi]

Happened to me too. By using the up and down arrows I accidentally added negative orientations and Osmose flagged every node as suspicious.

355° and -5° are equivalent for the direction a stationary object is facing

That's certainly true, but using additional characters for more digits (i.e. 1075°) or negative numbers will mildly bloat the database. The wiki also states that numerical orientations should be in the range [0, 359].