Speeds and Data Plans
I'm researching data plans and noticed Cox updated and reformatted their Speeds and Data Plans page. A couple notes:
Gigablast Package & Maximum Limit. Cox defines an area with "periods of sustai...
Forum Discussion
How does 1.25 TB equal 1280 GB?
Data Units Converter
www.gigacalculator.com/.../data-storage-bandwidth-converter.php
With the "Use SI standard" box unchecked (conventional metrics), enter 1.25 in the box on the left and select TB, then select GB on the right. 1.25 TB = 1,280 GB
Now check the "Use SI standard" box (decimal) 1.25 TB = 1,250 GB
I don't think you read my reply. It's not a question of math or conversion. It's a grammatical or notational question.
1. Why convert? Does the average subscriber read or understand binary storage?
2. If you need to convert, use the concise notation of said conversion: 1280 GiB. "B" is understood as decimal and "iB" binary.
3. If you need to convert, convert all the established limits listed on the page.
A kilobyte has always been 1024 bytes, Not knowing that makes it obvious you don't have a programming background. You still don't understand what I tried to explain to you.
There is a technical and a general specification of kilobyte. However, the #1 rule of communications: analyze your audience. To whom is Cox communicating with on this page...programmers or everybody?
There are 2 systems to notate storage: base-10 and base-2. The IEC has completely standardized and notated storage for both systems up to the power of 8 (yottabyte and yobibyte). This system distinguishes "B" as base-10 and "iB" as base-2. Your reference (JEDEC) is base-2 but incomplete, limited and confusing because it also uses "B" as does base-10. Is 1280 GB base-10 or -2? Does Cox expect us to do some math?
I fully understand your post, but it wasn't a question about from where or how you get 1280 GB. I understand and appreciate your effort; however, it's a question of why use 1280 GB.
If it's a standard practice for Cox to bill storage as base-2, great...fantastic...tag it and footnote it. However, Cox just notated as 1280 GB and left it to our imagination. What happens if I consume 2 TB or data in 1 month? How would you, Curt, notate this size...2 TB or 2 TiB? As far as I know, JEDEC can't express in tera. JEDEC may have updated to YB...I don't know...but why not just distinguish base-2 with an "iB" notation?
You're original question was
Monthly data plan. How does 1.25 TB equal 1,280 GB? Do you mean 1.28 TB or 1,250 GB? At which threshold would Cox start "automatically" charging $10 for exceeding a data plan: 1.25 TB or 1,280 GB? It's only a difference of 30 GB or 2 UHD movies. Why can't Cox be "StraightUp" with us?
How 1.25 TB = 1280 GB has been explained enough.
You're other concern was losing 30 GB of data. So I'll back out of the 1280 to get you to the 1250 you want to see. (This should look familiar. I'm just going in the other direction than in the earlier post).
1024 * 1 billion * 1.25 = 1280 Billion
1000 * 1 Billion * 1.25 = 1250 Billion
1024/1000 = 1.024
1280 Billion / 1.024 = 1250 Billion
For the math to work, we've determined that the 1280 GB referenced is actually 1280 Billion bytes. 1280 GB is 1310.72 Billion bytes. The website author probably failed to make that distinction (or didn't expect anybody to fact check it). But if you were expecting a 1250 Billion byte data limit, you're getting an extra 30 Billion bytes.
See? You're not losing any data. Had Cox simply omitted the "(1,280 GB)", you would have been fine. Ironically, including that bit of explanation appears to have been Cox trying to be "StraightUp" with us.
A kilobyte is and will always be 1024 bytes because computers can more easily calculate 210 than add up individual bytes. You can look it up. There are a few bazillion websites that mention it.
