read_json(path_or_buf=None, orient=None, typ='frame', dtype: 'DtypeArg | None' = None, convert_axes=None, convert_dates=True, keep_default_dates: 'bool' = True, numpy: 'bool' = False, precise_float: 'bool' = False, date_unit=None, encoding=None, encoding_errors: 'str | None' = 'strict', lines: 'bool' = False, chunksize: 'int | None' = None, compression: 'CompressionOptions' = 'infer', nrows: 'int | None' = None, storage_options: 'StorageOptions' = None)
Specific to orient='table'
, if a DataFrame
with a literal Index
name of :None:None:`index`
gets written with to_json
, the subsequent read operation will incorrectly set the Index
name to None
. This is because :None:None:`index`
is also used by DataFrame.to_json
to denote a missing Index
name, and the subsequent read_json
operation cannot distinguish between the two. The same limitation is encountered with a MultiIndex
and any names beginning with 'level_'
.
Any valid string path is acceptable. The string could be a URL. Valid URL schemes include http, ftp, s3, and file. For file URLs, a host is expected. A local file could be: file://localhost/path/to/table.json
.
If you want to pass in a path object, pandas accepts any os.PathLike
.
By file-like object, we refer to objects with a read()
method, such as a file handle (e.g. via builtin open
function) or StringIO
.
Indication of expected JSON string format. Compatible JSON strings can be produced by to_json()
with a corresponding orient value. The set of possible orients is:
The type of object to recover.
If True, infer dtypes; if a dict of column to dtype, then use those; if False, then don't infer dtypes at all, applies only to the data.
For all orient
values except 'table'
, default is True.
Not applicable for orient='table'
.
Try to convert the axes to the proper dtypes.
For all orient
values except 'table'
, default is True.
Not applicable for orient='table'
.
If True then default datelike columns may be converted (depending on keep_default_dates). If False, no dates will be converted. If a list of column names, then those columns will be converted and default datelike columns may also be converted (depending on keep_default_dates).
If parsing dates (convert_dates is not False), then try to parse the default datelike columns. A column label is datelike if
it ends with '_at'
,
it ends with '_time'
,
it begins with 'timestamp'
,
it is 'modified'
, or
it is 'date'
.
Direct decoding to numpy arrays. Supports numeric data only, but non-numeric column and index labels are supported. Note also that the JSON ordering MUST be the same for each term if numpy=True.
Set to enable usage of higher precision (strtod) function when decoding string to double values. Default (False) is to use fast but less precise builtin functionality.
The timestamp unit to detect if converting dates. The default behaviour is to try and detect the correct precision, but if this is not desired then pass one of 's', 'ms', 'us' or 'ns' to force parsing only seconds, milliseconds, microseconds or nanoseconds respectively.
The encoding to use to decode py3 bytes.
How encoding errors are treated. :None:None:`List of possible values
<https://docs.python.org/3/library/codecs.html#error-handlers>`
.
Read the file as a json object per line.
Return JsonReader object for iteration. See the :None:None:`line-delimited json docs
<https://pandas.pydata.org/pandas-docs/stable/user_guide/io.html#line-delimited-json>`
for more information on chunksize
. This can only be passed if :None:None:`lines=True`
. If this is None, the file will be read into memory all at once.
JsonReader
is a context manager.
For on-the-fly decompression of on-disk data. If 'infer' and 'path_or_buf' is path-like, then detect compression from the following extensions: '.gz', '.bz2', '.zip', '.xz', or '.zst' (otherwise no compression). If using 'zip', the ZIP file must contain only one data file to be read in. Set to None
for no decompression. Can also be a dict with key 'method'
set to one of { 'zip'
, 'gzip'
, 'bz2'
, 'zstd'
} and other key-value pairs are forwarded to zipfile.ZipFile
, gzip.GzipFile
, bz2.BZ2File
, or zstandard.ZstdDecompressor
, respectively. As an example, the following could be passed for Zstandard decompression using a custom compression dictionary: compression={'method': 'zstd', 'dict_data': my_compression_dict}
.
The number of lines from the line-delimited jsonfile that has to be read. This can only be passed if :None:None:`lines=True`
. If this is None, all the rows will be returned.
Extra options that make sense for a particular storage connection, e.g. host, port, username, password, etc. For HTTP(S) URLs the key-value pairs are forwarded to urllib
as header options. For other URLs (e.g. starting with "s3://", and "gcs://") the key-value pairs are forwarded to fsspec
. Please see fsspec
and urllib
for more details.
The type returned depends on the value of :None:None:`typ`
.
Convert a JSON string to pandas object.
DataFrame.to_json
Convert a DataFrame to a JSON string.
Series.to_json
Convert a Series to a JSON string.
json_normalize
Normalize semi-structured JSON data into a flat table.
>>> df = pd.DataFrame([['a', 'b'], ['c', 'd']],
... index=['row 1', 'row 2'],
... columns=['col 1', 'col 2'])
Encoding/decoding a Dataframe using 'split'
formatted JSON:
>>> df.to_json(orient='split') '{"columns":["col 1","col 2"],"index":["row 1","row 2"],"data":[["a","b"],["c","d"]]}'This example is valid syntax, but we were not able to check execution
>>> pd.read_json(_, orient='split') col 1 col 2 row 1 a b row 2 c d
Encoding/decoding a Dataframe using 'index'
formatted JSON:
>>> df.to_json(orient='index') '{"row 1":{"col 1":"a","col 2":"b"},"row 2":{"col 1":"c","col 2":"d"}}'This example is valid syntax, but we were not able to check execution
>>> pd.read_json(_, orient='index') col 1 col 2 row 1 a b row 2 c d
Encoding/decoding a Dataframe using 'records'
formatted JSON. Note that index labels are not preserved with this encoding.
>>> df.to_json(orient='records') '[{"col 1":"a","col 2":"b"},{"col 1":"c","col 2":"d"}]'This example is valid syntax, but we were not able to check execution
>>> pd.read_json(_, orient='records') col 1 col 2 0 a b 1 c d
Encoding with Table Schema
This example is valid syntax, but we were not able to check execution>>> df.to_json(orient='table') '{"schema":{"fields":[{"name":"index","type":"string"},{"name":"col 1","type":"string"},{"name":"col 2","type":"string"}],"primaryKey":["index"],"pandas_version":"1.4.0"},"data":[{"index":"row 1","col 1":"a","col 2":"b"},{"index":"row 2","col 1":"c","col 2":"d"}]}'See :
The following pages refer to to this document either explicitly or contain code examples using this.
pandas.core.generic.NDFrame.to_json
pandas.io.json._table_schema.parse_table_schema
pandas.io.xml.read_xml
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them