diff --git a/Modules/Core/include/mitkNodePredicateGeometry.h b/Modules/Core/include/mitkNodePredicateGeometry.h
index 42c8fd55c5..105bbf1d6e 100644
--- a/Modules/Core/include/mitkNodePredicateGeometry.h
+++ b/Modules/Core/include/mitkNodePredicateGeometry.h
@@ -1,80 +1,83 @@
 /*============================================================================
 
 The Medical Imaging Interaction Toolkit (MITK)
 
 Copyright (c) German Cancer Research Center (DKFZ)
 All rights reserved.
 
 Use of this source code is governed by a 3-clause BSD license that can be
 found in the LICENSE file.
 
 ============================================================================*/
 
 #ifndef MITKNODEPREDICATEGEOMETRY_H_HEADER_INCLUDED_
 #define MITKNODEPREDICATEGEOMETRY_H_HEADER_INCLUDED_
 
 #include "mitkNodePredicateBase.h"
 #include "mitkBaseGeometry.h"
 #include "mitkTimeGeometry.h"
 
 namespace mitk
 {
   class BaseData;
 
   /**Documentation
    @brief Predicate that evaluates if the given DataNode's data object
    has the same geometry (in terms of spacing, origin, orientation) like
    the reference geometry.
 
    One can either check the whole time geometry of
    the date node by defining a referenc time geometry or check against one given
    reference base geometry. If the predicate should check against a base geometry,
    you can specify the timepoint of the data's time geometry that should be checked.
    If no timepoint is defined the predicate will evaluate the data geometry in
    the first timestep.
    Evaluates to "false" for unsupported or undefined data objects/geometries.
 
    One can specify the tolerance/precision of the check via SetCheckPrecision().
    @remark The default tolerance is 1e-6 and therefore not as strict as mitk::eps. The reason is,
    that, for the typical use of the node predicate, mitk::eps would be to pedantic. We
    often encounter floating point differences and practically it makes no difference e.g.
    if two images differ something like 0.000001 mm in size or spacing.
    @ingroup DataStorage */
   class MITKCORE_EXPORT NodePredicateGeometry : public NodePredicateBase
   {
   public:
     mitkClassMacro(NodePredicateGeometry, NodePredicateBase);
     mitkNewMacro1Param(NodePredicateGeometry, const TimeGeometry*);
     mitkNewMacro1Param(NodePredicateGeometry, const BaseGeometry*);
     mitkNewMacro2Param(NodePredicateGeometry, const BaseGeometry*, TimePointType);
 
     itkSetMacro(CheckPrecision, mitk::ScalarType);
     itkGetMacro(CheckPrecision, mitk::ScalarType);
 
     ~NodePredicateGeometry() override;
 
     bool CheckNode(const mitk::DataNode *node) const override;
 
   protected:
 
     /**Constructor that is used configures the predicate to check the reference geometry against the first data timepoint.*/
     NodePredicateGeometry(const BaseGeometry* refGeometry);
     /**Constructor allows to define the timepoint that should be evaluated against the reference.*/
     NodePredicateGeometry(const BaseGeometry* refGeometry, TimePointType relevantTimePoint);
     /**Constructor that is used configures the predicate to check against the whole time geometry.*/
     NodePredicateGeometry(const TimeGeometry* refGeometry);
 
     BaseGeometry::ConstPointer m_RefGeometry;
     TimeGeometry::ConstPointer m_RefTimeGeometry;
     TimePointType m_TimePoint;
     /**Indicates if m_TimePoint should be regarded or always the first timestep should be used.*/
     bool m_UseTimePoint;
     /**Precision that should be used for the equal checks.*/
     mitk::ScalarType m_CheckPrecision;
   };
 
-  constexpr double NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_PRECISION = 1e-6;
+  /* Changed NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_PRECISION from 1e-6 due to
+     T28127. If https://github.com/QIICR/dcmqi/issues/414 is clarified we could
+     change it back*/
+  constexpr double NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_PRECISION = 5e-5;
 
 } // namespace mitk
 
 #endif /* MITKNodePredicateGeometry_H_HEADER_INCLUDED_ */