Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail
poc/build/interior.json is our drawing of the inside of the Orlando Sanford terminal. It is also the first load of the location registry (R49), in the shape set by poc/build/location-registry.schema.json. This note records where every element came from, the terms that apply to the source, the owner's decision, and the limits on use.
Use: the bid copy only
The model is for the bid copy only. It does not go into any public version of the POC, any public film or any public page until the rights are confirmed. The label on every view of it reads: "Interior drawn by us from the airport's public map; positions approximate; not the Authority's drawings."
The airport's own terms: the site footer links to https://flysfb.com/legal. That page says "By accessing and using this web site, you agree to be bound by the following terms and conditions," and that the materials are provided "as is". It says nothing about maps, data, copying or scraping.
Mappedin's terms: "Mappedin Inc. Website & Subscription Terms & Conditions", last updated August 5, 2026 (https://info.mappedin.com/terms). They bind Mappedin's customers, here the Sanford Airport Authority, and require the customer to put these terms on its end users:
"You may only use or reproduce any digital maps, floorplans or data contained therein" "for your own immediate, personal and non-commercial use."
"The framing, scraping, datamining, extraction or collection of the digital maps, floorplans or data contained therein" is prohibited "in any form and by any means whatsoever." "Furthermore, you may not mirror any such materials."
Customers must stop end users from obtaining "commercial benefits from any Digital Map produced from the Mappedin Technology", and nobody may "create derivative works" of the Mappedin technology.
An older "Software Access License for End Customer" (dated 01/11/2021, https://www.mappedin.com/salec) also limits use to the "personal and non-commercial use" of its users.
The owner's decision
On 2026-10-30 the reading of these terms went to the owner before the model was built. His answer: "collect anyway. We have been here 300 times, in and out on flights and more. Visual inspection is feasible." The model was then built on these conditions:
Every element records two sources: "observed on flysfb.com/maps (Mappedin viewer), read 2026-10-30" and "to be confirmed by visual inspection on site (owner's visits; site tour 2026-11-06)". Every element carries trust.confirmed_on_site: false until a visit on site confirms it.
Polite pacing. Only what the public page loads for any visitor was read. The page's API key was never called directly, stored or reused outside the page's own session.
No tiles, artwork, photographs, logos or the page's geometry were copied. The descriptions on the place cards were not copied. The repo holds names, plain-words locations, categories and our own positions and corridors.
How it was read and drawn
The page: opened in a headless browser, one session at a time, with pauses of one to three seconds between actions. Every category list was walked, each place opened as a visitor would open it, and the name, the plain-words location ("Near Gate 11, Level 2, Terminal") and the categories were noted. The screenshots taken for reference stayed in the session scratchpad and are not in this repo.
Positions: for each place, we measured where the page draws its marker after the camera is turned to look straight down. We then mapped that point into one fixed reference view by matching image features between the two views.
Registration: the reference view was fitted to the OpenStreetMap terminal footprints the POC already uses (Terminal A, Terminal B, International Arrivals and one unnamed footprint, poc/build/sfb-osm.json). The fit is a similarity transform (scale, rotation, shift). It minimises the distance from the footprint outlines to the terminal floor's edge in the view. The result is in the file's registration block.
Corridors: our own trace of the open floor on each level, drawn as a graph of nodes and edges. Spurs from each place to its nearest corridor node are inferred. The stair or escalator symbols seen at the same spot on both levels are joined as vertical links and marked inferred. The link through the security checkpoint is marked inferred.
Doors: openings drawn on the building outline were detected in the reference views. The map gives them no names, so each carries our label and nameSource: "ours".
Level height: 6 m between Level 1 and Level 2 is our assumption, to measure on site.
Limits
Positions are approximate. The registration error is stated in the file. The floor the map draws and the OpenStreetMap footprints differ at the south annexes and the southwest corner, and that difference sets the outer error.
The map draws four stair or escalator symbols at the same spots on both levels, but they open nothing when clicked and carry no names. Each is in the registry under our label, typed as a stair and marked inferred. The map shows no lifts.
The map does not show plant rooms, electrical panels, escalator pits or fire exits. None is in the model.
Baggage Claim 4 and Baggage Claim 5 are listed by the map with no position. They are in the registry with no position.
The Parking Garage, the Rental Car Center and the Alamo Building are listed. Only places inside the Terminal are on the corridor graph.
What closes each element
A visit on site (the owner's visits; the site tour on 2026-11-06) confirms or corrects each place. The confirmer sets trust.state to "confirmed", confirmed_on_site to true, and fills confirmedBy and confirmedAt. The Authority's own floor plans or building model, once supplied (Q-14), replace this drawing.