Report that uses templates and can translate properties with $propertyKey$, attributes in between @AttributeID@ and special tags in between %SPECIAL_TAG%

List of special tags on main level:


Tags main level:

%SUB_LOCATIONS(subLocationsStructureId)% for each sub location the text of the template belonging to the sub locations structure will be inserted. Within this template more tags can be translated.
%LOCATION_ID% location id of main location
%LOCATION_NAME% location name of main location
%FORECAST_TIME% forecast time of main time series => (system time when main time series has been saved)
%EXPIRY_TIME% forecast time + 30 hours
%CURRENT_TIME% real world time -> moment of translating this tag

%PHASE% this tag will be translated to the overall PHASE which is a combination of the PHASE of all sublocations => 

no sublocations with a phase => no overall phase
all sublocations new => NEW
all sublocations final => FIN
all combinations of new update and final => UPD


%WATCH_RELATED_LOCATIONS% for each sub location the text of the template belonging to the (first configured) sub locations structure will be inserted. Within this template more tags can be translated. The difference with the sub locations tag is that only for locations with an active WATCH PHASE are included.

%WARNING_SUBCATCHMENTS% for each sub location the text of the template belonging to the (first configured) sub locations structure will be inserted. Within this template more tags can be translated. The difference with the sub locations tag is that only for locations with an active WARNING PHASE (based on connected forecast locations) are included. 

%WARNING_FORECAST_LOCATIONS% for each sub location belonging to the sub locations structure (connected to the first configured sub locations structure) the text of the sub locations structure template will be inserted. Within this template more tags can be translated. The difference with the sub locations tag is that only for locations with an active WARNING PHASE are included.


%WARNING_OBSERVATION_LOCATIONS% for each sub location of the sub locations structure (connected first configured sub locations structure) the text of a hardcoded xml template be inserted. Within this template more tags will be translated:
            <area aac="%EXTERNAL_OBSERVATION_LOCATION_ID%" description="%OBSERVATION_LOCATION_NAME%" type="river-obs-site" parent-aac="%FLOOD_WARNING_AAC%">
                <forecast-period start-time-local="%FORECAST_TIME(issueTimeLocal)%" end-time-local="%FORECAST_TIME(issueTimeLocal)%" start-time-utc="%FORECAST_TIME(issueTimeUtc)%" end-time-utc="%FORECAST_TIME(issueTimeUtc)%">
                    <element type="obs_site_description">%OBSERVATION_LOCATION_NAME%</element>
                    <element type="obs_site_latitude">%LATITUDE%</element>
                    <element type="obs_site_longitude">%LONGITUDE%</element>
                    <element type="obs_river_height">%LEVEL%</element>
                    <element type="observation_time">%TIME_STEP%</element>
                    <element type="obs_river_height_tendency">%TENDENCY%</element>
                </forecast-period>
            </area>


%FLOOD_WARNING_TITLE% tag that is constructed based on the overall WARNING PHASE and overall SEVERITY of the main location. Can be overruled by property with key => floodWarningTitle

%WATCH_NEXT_ISSUE% will be translate to a filled xml element based on WATCH PHASE. 
When Final => <text type="warning_next_issue">This is a final Flood Watch, no further watches will be issued for this event</text>
When New or Update => <text type="warning_next_issue">The next Flood Watch will be issued by %s</text> where %s will be replaced by the time stored in date time property NEXT_ISSUE_TIME

%CAP_REFERENCE% currently translated to <text type="cap_reference">PREVIOUS ISSUED WATCH</text> when PHASE not is New

%REISSUE_COMMENT% translated to <element type="reissue_comment">%s</element> where %s is translated to property value of REISSUE

%AREA_INCLUDED_TITLE% translated to <text type="area_included_title">Catchments likely to be affected include:</text> when PHASE is New or Update

%AREA_REMOVED_SUMMARY%

  • when there are no locations where flooding is no longer expected AND there are no locations for which warnings are current this tag is translated to empty text.
  • when there are no locations where flooding is no longer expected translated to <text type="area_removed_summary"><p>Flood Warnings are current for the following catchments: %s</p></text> where %s is replaced with all locations with warnings current
  • when there are no locations for which warnings are current this tag is translated to: <text type="area_removed_summary"><p>Flooding is no longer expected in the following catchments: %s</p></text>where %s is replaced with all locations for which flooding is no langer expected.
    When there are locations with warnings current and locations for which flooding is no longer expected it will be a combination:
                    <text type="area_removed_summary"><p>Flood Warnings are current for the following catchments: %s</p>
                    <p/>
                    <p>Flooding is no longer expected in the following catchments: %s</p></text>


Tags sub location level

%PARENT_ATTRIBUTE(attributeId)% attribute of main location with attribute id between parentheses
%PRODUCT_LOCATION_ID% Location id of main location
%LOCATION_ID% location id of sub location 
%LOCATION_NAME% name of sub location
%LOCATION_PHASE% watch phase of sub location -> stored in property with key "phase"
%WARNING_PHASE% warning phase of sub location -> depends warning severity and previous warning severity
%WARNING_SEVERITY% severity for sub location based on water level and minor moderate major attribute values
%WATCH_SEVERITY% severity for sub location based on property with key "severity"
%SUBCATCHMENT_HEADLINE% translated to sentence based on severity and phase. Can be overruled in property with key "subcatchmentHeadline"
%CONNECTED_LOCATIONS% for each forecast location connected to the sub location with PHASE new, update or final an element <area aac="%s" phase="%s" description="%s" type="river-site"/> will be added with %s translated to attribute with id "FWL_FOR_ID", phase, forecast location name
%LOCATION_INDEX% the index of the sub location being translated
%FORECAST_TIME% forecast time of main time series => (system time when main time series has been saved)
%EXPIRY_TIME% forecast time + 30 hours
%CURRENT_TIME% real world time -> moment of translating this tag


  • No labels

Disclaimer