* Introduced (extension)methods to easily identify a HydraulicBoundaryDatabase with imported or calculatable locations. * Renamed Resource name. * If no database with calculatable locations has been coupled, the HydraulicBoundariesGroupContext doesn't have children for GrassCoverErosionOutwards. * More uniform tooltips for dealing with no hydro database with calculatable locations coupled. * Introduced TestHydraulicBoundaryDatabase in Ringtoets.Common.Data.TestUtil and reused it where similar classes were created in inner scopes of unit tests. Related to Issue [WTI-1013]
Loading ...