awips2/cave/com.raytheon.viz.gfe/help/TextProductUserGuide/notes142.txt
root e2ecdcfe33 Initial revision of AWIPS2 11.9.0-7p5
Former-commit-id: a02aeb236c [formerly 9f19e3f712] [formerly a02aeb236c [formerly 9f19e3f712] [formerly 06a8b51d6d [formerly 64fa9254b946eae7e61bbc3f513b7c3696c4f54f]]]
Former-commit-id: 06a8b51d6d
Former-commit-id: 8e80217e59 [formerly 3360eb6c5f]
Former-commit-id: 377dcd10b9
2012-01-06 08:55:05 -06:00

2 lines
611 B
Text

Some regions are creating Regional product files as a starting point for the local sites. You could simply have a section in your Local file labeled "Overrides from Region" to isolate these changes and keep them separate from your Local overrides. Alternatively, you could implement an inheritance scheme as follows: First, comment out all overrides in the Local file. Then create a Text Utility (Define Text Products Text Utilities window) that has a class e.g. Regional_ZFP, that includes desired overrides. Finally, you can import and inherit this class into your Local file to enable it's overrides.