There's a decimal.

And over here, well the way I later put a decimal here, here you would count it, so if you have a decimal there you would count all five.

Now, do they want a decimal?

A decimal, then 13 zeroes and a 1.

Over here, there's a decimal so you count the trailing zero.

There's a decimal here so you count the trailing zero's.

I'll use this one since it doesn't have a decimal in it.

So we have our decimal point right here, right behind the 7 where it was up here.

So the easy way to think about is, if you have a decimal, if there is a decimal anywhere in your number, count them.

For this person to be less ambiguous they would want to put a decimal point right over there.

It's not a decimal point actually, let me erase it so it doesn't confuse you even more.

And then we have a decimal, and then we have a 1 and a 5.

If there is no decimal anywhere in the number, then it's kind of ambiguous.

And actually, just so that we make sure that everything's clean, let's put our decimal.

If you have a decimal count them as significant. they are significant.

Well, if you remember from the dividing decimals module, we can just add a decimal point here and add some trailing 0's.

If I say, let's say fifty and I'm just going to add one decimal of accuracy here just to show you a point fifty percent.

If someone really does measure, if you were to really measure something to the exact one, then you should put a decimal at the end like that.

We took a decimal point off what it cost to build these cities, and that's how we're going to be able to scale this out and make this reality a dream.

So clearly, over here, there's a decimal in the number so you count the trailing zeros these are adding to the precision.

3 goes into 10 three times, with a remainder of 1, carry the 1 again, then you could bring down another zero we now have a decimal point over here.

What I would recommend, if you have any trailing zeros with a decimal like this, you should actually just ignore those zeros, and then do the problem just the way I did it.

You just want to include all the non zero digits and everything in between. and and trailing zeros trailing zeros if a decimal point is involved.

Decimal point

Comma

Floating Point Value

Semicolon

If you didn't have the decimal, if you just had 37,000 like that it's ambiguous, and if someone doesn't give you more information you're best assumption is probably that they just measured to the nearest thousand, that they didn't measure exactly to the one and just happened to get exactly on 37,000.

Whether to use fixed decimal places

Whether to use fixed decimal places.

Custom...

So if there's no decimal, let me write it this way, it's ambiguous, which means that you're really not sure what it means, it's not clear what it means, and you're proabably safer assuming to not count the trailing zero's.

Comma separated list of mimetypes

Decimal Comma Number

Please enter a valid float value!

Comma separated list of the area borders

Comma separated list of structure keywords

Comma separated list of DTEPs that can be present inside this DTEP

Custom Fields

It's diddly point squat.

So (3, 2).

I don't know how many decimal places we'll do.

So we went to 3 decimals of significance.

Comma separated list of toolbars

Comma separated list of the common attribute groups