TAZ_Settings

settings activitysim.core.configuration.TAZ_Settings

Complex settings for TAZ skims that are not just OMX file(s).

New in version 1.2.

Fields:

• omx (str)

• zarr (str)

• zarr_digital_encoding (list[activitysim.core.configuration.network.DigitalEncoding])

field omx: str = None

The filename of the data stored in OMX format.

This is treated as a fallback for the raw input data, if ZARR format data is not available.

As an alternative to OMX, skim files can instead be provided in Parquet format (using a .parquet or .pq file extension). The input format is auto-detected from the file extension, so no other settings need to change to use Parquet input. Parquet skim files should have an origin column and a destination column (the first two columns in the file), followed by one column for each named skim matrix (matching the naming conventions used for OMX skims, including double-underscore delimited time periods). Parquet skim data may be dense (one row for every origin-destination combination, sorted in row-major or column-major order using any stable zone-ID order) or sparse (only some origin-destination combinations present, in any order). Parquet inputs are supported by both the legacy skim-dictionary loaders and Sharrow when Sharrow 2.16 or newer is installed.

field zarr: str = None

The filename of the data stored in ZARR format.

Reading ZARR data can be much faster than reading OMX format data, so if this filename is given, the ZARR file format is preferred if it exists. If it does not exist, then OMX data is read in and then ZARR data is written out for future usage.

New in version 1.2.

field zarr_digital_encoding: list[DigitalEncoding] = None

A list of encodings to apply before saving skims in ZARR format.

New in version 1.2.

Digital encodings transform how data is stored in memory and on disk, potentially reducing storage requirements without fundamentally changing the underlying data.