Map scale from measurement calculator

Zero or negative distances are rejected with a clear invalid_input error instead of inventing an impossible scale.

How representative fraction scale is defined from two measured lengths

A representative fraction (RF) map scale is the dimensionless ratio of map length to ground length for the same feature, conventionally written as 1:N or 1/N so that one unit on the map corresponds to N of the same units on the ground. There is no projection engine, no pixel sampling of a basemap image, and no dependence on zoom level or screen DPI: those problems belong to other tools. Keep map and ground measurements for the same feature; mixing unrelated segments produces a nonsense N even though the arithmetic still runs. When you already know both lengths—for example two centimetres on paper spanning one kilometre in the field—you convert both measurements into a single unit system and form N equals ground_length divided by map_length. This calculator performs that conversion in metres using published international factors (millimetre, centimetre, metre, kilometre, inch, foot, yard, and statute mile), then returns the integer-rounded denominator when the absolute value of N is at least one, which matches how cartographic legends and exam keys present scales such as 1:50000. The response echoes the rounded map_distance and ground_distance you supplied, records map_unit and ground_unit, publishes map_distance_m and ground_distance_m, exposes scale_denominator and scale_denominator_raw, scale_ratio as the string 1:N, representative_fraction as 1/N, precision, method tag map_scale_from_measure, formula as the string N equals ground_m over map_m, message as a short English summary, and steps as an ordered substitution log. The engine either divides two positive finite metre lengths inside the supported magnitude range or rejects the input with invalid_input. Rejected cases include missing map_distance or ground_distance, non-finite values, magnitudes outside the published ceiling, unit tokens outside the enum, and any distance that is zero or negative, because a non-positive geometric length cannot define a ratio scale.

Input contract, response shape, and error behaviour

On success the response includes the converted metre lengths, the scale fields listed above, formula and message, and steps as the substitution log you can assert in tests or show next to a sketch. Prefer sending numbers rather than pre-formatted strings when you control the client; when you must send strings, put units only in the unit fields, not glued to the distance values. Send a JSON body with two required fields: map_distance for the length measured on the map (aliases map_dist, map, measured_map, d_map) and ground_distance for the corresponding real-world length (aliases ground_dist, ground, real_distance, d_ground, true_distance). Both must be finite and strictly positive within the published absolute range so the intermediate metre conversions and the ratio remain positive finite IEEE doubles. Optional map_unit defaults to centimetres and ground_unit defaults to kilometres—the usual paper-map and scale-bar pairing—and each accepts the closed enum mm, cm, m, km, in, ft, yd, mi so the form renderer can offer a select control instead of free text. Optional precision (aliases decimals, dp) chooses how many decimal places to expose for non-integer numeric fields, defaulting to twelve and capped at fifteen so JSON goldens stay stable across runtimes; when the absolute denominator is at least one it is integer-rounded for conventional RF display while scale_denominator_raw preserves the unrounded quotient. String forms of numbers are accepted when they match a strict finite decimal pattern with optional scientific notation; embedded spaces, unit suffixes inside the number fields, and non-numeric tokens fail with a clear invalid_input message naming the field. Failed validation—missing fields, non-finite numbers, zero or negative distances, unknown units, or values outside absolute limits—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item.

Where map scale from measurement fits in field work, study, and software

On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split—free interactive exploration and a priced, identical API—matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result.