API Query Building Approach

I need to extract ~50 metrics from the UIS API. As the metrics are all built using slightly different dimensions, the only way I can currently achieve this easily is by making ~50 API requests. Is there something I am missing or is this the only way to query the API? (i.e. Is there a recommended approach for thinking about the query that I need to make?) Best Regards, Josh

Comments

  •  
    As an example, 5 of the indicator IDs I need are: ROFST.1.cp, CR.2, PTRHC.2t3, FOSGP.5t8.F500600700, MSEP.5t8
    Posted by Hidden Tue, 04 Dec 2018 15:41:24 GMT
  •  
    Hello, I looked at the indicators (metrics) definitions and they have diverse definitions using many different dimensions. That's why I suggest that you continue to create one request per metric. I know this is not ideal and we're currently looking for ways to improve that. However, building a one request for 2 or more metrics currently has the following risks: 1. You'll pull more data than you need. This could be much more data depending on your dimension selection. 2. You'll run into the current data limit of 10,000 observations per request. It would help us if you can share more info about your use-case and what you're trying to achieve so that we hopefully can help you better. Best.
    Posted by Hidden Wed, 05 Dec 2018 14:39:13 GMT
  •  
    Thanks for getting back to me - that was pretty much what I expected. I just wanted to check that I had not missed anything obvious as this is the first API that I have come across where the response is based on the dimensions you required (rather than just inputting a single, unique identifier for an indicator). My use case is that I am trying to build an index which is an aggregation of multiple indicators (including multiple from UNESCO). Once established, the index (and therefore the call to the API) will only be updated once a year. However, during the index development process, is it likely that there will be multiple iterations. I anticipate that we will start with ~50 indicators which makes the 100 indicators / hour limit quite constraining. Do you have any suggestions?
    Posted by Hidden Wed, 05 Dec 2018 14:46:07 GMT
  •  
    If understand correctly and please correct me if I’m wrong, you’re pulling data from various sources to create new indicator(s) which you will then publish elsewhere. Unfortunately I don’t have any other suggestions for now. However, we’re currently looking for way to improve our API so thanks for sharing your valuable feedback and use case.
    Posted by Hidden Wed, 05 Dec 2018 14:59:35 GMT


You're not signed in. Please sign-in to report an issue or post a comment.