Closed jheeffer closed 6 years ago
Old concepts that need forwarding to other concepts:
yearly_co2_emissions_tonnes
=> yearly_co2_emissions_1000_tonnes
how_far_to_the_north
has datapoints in 1700 and 2030, which aren't fetched by current Gapminder Tools and thus interpolation doesn't work. In latest SG it's even removed but Vizabi can't use (numeric) properties on the axes yet so there is no good alternative at the moment.
Blocker imo.
age_at_1st_marriage_women
has data for 1780 which is used in GW to interpolate a value for 1800. In GT we can't do this as interpolation happens client side and client side requests only datapoints between 1800 and 2018. I.e. it won't see 1780 data and thus can't interpolate 1800 using it.
Low hanging solution: fill out interpolated values for 1800 in dataset. Harder solution: make ddfql able to interpolate to min value if earlier values exist.
Update 2018-05-02: Fixed as tools page config does not include 1800-201x anymore. Always full timeseries are queried. If we re-introduce lower bound (e.g. 1800) this issue would regress.
Make an adapter which can covert Gapminder World urls to Gapminder Tools urls.
https://github.com/Gapminder/world-to-tools-url-adapter