## table1_3 — dataset overview

## Source details

**Canonical URL:** [table1_3 — dataset overview](https://www.imf.org/en/publications/gfsr/issues/2016/12/31/c1/table1_3.csv)

## Other formats

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

---

### Dataset description
- Worksheet name: "csv"
- rowCount: 439
- columnCount: 1
- The single column contains HTML/JavaScript content corresponding to an HTTP 404 error page (page title "404") rather than structured CSV data.
- The worksheet includes site metadata tags and inline scripts (for example, meta tags, preload links, analytics snippets, and site navigation HTML).

### Sample content excerpts (verbatim)
- "          function gtag() {"
- "          dataLayer.push(arguments);"
- "        }"
- "          gtag('js'"
- " new Date());"
- "          gtag('config'"
- " 'G-CPJPTDPL31'"
- " {"
- "          'page_location': decodeURI(window.location.href.toLowerCase())"
- "        });</script><byoc-registration components=[] datasources=[]></byoc-registration><script type=text/javascript src=https://cdn.addevent.com/libs/atc/1.6.1/atc.min.js defer=></script><div class=coveo-no-index><input type=hidden id=imfembargodatetime name=imfembargodatetime value=2000/01/01@11:00:00+00:00/>"

### Key findings
- The file contents indicate an error/HTML page was returned instead of the expected CSV dataset.
- The worksheet size and contents (rowCount: 439; columnCount: 1) reflect the HTML lines captured as rows rather than tabular dataset fields.
- The sampleRows show repeated HTML/JavaScript fragments, site metadata (including meta name=parsely-pub-date content=2025-08-26), and navigation markup.

### Implications and recommended actions
- The dataset in this file is not usable for data analysis in its current form because it contains an HTML error page rather than structured CSV records.
- Recommended next steps:
  - Re-request or re-download the dataset from the canonical source to obtain the intended CSV file.
  - Verify HTTP response status and content-type when fetching the file to ensure a valid CSV was returned.
  - If automated ingestion is used, implement checks that validate file headers and minimum expected columns to detect HTML error pages early.
  - Inspect server-side access logs or the source host to determine why the 404/error page was served for this resource.

*Source: https://www.imf.org/en/publications/gfsr/issues/2016/12/31/c1/table1_3.csv*

---


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