ASM #17359 - Warngen: it takes long time to get warning areas hatched when switching from Marine Weather Statement to Special Marine Warning
Change-Id: I02d432e4d335069a15700c9dc564bd19dbd14527 Former-commit-id: 3820522a7b6adb79f9eca4e75f66f93779ef7698
This commit is contained in:
parent
960f968bbf
commit
f8f4d8573e
1 changed files with 15 additions and 8 deletions
|
@ -159,6 +159,10 @@ import com.vividsolutions.jts.geom.Polygon;
|
|||
* Jul 01, 2014 DR 17450 D. Friedman Use list of templates from backup site.
|
||||
* Jul 21, 2014 3419 jsanchez Created a hidden button to make recreating polygons easier.
|
||||
* Feb 26, 2015 3353 rjpeter Fixed NPE on clear.
|
||||
* Apr 27, 2015 DR 17359 Qinglu Lin Updated changeTemplate(). The approach for solving slowness issue while switching from
|
||||
* one marine product to another is to skip computing hatching area. The hatching area might
|
||||
* not be as expected if percentage/area is different between the two products. But the
|
||||
* chance for that to occur is trivial.
|
||||
* </pre>
|
||||
*
|
||||
* @author chammack
|
||||
|
@ -1657,6 +1661,8 @@ public class WarngenDialog extends CaveSWTDialog implements
|
|||
.equalsIgnoreCase(lastAreaSource);
|
||||
boolean snapHatchedAreaToPolygon = isDifferentAreaSources;
|
||||
boolean preservedSelection = !isDifferentAreaSources;
|
||||
if (isDifferentAreaSources || !warngenLayer.getConfiguration()
|
||||
.getHatchedAreaSource().getAreaSource().toLowerCase().equals("marinezones")) {
|
||||
// If template has a different hatched area source from the previous
|
||||
// template, then the warned area would be based on the polygon and not
|
||||
// preserved.
|
||||
|
@ -1666,6 +1672,7 @@ public class WarngenDialog extends CaveSWTDialog implements
|
|||
} catch (VizException e1) {
|
||||
statusHandler.handle(Priority.PROBLEM, "WarnGen Error", e1);
|
||||
}
|
||||
}
|
||||
// Properly sets the "Create Text" button.
|
||||
setInstructions();
|
||||
}
|
||||
|
|
Loading…
Add table
Reference in a new issue