Child pages
  • API Statistics - migrating from JSON web service to API Statistics

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • There are methods and parameters that are decommissioned. See this chapter for more information.

  • There are differences in the JSON format. See this chapter for more information.

Differences between the 1.1 and 2.1 WDDS versions

Initial modification

...

  • .

...

  •  

...

  • "title" has been renamed to "label" on the root-level

  • “updated” is used instead of “lastUpdateDate”

  • All non-standard properties (datasetID, language, agency, description, status) have been moved inside “extension” section

  • The standard “status” property has been updated to include any metadata information at the observation level

  • The possible values of “class” have been updated to include the “dataset” response instead of “bundle” (“bundle” was an accepted value before version 2.0)

JSON-stat modifications

  • JSON-stat 2.0 support in WDDS:

    • The “version” property has been added with the value “2.0”

    • The “id”, “size” and “role” properties have been moved from the dimension level to the dataset level

  • JSON-stat status property:

    • The “status” property is not displayed in case it contains no information

  • JSON-stat error message change for too voluminous extractions:

    • “Too many categories have been requested. Maximum is 50" error message is displayed in case the extraction to be retrieved is too big. It replaces the previous error message “Maximum 50 datasets can be retrieved at a time” or the response of the query builder “Maximum 50 sub-indicators can be retrieved at a time. Please filter your selection”

  • JSON-stat error specification:

    • the communicated error message is in JSON format instead of plain text. The error elements are:

      • status: The HTTP status code

      • id: The provider’s internal error code (optional)

      • href: A link to a web page where information about this error is published (optional)

      • label: A short descriptive text about the error

Example:

Code Block
{ "error": [\{"status": 400,"id": 100,"label": "NO_RESULTS: No data found"}]}
  • JSON-stat HREF element contains all parameters:

    • The HREF property at the root contains the URL of the request

  • JSON-stat “updated” property contains a date instead of timestamp:

    • if no time is specified, the value of "updated” should contain a date and not a timestamp with 0 values set for time

  • JSON-stat “source” value is “Eurostat”, instead of “ESTAT”.

Anchor
DECOMMISSION
DECOMMISSION
Methods, parameters and elements

...

changes in API Statistics

The table below are lists the methods, parameters and elements that will be decommissioned are removed in API Statistics:

target

method


filterNonGeo

method


getRegionalCategorization

method

The "geo_categorical" parameter is used for the UNICODE which won’t be supported anymore.

getCountryLabel

method

The "country_label" parameter is used for the UNICODE which won’t be supported anymore.

callBack

method

callBack is replaced by CORS.

precision

parameter

The "precision" parameter is used for the UNICODE which won’t be supported anymore.

shortLabel

parameter


groupedIndicators

parameter


unitLabel

parameter


HREF

Response JSON-stat element

Not used.

...