Changelog
What changed, newest first. A result change means a published answer moved; it names the test vectors it replaced, which stay in each tool's downloadable test vectors, marked superseded. Every release also has a verification report.
2026-11-07
Fixed Build-tool dependencies are up to date, clearing every high and medium security advisory the project was carrying. These are development tools, not part of the site or the calculators: no shipped code changes and no answer moves. Three low-severity advisories remain in a build plugin whose only published fix is an older, incompatible version; they affect the build machine rather than any reader, and they are tracked rather than forced.
Fixed The time-zone boundary data is now delivered in two pieces, which is what the site needed to deploy at all. Cloudflare Workers refuses any single file over 25 MiB and the boundary index is 26.9 MB, so no deploy could start, whatever else was ready. The index is split into two pinned pieces that the runtime joins back before anything reads them, checking each piece against its own fingerprint and the joined file against the one published for the whole, so a reader gets the same bytes as before and a damaged download is refused rather than used. Nothing changes in what any tool answers.
Fixed The site is deployable again. Cloudflare Workers refuses any single asset over 25 MiB, and the build was shipping two: the 49.5 MB upstream time-zone source archive, which the asset registry marks as kept for provenance rather than serving but which the copy step took along anyway, and the 26.9 MB boundary index derived from it. The deploy aborted on the first file it met, so geoprims.com had been serving a build from before 12 October while every other gate stayed green. The archive is no longer served, which drops the build by 49.5 MB, and a new check fails the build rather than the deploy if an oversized asset appears. The boundary index itself is still over the limit and still needs sharding, so it is recorded as the one known exception.
Added New Zealand's national grid, both ways. NZTM2000 draws the whole country in one transverse Mercator zone, and every New Zealand map, title, and council dataset is in it. The pair converts between it and latitude and longitude, and returns the grid convergence and the point scale factor beside the coordinates, which is what turns a true bearing into a grid bearing and a ground distance into a grid distance. One zone over 1,600 km means the scale factor reaches 1.2 m per kilometre at the ends, so it is an answer rather than a footnote. Both are experimental.
Tools: Latitude and longitude to NZTM2000, NZTM2000 to latitude and longitude
Result change The Irish Transverse Mercator tools reported a grid convergence 57.3 times too large, and projected on the wrong ellipsoid. The series returns the convergence in degrees and the tools converted it to degrees again, so a reader near Dublin was told 79.98 degrees where the answer is 1.40. Separately, the lookup for GRS 80 searched the ellipsoid table for an upper-case name it does not use and silently fell back to the table's first entry, WGS 84; that moved the coordinates by about a micrometre in Ireland, inside the millimetre the vectors allowed. Both are fixed. No golden vector moved, because none of them had pinned either the convergence or the coordinates tightly enough to notice; five vectors per tool now do, from GeographicLib, along with the point scale factor.
Tools: Latitude and longitude to Irish Transverse Mercator, Irish Transverse Mercator to latitude and longitude
Fixed The worked example on the Irish Transverse Mercator pages named a point 1.1 m from where it said it was. Both pages give the Spire of Dublin as their example; the easting and northing printed with it, and used as the inverse tool's example input, were wrong in their last digits, so the inverse tool's example answered with a place 1.1 m from the Spire while claiming to answer with the Spire. The numbers are now the ones the tools actually produce. A new gate checks the class: where a forward tool and its inverse give their example the same title, carrying one through the other must land back on the same point.
Tools: Latitude and longitude to Irish Transverse Mercator, Irish Transverse Mercator to latitude and longitude
Changed The legacy datum tool now knows New Zealand's. NZGD49 was the datum behind New Zealand mapping until 2000, and a position read from an older map or plan as if it were WGS 84 is about 200 metres out. The tool converts either way by the seven-parameter transformation EPSG publishes, states its four-metre accuracy like the others, and points at the grid that does better where centimetres matter.
Added A new tool carries a position between the global frames a satellite works in and ETRS89, which every European national grid is built on. The two drift apart, because ETRS89 is pinned to the European plate as it sat in 1989 and the plate has been moving since: measured at Dublin, a position is 0.48 m from ETRS89 at epoch 2010 and 0.84 m at 2026, running south-west. That is why the tool asks when the coordinates were measured rather than assuming today, and why the Irish and Swiss grid tools say a satellite position is a step away from the grid they are defined on: this is that step.
Tools: ITRF or WGS 84 to ETRS89
Added A new tool moves an Australian position between GDA94 and GDA2020, the datums behind MGA94 and MGA2020 coordinates. The two differ by about a car's length: the plate carried the country between 1.49 metres in the south-east and 1.80 in the north, always to the north-east, so a GDA94 coordinate read as GDA2020 is wrong by that much. The tool applies the conformal transformation ICSM publishes, and says plainly what that leaves out: the distortion in GDA94's own network, up to about a tenth of a metre in places, which ICSM's second grid carries and which matters for cadastral work. Outside the area the transformation is published for, the answer still comes, flagged as extrapolation.
Tools: GDA94 and GDA2020
Added Two tools convert the Swiss national grid, LV95 and the older LV03, either way. The Swiss grid is not a transverse Mercator: it is an oblique one, laid so that the cylinder touches the ellipsoid along a line through Bern rather than along a meridian, which is what keeps distortion small across a country wider east to west than north to south. These follow swisstopo's own rigorous formulas, not the approximate ones their document warns against for cadastral work, and reproduce their worked example for the station Rigi to the centimetre they print. The forward tool gives the LV03 coordinates beside the LV95 ones; the reverse tool recognises a six-figure LV03 easting and says it shifted it.
Tools: Latitude and longitude to Swiss LV95, Swiss LV95 to latitude and longitude
Added Two tools convert Irish Transverse Mercator, the grid Ireland and Northern Ireland have used since 2001, either way: a latitude and longitude into easting and northing, or those back into a latitude and longitude, with the grid convergence and the point scale factor beside them, which is what turns a true bearing into a grid bearing and a ground distance into a grid distance. The results say which frame they are on: ITM is defined on ETRS89, fixed to the European plate, and a satellite position is about half a metre away from that today and drifting. These are not Irish Grid coordinates, which are a different projection on a different datum.
Tools: Latitude and longitude to Irish Transverse Mercator, Irish Transverse Mercator to latitude and longitude
Added Two tools read and write British National Grid references. One turns a latitude and longitude into the reference a British map, a rights-of-way notice, or a rescue report is written in, at the precision you ask for: two figures for a 10 km square, six for 100 m, ten for a metre. The other reads a reference like TQ 30 80 and gives back the square it actually names, with its corner, its size, its edges for the map, and the latitude and longitude of its middle. Coordinates on WGS 84 go through Ordnance Survey's published seven-parameter transformation, which they state as about two metres, and the result says so rather than implying that a ten-figure reference is good to a metre.
Tools: Latitude and longitude to a British National Grid reference, British National Grid reference to latitude and longitude
Changed The six hydrology tools now hand their work along. Every flow tool tells you to condition the grid first, and the fill tool's answer is exactly what they want, so its page now offers to carry the conditioned grid straight into the flow tools, with the cell size and the no-data value. The tools also point at each other in the order you would use them: fill, flow direction, accumulation, streams, watershed, longest path. A test routes water over a conditioned grid and over the grid as entered, and shows the difference: no cell left stranded in the first, a pit swallowing the bowl in the second.
Tools: Fill or breach the pits in a DEM, Flow direction over a DEM, Flow accumulation over a DEM, Stream network and Strahler order, Watershed above a pour point, Longest flow path to a point
Changed The stream and watershed tools now draw what they found, over the grid you entered and to scale. The stream page draws every link through the cells it runs, thicker as its Strahler order rises, so the main stem reads at a glance and the headwaters read as headwaters, with a dot where the network leaves the window. The watershed page shades the cells that drain to your point and draws the longest flow path down them, from its top to the outlet. Both drawings are your own numbers, not an illustration of the idea.
Tools: Stream network and Strahler order, Watershed above a pour point
Added The sixth and last hydrology tool measures the longest way water travels to a point: the hydraulic length that a time-of-concentration formula asks for. Give an elevation grid and a cell, and it returns the distance, the height the water falls over it, the average slope along it, and the path itself cell by cell, with the elevation at each. Add the grid's north-west corner and the path comes back placed in latitude and longitude, ready to draw. Diagonal steps count as root two cells, which is why a path down a diagonal valley reads longer than the straight distance across the map.
Tools: Longest flow path to a point
Added A fifth hydrology tool answers what drains to a point. Give an elevation grid and a cell, and it returns every cell whose water reaches it: the basin as a grid you can draw, its area, how much higher its highest ground is than the outlet, its mean slope, and the longest path water takes to get there, with the drop along it. It moves your point onto the channel first, either to the nearest channel cell or to the cell with the most water nearby, and says whether it moved and how far, because a point one cell off the channel maps a hillside instead of a basin. When the basin runs into the edge of your data the result says so, since the real basin may continue past it.
Tools: Watershed above a pour point
2026-11-06
Added A fourth hydrology tool pulls the channels out of an elevation grid. You set what counts as a channel, as the number of cells or the area of ground that must drain through one, and the tool returns the network split into links: the stretch from one junction to the next, with its Strahler order, its length, how many cells it runs through, and the ground draining through its lower end. Order follows Strahler's own rule, where two streams of the same order make the next order up and a smaller tributary leaves the order alone, so the main stem is the highest number on the page. Give the grid's north-west corner and every link carries latitudes and longitudes, ready to draw. Set the threshold too high and the answer is an empty network with the most that drains through any cell, so you know what to ask for instead.
Added A third hydrology tool says how much ground drains through each cell of an elevation grid. The count is the cell itself plus everything upslope of it, and the area is that count times one cell, which is how a channel shows itself: it is where the accumulation passes a threshold. D8 sends each cell's water whole to one neighbour, which is what a watershed needs; D-infinity splits it between the two neighbours the slope angle falls between, which is smoother on open hillside. Near the window's edge a value counts only what drains in from inside the grid, so it is a lower bound, and the result says so. A pit keeps whatever reaches it, so fill or breach the grid first; the tool counts the pits it found and warns.
Tools: Flow accumulation over a DEM
Added A second hydrology tool says which way water leaves every cell of an elevation grid. D8 sends each cell's water to whichever of its eight neighbours lies steepest downhill, which is what a watershed or a stream network needs, because it makes the grid something you can walk cell to cell. D-infinity gives the angle instead, which is truer on a hillslope where the water spreads between two neighbours. The pointer grid comes in whichever of the three tables your software reads: the powers of two that ArcGIS uses, the WhiteboxTools table, or TauDEM's 1 to 8. Cells with no lower neighbour get a zero, and the result counts them apart from the ones that simply drain out of the window, with a warning to condition the grid first.
Tools: Flow direction over a DEM
Added A new tool conditions a DEM so water can leave every cell, which every flow calculation assumes and no measured elevation grid gives you: noise, bridges, culverts, and road embankments leave hollows that trap water. Enter the grid and its cell size and it either fills each hollow to the height it would spill at, by the Priority-Flood method, or cuts a channel out of it, which moves far less earth where a road or a dam is what dammed the water. It reports every cell it moved, before and after, and the earth that represents, so you can judge whether the conditioning changed the ground more than you want. Cells marked no data are never raised, never cut, and never crossed, and the window's edge is treated as an outlet, so clip wider than the basin you care about.
Fixed The three-dimensional Helmert fit now refuses systems that are turned too far for it, instead of answering anyway. It fits the small-rotation model geodetic datum transformations use, which is good to about a degree; past that the approximation is worth more than 150 parts per million. Fed a published example whose two systems differ by rotations of 130, 86, and 190 degrees, it used to settle on rotations of tens of degrees, a negative scale, and residuals of metres, with only the scale warning to hint that anything was wrong. It now says plainly that the fit wants a rotation past the one degree the model holds to, and suggests bringing the axes together first. Nothing changes for the small rotations the tool is for: no published vector moved.
Added A new tool works out under-keel clearance. You give the charted depth, the tide you expect at the hour you pass, your static draft, and the margin you or the port require, and it writes the stack out: the water over the datum, what the ship draws once squat is added, what is left under the keel, and what is left after the margin, in meters and feet, with a drawing of the stack to scale. Squat is estimated by Barrass's formula for the speed you intend, in open water, a confined channel, or from a blockage factor you work out, and the tool refuses outside the block coefficients and depth-to-draft ratios that formula is published for rather than extrapolating. You can give a squat figure of your own instead. The result never calls a clearance safe: it reports the numbers, and says that the master and the port authority decide. The tool is experimental, because the one published worked example found for Barrass's formula does not follow its own printed equations.
Changed The celestial almanac is now stable, and it ships ten more golden vectors. The ten added instants come from the same US Naval Observatory celestial-navigation data as the first ten, from the half of that record the vector generator had been skipping, so the published numbers the tool is held to now span twenty instants between 1995 and 2045 rather than ten. Nothing it computes changed, and none of the first fourteen vectors moved. The Nautical Almanac remains the governing publication, as the tool's own page says.
Changed Eight marine and celestial tools are now stable: sextant altitude corrections, sight reduction, set and drift, plane sailing, tide datum conversion, tide prediction, the moon's position, and moonrise and moonset. Nothing they compute changed. Each was already checked against a published source rather than against itself: Bowditch's own worked examples for the sights, the sailings, and the current triangle, NOAA's published tide predictions and station datums for the tides, and the US Naval Observatory's computed data for the moon. What the stable mark adds is that the build now holds them to the whole bar on each commit. Their pages no longer carry the experimental warning. The navigation MCP toolset grows to 37 tools, still under its cap.
Tools: Sextant altitude corrections, step by step, Sight reduction by the intercept method, Current triangle (set and drift), Plane sailing, Tidal datum conversion, Tide prediction from harmonic constituents, Moon position, Moonrise, moonset, and transit
Changed Thirteen tools are now marked stable rather than experimental: cabin altitude, approach category, circling radius, RVR to visibility, fuel density with temperature, climb requirement, hydroplaning speed, supplemental oxygen, time of useful consciousness, parallax height, photo scale, relief displacement, and sidereal time. Nothing they compute changed. Stable means each one now carries what the verification bar asks for: a derivation note with its equations and domain, a worked example taken from a published source rather than from our own arithmetic, an invariants test, at least twenty golden vectors, and a page that says when to reach for the tool and where its answer stops. The pages drop the experimental warning, and the tools join their MCP toolsets, so an agent can call them by name.
Tools: Cabin altitude from pressure differential, Aircraft approach category, Circling approach radius, RVR to ground visibility, Fuel density at a temperature, Climb requirement check, Tire hydroplaning speed, Supplemental oxygen requirement, Time of useful consciousness, Height from stereo parallax, Photo scale and flying height, Relief displacement and object height, Sidereal time
2026-10-28
Changed The three-dimensional Helmert fit now draws its residuals and reports them as numbers. Residuals in three dimensions have no one plane to live in, so the points are drawn in plan with each horizontal residual as an arrow and each vertical residual as a bar beside it, both at an exaggeration the caption states, because the residuals are millimetres against hundreds of metres. What it is for is telling scatter, which is noise, from a pattern, which means something the seven parameters do not model. Each residual row also carries its X, Y, and Z components as numbers now, beside the printed line, so a machine reader does not have to parse that line. The partition, Helmert-fit, and levelling-network tools also gained an independent check: the same mathematics solved again in numpy, which agrees to double precision on the levelling network, to a nanometre on the fit's translations, and to two parts per billion of the parcel on the partition.
Changed Two drawings and two explainers for the celestial and moon tools. The sextant altitude corrections now draw as the work form a navigator writes down the margin: the altitude read off the arc at the top, each correction stepping it left or right by its own size to scale, and the observed altitude at the bottom. Moonrise and moonset now draw a sky plot with the moon's path and the sun's behind it, north up and the horizon at the rim, with rise and set marked where the moon crosses it; the tool returns both paths for the day to make that possible. Two new explainers: how a sextant sight becomes a line of position, and how much light the moon will give you, which covers why a half moon is far dimmer than half as bright and why a calendar date can hold two moonrises or none.
Tools: Sextant altitude corrections, step by step, Moonrise, moonset, and transit
Added Two new experimental tools, an astro group in Survey: the azimuth of a survey line from a timed observation of Polaris or of the sun, by the hour-angle method of Coast and Geodetic Survey Special Publication 237. Enter the station, then each pointing's instant in UTC and the horizontal angle from the reference mark to the body, and the limb you sighted if it was the sun. Each pointing's azimuth comes back with the mean of the set, the scatter, and a flag on any pointing that sits more than three times the others' scatter away from them, with the mean recomputed without it. A pointing on a limb is carried to the centre by the semidiameter over the cosine of the altitude. The result says plainly that the azimuth is astronomic, referred to the local vertical, and reports the geodetic azimuth beside it when you supply the Laplace correction for the station. The body's place is the same series the celestial almanac publishes, and its azimuth agrees with the US Naval Observatory within 0.0002 degrees at 54 places and instants from 1995 to 2045.
Tools: Astronomic azimuth from a Polaris observation, Astronomic azimuth from a solar observation
Added Three new experimental tools, a moon group in Time. Moonrise, moonset, and the moon's highest point for a place and local date, by the US Naval Observatory's own definition of the upper limb on the horizon, in local time and Zulu, with the dates the moon's daily retardation leaves without a rise or without a set named along with the times either side, and the polar days it never rises or sets at all. Where the moon is in the sky at an instant, as seen from the ground rather than from the centre of the Earth, with its distance, parallax, and apparent size. And how much of the disc is lit, how old the moon is, and when the next new moon, first quarter, full moon, and last quarter fall. Checked against USNO at 1,361 rise, set, and transit times over 500 places and dates and at all 208 of its published phase instants, every one within a minute.
Tools: Moon position, Moonrise, moonset, and transit, Moon phase and illumination
2026-10-27
Added New, both experimental: latitude by Polaris, and a compass check by the Sun. The first turns one corrected altitude of Polaris into a latitude, and it solves the navigational triangle for Polaris's own place at the second of the sight rather than reading the Almanac's a0, a1, and a2 tables, so it holds at any latitude and will not drift as Polaris moves. It reports the correction it applied, which is the same quantity those three tables add up to, and Polaris's true azimuth for the line of position. The second gives the Sun's true azimuth at a time and place, its amplitude for an observation taken as the Sun's centre crosses the celestial horizon, and the error of the compass against a bearing you read, split into variation and deviation for a magnetic compass. Bowditch's own worked Polaris sight, its two gyro errors by Pub. No. 229, and its worked amplitude are all reproduced, and both tools are checked against the US Naval Observatory's own data at 60 instants and places from 1995 to 2045. The Nautical Almanac still governs.
Added New, both experimental: sextant altitude corrections and sight reduction. The first turns the altitude you read off the arc into the observed altitude, showing the index correction, the dip of the horizon, refraction for the air you measured, the semidiameter of the limb you touched, and parallax, one line at a time. The second reduces that sight to a line of position by the intercept method: the body's hour angle and declination for the second of the sight, the computed altitude and true azimuth at your assumed position with the quadrant rule stated, and how far to shift the line toward or away from the body, with the line itself drawn on the chart. The Pub. No. 229 assumed-position rule is one click away. Every worked example in Bowditch chapter 16 and three columns of its chapter 20 four-star fix are reproduced, and both tools are checked against the US Naval Observatory's own data at 148 body-instants from 1995 to 2045. The Nautical Almanac still governs.
Tools: Sextant altitude corrections, step by step, Sight reduction by the intercept method
2026-10-20
Changed RVR to visibility can also use the approach chart legend's longer table, which takes the next higher listed RVR between rows; rows the regulation does not list carry a caution that they are not takeoff or landing minima. Each result now names the row it used. Results in the default regulation mode are unchanged.
Tools: RVR to ground visibility
Changed The circling approach radius also shows the radius the Terminal Procedures legend prints for the circling MDA band, beside the computed one. The legend's table is the formula at each band's lowest MDA, cut down to a tenth. Results are unchanged.
Tools: Circling approach radius
Changed Fuel weight takes an optional fuel temperature with an entered density and names it in the result, so a density corrected by the new fuel density tool carries its temperature. Results are unchanged.
Tools: Fuel weight
2026-10-19
Result change The RTK accuracy calculator's 95% horizontal factor is now the NSSDA's 2.4477 (√χ²₂,0.95, FGDC-STD-007.3-1998) instead of a rounded 2.448, matching the ALTA RPP tool. 95% horizontal results drop by about 0.01% (for example 44.064 mm to 44.059 mm); one-sigma and vertical results are unchanged. The tool is now version 1.2.0 and declares both 95% factors.
Tools: RTK and PPK precision budget
Replaced vectors: survey.gnss.rtk-budget v002, survey.gnss.rtk-budget v004, survey.gnss.rtk-budget v018
Changed The ENU and NED frame converter and the ECEF-to-local rotation matrix are now stable, held to MathWorks' published ecef2enu and ecef2ned examples, with four new vectors and a new invariant test. Results are unchanged.
Tools: ENU and NED frame converter, ECEF to local frame rotation matrix
Changed Station and offset from a line, with its two focused views (perpendicular foot and point from station and offset), is now stable. All three are held to the Autodesk Civil 3D station-and-offset example, with 16 new vectors and a new invariant test. Results are unchanged.
Tools: Station and offset from a line, Perpendicular foot and station, Point from station and offset
2026-10-14
Changed ASPRS checkpoint requirements is now stable, held to the ASPRS Edition 2 Annex C example and a new invariant test across Table C.1's areas and vegetated shares. Results are unchanged.
Fixed Survey tools that read a bearing or azimuth now accept a degree unit written out, like 123.456 deg or 90 degrees. Before, the G at the end of deg was taken for the gon suffix, and the direction was refused as an unreadable number of gons. Directions that were already accepted give the same results.
Tools: Azimuth and bearing converter, Coordinates from a bearing and distance
Changed The focused S2 operations (cell area, hierarchy, token, and vertices), held to s2sphere, and the XYZ-TMS and quadkey tile conversions, held to the slippy-map and quadkey definitions, are now stable, with a new invariants test for areas, parents, corners, and round trips. Results are unchanged.
Tools: S2 cell area, S2 cell hierarchy, S2 token and cell id, S2 cell vertices, XYZ and TMS tile numbering, Map tile to quadkey and back
Changed Ten focused geodesy operations are now stable: degree lengths and meridian arcs (held to GeographicLib), the MGRS grid-zone lookup and reference precision (NGA's GeoTrans), both directions of the height conversion (GeographicLib's GeoidEval), the WMM and IGRF comparison and the compass reliability zone (pygeomag and ppigrf), and UTM convergence and scale factor (GeographicLib's exact transverse Mercator). A new invariants test checks each note's stated properties. Results are unchanged.
Tools: Length of a degree of latitude and longitude, Meridian arc length, Grid zone and 100 km square in MGRS, Precision of an MGRS reference, Ellipsoidal height to orthometric height, Orthometric height to ellipsoidal height, Compare WMM and IGRF declination, Compass reliability zone, Grid convergence in UTM, Point scale factor in UTM
Changed The fourteen focused H3 operations, from cell-to-latlng through edge-length, are now stable. Each is held to H3 C 4.5.0 through h3-py on 20 or more cases, and a new invariants test checks them together on hexagons and pentagons at five resolutions: centers, edges, vertexes, children, classes, distances, and areas. Results are unchanged.
Tools: H3 base cell, H3 cell area, H3 cell boundary, H3 cell to latitude and longitude, H3 center child, H3 child position, H3 directed edges, H3 edge length, H3 grid distance, H3 resolution class check, Is this H3 cell a pentagon?, H3 cell resolution, Validate an H3 index, H3 vertexes
Changed The elevation factor, grid-to-ground, and ground-to-grid conversions, each reproducing NGS Manual 5's Section 4.4 example, and mission pattern statistics, held to GeographicLib's GeodSolve, are now stable. Each has 23 vectors and named invariant tests. Results are unchanged.
Tools: Elevation factor, Grid distance to ground distance, Ground distance to grid distance, Flight path statistics
Changed DEM statistics, the highest point of a DEM grid, and the volume change between two DEM grids are now stable. Each is held to NumPy on 24 grids or survey pairs (the statistics also to gdalinfo -stats) and to invariant tests for shifting, swapping, and gapping the grids. Results are unchanged.
Tools: Elevation statistics for a DEM grid, Highest point in a DEM grid, Volume change between two DEM grids
Changed Slope, aspect, hillshade, the terrain ruggedness index, and the topographic position index, each as its own tool, are now stable. Each matches gdaldem 3.13.3 on 24 windows (hillshade exactly; the rest within gdaldem's 32-bit rounding) and its parent tool on 208 fixture windows, with invariant tests for turning, raising, and inverting the ground. Results are unchanged.
Tools: DEM slope by Horn's method, DEM aspect, the way the ground faces, Hillshade value for one DEM cell, Terrain ruggedness index (TRI), Topographic position index (TPI)
Result change Slope, aspect, and hillshade (version 1.1.0) now scales hillshade the way gdaldem does: 1 plus 254 times the cosine of the angle to the sun, and 1 where the ground faces away. The old result used 255 times the cosine and ran up to one gray level low. Hillshade now matches gdaldem exactly on all 1,452 test windows; slope and aspect are unchanged.
Tools: Slope, aspect, and hillshade
Replaced vectors: raster.terrain.slope-aspect v001, raster.terrain.slope-aspect v002, raster.terrain.slope-aspect v004, raster.terrain.slope-aspect v006, raster.terrain.slope-aspect v007
2026-10-13
Added EDM atmospheric and prism correction (version 1.1.0, experimental) now includes named Trimble Access formulas for the 5600, 3300/3600, and TTS300/500 instrument families. Each preset uses the guide's published J and N constants, and mixed direct-ppm, custom-IAG, and preset inputs are refused instead of silently ignored. The vector set grows from 9 to 25 without changing existing vectors.
Changed Curvature and refraction correction (version 1.1.0) is now stable. It reproduces the U.S. Geological Survey's published 500 ft correction table, and 25 vectors plus five invariant tests cover quadratic distance scaling, separated components, refraction coefficients, Earth radii, units, and invalid inputs. Valid calculation results are unchanged; nonfinite distances and radii are now refused explicitly.
Changed Angular closure (version 1.1.0) is now stable. It reproduces Walla Walla University's published seven-angle traverse and equal corrections, and 25 vectors plus five invariant tests cover geometric sums, both angle conventions, DMS input, allowable boundaries, equal bias, and invalid rows. Valid calculation results are unchanged; the exterior option is now explicitly labeled as reflex exterior.
Fixed The RTK and PPK precision budget (version 1.1.0) is now stable. It reproduces Tersus's published 40 km example at 48 mm horizontal and 55 mm vertical, and 25 vectors plus five invariant tests cover ppm scaling, confidence factors, units, targets, boundaries, and invalid inputs. Valid calculation results are unchanged; negative vertical constants and targets are now refused, and incomplete or invalid terms identify the field that needs correction.
Tools: RTK and PPK precision budget
Result change OPUS session planning (version 1.1.0) is now stable and fixes partial-day RINEX 2 names. The old result used `0`, which NGS reserves for a 24-hour data set; partial sessions now require the UTC start hour and use `a` through `x`. The tool reproduces NGS's published `g287009q.23o` example, and 25 live vectors plus five invariant tests cover processing boundaries, calendars, units, hour codes, and incomplete inputs.
Tools: OPUS session planning
Replaced vectors: survey.gnss.opus-plan v001, survey.gnss.opus-plan v002, survey.gnss.opus-plan v003
Fixed GNSS slant antenna height (version 1.1.0) is now stable. It reproduces both worked examples in the iGage iG9 manual, and 26 vectors plus five invariant tests cover the right-triangle identity, signed offsets, metric and US units, boundaries, and invalid inputs. Valid calculation results are unchanged; invalid radii and offsets now identify their own fields instead of the slant field.
Changed Mission VLOS checking (version 1.1.0) is now stable. Its 25 GeographicLib-backed vectors plus two invariant tests cover entered and EASA-derived ranges, list consistency, exact range boundaries, metric and US units, polar and antimeridian routes, visibility limits, and invalid inputs. Calculation results are unchanged.
Fixed Return-to-home energy (version 1.1.0) is now stable. It reproduces the FAA's published 134.4 mph minus 30 mph headwind example, and 25 vectors plus five invariant tests cover groundspeed, time, energy, margin, round-trip reach, units, wind boundaries, invalid inputs, and insufficient energy. Valid calculation results are unchanged; negative reserve energy is now refused instead of increasing the available flight energy.
Tools: Return-to-home energy budget
Fixed Maximum payload (version 1.1.0) is now stable. It inverts Van Mulders et al.'s measured payload-hover fit to recover a 50 g load, and 25 vectors plus five invariant tests cover the inverse power model, units, energy and time scaling, atmosphere and loss inputs, boundaries, invalid inputs, and infeasible targets. Valid calculation results are unchanged; negative avionics power is now refused instead of inflating the payload budget.
Changed Payload impact (version 1.1.0) is now stable. It reproduces the mass-to-power fit from Van Mulders et al.'s measured payload-hover tests, and 25 vectors plus four invariant tests cover payload mass and electrical draw, energy and unit scaling, atmosphere and loss inputs, domain boundaries, and invalid loads. Calculation results are unchanged.
Changed Test-flight hover calibration (version 1.1.0) is now stable. It reverses Embry-Riddle's published 45,000 lb tiltrotor example, and 25 vectors plus four invariant tests cover energy and time units, aircraft sizes, atmosphere inputs, avionics draw, efficiency, domain boundaries, and invalid measurements. Calculation results are unchanged.
Changed Thermal pixel footprint (version 1.1.0) is now stable. It reproduces FLIR's published E8 example at 10 ft, and 26 vectors plus four invariant tests cover direct IFOV, pixel pitch and focal length, unit conversions, pixel rules, inverse target distance, domain boundaries, and invalid camera inputs. Calculation results are unchanged.
Tools: Thermal pixel footprint
Result change Promoting site localization to stable removed the EXPERIMENTAL_TOOL warning, so NO_REDUNDANCY and SCALE_SUSPECT moved from warning index 1 to index 0. Calculation results are unchanged. v002, v004, and v005 are superseded by v025, v026, and v027, which match each warning by code instead of list position.
Tools: Site localization (calibration)
Replaced vectors: survey.gnss.localization v002, survey.gnss.localization v004, survey.gnss.localization v005
Fixed Site localization (version 1.1.0) is now stable. It recovers IOGP Guidance Note 7-2 method 9621's published scale and rotation, and 24 live vectors plus three invariant tests cover similarity, genuine affine fits, residuals, mixed units, invalid geometry, and the documented rotation sign. Compact control networks are no longer incorrectly rejected merely because their coordinate origin is large; previously accepted calculation results are unchanged within tolerance.
Changed Unequal-tangent vertical curve (version 1.1.0) is now stable. It reproduces Pearson's published problem 25.15 stations and elevations, and 20 vectors plus equal-curve, join-continuity, and published-example invariants cover crest, sag, monotone, straight, endpoint-turning, and tangent-extension cases. A nonpositive second tangent now points to length2 instead of length1; valid-input calculation results are unchanged.
Changed Vertical curve length for sight distance (version 1.1.0) is now stable. Its crest calculation reproduces FHWA-HRT-04-103 table 20's published 49.8 m result within 0.2 m from the rounded source inputs, and 28 vectors plus scale, symmetry, domain, and zero-height-object invariants cover both crest and headlight-sag cases. Invalid eye, headlight, and beam-angle inputs are now refused; valid-input calculation results are unchanged.
Changed Side slope and grade (version 1.0.0) is now stable. It reproduces FHWA's published 20 m over 400 m roadway example, and 23 vectors plus representation and 3-4-5 triangle invariants cover every notation, both ratio conventions, descending grades, length reconstruction, and refusal cases. Nonpositive distances are now refused; valid-input calculation results are unchanged.
Tools: Side slope and grade (H:V)
Changed Multirotor hover power (version 1.1.0) is now stable. Its ideal and figure-of-merit-adjusted power reproduce the 2026 Embry-Riddle aerospace textbook's 45,000 lb tiltrotor example within 0.03%; 20 vectors and new scaling invariants cover density, losses, avionics draw, rotor scale, and coaxial inputs. Calculation results are unchanged.
Tools: Multirotor hover power
Changed Mission sorties and battery swaps (version 1.1.0) is now stable. Sixteen new vectors extend coverage to 22 cases across reserves, energy and flight-time inputs, wind, separate transit speeds, unit conversions, route sizes, and an unreachable waypoint. Calculation results are unchanged.
Changed GPS satellite visibility and DOP (version 1.1.0) is now stable. A new vector reproduces Orekit 13.1.9's YUMA-almanac comparison with Trimble Planning: 11 satellites and GDOP 1.53, PDOP 1.35, HDOP 0.84, and VDOP 1.06 within the source's 0.01 tolerance. Calculation results are unchanged.
Changed Terrain curvature (version 1.1.0) is now stable. Its primary example reproduces xDEM 0.2.3's published Zevenbergen-Thorne directional profile curvature of -100 per 100 m and zero tangential curvature, and it now has 24 vectors plus rotation, decomposition, tilt, scaling, and flat-cell invariants. Calculation results are unchanged.
Tools: Terrain curvature
Changed Line of sight over a ground profile (version 1.1.0) is now stable. Two new vectors reproduce the hidden-to-visible boundary in the published GRASS GIS 8.5.0 r.viewshed fixture, alongside 22 spherical-geometry vectors and five invariant tests. Calculation results are unchanged.
Changed Slope distance to horizontal and vertical (version 1.1.0) is now stable. Its primary example matches the U.S. Geological Survey's published 127.531-foot trigonometric-leveling reduction to a -0.145-foot mark-to-mark vertical difference, and it now has 20 vectors plus component, scaling, angle, two-face, height, and correction-threshold invariants. Calculation results are unchanged.
Changed Heading to intercept a radial (version 1.1.0) is now stable. Its primary example matches the FAA Instrument Flying Handbook's published 160-to-205 radial intercept on heading 295 degrees, and it now has 20 vectors plus rotation, bound, mirror, override, and on-course invariants. Calculation results are unchanged.
Changed DME arc lead points (version 1.1.0) is now stable. Its primary example matches the Naval Air Training Command's published 12 DME, 180-knot result, and it now has 20 vectors plus scaling, override, equivalent-unit, and tangent-circle invariants. Nonpositive groundspeed now identifies the groundspeed field; calculation results are unchanged.
Tools: DME arc lead points
Changed Performance table lookup (version 1.1.0) is now stable. Its primary example matches the FAA Pilot's Handbook's published interpolation at 2,500 ft pressure altitude, and it now has 20 vectors plus affine-grid, weight-sum, translation, refusal, and correction-order invariants. Calculation results are unchanged.
Tools: Performance table lookup
Changed Holding wind correction and timing (version 1.1.0) is now stable. Its primary example matches the current FAA AIM's 8-degree-left inbound and 24-degree-right outbound relationship, and it now has 20 vectors plus rotation, scaling, timing, equivalent-unit, and turn-direction invariants. Negative wind speed now identifies the wind-speed field; calculation results are unchanged.
Changed Time and distance to a station (version 1.1.0) is now stable. Its primary example matches the FAA Pilot's Handbook's published 75-second, 10-degree, 120-knot result, and it now has 20 vectors plus equation, scaling, equivalent-unit, and optional-output invariants. Its accuracy note now bounds the rule's overstatement to the recommended 5- to 20-degree range; calculation results are unchanged.
Changed DME slant range (version 1.1.0) is now stable. Its primary example matches FAA Order 8260.3G's published 5 NM at 13,000 ft result, and it now has 22 vectors plus right-triangle, scaling, equivalent-unit, and zero-height invariants. Negative heights now identify the height field; calculation results are unchanged.
Changed True altitude (version 1.1.0) is now stable. Its primary example matches the FAA Safety Briefing's sea-level, -30 °C example at the source table's precision. The tool now has 20 vectors plus identity, sign, symmetry, equivalent-unit, and standard-temperature invariants; calculation results are unchanged.
Tools: True altitude
Changed Cold-temperature altitude correction (version 1.1.0) is now stable. Its primary example reproduces the FAA AIM's approximate 1,314-foot, -12 °C table example at the source's precision. The tool now has 20 vectors plus row-consistency, equivalent-unit, and no-correction invariants; calculation results are unchanged.
Changed The true-course-to-compass-heading chain (version 1.1.0) is now stable. Its primary example reproduces every heading in the FAA Pilot's Handbook's Chickasha-to-Guthrie flight log. The tool now has 20 vectors plus wrap, sign, empty-card, and cross-north interpolation invariants; calculation results are unchanged.
Changed Specific range (version 1.1.0) is now stable. Its primary example derives exact range and fuel-per-distance values from the FAA Pilot's Handbook's published 400 NM, 100-knot, 5-gal/h trip, and it now has 20 vectors plus scaling, separation, and equivalent-unit invariants; calculation results are unchanged.
Tools: Specific range
Changed Turn performance (version 1.1.0) is now stable. Its primary example reproduces the FAA Pilot's Handbook's printed 120-knot, 30-degree-bank turn rate. The tool now has 20 vectors across direct, inverse, stall-speed, load-limit, and invalid-input cases; calculation results are unchanged.
Changed Pivotal altitude (version 1.1.0) is now stable. Its primary example reproduces the FAA Airplane Flying Handbook's printed 100-knot, 885-foot row. The tool now has 20 vectors plus quadratic-scaling, equivalent-unit, and rule-error invariants; calculation results are unchanged.
Tools: Pivotal altitude
Changed Climb gradient (version 1.1.0) is now stable. Its primary example reproduces the FAA Instrument Procedures Handbook's printed 2.8-degree, 180-knot, 892-fpm example. The tool now has 20 vectors plus scaling, inverse, and equivalent-unit invariants; calculation results are unchanged.
Changed Fuel weight (version 1.1.0) is now stable. Two vectors reproduce the FAA Pilot's Handbook's printed 40-gallon/240-pound and 75-gallon/450-pound avgas rows. The tool now has 20 vectors plus scaling, inverse, unit, and density-override invariants; calculation results are unchanged.
Tools: Fuel weight
Changed Off-course correction (version 1.1.0) is now stable. Its primary example reproduces the UK Ministry of Defence AP3456 worked result that 2 NM off after 30 NM is a 4-degree track error by the 1-in-60 rule. The tool now has 20 vectors plus scale, symmetry, zero-offset, and unit invariants; calculation results are unchanged.
Changed Fuel burn rate (version 1.1.0) is now stable. The primary example reverses the FAA Pilot's Handbook's 4-hour, 20-gallon, 5-gallon-per-hour calculation, and three more vectors reproduce exact rows from the FAA Middle Aviation Curriculum Guide. The tool now has 20 vectors plus scaling and unit invariants; calculation results are unchanged.
Tools: Fuel burn rate
Changed Oblique GSD and footprint (version 1.2.0) is now stable. Its near, center, and far GSD values are checked against Andrew Lassiter's independent oblique-photo simulation at a pinned source revision, with 20 vectors and new scaling, ordering, and nadir invariants. The independent Canon example is now the default; calculation results are unchanged.
Tools: Oblique GSD and footprint
Changed Wind limit at flying height (version 1.1.0) is now stable. Its NREL power-law model and NYSERDA worked example are covered by 22 golden vectors across every terrain class, both rating paths, height and unit boundaries, and both warning branches. Calculation results are unchanged.
Tools: Wind limit at flying height
Changed Motion blur (version 1.1.0) is now stable. Its formula and primary example are checked against Han and Han (2024), and its default 0.5 px limit is sourced to Grenzdörffer, Niemeyer, and Schmidt (2012). Calculation results are unchanged.
2026-10-12
Added Orbit planning (version 1.1.0) now accepts a maximum angular step instead of a photo count. It rounds up to enough waypoints to close the circle with equal gaps no larger than requested, and reports the photo count and actual angular step. Existing calls and waypoint positions are unchanged.
Changed Tool pages now load diagram and map export code only when a download is requested. Maps draw their useful Canvas2D view first, then load the optional WebGPU or WebGL2 compositor after map interaction or the startup window. All 50 sampled routes are back under the 90 KB compressed JavaScript budget; map behavior and export formats are unchanged.
Fixed The animated fly-by diagram now keeps its time and course readout clear of the inbound-leg label at phone width. The route calculation and animation are unchanged.
Tools: Fly-by turn anticipation
Changed The contour tool now accepts a north-up geographic grid from its north-west coordinate and angular cell size. It uses latitude-aware WGS 84 east-west and north-south dimensions, returns latitude and longitude on every contour vertex, and draws separate contour polylines on the map. Existing meter-grid results and contour topology are unchanged.
Added The local MCP server's --allow-asset-download option now works. When a tool needs a registered file that is not installed, the opt-in server downloads it only from the geoprims asset origin, verifies its size and digest or signed tile index, and caches it for offline reuse. The default remains fully offline and names the missing file, its size, and the opt-in flag.
Changed The survey-grid tool now plays the mission at the entered groundspeed. The core returns the playhead, flown path, aircraft position, and the photo triggers and footprints captured so far; the map keeps the remaining plan visible and fills coverage as the aircraft advances. Scrubbed permalinks reopen paused. Planning answers are unchanged.
Changed The route-legs tool now plays the route at the entered groundspeed. The core returns the playhead time, route duration, flown path, and aircraft position; the map shows the remaining plan and the completed route separately, and scrubbed permalinks reopen paused. Distance, course, time, and arrival answers are unchanged.
Changed The sun-position tool now has a 24-hour UTC scene. It opens paused at the entered instant, returns the UTC playhead, subsolar point, and a core-computed day-night boundary, and restores a scrubbed time from its permalink. The globe and map draw that boundary directly from the core samples. Solar-position answers are unchanged.
Result change The maximum holding airspeed tool is now stable, so it no longer carries the experimental warning. Twenty-one live vectors hold its unchanged speed-limit answers to the current FAA AIM bands at and around both altitude boundaries and to the charted-limit override. The six original vectors are superseded because their source locator named obsolete AIM figure and table labels; their replacements cite paragraph 5-3-8j.
Tools: Maximum holding airspeed
Replaced vectors: aviation.ifr.hold-speed-limit v001, aviation.ifr.hold-speed-limit v002, aviation.ifr.hold-speed-limit v003, aviation.ifr.hold-speed-limit v004, aviation.ifr.hold-speed-limit v005, aviation.ifr.hold-speed-limit v006
Result change The US 1976 atmosphere (version 1.0.1) now keeps molecular weight constant below its 86 km upper-atmosphere boundary, as NOAA-S/T 76-1562 specifies, instead of applying a correction from 80.5 to 85.5 km. Temperatures in that band rise by up to 0.068 K. US76 pressure, density, and speed of sound now use its adopted R*/M0 gas constant; pressure and density move by less than 0.001%. All nine printed rows from 82 to 86 km now match Table I within its final printed digits. ICAO results are unchanged.
Tools: Standard atmosphere
Replaced vectors: aviation.atmosphere.isa v011, aviation.atmosphere.isa v012, aviation.atmosphere.isa v013, aviation.atmosphere.isa v014
Added Three experimental A5 0.10.1 tools now index a point into an equal-area pentagonal cell, inspect its center, area, and boundary, and move through its immediate parent and children. Their indexes, hierarchy, areas, centers, and boundary vertices match pinned a5-js 0.10.1 across 120 cases at every resolution.
Tools: A5 cell from latitude and longitude, A5 cell boundary, A5 parent and children
Changed Large H3 fills now choose a visible parent resolution from the map or globe view instead of drawing thousands of sub-pixel outlines. An 889,954-cell fill compacts to 6,256 cells, then draws 541 view-level cells at its fitted view; p95 pan frames stayed below 12.7 ms at the reference CPU profile. Zooming restores finer levels. Mixed-resolution sets use a different outline weight and a named legend entry for every resolution. Results are unchanged.
Result change H3 polygon fill (version 1.2.0) now includes the fourth H3 containment mode, overlapping-bbox, which conservatively follows buffered boxes through H3's cell hierarchy. The same hierarchical traversal fixes overlapping results on degenerate rings that reach a pole, where the earlier edge-seeded search could differ from H3 C by one or two cells. All four modes now match H3 C 4.4.1 cell for cell on 1,000 random polygons with holes and antimeridian crossings, 15 polar rings, and 44 resolution 0 and 1 cases. Center and full results are unchanged.
2026-10-10
Changed The glide range tool is now stable. The points of its reachable ring agree with GeographicLib for Python at 15 glides from 60° S to 70° N, with winds up to 60% of the airspeed. Its answers are unchanged.
Tools: Glide range with wind
Changed The runway ranking tool is now stable. Its headwind and crosswind on every runway end agree with the wind resolved by MetPy at 14 airports, with winds from 7 to 40 kt and with crosswind and tailwind limits. Its answers are unchanged.
Tools: Rank runways for the wind
Changed The winds aloft between levels tool is now stable. Its wind and temperature agree with MetPy and NumPy at 16 altitudes between forecast levels from 3,000 to 39,000 ft, including winds that swing through north. Its answers are unchanged.
Tools: Winds aloft between levels
Changed The total and static air temperature tool is now stable. It agrees with flightcondition, a separately written Python library, at 16 heights and Mach numbers from sea level to 51,000 ft, in both directions. Its answers are unchanged.
Changed The cloud base and freezing level tool is now stable. Its lifting condensation level agrees with MetPy, Unidata's meteorology library, within 0.08% at 16 surface readings from −20 °C to 45 °C. Its answers are unchanged.
Changed The QNH, QFE, and QNE tool is now stable. It was checked against ambiance, a separate implementation of the ICAO standard atmosphere, at 14 fields from 1,300 ft below sea level to 13,325 ft, and its NWS altimeter setting against MetPy, within 0.001 inHg. Its answers are unchanged.
Tools: QNH, QFE, and QNE
Changed The humidity and moist air tool is now stable. It was checked against MetPy, Unidata's meteorology library, at 16 cases from −40 °C to 45 °C: air density agrees within 2 parts in 100,000, and vapor pressure, relative humidity, and mixing ratio within 0.31%, which is the difference between the two libraries' saturation formulas. Its answers are unchanged.
Tools: Humidity and moist air
Changed The facade scan tool is now stable. Every photo station of 12 scans, on walls from 12 to 400 m long between 55° S and 78° N, agrees with GeographicLib for Python to a tenth of a millimeter. Its answers are unchanged.
Tools: Facade scan
Changed The corridor mapping tool is now stable. Every waypoint of its offset lines agrees with GEOS and PROJ within about 2 mm for 18 corridors from 55° S to 69° N, with bends up to 120° and up to six lines. Its answers are unchanged.
Tools: Corridor mapping lines
Changed The TFR and NOTAM area tool is now stable. Its circles, fix-radial-distance centers, and point-list areas agree with GeographicLib in both its C++ and Python forms, for circles from 0.5 to 400 NM between 71° N and 55° S. Its answers are unchanged.
Tools: TFR and NOTAM area
Result change The fix from a radial and distance tool is now stable. Its answers are unchanged. The fix was checked against GeographicLib for Python and the magnetic declination against pygeomag, a separate implementation of the World Magnetic Model, at 14 stations around the world: the fix agrees within a billionth of a degree and the declination within a millionth. Promotion removed the experimental warning, which moved the station-variation warning from second to first in the list; the two test vectors that pinned its old place are superseded.
Tools: Fix from a radial and distance
Replaced vectors: aviation.ifr.radial-fix v001, aviation.ifr.radial-fix v002
Result change The geofence tool is now stable. Its answers are unchanged. Which waypoints fall outside a fence, and by how far, were checked against GEOS and PROJ for ten irregular fields from 55° S to 69° N, to within 2 mm. Promotion removed the experimental warning, which moved the outside-the-fence warning from second to first in the list; the one test vector that pinned its old place is superseded.
Tools: Geofence around an area
Replaced vectors: drone.mission.geofence v008
Changed The isogonic lines tool is now stable, the last geodesy tool to be. Every point on its lines was checked against a separate implementation of the World Magnetic Model: within 0.12° over a region, and on a whole-globe map within 0.21° for 95% of points and 0.8° at worst, beside the magnetic poles. Its accuracy note now gives those figures.
Changed The orbit pattern is now stable. Its waypoints and headings agree with GeographicLib for Python, the original implementation of the geodesic method, at 15 orbits from near both poles to the equator and across the antimeridian.
Changed The ISA temperature tool is now stable. Its standard temperature agrees with flightcondition, a separately written Python library, within 0.0001 °C at 14 pressure altitudes from 1,000 ft below sea level to 80,000 ft.
Changed The two airspeed tools, and the seven airspeed pairs built on them, are now stable. Below Mach 1 they agree with flightcondition, a separately written Python library, to within 0.001 kt and 2 parts in a million of Mach at 26 points from sea level to 41,000 ft. Above Mach 1 that library is not a reference, so the supersonic branch still rests on this project's own second implementation and round-trip tests.
Tools: True airspeed from indicated or calibrated airspeed, Calibrated airspeed from true airspeed, Mach, or EAS, Indicated to true airspeed, Indicated airspeed to Mach, Indicated to equivalent airspeed, Equivalent to true airspeed, Equivalent airspeed to Mach, Mach to equivalent airspeed, True to equivalent airspeed
Changed Dragging or zooming a map with a long route or a large area on it is smoother: while the view moves, the light outline under result lines waits, as the coastline and state lines already do, and comes back when the view stops. A turning globe with two 100,000-point shapes draws each frame about 20% faster.
Result change The radio link budget (version 1.1.0) now works free-space loss from the exact form, 20 log(4πdf/c), where it used a rounded constant of 32.44: every loss is 0.008 dB higher, and received power and fade margin 0.008 dB lower. Its citation moves to the current edition of the ITU recommendation, P.525-5 of November 2024. The tool is now stable, with its 2.4 GHz power limits checked against 47 CFR 15.247 and ETSI EN 300 328.
Tools: Radio link budget
Replaced vectors: drone.links.link-budget v001, drone.links.link-budget v002, drone.links.link-budget v003, drone.links.link-budget v004
Changed The EASA open subcategory tool is now stable, held to every row of EASA's class label table. Its description is also corrected: the regulation's own list for A3 does not name C0 or C1 drones, and that they may also fly there is EASA's published reading, which the tool now cites as such.
Tools: EASA open subcategory
Changed The drone kinetic energy tool is now stable. Its two thresholds are held to the rules' own words: under 80 J or under 900 g for EASA class C1 (Regulation (EU) 2019/945), and 11 foot-pounds for FAA category 2 operations over people (14 CFR 107.120). It remains a screen, not a compliance finding.
Tools: Drone impact kinetic energy
Changed The mission export is now stable. Its KML and GeoJSON files are read back by GDAL, a separate implementation of both formats, which must find every waypoint in order, in the right place, at the height the chosen height reference gives.
2026-10-09
Changed The lidar flight plan is now stable. The quality level it names is held to the minimum pulse densities in table 1 of the USGS Lidar Base Specification 2025 rev. A, with plans placed just above and just below each one.
Tools: Lidar mission planning
Changed The dataset size tool is now stable. Its LAS point cloud size is held to the header and record sizes the LAS 1.4 specification gives for each of the 11 point formats. Its compression figures remain assumptions you can change.
Tools: Dataset size estimate
Changed The legacy survey units tool is now stable. Its chains, links, rods, and furlongs are held to each line of the surveyor's chain table in NIST Handbook 44 (2026), Appendix C. The vara and arpent values are the commonly cited ones for each state and were not re-checked against the statutes.
Tools: Legacy land units
Changed The ALTA/NSPS relative positional precision check is now stable, its allowable held to the 2026 standard's own words, 2 cm (0.07 feet) plus 50 parts per million, at distances in feet and meters.
Changed The fuel plan is now stable. Each reserve preset is held to the minutes 14 CFR 91.151 and 91.167 state, read from the eCFR: 30 and 45 minutes for airplanes under VFR, 45 under IFR, and 20 and 30 for rotorcraft.
Tools: Fuel planning
Changed The Part 107 groundspeed check is now stable, held to the limit as 14 CFR 107.51(a) states it, 87 knots (100 miles per hour), in mph, knots, m/s, and km/h, on both sides of the limit and exactly on it.
Tools: Part 107 groundspeed check
Changed The flight level tool is now stable. Its lowest usable flight level is checked against both ends of every row of the 14 CFR 91.121(b) table, read from the eCFR.
Tools: Flight level and altitude
Fixed Three tools' own descriptions are corrected: time-to-station's 60-times rule reads about 4% long at a 10° change, not 5%; ISA temperature no longer lists an Earth radius among its constants, because it never uses one; and the holding wind tool now says the turn direction only places the drawing, since the headings and times are the same for left and right turns.
Tools: Time and distance to a station, ISA temperature and deviation, Holding wind correction and timing
Changed Coordinate system search and coordinate system transform are now stable: each has a derivation note, an independent worked example from PROJ 9.9 with the EPSG dataset, at least 20 golden vectors, and invariant tests.
Tools: Coordinate system finder, Coordinate system to coordinate system
Fixed The polygon overlap tool, with planar edges, stopped with an internal error when a longitude was absurdly large; it now refuses longitudes past 540° with a clear message. The motion-blur tool now lists the no-solution answer it gives at zero groundspeed among its errors. Both found by the fuzzer.
Tools: Overlap, union, or difference of two polygons, Motion blur and slowest shutter
Added A fuel burn rate tool: the fuel a flight used and its time give the average burn, and the fuel on board gives the endurance at that rate. 28 gal over 2.5 h is 11.2 gal/h.
Tools: Fuel burn rate
Fixed Each tool's list of error codes, which agents read through the MCP server, now names every refusal the tool can give. Tools that take a measurement now list OUT_OF_DOMAIN, which any of them returns for an impossible magnitude, and five tools gained a code they returned without listing it. A new check holds every refusal in the test vectors and every one the fuzzer finds to the tool's list.
Added A new workflow, Lay out a road curve, works a circular curve and a vertical curve together and draws them as one plan-and-profile sheet on a shared station scale, with each curve point joined to the other view at its station.
Added A new workflow, Preflight performance check, goes from the METAR to pressure and density altitude, reads your POH takeoff table at today's pressure altitude and temperature, and splits the wind on your runway.
Added Pressure altitude can now use the National Weather Service constants, to check an answer against weather.gov's calculator, and a new explainer shows why the two disagree: by a few feet from the constants, and by up to tens of feet at a high field from the NWS station-pressure shortcut. The tool's accuracy note had said about 12 ft at most; it now gives the larger figure.
Tools: Pressure altitude
Changed H3 polygon fill now refuses a polygon whose edges are too long for the resolution at a lower bound, 250,000 edge samples instead of 2,000,000, because a browser runs the fill about ten times slower than the first measure assumed. A thin polygon thousands of miles long at resolution 9 now gets a clear limit message at once instead of a long wait.
Fixed SPCS2022 forward now refuses a point at the far pole of a Lambert zone, which has no place on its grid, instead of failing with an internal error.
Tools: Latitude and longitude to state plane (SPCS2022 beta)
Added The calibrated-airspeed tool now also takes an equivalent airspeed: EAS 248.1 kt at 10,000 ft gives 250 kt calibrated, with Mach, and true airspeed when you give the temperature. Seven airspeed pairs join it, each a narrower form of the two airspeed tools: IAS to TAS, IAS to Mach, IAS to EAS, EAS to TAS, EAS to Mach, Mach to EAS, and TAS to EAS.
Tools: Calibrated airspeed from true airspeed, Mach, or EAS, Indicated to true airspeed, Indicated airspeed to Mach, Indicated to equivalent airspeed, Equivalent to true airspeed, Equivalent airspeed to Mach, Mach to equivalent airspeed, True to equivalent airspeed
Changed Tool pages load less: a page now carries only its own tool's drawings, loaded when needed, instead of every diagram on the site, so a tool page's JavaScript fell from about 90 KB to 71 KB compressed (76 to 79 KB with a diagram). The first drawing is still in the page as it loads.
Added The spiral-curve-spiral tool draws the curve in plan: both tangents into the PI, the entry and exit spirals and the circular arc between, each point named with its station. The result also lists the alignment's points along the back tangent and toward the inside of the curve.
Added Survey grids take the camera's ground footprint across and along the line, as the ground sample distance tool gives it. The map then draws every photo's footprint, darker where photos overlap, and the result gives the forward and side overlap the spacings make, with a warning when the photos leave gaps. Without a footprint nothing changes.
Changed GPS satellite visibility and DOP now also reads SEM almanacs, the Coast Guard's other almanac format, telling the two apart by themselves. The same week's SEM and YUMA files give the same answer.
Added New: convert coordinates between two EPSG coordinate systems, such as State Plane on NAD 83 (2011) to UTM on WGS 84. It undoes the source projection, moves the position between frames at the epoch you give, and applies the target projection, listing each step with its accuracy. It follows each EPSG code's own definition, including the feet versions of State Plane zones.
Added New: a coordinate system finder. Give an EPSG code from a file's metadata, a name like Colorado Central, or a point, and it lists the UTM zones, State Plane 1983 zones in meters and feet, SPCS2022 beta zones, and geographic systems that fit, with each one's unit, status, and the tool that converts to it. Its index comes from EPSG v13.102.
Tools: Coordinate system finder
Fixed The State Plane 1983 zones now use EPSG's current areas of use (v13.102). Five had been revised since the older copy: Louisiana Offshore now covers the Gulf (25.58° to 29.35° N) instead of a mostly onshore box, and the Arkansas and Georgia zones moved by up to 0.19°. A point in those slivers can now get a different zone from the zone lookup, a different automatic zone, or a different outside-the-zone warning. Projection parameters did not change. State plane forward also refuses a point too far from its zone to place on the grid, such as the opposite pole of a Lambert zone, instead of failing with an internal error.
Tools: Latitude and longitude to state plane (SPCS83), State plane (SPCS83) to latitude and longitude, State plane zone lookup
Added New: GPS satellite visibility and DOP. Paste this week's YUMA almanac from the Coast Guard, give a site and a time window, and see how many satellites are above your elevation mask and how PDOP, HDOP, and VDOP move through the window, with a sky plot. Enter the skyline where trees or buildings block the sky. Long text fields, such as an almanac, a deed, or GeoJSON, now get a multi-line box that keeps their line breaks.
Changed The navigation log's map labels each leg with its magnetic heading, groundspeed, and time, and maps of a planned flight path (a nav log, a corridor, an orbit) now open framed on the path instead of a wide regional view.
Tools: Navigation log
Added New: terrain curvature for one cell of an elevation model, by Zevenbergen and Thorne's method. It gives total, profile, and plan curvature per 100 m, positive where the ground is convex, and says in words whether water running over the cell speeds up or slows down and spreads or gathers.
Tools: Terrain curvature
Added New: line of sight over a ground profile. Enter the ground from an observer to a target and both heights above it: the tool says whether the target is in sight with the Earth's curve and refraction, which point blocks the view and by how much, how high the observer would need to be, and, with a frequency, whether 60% of the first Fresnel zone is clear and where it is not.
2026-10-07
Changed Height per hectopascal is now stable: its derivation note, 22 vectors from the ambiance package's independent standard atmosphere, and an invariants test are in place, so its results no longer carry the EXPERIMENTAL_TOOL warning. No numbers changed.
Fixed A point too far from a state plane zone to have a place on its grid, such as the opposite pole of a Lambert zone, is now refused with OUT_OF_DOMAIN naming the point, instead of failing with an internal error.
Added New: isogonic lines, lines of equal magnetic declination at a chosen interval over an area and date, with the agonic line and the WMM compass caution and blackout zone edges. The declination map has an Isogonic lines button that draws them around your point.
Tools: Isogonic lines and compass zones, Magnetic declination
Added UTM results now name the latitude band and the edges of the grid zone, with the Norway and Svalbard exceptions, and the map highlights that zone. Maidenhead, GARS, and GEOREF maps draw the grid of the same cell size around the highlighted cell. Coordinates are unchanged.
Tools: Latitude and longitude to UTM, Latitude and longitude to Maidenhead locator, Latitude and longitude to GARS, Latitude and longitude to GEOREF
Added The MGRS map now draws the grid around the referenced square: the square's size (at least 1 km) three squares out, and the 100 km square that holds it. The lines follow the zone's grid, so they lean by the grid convergence. The reference and the square are unchanged.
Added New: how much height one hectopascal and one inch of mercury span at a pressure altitude, from the standard atmosphere, with the 27 ft per hPa rule of thumb beside it. At sea level 1 hPa is 27.31 ft; at 18,000 ft it is 47.92 ft. Search also keeps a number that is part of a tool's name, so "state plane 2022 to lat long" finds the 2022 tool.
Added The polygon area tool takes an interior rule. The default is unchanged: the smaller of the two regions a ring divides the Earth into. With interior set to orientation, the ring's direction decides, as in GeoJSON, so a clockwise ring measures the rest of the world. The result now says which rule was used.
Changed The oblique GSD tool takes an optional location and camera heading, and then gives each footprint corner a latitude and longitude, so the page draws the trapezoid the image covers on the map. Results without a location are unchanged.
Tools: Oblique GSD and footprint
Changed Survey grid waypoints now carry the flight height when one is given, so they can go straight into a mission export; the drone mapping workflow ends with a mission KML to download, and the VFR cross-country workflow offers its nav log as CSV. Existing results are unchanged.
Added The waypoints tool can lay its points along the great circle on a sphere of the IUGG mean radius, for comparison with the geodesic. Map pages for two-point routes have a Compare methods button that adds that great circle beside the geodesic and the rhumb line, with each line's length in the legend. Geodesic and rhumb results are unchanged.
Tools: Waypoints along a route line, Distance between two points (geodesic)
2026-09-28
Changed The dataset estimator now shows the LAS 1.4 header, point-record sizes, and default format behind its point-cloud estimates. The lidar planner now shows the USGS QL1, QL2, and QL3 pulse-density thresholds behind its quality label. Calculated results are unchanged.
Changed The facade scan now shows the Pix4D guidance behind its 75% and 60% overlap defaults, and the thermal footprint tool shows the FLIR 3 × 3 pixel rule behind its default target size. Calculated results are unchanged.
Tools: Facade scan, Thermal pixel footprint
Changed The GSD, height-for-GSD, and trigger tools now show the sourced camera and mission defaults used when the caller omits them: the 36 × 24 mm full-frame basis, the 400 ft altitude ceiling, and Pix4D's general and forest overlap presets. Calculated results are unchanged.
Tools: Ground sampling distance (GSD), Height for a target GSD, Overlap, trigger interval, and line spacing
Changed The GSD answer now says whether its resolution is finer than, within, or coarser than the approximately 1–5 cm/px range published as typical for a real UAV mapping flight. The answer cites Ruiz et al. (2013), Table 2, and does not present the range as a safety limit. Calculated results are unchanged.
Fixed The Part 107 speed check now draws groundspeed against the 87 kt limit, and the battery calculator draws usable energy against the full pack and landing reserve. Unsupported gauge declarations were removed, and a build gate now requires every declared gauge and profile chart to render its worked example. Results are unchanged.
Tools: Part 107 groundspeed check, Battery energy (mAh to Wh)
Changed The GCP and checkpoint planner is now stable. Its 20 golden vectors cover every ASPRS Table C.1 area band, open and vegetated land, horizontal and vertical accuracy classes, the standard's published 1,500 km² example, and the table's upper limit. No calculated results changed.
Tools: GCP and checkpoint plan
Changed The equal time point and point of no return planner is now stable. Direct groundspeeds, wind-derived groundspeeds, safe endurance, and fuel-derived endurance match an independent Python calculation across 20 golden vectors, including the CASA worked example. No calculated results changed.
Changed The climb planner is now stable. Its climb time, wind-adjusted top-of-climb distance, fuel, and taxi total match an independent Python calculation across 20 golden vectors, including the FAA handbook table example. No calculated results changed.
Changed The navigation log is now stable. Its route totals, wind corrections, headings, times, fuel, compass wrap, and geodesic legs match an independent Python and GeographicLib calculation across 20 golden vectors, including the FAA handbook example. No calculated results changed.
Tools: Navigation log
Added The magnetic tools can now use WMMHR2025, the degree-133 high-resolution World Magnetic Model, from 2025.0 through 2030.0. Its pinned 533 KB coefficient file loads only when selected. Every field element and annual rate matches all 12 official NCEI test rows, and official cases also run through the website and MCP asset loaders.
Tools: Magnetic declination, True and magnetic bearings, Grid variation (grivation)
Added Two new stable tools convert to and from all 953 NGS SPCS2022 beta zones. Every result names its 2022 terrestrial reference frame and carries NON_OFFICIAL_DATUM with the June 1, 2026 definition date. All zones match the official NGS example coordinates to the published millimeter.
Tools: Latitude and longitude to state plane (SPCS2022 beta), State plane (SPCS2022 beta) to latitude and longitude
2026-09-25
Added MGRS results now include the outline of the square the reference names, so the map draws the square instead of a point. Existing outputs are unchanged.
Tools: Latitude and longitude to MGRS, MGRS to latitude and longitude
2026-09-24
Fixed dNBR (version 1.1.0) now reads the Key and Benson severity table the way it is printed, in whole units of dNBR times 1,000, so a drop of exactly 0.10 (such as 0.37 to 0.27) is low severity, not unburned by a rounding hair; the same holds at every class edge. Values beyond about -550 or +1,350, which the table's authors attribute to clouds or misregistration rather than fire, are now flagged. The tool is now stable.
Tools: dNBR (burn severity)
Result change S2 coverings of rectangles and circles (version 2.0.0) now come from a port of S2's own RegionCoverer, so they are the same cells S2 itself returns and can be exchanged with other S2 systems. Before, this tool refined from the six cube faces with its own rule, which gave valid but different coverings, often with more cells than needed. The new coverings match s2sphere cell for cell on 400 random regions. Polygon coverings are unchanged. The superseded vectors pinned the old coverings.
Tools: S2 cells covering a region
Replaced vectors: indexing.s2.covering v001, indexing.s2.covering v002, indexing.s2.covering v003, indexing.s2.covering v005, indexing.s2.covering v006, indexing.s2.covering v007, indexing.s2.covering v008, indexing.s2.covering v009, indexing.s2.covering v010, indexing.s2.covering v011, indexing.s2.covering v012, indexing.s2.covering v013, indexing.s2.covering v014, indexing.s2.covering v015, indexing.s2.covering v016, indexing.s2.covering v017, indexing.s2.covering v018, indexing.s2.covering v019, indexing.s2.covering v020, indexing.s2.covering v021, indexing.s2.covering v022
Added MGRS references (version 1.1.0) can now be made and read on the Clarke 1866 and Bessel 1841 ellipsoids, with the older AL row lettering NGA keeps for them, which starts the 100 km rows ten letters later than the AA lettering used on WGS 84. They match NGA GEOTRANS on 600 references. References on WGS 84 are unchanged.
Tools: Latitude and longitude to MGRS, MGRS to latitude and longitude
Added A new stable tool moves a position between any two ITRF, WGS 84, and NAD 83 realizations at one epoch. It finds the chain of published transformations with the least combined uncertainty (IERS, NGA's WGS 84 alignment, and NGS HTDP) and lists each step with its accuracy and the combined total. Its steps match NGS HTDP within a millimeter and PROJ's IERS parameters.
Added Two new stable tools compute the transverse Mercator exactly, with elliptic functions, so it holds to nanometers anywhere on the ellipsoid rather than only within 3,900 km of the central meridian. They are a port of GeographicLib's TransverseMercatorExact and agree with it within a micrometer on 10,000 random points over the whole globe.
Tools: Latitude and longitude to exact Transverse Mercator, Exact Transverse Mercator to latitude and longitude
Changed The hull, bounding rectangle, and enclosing circle tool (version 1.1.0) can now draw the hull with edges straight in longitude and latitude, as most mapping software does, beside the great-circle hull it gives by default. The circle and the rectangle are unchanged.
Fixed Check and repair a polygon could list the problems it found in a different order depending on what had run before it in the same session, so the MCP server and a freshly opened page could disagree. The order now depends only on the input. The problems found, and every repair, were already the same.
Tools: Check and repair a polygon
Changed The overlap, union, and difference of two polygons (version 1.2.0) can now treat edges as straight in longitude and latitude, as most mapping software draws them, beside the geodesic edges it uses by default. The overlay is then done on the coordinates as written, and the areas follow those straight edges. Results with geodesic edges are unchanged.
Added Two new stable tools convert on a transverse Mercator you define, for grids other than UTM like the British National Grid and Gauss-Krüger zones. They use the same sixth-order series as UTM, good to 5 nanometers within 3,900 km of the central meridian, and warn beyond. They agree with GeographicLib's own implementation within a micrometer on 10,000 random points. State Plane's transverse Mercator zones now run through the same code, results unchanged.
Tools: Latitude and longitude to Transverse Mercator, Transverse Mercator to latitude and longitude
Added Two new stable tools convert on a Hotine Oblique Mercator you define, variant A or B: the projection for grids along a slanted band, like the Alaska panhandle's state plane zone and the Malaysian and Borneo grids. They reproduce the RSO Borneo example in IOGP Guidance Note 7-2 and agree with PROJ within a micrometer on 10,000 random points. State Plane's Alaska zone 1 now uses the same code, with its results unchanged.
Tools: Latitude and longitude to Hotine Oblique Mercator, Hotine Oblique Mercator to latitude and longitude
Added Two new stable tools draw the Earth as a globe seen from space above a center you choose, and read points back: the ellipsoidal Orthographic of EPSG. The far side is refused. They agree with PROJ within a micrometer on 10,000 random points, and give the exact convergence and scales.
Tools: Latitude and longitude to Orthographic, Orthographic to latitude and longitude
Added Four new stable tools map points around a center you choose, and back: the azimuthal equidistant, where the distance and direction from the center are the true geodesic ones, and the gnomonic, where geodesics through the center are straight lines. The gnomonic refuses points 90 degrees or more from its center. Both agree with GeographicLib's GeodesicProj within a micrometer on 10,000 random points each, and the azimuthal equidistant reproduces the Yap Islands example in IOGP Guidance Note 7-2.
Tools: Latitude and longitude to Azimuthal Equidistant, Azimuthal Equidistant to latitude and longitude, Latitude and longitude to Gnomonic, Gnomonic to latitude and longitude
Added Ten new stable tools project a latitude and longitude with parameters you set, and back: Web Mercator (EPSG:3857), Lambert Conformal Conic with one or two standard parallels, Albers Equal Area, Polar Stereographic by scale at the pole or by standard parallel, and the ellipsoidal Equidistant Cylindrical. Each gives the grid convergence and the scale along the meridian and the parallel. They reproduce the worked examples in IOGP Guidance Note 7-2 and Snyder's Albers example, and agree with PROJ within a micrometer on 10,000 random points per method.
Tools: Latitude and longitude to Web Mercator, Web Mercator to latitude and longitude, Latitude and longitude to Lambert Conformal Conic, Lambert Conformal Conic to latitude and longitude, Latitude and longitude to Albers Equal Area, Albers Equal Area to latitude and longitude, Latitude and longitude to Polar Stereographic, Polar Stereographic to latitude and longitude, Latitude and longitude to Equidistant Cylindrical, Equidistant Cylindrical to latitude and longitude
Added Read any coordinate (version 1.3.0) now reads written UPS coordinates (like Z 2426773 1530125) and grid codes: full Plus Codes, Maidenhead locators, GARS, GEOREF, and geohashes, each code as the center of its cell, with a note saying so. A code valid in two grids, like fn20, gives both readings. Results for every notation it read before are unchanged.
Tools: Read any coordinate
Fixed Check and repair a polygon (version 1.1.0) now returns pieces that touch at a single point as separate parts, as a valid polygon needs, where it used to join them into one ring touching itself; and it no longer repairs some small rings to nothing: a corner lying on another part of its own ring sits a fraction of a micron off it once projected, and the side test could step across. Corners that nearly touch another part of the ring are now put on it first, and crossing points that fall at one place are made one point. The overlay (version 1.1.1) gets the same crossing-point fix, for three edges crossing at one place. Checked against GEOS on 600 self-crossing rings; results for rings that do not touch themselves are unchanged.
Tools: Check and repair a polygon, Overlap, union, or difference of two polygons
Fixed Overlap, union, or difference of two polygons (version 1.1.0) no longer loses or invents pieces where the polygons touch. A corner lying on the other polygon's edge, or on its own polygon's outline, sits a fraction of a micron off it once projected, and the side test could step across that gap: some unions came back empty and some differences a third too small. Corners within a millionth of the shapes' size (at most 1 mm) of another ring are now put on it first. Pieces that touch at a single point are now separate parts rather than one ring touching itself, which is not a valid polygon. Checked against GEOS on 400 pairs of touching and overlapping shapes through all four operations; results for polygons that do not touch are unchanged, and every earlier vector still passes.
Result change ASPRS accuracy (version 1.1.0) is stable and now takes a list of checkpoint errors: it computes the RMSEs, tests NVA and horizontal accuracy against their classes, reports VVA as found, lists blunders over three times the target RMSE, and flags a mean error of 25% of the target or more and checkpoints not twice as accurate as the product. Answers for the old inputs are unchanged. Promotion removed EXPERIMENTAL_TOOL from its warnings, which moved INSUFFICIENT_CHECKPOINTS from index 1 to index 0; the superseded vector pinned the old index.
Tools: ASPRS accuracy (Edition 2)
Replaced vectors: drone.photogrammetry.asprs-accuracy v006
2026-09-23
Fixed Converting UTC to local time, the sentence repeated the Zulu time you entered ("That is 2300Z.") instead of the answer. It now gives the local time and zone ("That is 15:00 AKDT."), and when the date changes it gives the local date. Three outputs are new: answer (the converted time in the direction asked), to_local (1 for UTC to local, 0 for local to UTC), and local_date_change. Local to UTC reads as before. The tool is now version 1.1.0.
Tools: Local time to UTC (Zulu)
Fixed Where a twilight or the sunrise does not happen, the page showed codes like "no-civil-twilight-begin" and "polar-day", and the sentence read "Sunrise is polar-day". The result keeps those documented codes for machines, but the page now shows plain words, like "None: the sun does not get low enough for civil twilight to begin", and the sentence says "The sun stays up all day, so there is no sunrise or sunset." The tool is now version 1.0.1.
Fixed A wind straight across the runway read "0 kt tailwind", and one straight down it read "0 kt crosswind from the none": float noise like −0.0000000000000018 kt was taken as a tailwind. Components under a billionth of a knot are now exactly zero, and the sentence says "no headwind or tailwind" or "No crosswind" whenever a component rounds to zero. The wind triangle said "a wind correction of 0° to the right" with no crosswind; it now says "with no wind correction". Runway wind components and the wind triangle are now version 1.0.1.
Tools: Runway wind components, Wind triangle: heading and groundspeed
Fixed An altimeter setting of A2980 showed as 29.8 inHg. Settings are given to hundredths (FAA-H-8083-28B section 24.4.3.11), so the METAR decoder and the QNH of the Q-codes tool now keep the trailing zero: 29.80 inHg. In hPa they read as before. The METAR decoder is now version 1.1.1 and the Q-codes tool 1.1.1.
Tools: METAR decoder, QNH, QFE, and QNE
Fixed The winds aloft code 7799 decoded as "270° true at 199 kt". FB forecasts code 200 kt and more as 199 kt (FAA-H-8083-28B section 27.2.1.1.1), so it now reads "270° true at 199 kt or greater", the row carries speed_bound "at-least", and the result has a SPEED_AT_LEAST note. The decoder is now version 1.1.0.
Tools: Winds aloft (FB) decoder
Fixed NADCON5 (version 1.0.1) cited NOAA Technical Memorandum NOS NGS 84 as the NADCON5 report. That memo is Dru Smith's Biquadratic Interpolation (2022). The tool now cites the NADCON 5.0 report, NOAA Technical Report NOS NGS 63 (Smith and Bilich, 2017, revised 2020), and cites TM 84 separately for the interpolation between grid nodes, which the tool does use. Results are unchanged.
Fixed Identifiers no longer show digit grouping: the EPSG code in SPCS83 forward and zone lookup reads 32129, not 32,129, and the decimal year in magnetic declination reads 2026.71, not 2,026.71 (all version 1.0.1). SPCS83 forward in US survey feet also gave the deprecated-unit warning (LEGACY_UNIT) twice, once for easting and once for northing; every tool now gives it once per result. Values are unchanged.
Tools: Latitude and longitude to state plane (SPCS83), State plane zone lookup, Magnetic declination
Fixed Short distances lost their meaning: a 0.859 m geodesic showed as 0.001 km. Distances in the navigation tools (version 1.0.1) still show to the meter in kilometers, but a short one now keeps three significant digits, down to the millimeter, so it shows as 0.000859 km. Differences such as the rhumb line's extra distance keep fixed decimals. Values are unchanged.
Tools: Distance between two points (geodesic), Haversine distance (spherical), Where two geodesic segments cross, Midpoint on the geodesic, Great-circle distance and course (spherical), Highest point of a geodesic (vertex), Waypoints along a route line, Destination on a constant course (rhumb line), Rhumb line distance and course, Closest point on a route, Where two courses cross, Cross-track and along-track distance, Intercept a moving target, Range rings
Fixed Where the geoid is below the ellipsoid, the sentence said the geoid was a negative height above it ("-17.21 m above the ellipsoid"). It now says "17.21 m below the ellipsoid", and a point under the ground given reads as below the ground. The height converter's second example, a drone reporting 120 m above the ellipsoid over 250 m terrain, put the drone underground; it is replaced by a drone at 180 m above the ellipsoid over 40 m terrain, 117.539 m above the ground. Both tools are version 1.0.1; values are unchanged.
Tools: Geoid height (EGM96), Ellipsoidal and orthometric height
Fixed Tile from point (version 1.0.1) rejected a tile size given as the number 512 ("Tile size must be a string"). Every tool now accepts a numeric option such as 512 as a number or as text.
Result change The forest overlap preset (version 1.1.0) is now 85% front and 85% side. It used 85% front and 70% side, but Pix4D's page recommends at least 85% frontal and side overlap for forest and dense vegetation; 85/70 is its advice for snow and sand. With the preset, flight lines are now closer together: 22.5 m instead of 45 m for a 1-inch camera at 100 m. The superseded vector pinned the old line spacing.
Tools: Overlap, trigger interval, and line spacing
Replaced vectors: drone.photogrammetry.trigger v010
Fixed Visual line of sight (version 1.2.0) now warns when the ground visibility is below 5 km, the least EASA's guidelines recommend. It gave no warning at 1 km or 0.3 km. Above 5 km it still counts only 5 km, but it now credits that cap to the LBA guidance EASA points to, and cites it; it wrongly called 5 km the most the EASA procedure assumes. No distance changes.
Fixed Plain-number results in a fixed unit now show that unit: the battery current reads 9.7 A where it read 9.7, and decibels, gigabytes, pulses per square meter, grams per kilogram, nautical miles per gallon, hours, nanoteslas, and minutes now carry their units too. The numbers themselves do not change. Each tool's patch version went up.
Tools: Battery energy (mAh to Wh), Radio link budget, Dataset size estimate, Lidar mission planning, Humidity and moist air, Specific range, TAF decoder, Magnetic declination, Sunrise, sunset, and twilight
Fixed The unequal-tangent vertical curve's sentence said the curve passed, for example, "96.25 ft under the PVI", when 96.25 ft is the curve's elevation at the PVI station and the curve is 3.75 ft below the PVI. It now says "At the PVI station it is at 96.25 ft, and the PVI is at 100 ft". Version 1.0.1; no numbers change.
Fixed Survey tools cite Ghilani and Wolf's Elementary Surveying, 16th edition (2021), but their method notes said "Ghilani & Wolf 2018". The notes now give 2021, the edition cited. No results change.
Tools: Angular closure of a loop traverse, Intersection (bearings and distances), Least-squares network adjustment (2D), Total-station offset shot, Three-point resection, Station and offset from a line, Circular curve layout table, Vertical curve length for sight distance, Spiral-curve-spiral transition, Unequal-tangent vertical curve, Grid (borrow-pit) volume, Cross-section cut and fill areas, Slope stake (catch point), Stockpile volume (TIN), Site localization (calibration), Curvature and refraction correction, Height of an inaccessible object, Level run reduction and closure, Slope distance to horizontal and vertical, Stadia reduction
Fixed The worked example was titled a 600 m by 150 m field, but its corners are 602 m apart along the lines, which is why it gives 22 photos a line and 104 in all. The title now says 602 m by 150 m. No results change.
Tools: Image count and survey size, Survey grid (lawnmower pattern)
Result change Image count and the survey grid (version 1.1.0) now count the way published flight planning does (Penn State GEOG 892): ⌈width / spacing⌉ + 1 lines with the outer lines on the edges, and ⌈length / photo spacing⌉ + 1 photos per line plus extra photos past each end, 2 by default (a new input; 0 leaves them out). Most areas gain a line. The Penn State block now gives its published 10 lines and 430 photos, where 1.0.0 gave 9 and 342. The superseded vectors pinned the old line counts.
Tools: Image count and survey size, Survey grid (lawnmower pattern)
Replaced vectors: drone.photogrammetry.image-count v001, drone.photogrammetry.image-count v002, drone.photogrammetry.image-count v003, drone.photogrammetry.image-count v004, drone.photogrammetry.image-count v005, drone.mission.survey-grid v001, drone.mission.survey-grid v002, drone.mission.survey-grid v003, drone.mission.survey-grid v004, drone.mission.survey-grid v005
Fixed A left-turn hold flown exactly on the reciprocal of the inbound course got the parallel entry, while the mirror-image right-turn hold got the teardrop. Both entries are acceptable on that line, and the tool still says so, but it now names the teardrop for either turn direction, so a left hold mirrors a right one exactly. Every other heading is unchanged. The worked-out steps now show an arrival along the inbound course as 0 degrees rather than 360. The page diagram also drew each sector label on the wrong side of the fix, as a heading instead of where you arrive from, and drew the pattern to the east of the fix whatever the inbound course; both now match the AIM figure. The tool is now version 1.1.0 and stable.
Tools: Holding pattern entry
Changed Drone flight time is stable. It reproduces the endurance step of Bauersfeld and Scaramuzza's DJI Mavic 3 example (IEEE Robotics and Automation Letters, 2022): 4.89 Ah at 4 × 3.7 V and 89.5 W is 2,909 s, and 4.88 Ah at 107.0 W is 2,429 s, both within the rounding of the printed capacity. The derating field's help now asks for a percent, like 15, where it used to suggest 0.85, which the tool would have read as 0.85%. The reserve's help now says it is a share of the usable energy, which is what the tool has always computed. Results are unchanged.
Tools: Drone flight time
Result change Promoting this tool to stable removed EXPERIMENTAL_TOOL from its warnings, which moved OVERLAP_BELOW_TARGET from index 1 to index 0 and broke eight vectors that pinned the index. Nothing computed changed. v001, v003, v004, v005, v007, v010, v011, and v012 are superseded by v015 to v022, which name the warning with the meta.warnings.*.code form.
Tools: Overlap over high terrain
Replaced vectors: drone.photogrammetry.terrain-overlap v001, drone.photogrammetry.terrain-overlap v003, drone.photogrammetry.terrain-overlap v004, drone.photogrammetry.terrain-overlap v005, drone.photogrammetry.terrain-overlap v007, drone.photogrammetry.terrain-overlap v010, drone.photogrammetry.terrain-overlap v011, drone.photogrammetry.terrain-overlap v012
Result change Station pressure now comes from the altimeter-setting relation instead of a sea-level ratio shortcut. The worked example moved from 5,108 to 5,112 ft pressure altitude and 7,932 to 7,937 ft density altitude; at an 8,000 ft field with 28.20 inHg the old answer was 90 ft low.
Tools: Pressure altitude, Density altitude, QNH, QFE, and QNE, Flight level and altitude
Replaced vectors: aviation.altimetry.pressure-altitude v001, aviation.altimetry.pressure-altitude v004, aviation.altimetry.pressure-altitude v005, aviation.altimetry.pressure-altitude v006, aviation.altimetry.pressure-altitude v007, aviation.altimetry.pressure-altitude v008, aviation.altimetry.pressure-altitude v009, aviation.altimetry.pressure-altitude v010, aviation.altimetry.pressure-altitude v011, aviation.altimetry.pressure-altitude v012, aviation.altimetry.pressure-altitude v013, aviation.altimetry.pressure-altitude v014, aviation.altimetry.pressure-altitude v015, aviation.altimetry.pressure-altitude v016, aviation.altimetry.pressure-altitude v018, aviation.altimetry.pressure-altitude v019, aviation.altimetry.density-altitude v001, aviation.altimetry.density-altitude v002, aviation.altimetry.density-altitude v004, aviation.altimetry.density-altitude v005, aviation.altimetry.density-altitude v006, aviation.altimetry.density-altitude v007, aviation.altimetry.density-altitude v008, aviation.altimetry.density-altitude v010, aviation.altimetry.density-altitude v011, aviation.altimetry.density-altitude v012, aviation.altimetry.density-altitude v013, aviation.altimetry.density-altitude v014, aviation.altimetry.density-altitude v015, aviation.altimetry.density-altitude v016, aviation.altimetry.density-altitude v017, aviation.altimetry.density-altitude v018, aviation.altimetry.density-altitude v019, aviation.altimetry.density-altitude v020, aviation.altimetry.q-codes v001, aviation.altimetry.q-codes v002, aviation.altimetry.q-codes v004, aviation.altimetry.q-codes v005, aviation.altimetry.q-codes v006, aviation.altimetry.q-codes v007, aviation.altimetry.flight-level v001, aviation.altimetry.flight-level v002, aviation.altimetry.flight-level v003, aviation.altimetry.flight-level v004, aviation.altimetry.flight-level v005, aviation.altimetry.flight-level v006
Result change Promoting this tool to stable removed EXPERIMENTAL_TOOL from its warnings, which moved POLE_ENCLOSED from index 1 to index 0 and broke v008, which pinned the index. Nothing computed changed. v008 is superseded by v018, which names the warning by its code with the meta.warnings.*.code form the runner supports, so no warning sorting above it can shift it again -- the same fix time.scale.gps-week v007 took.
Tools: Range rings
Replaced vectors: navigation.route.range-rings v008
Result change Promoting this tool to stable removed EXPERIMENTAL_TOOL from its warnings, which moved LEAP_SECOND_TABLE_EXPIRED from index 1 to index 0 and broke v007, which pinned the index. Nothing computed changed. v007 is superseded by v025, which names the warning by its code with the meta.warnings.*.code form the runner supports, so no warning sorting above it can shift it again -- the same fix units.fuel.convert v001 took.
Tools: UTC to GPS week and seconds
Replaced vectors: time.scale.gps-week v007
Result change Promoting these two tools to stable removed EXPERIMENTAL_TOOL from their warnings, which moved NOMINAL_VALUE_USED and UNIT_ASSUMED from index 1 to index 0 and broke the two vectors that pinned the index. Nothing computed changed. v001 is superseded by v021 and v002 by v025, both naming the warning by its code with the meta.warnings.*.code form the runner supports, so no warning sorting above them can shift them again -- the same fix geometry.validity.make-valid v001 took for the same reason.
Tools: Fuel volume and weight, Normalize a unit-tagged value
Replaced vectors: units.fuel.convert v001, units.quantity.normalize v002
Result change Promoting this tool to stable removed EXPERIMENTAL_TOOL from its warnings, which moved GEOMETRY_INVALID from index 1 to index 0 and broke v001, which pinned the index. Nothing computed changed. v001 is superseded by v022, which names the warning by its code with the meta.warnings.*.code form the runner supports, so no warning sorting above it can shift it again -- the same fix geometry.area.polygon v030 took for the same reason.
Tools: Check and repair a polygon
Replaced vectors: geometry.validity.make-valid v001
2026-09-22
Result change The planar-area vector now names the warning it expects by its code rather than by its place in the list, using the meta.warnings.*.code form the runner already supports. Nothing computed changed. v029 had pinned index 1 and broke when promotion removed EXPERIMENTAL_TOOL from the list; v030 pinned index 0, which would have broken again the next time a warning sorted above this one. v031 cannot be shifted by either.
Tools: Polygon area and perimeter on the ellipsoid
Replaced vectors: geometry.area.polygon v030
Result change Promotion to stable removed the EXPERIMENTAL_TOOL warning from the envelope, and the warnings are ordered by severity, so PLANAR_ON_GEOGRAPHIC moved from index 1 to index 0. The area, the perimeter, and every other value are unchanged; what moved is where the warning sits in the list. v029 is superseded by v030, which pins the same warning at its new index.
Tools: Polygon area and perimeter on the ellipsoid
Replaced vectors: geometry.area.polygon v029
Result change The cross-index tool now includes S2, which sits between Maidenhead and MGRS in its list, so the rows after it shift by one. The cell each system reports is unchanged; only the positions in the list moved, and the golden vectors that addressed rows by position were superseded.
Tools: One place in every index, at a matched cell size
Replaced vectors: indexing.convert.cross-index v001, indexing.convert.cross-index v002, indexing.convert.cross-index v003, indexing.convert.cross-index v004, indexing.convert.cross-index v005
Changed Geodesic distance and destination now work on strongly flattened ellipsoids (|f| from 0.02 up to 0.5) by the exact method, where they used to refuse. On 480 geodesics at six flattenings they match GeographicLib's GeodesicExact to rounding. Results on WGS 84 and other catalog ellipsoids are unchanged.
Tools: Distance between two points (geodesic), Destination from a start, course, and distance (geodesic)
Changed Traverse closure now offers the Crandall rule: it holds every measured bearing and puts the whole correction into the distances. Existing compass and transit results are unchanged.
Result change The reserve basis now links 14 CFR 91.151 and 91.167 where eCFR files them, in subpart B; the first release pointed at subpart C, which does not hold them. The fuel figures are unchanged. Tool version 1.1.0.
Tools: Fuel planning
Replaced vectors: aviation.loading.fuel-plan v001
2026-09-19
Changed Distance to the horizon is stable. Its rule-of-thumb figure reproduces all 126 heights of Bowditch's printed Distance of the Horizon table (NGA Pub. 9, Volume II, 2024 edition), in both the nautical and statute columns, to the tenth of a mile the table shows. One row is a misprint: the table gives 29.5 nautical miles at 640 feet where 1.17 times the square root of 640 is 29.6, and that row's own statute figure follows the rule. The tool gives 29.6, and a test pins the difference. Results are unchanged.
Tools: Distance to the horizon
Changed Time, speed, and distance is stable. It reproduces every one of the 4,800 cells of Bowditch's printed Speed, Time, and Distance table (NGA Pub. 9, Volume II, 2024 edition) to the tenth of a mile the table shows, with one exception: the table prints 6.8 nautical miles for 38 minutes at 10.5 knots, where the arithmetic gives 6.65 and every neighboring cell follows speed times time. The tool gives 6.65, and a test pins the difference. Results are unchanged.
Tools: Time, speed, and distance
Changed The site has a simpler shell. The header now carries only the site title, a one-line description, and a light/dark control; Units, All tools, Agents, Settings, and Source moved to the footer. The display modes are down to two, paper and ink: sunlight, night, and high contrast are gone, and a saved choice of any of them now opens in its closest replacement. The home page explains what the site does, then offers one search field and the topic categories, and a new page at /tools/ lists every calculator by category.
Changed Cross-track distance is stable. Its spherical method reproduces the Aviation Formulary's LAX to JFK example (7.4512 nm off course, 99.588 nm along it) once the formulary's minute-of-arc radius is accounted for, and the ellipsoidal foot point matches a brute-force search along the geodesic within a millimeter. Results are unchanged.
Changed The rhumb-line tools are stable. They reproduce Bowditch's Mercator sailing examples (NGA Pub. 9, 2024 edition) to within its 1 minute = 1 nautical mile convention, and match GeographicLib's RhumbSolve within 0.4 µm on 2,000 pairs run through the tools, including nearly east-west, nearly meridional, and near-pole lines. The Bowditch citation is now the 2024 edition, verified at NGA. Results are unchanged.
Tools: Rhumb line distance and course, Destination on a constant course (rhumb line)
Changed The GARS, GEOREF, Maidenhead, and USNG tools are stable, both directions. They reproduce NGA's GARS band definitions, the Wikipedia GEOREF (NAS Patuxent River) and Maidenhead (W1AW) examples, and the FGDC USNG Washington Monument, and match GeographicLib, pygeodesy, an exact Maidenhead reference, and NGA GEOTRANS on thousands of points. Results are unchanged apart from the fix below.
Tools: Latitude and longitude to GARS, GARS to latitude and longitude, Latitude and longitude to GEOREF, GEOREF to latitude and longitude, Latitude and longitude to Maidenhead locator, Maidenhead locator to latitude and longitude, Latitude and longitude to USNG, USNG to latitude and longitude
Fixed A longitude or latitude typed on a Maidenhead grid line in decimal degrees (like 145.83333333333334 for 145°50′) could land in the cell on either side of the line, depending on floating-point rounding. It now always falls in the cell east or north of the line. The tool is now version 1.1.0.
Changed The four frame conversions are stable: geodetic to ECEF and back, and to and from a local east-north-up frame. They reproduce the IOGP Guidance Note 7-2 worked examples and agree with GeographicLib's CartConvert within 15 nm on 1,000 ECEF points (poles to beyond geostationary orbit) and 500 local targets. Results are unchanged.
Tools: Latitude, longitude, and height to ECEF, ECEF to latitude, longitude, and height, Point to local ENU, NED, and AER, Local ENU, NED, or AER to point
Changed Every indexing tool is now stable. Geohash decode and neighbors match pygeohash on 1,000 and 500 cases; the Plus Code tools pass every row of the Open Location Code test data; tile ground resolution matches the Bing Maps table; the H3 resolution chooser matches H3's resolution table; and H3 polygon fill gives H3 C's own test counts (1,253 cells, 1,214 with a hole). Results are unchanged apart from the fix below.
Tools: Geohash decoder, Geohash neighbors, Plus Code encoder, Plus Code decoder, Shorten a Plus Code, Map ground resolution and scale, H3 resolution chooser, H3 polygon fill (polygonToCells)
Fixed Shortening an 8-digit Plus Code next to its own center returned a bare "+", which is not a valid code. It now keeps the last pair (for example 8F+), so the short code always recovers. The tool is now version 1.1.0.
Tools: Shorten a Plus Code
Changed Eight more H3 tools are stable: the cell inspector, grid ring, grid path, parent, children, compact, uncompact, and edges. On 300 cells at every resolution, one in eight a pentagon, they match H3 C exactly, including every path H3 C refuses; cell areas agree to 2e-8 relative even at resolution 15. Results are unchanged.
Tools: H3 cell inspector, H3 grid ring, H3 grid path and distance, H3 parent cell, H3 children cells, H3 compact, H3 uncompact, H3 edges and vertexes
Added Every tool page now explains its abbreviations under "Terms on this page": 92 plain-language definitions (METAR, GSD, HAE, PLSS, and more), each with its expansion and a cited source. A build gate stops any new label from using an undefined abbreviation. Two labels were reworded to plain language (motor and speed-controller efficiency; the station part of the daily file name).
Fixed VLOS guidance now takes ground visibility as at most 5 km, as EASA's procedure and the German LBA guidance assume, so VLOS never exceeds 1,500 m. Without a visibility it used only the aircraft's size, so a 10 m multirotor showed 3,290 m. It is now stable, matching the LBA's worked table, and cites EASA's guidelines at Issue 03 (17 July 2025). Tool version 1.1.0.
Fixed The deed plotter now reports in the unit the calls use. It converted every call to US survey feet, so a deed in meters came back in US survey square feet, international feet were shifted by 2 parts per million, and each result carried the legacy-unit warning three times. Mixing US survey and international feet is now refused, as in the traverse tool. Tool version 1.1.0. It is now stable, matching the University of Memphis worked traverse (0.182 ft misclosure, 36,320 sq ft).
Tools: Deed plot, closure, and area
Fixed The coordinate reader had three defects, found by 1,500 independently written strings in ten notations and now fixed: spaced DMS with a one- or two-digit longitude (like 30 34 14.3 N 1 25 23.9 E) was misread as packed aviation notation, so 1°25′ became 125°; signed DMS with degree signs and no hemisphere letters crashed; and one-digit decimal degrees with a hemisphere letter could fail. Tool version 1.1.0. It is now stable.
Tools: Read any coordinate
Changed Battery energy (mAh to Wh) is now stable. It matches the FAA PackSafe worked example (12 V and 8 Ah is 96 Wh) and 19 vectors from a separate implementation. Results are unchanged.
Tools: Battery energy (mAh to Wh)
Changed Large H3 polygon fills run about four times faster on the web and in the MCP server (a 250,000-cell county-sized fill: 12.5 s to about 3 s), because the H3 code is now compiled for speed instead of size. Results are unchanged.
Fixed The TAF decoder now reads the ICAO TX and TN maximum and minimum temperature groups (they were listed as not decoded) and flags a change group that falls outside the forecast's valid period instead of placing it silently (found in a live Geneva TAF). Tool version 1.2.0. It is now stable, agreeing with pytaf on 588 live TAFs and with the FAA Aviation Weather Handbook's example.
Tools: TAF decoder
Result change Present weather now reads as the FAA Aviation Weather Handbook does, with intensity on the precipitation: +TSRA is "thunderstorm with heavy rain" (was "heavy thunderstorm rain"), +SHRA is "heavy rain showers", and VCSH is "showers in the vicinity". Tool versions 1.1.0. The METAR and winds-aloft decoders are now stable.
Tools: METAR decoder, TAF decoder
Replaced vectors: aviation.weather.metar-decode v004
Fixed A differential against python-metar on 612 live reports found three METAR defects, now fixed: cloud layers with /// (type not determined by an automated station) were dropped, BECMG and TEMPO trend groups were applied to the current observation (a forecast wind could replace the observed one), and 9999NDV visibility was not read. The winds-aloft decoder now accepts a whole pasted FB product and takes its levels from the FT header.
Changed The Aviation Weather Handbook is now cited at its current edition, FAA-H-8083-28A (2024), which cancels and supersedes FAA-H-8083-28 (2022). Its altimetry, flight-category, METAR, and FB rules used here are unchanged.
Changed Top of descent and the visual descent point are now stable. Both match the FAA Instrument Procedures Handbook examples (FL 310 to 6,000 ft is 75 NM by the 3-to-1 rule; 300 ft per NM on a three-degree path) and 18 to 19 vectors each from a separate implementation. Results are unchanged.
Tools: Top of descent, Visual descent point
Result change The horizontal curve, vertical curve, and area by coordinates are now stable, so their results no longer carry the EXPERIMENTAL_TOOL warning; the legacy-unit warning on area moved to the first position. They match FM 5-233 (Army Construction Surveying), the Indiana Design Manual vertical-curve example, and Wikipedia's shoelace example. No numbers changed.
Tools: Horizontal circular curve, Vertical curve, Area by coordinates (acreage)
Replaced vectors: survey.cogo.area-by-coordinates v006
Fixed The circular curve now solves from any two elements in every case: external with middle ordinate failed (the formulas lost all precision near zero), and a tangent with a middle ordinate, which fit two different curves, could fail or pick one silently. It now returns the flatter curve and names the other with AMBIGUOUS_INPUT. A chord-definition degree of curve (degree_chord) is accepted as an input, as the survey spec requires.
Tools: Horizontal circular curve
Changed The four aviation nights and local time to Zulu are now stable. The nights match 491 regulatory windows built from US Naval Observatory times at 100 places; Zulu matches Python zoneinfo on 2,388 instants and the Python documentation's Los Angeles examples. Results are unchanged.
Fixed Short and legacy tzdb zone names such as CET, EET, and EST5EDT are now accepted wherever a time zone is asked for; before, they were refused as malformed UTC offsets.
Tools: Local time to UTC (Zulu), Sunrise, sunset, and twilight, The four aviation nights, Mapping light window
Changed Sunrise, sunset, and twilight is now stable, checked against 1,200 US Naval Observatory events at 300 places and dates (all within a minute, 94% to the same minute).
Fixed Sun event times now use the NREL SPA geometric sun instead of the low-precision NOAA series, and each side of the day is decided on its own. A twilight that grazes its altitude is now placed correctly: at 67.19°S on February 1, 2026, evening civil twilight ends at 23:59 local (matching USNO) instead of never. Across 1,200 USNO events every time is within a minute; published vectors are unchanged.
Tools: Sunrise, sunset, and twilight, The four aviation nights, Mapping light window
Changed Weight and balance is now stable. It matches three worked examples in the FAA Aircraft Weight and Balance Handbook (FAA-H-8083-1B): a weighed airplane, a loaded light twin inside its CG range, and a CG in percent of MAC. Results are unchanged.
Tools: Weight and balance
Changed MGRS encode and decode are now stable. They match the Washington Monument example in the FGDC US National Grid standard and 2,000 references from NGA GEOTRANS; where GEOTRANS's own projection is 1.5 cm off near the poles and in Svalbard, PROJ confirms geoprims. Results are unchanged.
Tools: Latitude and longitude to MGRS, MGRS to latitude and longitude
Fixed Stable tools no longer list the EXPERIMENTAL_TOOL warning in geoprims_describe and the catalog; they never emit it. The stable-promotion gate now checks this.
Result change Traverse closure and the combined grid-to-ground factor are now stable, so their results no longer carry the EXPERIMENTAL_TOOL warning; the perfect-closure and elevation-as-ellipsoid-height warnings moved to the first position. Both match published worked examples (University of Memphis traverse notes and NOAA Manual NOS NGS 5) to every printed digit. No numbers changed.
Tools: Traverse closure and adjustment, Combined scale factor (grid and ground)
Replaced vectors: survey.cogo.traverse-closure v006, survey.reduction.combined-factor v006
Changed Ground sampling distance and height for a target GSD are now stable. Both match a published worked example (a 1-inch camera at 120 m gives 3.13 cm per pixel) and 20 vectors each from a separate implementation. Results are unchanged.
Tools: Ground sampling distance (GSD), Height for a target GSD
Result change The geohash encoder, map tile for a point, tile bounds, H3 grid disk, and haversine distance are now stable, so their results no longer carry the EXPERIMENTAL_TOOL warning; the Web Mercator clamp and pentagon warnings moved to the first position. Each matches published worked examples (Wikipedia, the mercantile README, the Bing Maps Tile System, H3 C, and Rosetta Code) and agrees with a separately written library on 250 to 1,000 cases. No numbers changed.
Tools: Geohash encoder, Map tile for a point (XYZ, TMS, quadkey), Map tile bounds, H3 grid disk (k-ring), Haversine distance (spherical)
Replaced vectors: indexing.tile.from-point v006, indexing.h3.grid-disk v007
Changed Pressure altitude, density altitude, runway crosswind and headwind, and the wind triangle are now stable. Each matches the worked examples in the FAA Pilot's Handbook of Aeronautical Knowledge (FAA-H-8083-25C) and at least 20 vectors from a separate implementation. Results are unchanged.
Tools: Pressure altitude, Density altitude, Runway wind components, Wind triangle: heading and groundspeed
Fixed An input so small that it rounds to zero in meters (like 5e-324 ft) is now refused as out of range for every tool, instead of being treated as zero; bounds fuzzing found it through the circular-curve tool. A non-positive curve element is now reported on the field that holds it.
Tools: Horizontal circular curve
Added New navigation tools: rhumb lines, cross-track and along-track distance, fly-by turn anticipation, time-speed-distance with arrival times, closest point of approach, and route legs with true and magnetic courses; and the first geometry tool, polygon area on the ellipsoid.
Tools: Rhumb line distance and course, Destination on a constant course (rhumb line), Cross-track and along-track distance, Fly-by turn anticipation, Time, speed, and distance, Closest point of approach, Route legs, courses, and totals, Polygon area and perimeter on the ellipsoid
Changed Five more tools passed the stable verification bar: geodesic distance and destination (checked against GeographicLib's GeodTest), UTM forward and inverse (checked against exact transverse Mercator values), and the standard atmosphere (checked against a separately written implementation).
Tools: Distance between two points (geodesic), Destination from a start, course, and distance (geodesic), Latitude and longitude to UTM, UTM to latitude and longitude, Standard atmosphere
Result change UTM forward is now stable, so its results no longer carry the EXPERIMENTAL_TOOL warning. The nonstandard-zone warning moved to the first position; no numbers changed.
Tools: Latitude and longitude to UTM
Replaced vectors: geodesy.utm.forward v009
Result change State plane convergence and scale factor in the Hotine oblique Mercator zone (Alaska zone 1) are now computed with Richardson-extrapolated differences. They moved by up to 0.0000001°, well inside the published tolerance, and now agree between the forward and inverse tools.
Result change Sun position is now stable, so its results no longer carry the EXPERIMENTAL_TOOL warning. The UT1 warning moved to the first position; no numbers changed.
Tools: Sun position (azimuth and elevation)
Replaced vectors: time.sun.position v028
Added The site installs as an app and works offline after the first visit, has a command palette (press / or Ctrl+K), and ships a strict Content Security Policy.
2026-09-18
Changed The first six tools passed the stable verification bar: a derivation, an independent worked example, invariant and differential tests, and at least 20 golden vectors each.
Tools: Magnetic declination, Latitude and longitude to state plane (SPCS83), State plane (SPCS83) to latitude and longitude, Geoid height (EGM96), H3 cell for a point, Sun position (azimuth and elevation)
Result change Named IANA time zones like America/Denver are supported, so inputs that returned UNSUPPORTED now resolve to local times.
Tools: Local time to UTC (Zulu), Sunrise, sunset, and twilight
Replaced vectors: time.scale.utc-offset v006, time.sun.events v007
Result change Sun position uses the NREL Solar Position Algorithm (±0.0003°) instead of the NOAA equations (about ±0.01°). Elevation and azimuth changed by up to a few hundredths of a degree.
Tools: Sun position (azimuth and elevation)
Replaced vectors: time.sun.position v001, time.sun.position v002, time.sun.position v003, time.sun.position v004, time.sun.position v005, time.sun.position v006, time.sun.position v007
Fixed Bounds fuzzing found 16 inputs that produced non-finite numbers, a trap, or a hang. Each now returns a clear error and is pinned as a regression test.