API Divots with wind_string: partial translation, missing metric string

  • 2
  • Problem
  • Updated 4 years ago
With language FR, I noticed that current_observation -> 'wind_string' => 'From the Nord at 9.2 MPH Gusting to 9.2 MPH'

There are two issues:

1) The string is only partially translated. It should be something like: "Du nord au 9.2 MPH avec rafales à 9,2 MPH"

2) There isn't a metric version (kph). I suggest 'wind_string_metric' as consistent with similar composite strings...

I haven't checked other languages, but I wouldn't be surprised if they had similar faults.

Thanks.
Photo of tlhackque

tlhackque

  • 3 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 2
Photo of tlhackque

tlhackque

  • 3 Posts
  • 0 Reply Likes
There appear to be other partial/missing translations.

I've found these (again, with French):

current_observation =>
'observation_time' => 'Last Updated on janvier 12, 15:51 EST' is also mixed english and French.

forecast => simpleforecast => forecastday [n] => date => pretty => '10:00 PM EST on January 12, 2014', Here, monthname, monthname_short and the other individual fields are translated, but the 'pretty' string is entirely in English.

The 'icon' field in the same structure is also untranslated - I assume it is intended for ALT text (that's how I use it). In that case, it should be translated as well.

Finally (so far), the termsofService URL returns a page in English. I currently link the credit line to that URL. I know it's a pain to translate TOS, but I think that if not this page, some localized URL should be returned to put my customers on notice for you.

These divots aside, so far the API has been usable.

Oh - one more item: the icon_urls are http. If accessed via https, the certificate is invalid. This makes the API difficult to use on a server-built secure page. I fetch the icons and convert them to data: uris on demand. That's an acceptable work around for me, though it would be better if the client could fetch them.

Thanks again.
Photo of kilkenny

kilkenny

  • 1 Post
  • 0 Reply Likes
I too would like to see metric versions of the *_string variables. In addition to the wind_string asked about above, other strings ought to have a "metric first" option, ie:

"windchill_string":"6 F (-14 C)"

can have an equivalent:
"windchill_string_metric":"-14 C (6 F)"

Whether it's a separate value like this example, or a parameter in the Request URL to reverse the Imperial/Metric ordering in the existing variables,