In order to consume the AFOD 2.0.0 services, the Data Consumer user must have the appropriate user roles corresponding to the licenses allocated to their organisation.
SERVICE_CONSUMPTION_CONSTRAINT
The authentication requires all users to sign the requests using an X.509 certificate received from eEAD.
Customers can be negatively impacted when data usage is disproportionate and for extended periods. As protection mechanism, AFOD 2.0.0 service will restrict excessive requests originated from the same client.
Reference
AIMSL RefMan ICD External
https://url.witheld
There shall be a service consumption constraint to ensure that a service consumer does not impose undue loads on computer and network resources, for example, by polling it at a higher frequency than the status is normally provided.
Usage is limited as per our Throttling standard policies.
Limited to either:
200 requests per day per unique user.
or
1000 requests per day per unique user.
The API makes use of standard HTTP headers, as specified in the SWIM Yellow Profile, WS Light Service Interface Binding.
Consumers needs to contact METEO FRANCE to register administratively to METGATE_MF.
According to ICAO Annex 3 the meteorological information is retained for a period of at least 30 days from the date of issue. This relates to the information itself and not the request time of the customer.
Consumers needs to contact METEO FRANCE to register administratively to METGATE_MF.
According to ICAO Annex 3 the meteorological information is retained for a period of at least 30 days from the date of issue. This relates to the information itself and not the request time of the customer.