Displaying an Indoor Map

At a glance

Project structure

Source bundle/
└── Dinoseum/
    ├── AppDelegate.swift
    ├── IMDFDecoder.swift
    ├── Views/
    │   ├── LevelPickerView.swift
    │   ├── LabelAnnotationView.swift
    │   └── PointAnnotationView.swift
    ├── IndoorMapViewController.swift
    ├── Styles.swift
    └── IMDFModel/
        ├── Amenity.swift
        ├── Anchor.swift
        ├── Level.swift
        ├── Occupant.swift
        └── Opening.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 6 project/configuration file(s) and 31 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["IndoorMapViewController"]
    N3["MapKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

Dinoseum/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?
    
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into MapKit.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    IMDFArchive *-- URL : baseDirectory
    IMDFDecoder *-- MKGeoJSONDecoder : geoJSONDecoder
    LevelPickerView o-- LevelPickerDelegate : delegate

Ownership evidence

Dinoseum/AppDelegate.swift:13 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?
    
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

Dinoseum/Views/LevelPickerView.swift:10 — representative type boundary

@objc protocol LevelPickerDelegate: AnyObject {
    func selectedLevelDidChange(selectedIndex: Int)
}

The source explicitly defines local protocol relationships: IndoorMapViewController → LevelPickerDelegate, Level → StylableFeature, Unit → StylableFeature, Opening → StylableFeature, Amenity → StylableFeature, Occupant → StylableFeature.

Access control

Reference code

Dinoseum/IMDFDecoder.swift:56 — representative boundary

    private let geoJSONDecoder = MKGeoJSONDecoder()

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Controller: IndoorMapViewController; Delegate: AppDelegate, LevelPickerDelegate; View: LabelAnnotationView, LevelPickerView, PointAnnotationView.
• Protocols: LevelPickerDelegate, IMDFDecodableFeature, StylableFeature.
• Methods: fileURL, decode, decodeOccupants, decodeFeatures, selectedLevelDidChange, awakeFromNib, generateStackViewButtons, levelSelected.
• Files: Dinoseum/AppDelegate.swift, Dinoseum/IMDFDecoder.swift, Dinoseum/Views/LevelPickerView.swift, Dinoseum/IndoorMapViewController.swift, Dinoseum/Views/LabelAnnotationView.swift, Dinoseum/Views/PointAnnotationView.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches MapKit, UIKit, CoreLocation through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation