RackIQ: The Scored Call™

Under the hood

What RackIQ Actually Runs

RackIQ™ leads with the call, not the map. But the call is built on real ground data, and people ask what is underneath it. This is the plain answer, including the parts we refuse to claim.

Terrain

Elevation comes from the USGS 3D Elevation Program, which is LiDAR-derived where LiDAR has been flown and coarser elsewhere, with fallbacks so a read still works outside covered ground. Raw LiDAR point-cloud analysis is not currently enabled.

What we do instead is the part worth knowing. RackIQ measures the effective resolution of every read and refuses to name a landform the data cannot support. A saddle or a bench needs fifteen metres or better. A ridge needs sixty. Below that the feature is withheld rather than guessed, and the screen tells you the detail level and how much was held back.

Most tools draw the same confident lines everywhere and let you find out the hard way. A read that lands on ten metres is a ten-metre read, and calling it high detail is the kind of rounding that turns into a claim.

From that surface RackIQ reads benches, saddles, points, draws, ridges and pinch points, plus slope and aspect, and renders the ground in relief and in three dimensions with the vertical exaggeration labelled on screen rather than quietly tuned.

Your ground

LayerSource
Parcel boundaries, owner and acreageState and county public GIS where published, licensed national data elsewhere. Coverage varies by jurisdiction.
Public landUSGS Protected Areas Database (PAD-US), plus federal agency boundaries
Satellite and aerial imageryEsri World Imagery, USGS NAIP, Copernicus Sentinel-2
Topographic maps, contours, hillshadeUSGS The National Map
Land cover and canopyUSGS and MRLC National Land Cover Database
Crops and forageUSDA Cropland Data Layer, Sentinel-2 change detection
BuildingsFEMA USA Structures
Roads, trails and accessOpenStreetMap

Drop a pin and RackIQ pulls the parcel under it with the owner and the acreage, and offers the outline as your property line. Adjacent parcels under the same owner join into one property. Where no parcel source covers your ground, you draw the line and it snaps to real features rather than making you trace freehand. A miss tells you it was a miss, which is not the same as telling you the ground is unowned.

Every dataset above is credited in full on the data sources page.

What the terrain is for

This is where RackIQ stops describing the ground and starts telling you what it does to your hunt.

Terrain is not a picture in RackIQ. It is an input to a decision.

In the field

Maps cache for offline use, because the product is used where there is no service. In the field you get GPS, waypoints, stand and camera markers, track recording, distance and area measure, and an approach route worked out against the wind. Arrive at a stand and it offers to start the sit; leave and it asks what you saw, while it is still fresh.

Cameras and bucks

Photos come in from any camera, by card or by upload, and RackIQ sorts them, reads the timestamp, detects what is in them, and drops the duplicates.

Then it does the part most tools do not. It builds a profile per buck across cameras and weeks: when he moves, the winds he favors, how huntable he really is, and his best window ahead. It works because it matches against the bucks on your property rather than a national pool of images, which is a far smaller and far more answerable question.

Antler scores come back as a range with a confidence tier against the county bar. Never a single invented number, and the language model never picks the figure you see.

What we will not claim

This list matters more than the one above it.

Maps are the ante. The call is the hand. Everything above exists so that one line at four o'clock is worth trusting: hunt it or save it, which stand, and why.

Read your ground free →