Index: DamClients/DamUI/trunk/doc/Differences with previous release.txt
===================================================================
diff -u -r1715 -r1719
--- DamClients/DamUI/trunk/doc/Differences with previous release.txt	(.../Differences with previous release.txt)	(revision 1715)
+++ DamClients/DamUI/trunk/doc/Differences with previous release.txt	(.../Differences with previous release.txt)	(revision 1719)
@@ -48,4 +48,7 @@
 This issue has been solved, so the safety factors in design calculation with geometry adaption will be different than in the 15.1 release version. The new answers are the correct answers.
 
 MWDAM-1273
-See MWDAM-1219 above as this has the same cause for the problem: In Old DAM, the determination of the regional scenarios is done based on een suface line given in global RD coordinates. This while all plline data is local. So trying to find the proper phreatic level for any given point of the surface line ALWAYS results in the last level of line PL1 as the point of the surfacel line is way betong the PL1 line. The new version has all data in local coordinates so the proper phreatic level is found, resulting in a better uplift factor and therefor other results (amongst which the proper status for hydraulic shortcut).  
+See MWDAM-1219 above as this has the same cause for the problem: In Old DAM, the determination of the regional scenarios is done based on een suface line given in global RD coordinates. This while all plline data is local. So trying to find the proper phreatic level for any given point of the surface line ALWAYS results in the last level of line PL1 as the point of the surfacel line is way betong the PL1 line. The new version has all data in local coordinates so the proper phreatic level is found, resulting in a better uplift factor and therefor other results (amongst which the proper status for hydraulic shortcut).
+
+MWDAM-1274
+In v15.1, in the determination of regional assessment scenarios, extending the 1D geometry to the surface level (when needed) was done by stretching the top layer. This should have been done by adding a layer on top of the original top layer with DikeEmbankmentMaterial as material. In v18, this correct way is implemented. Note that the difference in results may be neglectable is most cases.