Type mapping enables a unified representation of an Ontology across Foundry and Gotham that users manage within Foundry's Ontology Manager application. Users can create new Gotham types based on existing Foundry object types, property types, and shared property types which remain synchronized as an Ontology evolves over time. After completing the type mapping process, Gotham will be able to query Foundry object types and their metadata through the Object Set Service - a Foundry backend service which supports object data searching, filtering, aggregating, and loading.
Type mapping is only available for enrollments using both Foundry and Gotham and must be enabled by a platform administrator before use. Once enabled for a Foundry Ontology, type mapping cannot be disabled. Only one Foundry Ontology per Gotham install can have type mapping enabled. Contact Palantir Support for assistance with type mapping enablement.
To integrate data in your Foundry Ontology with Gotham, you will first need to toggle on type mapping for your object type of interest within Foundry's Ontology Manager by following the steps below:
Allow objects of this type to be accessed from Gotham applications
.Type mapped objects must contain a Geohash
property to display on a Gaia map. The property can be native to the object type's backing dataset(s) or derived from a latitude/longitude pair or GeoPoint
using Pipeline Builder's Convert GeoPoint to Geohash transform feature.
Once you toggle on Gotham Integration, you can follow the steps below to create a new Gotham object type derived from an existing Foundry object type, specify the object type's Parent category, and configure its Property types:
Entity
(such as a person, organization, or vehicle), Event
(such as a flight, meeting, or concert), or Document
(such as a PDF file, text document, or report) based on your use case.Mapped
tag next to the property's name once you complete that configuration on a given property.
Assign to shared property
enables you to select an existing shared property to map against.Promote to shared property
creates a new shared property for use by other objects.Create a local clone of the property in Gotham
creates a duplicate of the selected property in Gotham that is compatible with its applications.Do not map property to Gotham
is the default option - Foundry properties you do not map will not propagate in the Gotham ontology.After you save your changes to the Ontology, scroll back up to the Gotham Integration section of the Capabilities page of your object type. You will now see a Gotham URI
assigned to the object type and be able to view the Installation status
reported by Gotham.
Foundry's Ontology Manager will display one of the following installation statuses:
Ready to integrate
: An object type is ready for type mapping to enable Gotham integration.Installation in progress
: The object type's installation process is underway.Installation complete
: The installation process is complete, so the object type is available for use in Gotham.Installation failed: {failureMessage}
: The object type's installation failed at least once and will be retried on the next installation run. The {failureMessage}
outlines the reason for failure. Common installation failures include:
Once your object type's installation status reads Installation complete
, you will be able to search for and use your object type in Gotham's applications.
To deprecate a type mapped object type in Gotham, you can delete the object type in Foundry's Ontology Manager. Once deleted in Foundry, the corresponding object type and its property types will not be accessible in Gotham or available to its applications.
Gotham models Foundry dataset security and markings, meaning that Foundry data made available in Gotham through type mapping carries over the same access controls and classification.