Environment first
GNSS works well outdoors but usually fails indoors. Indoor systems need anchors, beacons, readers, or Wi-Fi data.
Compare GNSS, Wi-Fi, BLE, UWB, LoRa, cellular, and RFID against real IoT location requirements
Choose a positioning approach by matching requirements to real tradeoffs. Compare indoor and outdoor fit, accuracy, update rate, battery life, infrastructure, coverage, and cost before deciding whether one technology is enough.
GNSS works well outdoors but usually fails indoors. Indoor systems need anchors, beacons, readers, or Wi-Fi data.
Centimeter and sub-meter location usually needs more infrastructure, calibration, power, or device cost.
Tracking a moving worker needs different updates than finding a pallet once per hour.
Many deployments combine wide-area location with a precise indoor or gateway-level method.
State what must be located and why.
Indoor, outdoor, or mixed conditions.
Match precision to the decision.
Power, cost, update rate, and infrastructure.
Choose one method or a hybrid.
Start by describing what location decision the system must support.
Location technology is chosen from the decision the user or system must make, not from accuracy alone.
GNSS and cellular score well when outdoor coverage matters more than indoor precision.
Use GNSS for outdoor fixes, and add cellular or gateway fallback when coverage is uncertain.
Pick a scenario, play through the selection stages, then adjust requirements to see which technologies rise or fall.
The score is a teaching heuristic for shortlisting. It helps explain tradeoffs, but a real deployment still needs a site survey and tests.
accuracy_fit = penalty_when_typical_accuracy_is_coarser_than_required
More precise than needed is acceptable, but it may still lose points through cost or infrastructure.
environment_fit = indoor_share * indoor_strength + outdoor_share * outdoor_strength
GNSS favors outdoor share; BLE, UWB, Wi-Fi, and RFID favor indoor or local zones.
constraint_fit = power_fit + infrastructure_fit + range_fit + update_fit + cost_fit
Deployment constraints explain why the most accurate method is not always the best method.
score = weighted_sum(accuracy, environment, power, infrastructure, range, update, cost)
High scores are shortlist candidates. Close scores are a signal to test or combine methods.
Use these cards to connect the selector to practical IoT location decisions.