If applicable, please label with relevant service in ingest.
Trying to subscribe to origin/a/wis2/eu-eumetnet-femdi/data/recommended/weather/surface-based-observations/synop works.
How often messages are sent ? So far, connection is OK, but, nothing received.
And I get some disconnections every now and then. It is a typical sign that the authorization on the broker is incorrect.
Is mquser allowed to subscribe to origin/a/wis2/eu-eumetnet-femdi/data/recommended/weather/surface-based-observations/synop ?
I will configure the subscription for the wis2dev environment when my test subscription works.
Then, I think there is some confusion on the rules for the Topic Hierarchy.
What is allowed and what in not allowed is exactly the same for core and recommended data
At the time of writing data/recommended/weather/surface-based-observations/synop is valid and data/recommended/weather/surface-based-observations/surface_observation is invalid. So, you should not use it !
Last, based on previous discussions, I thought that the centre-id name would NOT be -femdi but -something were something is a domain like observation or radar or...
Will that stay like that ?
If applicable, please label with relevant service in ingest.
Trying to subscribe to origin/a/wis2/eu-eumetnet-femdi/data/recommended/weather/surface-based-observations/synop works.
How often messages are sent ? So far, connection is OK, but, nothing received.
And I get some disconnections every now and then. It is a typical sign that the authorization on the broker is incorrect.
Is mquser allowed to subscribe to origin/a/wis2/eu-eumetnet-femdi/data/recommended/weather/surface-based-observations/synop ?
I will configure the subscription for the wis2dev environment when my test subscription works.
Then, I think there is some confusion on the rules for the Topic Hierarchy.
Last, based on previous discussions, I thought that the centre-id name would NOT be -femdi but -something were something is a domain like observation or radar or...
Will that stay like that ?