Runway ID

"Jose" wrote in message
. ..
Ah, because the REAL rounding rule, designed so that averages will not
become distorted high from rounding 1/2 up, is to round 1/2 to the
EVEN number.

I know of almost no teacher nor textbook that remembers this, much
less why it is so.

That's because it's not so.

The standard rounding rule is 5 goes up.

If you have 0.245, it is 0.24 rounded to hundreths. How is that '5 goes up?'

The rounding rules I am talking about are for preventing rounding bias in
data. If you took a big pile of numbers, rounded them all up, added them,
you would have a value that was way off of the true value of the sum.

0.247 0.25 0.2550.26 is that what you mean? That's exactly what I
stated.

The catch is that you ONLY round from the digit after the one you're
rounding to. For example, .2447 rounds to .245 or to .24 or to .2
although a common error is to round (to the hundredths) as .25, because
the "rounded to the thousanths" version would end in a five. When
rounding, always round from the source, not an already adulterated
version.

Jose

Yes, you don't round a number, then round it again.


"GeorgeB" wrote in message
...

If these runways were at the same field, your method would have runway
designators that differ by twenty degrees for runways that have a difference
in azimuth of only ten degrees. I think I'd round both in the direction
that local magnetic variation was moving.

Yes, that would be logical.