AERONOVA · TOTAL AIRPORT INTELLIGENCE · RELEASE 0.13

Find a location.
Draw the opportunity.

17 October 2026 · Integrated site selection and boundary workflow.

Open the map workspace → · Open the bidding assistant →

What changed

A single embedded OpenStreetMap workspace replaces the separate airport-search and map panels. Search by airport name, IATA/ICAO code, place, address, decimal coordinates or an OpenStreetMap location link. Preview a result, place a pin, draw a boundary, finish, refine vertices and freeze the site into a new bid assessment.

Catalog airport identity is retained when its pin is kept. Moving the pin produces a manual study site. A valid study boundary and its approximate area/perimeter are saved with the case and included in the comprehensive report. Current assessments remain unchanged while a separate map draft is edited.

Controls include Pan, Place pin, Draw, Edit, Finish, Undo, Clear, Expand, coordinate entry, individual vertex editing, draft recovery and validated GeoJSON export. No duplicate planning or numerical engines were added.

Map validation

Sixteen additional core checks cover airport ranking, accent-insensitive search, coordinate parsing, safe geocoder normalization, spherical measurement, boundary validity and report inclusion. Browser tests use mocked tiles and geocoder replies to avoid automated harvesting of public map services. An interactive browser check separately confirmed real Photon results for Lyon and rendered OpenStreetMap airport tiles.

Existing suite regression

The existing bid workflow is checked for evidence review, ARDI forecasting, the supplied Lyon GENESIS schedule, capacity-linked quantities, costs, source hashes and invalidation. The specialist entry-point check covers Yardstick, ARDI, GENESIS, AeroPlanner, PowerPlan Pro, Meridian, RARE, AeroLens, TERRA-GENESIS and Integrated, plus browser PDF extraction and boundary checks. Detailed local and post-publication test records accompany the release package.

Provider and measurement basis

Airport identity uses the packaged OurAirports catalog, whose snapshot basis remains visible in the evidence. Place lookup uses Photon with explicit submitted queries, session caching, a minimum request interval and visible service errors. Exact airport-code lookup and coordinate parsing do not need the place provider. OpenStreetMap tiles load only when the map is visible and use normal browser caching and attribution.

Public map and place services have no availability guarantee. The replaceable endpoints and limits are in bid/map-services.json. For larger production usage, configure an appropriate dedicated service. There is no offline tile download or bulk search feature.

Boundaries are one closed ring with 3–500 vertices, no holes or self-intersections, and a site pin inside/on the ring. Vertices must be within one degree of the pin; polar and antimeridian studies are not supported. Area uses a spherical approximation and perimeter sums great-circle edge lengths with mean Earth radius 6,371,008.8 m. Neither represents a cadastral survey, certified airport boundary or safeguarded airspace.

GeoJSON export keeps full coordinate precision. The case continues to use browser-local storage. This map update does not introduce a hosted AI credential service or alter the existing specialist-engine assumptions.

OpenStreetMap tile policy · Photon service documentation