## sa_figure6

## Source details

**Canonical URL:** [sa_figure6](https://www.imf.org/en/publications/gfsr/issues/2016/12/31/sa/sa_figure6.csv)

## Other formats

- [Markdown version](/en/publications/gfsr/issues/2016/12/31/sa/sa_figure6.csv.md)
- [Structured JSON version](/en/publications/gfsr/issues/2016/12/31/sa/sa_figure6.csv.json)

---

### Description
- The worksheet labeled "csv" contains HTML content rather than structured CSV data. The first column begins with "<!DOCTYPE html><html dir=ltr lang=en>..." indicating an HTML 404/error page was captured instead of the intended dataset.
- Metadata embedded in the HTML indicates site/system values and timestamps (see "Key statistics and metadata" below).

### Key statistics and metadata
- Worksheet name: "csv"
- rowCount: 439
- columnCount: 1
- Embedded meta values and timestamps (preserve exact text):
  - meta name=parsely-pub-date content=2025-08-26
  - meta name=Date content=2026-08-28
  - meta name=imf_search_date content=2025-08-26T10:31:22Z
  - input id=imfdate name=imfdate value=2025/08/26@10:31:22+00:00/
  - input id=imfembargodatetime name=imfembargodatetime value=2000/01/01@11:00:00+00:00/
- Sample rows show HTML/script fragments exactly as captured, for example:
  - "          function gtag() {"
  - "          dataLayer.push(arguments);"
  - "        }"
  - "          gtag('js'", " new Date());"
  - "          gtag('config'", " 'G-CPJPTDPL31'", " {"
  - "          'page_location': decodeURI(window.location.href.toLowerCase())"
  - Long HTML fragments including navigation, meta tags, and script tags.

### Findings
- The file named sa_figure6 appears to be an HTML error/404 page captured in the CSV worksheet rather than the expected dataset contents.
- The captured HTML includes site framework assets, meta tags, JavaScript snippets, and site navigation markup, not tabular data fields or numeric observations.
- There is no structured CSV row with separate fields beyond a single-column container holding HTML text.

### Recommendations for users and data handlers
- Verify the canonical URL and rerun the data export or download process to obtain the intended CSV/XLSX dataset rather than the HTML error page.
- Check server-side routing or access permissions at the time stamps recorded (see metadata above) to determine why the dataset endpoint returned an error page.
- If programmatically retrieving the file, implement a content-type check (e.g., expect "text/csv" or "application/csv") and validate the first line for CSV headers to detect HTML/error responses early.
- Retain the captured HTML as a diagnostic artifact for troubleshooting (it includes timestamps, page identifiers, and script IDs useful for server logs correlation).

*Source: sa_figure6 — https://www.imf.org/en/publications/gfsr/issues/2016/12/31/sa/sa_figure6.csv*

---


_Source: https://www.imf.org/en/publications/gfsr/issues/2016/12/31/sa/sa_figure6.csv_