jinko travel-demand trend

Deep dive: one de-sampled search-volume series per (origin, destination) pair. —origin and —destination are repeatable (or comma-separated); v1 allows a list on only one side (keep the other a single location).

Usage

jinko travel-demand trend [options]

Options

Flag	Required	Description	Default
`--origin <level:code>`	No	origin selector, e.g. Country:US (repeatable)	`[]`
`--destination <level:code>`	No	destination selector, e.g. Country:FR (repeatable)	`[]`
`--traveler-type <type>`	No	Solo\|Couple\|Group\|Family
`--departure-date-from <YYYY-MM-DD>`	No	start of departure window (use with —departure-date-to; omit both for no departure-date filter, buckets count searches for all departure dates, recommended)
`--departure-date-to <YYYY-MM-DD>`	No	end of departure window (use with —departure-date-from; omit both for no departure-date filter)
`--trip-type <type>`	No	One-Way\|Round-Trip
`--trip-duration-min <n>`	No	minimum trip length in nights (round-trips only, >= 0)
`--trip-duration-max <n>`	No	maximum trip length in nights (>= —trip-duration-min)
`--search-window-min <n>`	No	minimum advance-purchase window in days before departure (>= 0)
`--search-window-max <n>`	No	maximum advance-purchase window in days (>= —search-window-min)
`--trend-window <n>`	No	number of buckets the series spans, in the granularity unit (day 2-60 \| week 2-52 \| month 2-12, default 12)
`--granularity <bucket>`	No	series bucket size: week (default) \| day \| month	`"week"`

Introduction

Travel Demand

Flights

Hotels

Cart & Payment

Account & utilities

Usage

Options

​Usage

​Options

Usage

Options