How object mapping works

SKYDB can translate building data between different representations. The API calls this process Object Mapping. It works in both directions: source information can be mapped into the SKYDB data model, while SKYDB objects can be converted back into another schema, data format or human-readable representation.

A source does not need to follow the SKYDB structure. It may provide a text description, an address, JSON from another API, a database record or only a few known properties. The mapper determines which parts correspond to SKYDB fields and related objects. For buildings, this may include names, location, height, floors, usage, status, dates, companies or regions. It can also report information that cannot be mapped clearly, conflicts with existing data or is missing altogether.

Developers access this functionality through the SKYDB API. A mapping request specifies the source data and the representation it should be mapped to. The response contains the resulting values and object references, together with mapping issues where relevant. Reverse mapping uses the same principle and converts an existing SKYDB object into the requested target representation.