You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For our three public services, we want to add the corresponding High Flow Magnitude (HFM) layer to the service as a sublayer, so users do not need to ingest two services to get the complimentary data to know where FIM is located and see FIM. The three public FIM Services and associated HFM:
For the existing public FIM .mapx files, I've created new HFM group layers (default - disabled visibility) named to mimic the source HFM service (ie: Medium-Range Max High Flow Magnitude Forecast with a 5 Days - Est. Annual Exceedance Probability layer). Screenshot below.
I've imported the symbology from the existing HFM services to the new HFM sublayers to ensure consistency.
I'm also updating the public FIM .yml file service descriptions based on the existing HFM service descriptions.
To Do:
Create new feature branch.
Edit the public fim ANA Inundation Extent .mapx and .yml below to include the ANA High Flow Magnitude service as a sublayer and an updated service description.
Edit the MRF NBM 5 Day Max Inundation Extent .mapx and .yml below to include the MRF NBM 5 Day Max High Flow Magnitude service as a sublayer and an updated service description.
Edit the RFC Based 5 day Max Inundation Extent .mapx and .yml below to include the RFC Max Forecast and RFC based 5 Day Max Streamflow services as sublayers and an updated service description.
For our three public services, we want to add the corresponding High Flow Magnitude (HFM) layer to the service as a sublayer, so users do not need to ingest two services to get the complimentary data to know where FIM is located and see FIM. The three public FIM Services and associated HFM:
The text was updated successfully, but these errors were encountered: