jinko travel-demand destination-trend - Jinko Platform

Ranks destinations by within-window growth, then returns each top-N destination’s series. —origin is required: use a location such as Country:US or City:NYC, or global for all origins. Optional —destination-country (a Country selector, allowed only with —level city) narrows the ranking to that country’s destination cities.

Usage

jinko travel-demand destination-trend [options]

Options

Flag	Required	Description	Default
`--origin <level:code>`	Yes	origin filter, e.g. Country:US or City:NYC (or ‘global’ for all origins)
`--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	oneway\|roundtrip
`--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"`
`--limit <n>`	No	max number of series (top-N), 1-50 (default 10)
`--level <level>`	No	ranked output granularity: country (default) or city	`"country"`
`--destination-country <Country:code>`	No	destination country to rank cities within, e.g. Country:FR, allowed only with —level city