CAMS GA Data Access by Razinger
•
0 j'aime•266 vues
How to access CAMS data and products?
Recommandé
Contenu connexe
Plus de Copernicus ECMWF
Plus de Copernicus ECMWF (20)
CAMS GA Data Access by Razinger
- 7. BETA
- 12. • • • • • • • •
- 13. 3 March
- 14. • • • • •
- 15. • • • • • •
- 16. • • • • •
- 17. • • • •
Notes de l'éditeur
- my name is and I would like to show you how we access data and products which are generated by CAMS.
- sketch the scale of data sets and the challenge to share it:
- poišči boljšo sliko
- In our day to day work we are mostly dealing with knowledgable users What would be the ideal journey of a user without any prior awareness of CAMS and Copernicus? -> semantic web search queries Of course everybody would be happy if our datasets can be discovered as simple as this If you try to type something like this into a search engine CAMS products don‘t appear on the first two pages. So something that we defenitety need to improve on. Ok, let‘s take a easier case of someone who has already heard about CAMS and want to know more. What king of questions does such potential user has?
- We‘ll hear more about what users are actually asking in Karl‘s talk but here are some questions that surely interest a potential user. Free, full and open data policy
- Federated approach to data delivery. Zoo of data serving solution, some of the popular datasets available in more than one way. Different level of operational support. Different kinds of access, interactive, batch The real problem was that this is done ad-hoc and out of convenience rather that from a strategic plan which makes it difficult to harmonize it. Common user registration and statistics monitoring is still a distant dream.
- Highly available infrastructure which is shared with ECMWF‘s ecCharts system. The data is kept in MARS, ECMWF‘s tape-based meteorologial archive or in case of smaller volume on disk. Size of request is limited to 20 GB, for huge ones Web API access should be used
- At the beginning clash of cultures between NWP community on one side and atmospheric composition and air quality communities on the other. We made a few attempts to introduce CF convention as you know it‘s a bit like perl – there‘s more than one correct way to do it and the problem was each group was using their own (completely valid) but non-compatible flavour. Lack of good common format validation tools made this difficult – producers interested in science, not to study in details specification documents. If you are really paranoid provide sample code In including more observational data and improving the model we produce a lot of experimental datasets which are not suitable for wider distribution. However there are users who can understand and accept these limitation and give us a valuable feedback.