com.airplaneian.contrail.temp.defs

airplaneian.com

Schema Diff

+8 -8

From

CID
bafyreialgthhl6a...
Indexed At
2026-07-25 18:50 UTC
View this version

To

CID
bafyreiacsplrjy4...
Indexed At
2026-07-26 02:16 UTC
View this version

Compatibility Analysis

Backward Compatible

No changes detected.

1 1
{
2 2
  "id": "com.airplaneian.contrail.temp.defs",
3 3
  "defs": {
4 4
    "place": {
5 5
      "type": "object",
6 6
      "properties": {
7 7
        "geo": {
8 8
          "ref": "community.lexicon.location.geo",
9 9
          "type": "ref",
10 -
          "description": "Coordinates of the place, for landing sites that no identifier system covers, or to disambiguate an ambiguous name. Note that the referenced def requires both latitude and longitude, expressed as decimal-degree strings referenced to WGS84. See the community.lexicon.location documentation for the coordinate conventions. Do not write coordinates that were merely looked up from an identifier already present in this object, because that is reference data about the world rather than an assertion about this flight."
10 +
          "description": "Coordinates, for landing sites that no identifier system covers. Do not write coordinates looked up from an identifier already in this object."
11 11
        },
12 12
        "gate": {
13 13
          "type": "string",
14 14
          "maxLength": 32,
15 -
          "description": "Gate or stand used by this particular flight at this place, as free text ('C19', '44C', 'A2E'). As with 'terminal', this is a fact about this flight rather than about the place. Not applicable to most general aviation operations."
15 +
          "description": "Gate or stand used by this flight at this place, as free text."
16 16
        },
17 17
        "iata": {
18 18
          "type": "string",
19 19
          "maxLength": 8,
20 -
          "description": "IATA location code, three characters, uppercase. For example 'OAK'. Absent for the great majority of general aviation fields. Note that IATA codes are reassigned between airports over time, so a code alone does not identify a place across decades, and it should be paired with 'icao' or 'geo' where possible."
20 +
          "description": "IATA location code, three characters, uppercase, for example 'OAK'. Reassigned between airports over time, so pair it with 'icao' or 'geo' where possible."
21 21
        },
22 22
        "icao": {
23 23
          "type": "string",
24 24
          "maxLength": 8,
25 -
          "description": "ICAO location indicator, four characters, uppercase. For example 'KOAK' for Oakland or 'EGLL' for Heathrow. Preferred over 'iata' for cross-repository matching because ICAO indicators are globally unique and are not reassigned. Many small airfields have none; omit the field rather than guessing."
25 +
          "description": "ICAO location indicator, four characters, uppercase, for example 'KOAK'. Preferred for matching. Many small airfields have none."
26 26
        },
27 27
        "name": {
28 28
          "type": "string",
29 29
          "maxLength": 256,
30 -
          "description": "Free-text name of the place, for landing sites that no identifier system covers: grass strips, private fields, off-airport landings, water landings. Also useful as a human-readable label alongside a code. Carries no matching guarantees, since two records may name the same field differently."
30 +
          "description": "Free-text name, for landing sites that no identifier system covers. Carries no matching guarantees."
31 31
        },
32 32
        "faaLid": {
33 33
          "type": "string",
34 34
          "maxLength": 8,
35 -
          "description": "FAA Location Identifier, for United States airfields that have one. For example '1G5'. Many US public-use fields have an FAA LID and no ICAO indicator at all, which is why this is a separate field rather than a fallback written into 'icao'."
35 +
          "description": "FAA Location Identifier, for United States airfields that have one, for example '1G5'. Many US fields have this and no ICAO indicator."
36 36
        },
37 37
        "terminal": {
38 38
          "type": "string",
39 39
          "maxLength": 32,
40 -
          "description": "Terminal used by this particular flight at this place, as free text, since terminal naming is entirely carrier- and airport-specific ('3', 'B', 'Main', 'INTL'). This describes how this flight was handled rather than a property of the place itself, which is why it lives here rather than in any airport reference dataset."
40 +
          "description": "Terminal used by this flight at this place, as free text. A fact about the flight, not about the place."
41 41
        }
42 42
      },
43 -
      "description": "An airport, airfield, or landing site referenced by a flight record. Every field is optional, and absent always means unknown or not applicable, never empty or a placeholder. A grass strip with no published identifier is a valid place carrying only 'name' and 'geo', while a major airport may carry every field. Write the identifier fields wherever they are known, because readers reconciling records of the same flight written by different people match on them. Prefer 'icao' where a place has one, since IATA codes are reassigned over time and many airfields have no IATA code at all. Never invent, translate, or derive an identifier the source did not supply, because an absent code is better than a wrong one. This def describes a place only as far as a flight record needs to, and is not a general-purpose airport reference entry."
43 +
      "description": "An airport, airfield, or landing site referenced by a flight record. Every field is optional, and absent means unknown or not applicable. The identifier fields come from different systems and a place may have any combination of them, so write each one the place actually has. A place with no published identifier is described by 'name' and 'geo' alone."
44 44
    }
45 45
  },
46 46
  "$type": "com.atproto.lexicon.schema",
47 47
  "lexicon": 1
48 48
}

Compare Other Versions

Lexicon Garden

@