Skip to main content
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

FlagRequiredDescriptionDefault
--origin <level:code>Noorigin selector, e.g. Country:US (repeatable)[]
--destination <level:code>Nodestination selector, e.g. Country:FR (repeatable)[]
--traveler-type <type>NoSolo|Couple|Group|Family
--departure-date-from <YYYY-MM-DD>Nostart 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>Noend of departure window (use with —departure-date-from; omit both for no departure-date filter)
--trip-type <type>NoOne-Way|Round-Trip
--trip-duration-min <n>Nominimum trip length in nights (round-trips only, >= 0)
--trip-duration-max <n>Nomaximum trip length in nights (>= —trip-duration-min)
--search-window-min <n>Nominimum advance-purchase window in days before departure (>= 0)
--search-window-max <n>Nomaximum advance-purchase window in days (>= —search-window-min)
--trend-window <n>Nonumber of buckets the series spans, in the granularity unit (day 2-60 | week 2-52 | month 2-12, default 12)
--granularity <bucket>Noseries bucket size: week (default) | day | month"week"