Numbers are easy. Understanding what a number means is harder.

A simple question can hide a surprisingly complex problem:

“How many gaj in 1 bigha in UP?”

The arithmetic is easy.

The difficult part is understanding what the user actually means.

Before calculating, a system may need to determine:

• What unit is being used?

• Which region does it belong to?

• Is the unit definition local to that region?

• What does the user mean by “bigha”?

• Which conversion definition should be applied?

For example, bigha isn't one universal unit. Its meaning can change by region.

That's what we've been building with LandUsers.

The LandUsers API takes natural-language land queries and turns them into structured, region-aware conversion results.

For example:

how many gaj in 1 bigha in up

→ 1 bigha = 3025 gaj

The interesting part isn't the multiplication.

It's understanding the question before doing the multiplication.

I'm curious:

How are other developers handling ambiguous, context-dependent units in their applications?

Would love to hear how you're approaching this.