Known Issue for Geospatial Features Beta

The following are known issues for Geospatial Features Beta and its workarounds, if available:

  • A warning displays in the browser console for any page or details panel that contains geospatial record types in mastering projects.

    • Workaround available. Please contact [email protected] to learn more. (Internal reference: SUP-4362)
  • Error when attempting sorting by a geospatial type attribute.

    • Version affected: 2020.001
    • The Pair details view for a record pair that uses the Relative Hausdorff similarity shows the similarity score in place of a map view
    • Workaround available. Please contact [email protected] to learn more. (Internal reference: SUP-4663)
  • Most frequent values are not showing up for a geospatial type field on a profiled attribute on the Schema Mapping page. (Internal reference: DEV-11886)

  • The schema mapping suggestion fails if a geospatial record type attribute is present. (Internal reference: DEV-11658)

  • Export is failing on a dataset with geospatial data. (Internal reference: DEV-11899)

  • The Pair details view for a record pair that uses the Relative Hausdorff similarity shows the similarity score in place of a map view

    • Workaround available. Please contact [email protected] to learn more. (Internal reference: SUP-4663)
  • On the Clusters page, when you select a different cluster while the map view is open Tamr does not automatically refresh the map. (Internal reference: SUP-4551)

  • While it is possible to use the Tamr user interface to change the type of a unified attribute from, or to, geospatial, these changes are not supported and will result in job failures.

    • Workaround available. Please contact [email protected] to learn more. (Internal reference: SUP-4927)
  • In order for polygons and multi-polygons to display, you must follow the right-hand rule when specifying the orientation. (Internal reference: SUP-5085)


Did this page help you?