Un Data API

Support queries answered here.

Hi there and thanks for this really useful api !

i noticed two little issues

1) there is a little error in the documentation here:
http://www.undata-api.org/wiki/filteredquery

the query accepts only
http://undata-api.appspot.com/data/query/{dataset name1}/{country3}/{year2}
and not
http://undata-api.appspot.com/data/query/{dataset name1}/{year2}/{country3}

2) also, i don’t know why, every record is doubled on this kind of query:

http://undata-api.appspot.com/data/query/Population%20annual%20growth%20rate%20%28percent%29/any/2000?user_key=xxx

or

http://undata-api.appspot.com/data/query/Population%20annual%20growth%20rate%20%28percent%29/France?user_key=xxx

Answers look like this, every year appears twice, maybe the data is half-yearly ?

<record>
<field name="Country or Area">France</field>
<field name="Year(s)">1990</field>
<field name="Value">0.5</field>
</record>
−
<record>
<field name="Country or Area">France</field>
<field name="Year(s)">1990</field>
<field name="Value">0.5</field>
</record>
−
<record>
<field name="Country or Area">France</field>
<field name="Year(s)">1991</field>
<field name="Value">0.5</field>
</record>
−
<record>
<field name="Country or Area">France</field>
<field name="Year(s)">1991</field>
<field name="Value">0.5</field>
</record>

thank you

woops, the forum formating engine messed a bit my text :)
hope it’s still understandable…

Issue: the country name "Côte d’Ivoire" is not encoded in UTF8 in query "Population annual growth rate (percent)/" (and maybe other queries if all queries use the same country table).

Issue: corrupted XML on this query:
http://undata-api.appspot.com/data/query/Population%20living%20below%20the%20poverty%20line%20%28percent%20living%20on%20less%20than%20US$1%20per%20day%29/any?user_key=xxx

there’s that text "<2.0" where it should be "2.0"

it’s for the first country "Albania" on query about poverty line

woops actually it’s on every country where the value is "2.0" because it means "less than 2%"

that is a piece of a question: what could be put instead of this special char ?

<2.0 issue noted by webving is big. This breaks xml parsers because a &lt; is not being issued. Malformed xml can’t be parsed by the endpoints unless it’s cleaned up first.