Data AnalyticsFundamentalsbeginner
Updated:

Levels of Measurement in Statistics

4 min read

The four levels of measurement — nominal, ordinal, interval and ratio — decide which statistics are valid on your data. Learn each with clear examples.

TL;DR – Quick Answer

The four levels of measurement are nominal, ordinal, interval and ratio. Nominal data is unordered labels, ordinal has a meaningful order but uneven gaps, interval has equal gaps but no true zero, and ratio has equal gaps and a true zero. The level determines which statistics and operations are valid on the data.

On This Page

The levels of measurement describe how much mathematical meaning a variable's values carry, and they come in four steps: nominal, ordinal, interval and ratio. This classification, introduced by psychologist Stanley Stevens, is not academic trivia — it decides which statistics you are allowed to compute. Averaging shirt sizes coded as numbers, or computing a ratio on a temperature in Celsius, are mistakes the framework helps you avoid. Every analyst should be able to place a column into one of these four levels on sight.

The levels refine the broader qualitative vs quantitative split into a more precise ladder, and they sit at the heart of the data analytics fundamentals track.

Nominal: labels with no order

Nominal data is pure categories with no inherent ranking. Eye color, country, product type, and yes-or-no fields are nominal. You can tell whether two values are the same or different, but "greater than" has no meaning — red is not more than blue. Valid operations are counting, proportions and finding the mode (the most frequent value). You cannot compute a mean or median.

Ordinal: order without equal gaps

Ordinal data has a meaningful order, but the distances between values are not guaranteed equal. Customer satisfaction rated low, medium, high is ordinal: high beats medium, but you cannot say the gap from low to medium equals the gap from medium to high. Education levels, medal rankings and survey scales are ordinal. Here the median and mode are valid, but a mean is questionable because the intervals are uneven.

Interval: equal gaps, no true zero

Interval data has equal spacing between values but lacks a true zero that represents "none of the quantity." Temperature in Celsius is the classic example: the difference between 20 and 30 degrees equals the difference between 30 and 40, but zero degrees does not mean "no temperature," so you cannot say 40 is "twice as hot" as 20. Means, medians and standard deviations all work; ratios do not.

Ratio: equal gaps and a true zero

Ratio data has everything interval data has, plus a meaningful zero that marks the absence of the quantity. Height, weight, age, income and counts are ratio. Because zero is real, ratios make sense — 40 kg genuinely is twice 20 kg. Every statistic is valid on ratio data, which is why it is the richest level.

A worked example

This snippet applies the correct statistic to each measurement level.

import pandas as pd

# illustrative survey sample data
df = pd.DataFrame({
    "city": ["Pune", "Delhi", "Pune", "Delhi"],      # nominal
    "satisfaction": ["low", "high", "medium", "high"], # ordinal
    "age": [24, 31, 28, 45],                           # ratio
})

# nominal: mode only
print("Most common city:", df["city"].mode()[0])

# ordinal: order the categories, take the median
order = pd.Categorical(df["satisfaction"],
                       categories=["low", "medium", "high"], ordered=True)
print("Median satisfaction:", order.sort_values()[len(order)//2])

# ratio: mean is valid
print("Mean age:", df["age"].mean())

Expected output:

Most common city: Pune
Median satisfaction: high
Mean age: 32.0

Each column gets the statistic its level permits: a mode for nominal city, a median for ordinal satisfaction, and a mean for ratio age. Trying to average the city names would fail or mislead — which is exactly the error the framework prevents.

How analysts use the levels

Before choosing a chart or statistic, an analyst silently classifies each variable. Nominal and ordinal data get bar charts, counts and proportions; interval and ratio data get histograms, means and correlations. The level also guides encoding: a nominal category should be one-hot encoded so no false order is implied, while an ordinal one can be mapped to ranked integers. Getting this right keeps analysis honest, and it ties directly into the data quality habit of understanding your columns before trusting them.

A practical tip is to remember the ladder as a one-way gain in permissions: each step up adds an operation the level below could not support. Nominal allows only counting and mode; ordinal adds ordering and the median; interval adds addition, subtraction and the mean; ratio adds multiplication and division, which is what makes true ratios meaningful. When you are unsure which statistic is safe, identify the level first and the answer follows automatically. This is why classifying a variable is not a formality — it is the step that quietly authorizes every calculation you make afterward.

Common mistakes

  • Averaging nominal codes. Encoding cities as 1, 2, 3 and averaging invents a meaningless "average city."
  • Claiming ratios on interval data. Saying 40 C is "twice as hot" as 20 C is wrong because Celsius has no true zero.
  • Ignoring that Likert scales are ordinal. Averaging survey points is common but technically imprecise; at least know it is a shortcut.
  • One-hot encoding ordinal data. Throwing away a real order (low, medium, high) loses information the model could use.

In interviews

Classification questions are frequent: "What level of measurement is temperature in Celsius?" or "Give an example of ordinal data." The interval-versus-ratio distinction and the ordinal nature of Likert scales are favorite traps. A strong answer names the level, states the reason (equal gaps, true zero), and notes which statistic each level allows — demonstrating you connect the theory to practical analysis choices.

Where this fits in your learning path

Levels of measurement sharpen the qualitative vs quantitative distinction into four actionable categories, so read that page first if the basics feel shaky. From here, the framework supports everything statistical you do later in the data analytics hub, and it reinforces the data quality dimensions practice of truly understanding each column before you analyze it.

Frequently Asked Questions

What are the four levels of measurement?
They are nominal, ordinal, interval and ratio. Nominal is categories with no order, ordinal is ordered categories with unequal gaps, interval has equal gaps but no true zero, and ratio has equal gaps plus a meaningful zero. Each higher level allows more mathematical operations.
What is the difference between interval and ratio data?
Both have equal spacing between values, but ratio data has a true zero that means absence of the quantity, while interval data does not. Temperature in Celsius is interval because zero is not the absence of heat, whereas weight is ratio because zero means no weight. Only ratio data supports meaningful ratios like twice as much.
Is a Likert scale ordinal or interval?
A Likert scale, such as strongly disagree to strongly agree, is technically ordinal because the gaps between points are not guaranteed to be equal. Many analysts treat it as interval to compute averages, which is a practical but debated shortcut. Knowing it is strictly ordinal shows deeper understanding.
Why do levels of measurement matter in analysis?
They decide which statistics are valid. You can find a mode for nominal data, a median for ordinal, and a mean for interval and ratio data. Applying the wrong statistic, like averaging unordered categories, produces meaningless results.
What statistics can I use with nominal data?
With nominal data you can count frequencies, find the mode, and compute proportions and percentages. You cannot compute a meaningful mean or median because the categories have no order. Bar charts and pie charts are the typical visuals.

Want to Build Your Career in Data Analytics with AI?

Join CodeBegun and train with working industry engineers — Explore the Data Analytics program

Apply for Demo Class →
Siva Prasad Galaba
Founder, CodeBegun · Staff Engineer

Founder of CodeBegun. 15+ years building Java systems at companies like Crunchyroll. Teaches Java, Spring Boot and system design the way the industry actually works, and mentors students through projects, mock interviews and placement preparation.

Technically reviewed by CodeBegun Technical TeamLast reviewed 16 July 2026 LinkedIn
Chat with us