openydt-data

Original：🇨🇳 Chinese

Translated

Uniview Smart Parking Open Platform Data Analysis Domain openydt data: Read-only data statistics and reports including parking lot payment bills, bill summaries, traffic flow, top license plate distribution, real-time parking lot data, daily vehicle exit/transaction counts, per-minute traffic flow, parking space usage, parking duration analysis, etc. Trigger words: data analysis/statistics/reports/check bills/payment bills/bill summaries/traffic flow/traffic statistics/top license plates/license plate distribution/real-time data/present vehicles/exit counts/transaction counts/per-minute traffic/parking space usage/parking space utilization rate/parking space occupancy/heatmap/echart/parking duration/duration analysis/parking duration distribution

6installs

Sourcexiaowen-0725/openydt-cli

Added on2026-05-30

NPX Install

npx skill4agent add xiaowen-0725/openydt-cli openydt-data

SKILL.md Content (Chinese)

View Translation Comparison →

CRITICAL: MUST use the Read tool to read
../openydt-shared/SKILL.md
before starting (Authentication / Profile / Signature / Status Codes / Rate Limiting / Security Rules), otherwise the command will fail due to missing credentials or signatures.

When to Use This Skill

Use this skill when users need to perform read-only data analysis and report statistics for parking lots, such as checking payment bills/bill summaries of a parking lot, viewing traffic flow and top license plate distribution, reading real-time present data of parking lots, counting daily vehicle exit counts and transaction counts, viewing traffic flow curves by minute, analyzing parking space usage (including echart heatmaps), and conducting parking duration distribution analysis.

Intent Routing:

For bills/payment details →
```
get-bill-summary
```
; for bill summary indicators →
```
get-park-bill
```
.
For traffic flow curves/trends → Use
```
get-traffic-flow
```
for per-minute data over a period; use
```
get-car-traffic-flow-analysis
```
for top license plate distribution.
For real-time/daily data → Use
```
get-real-time-park-info
```
for real-time present data; use
```
get-realtime-leave-and-charge-num
```
for daily vehicle exit and transaction counts.
For parking space usage → Use
```
parking-place-used
```
for list data; use
```
parking-place-used-for-echart
```
to generate echart heatmaps.
For parking duration distribution →
```
parking-time-analyse
```
.
If users need to initiate payment, check parking lot configurations, monthly tickets/coupons, devices, blacklists/whitelists, visitors, etc., these do not belong to this domain, please use corresponding skills (trade / parking / ticket / coupon / device / blacklist / redlist / visitor, etc.).

Available Commands

Chinese Name	Command	Read/Write	Key Parameters
Get payment bill information of a parking lot	`openydt data get-bill-summary`	Read	parkCode, dimension(0 day/1 month/2 year/3 custom), startTime, endTime, pageNum, pageSize
Get top license plate distribution of traffic flow	`openydt data get-car-traffic-flow-analysis`	Read	parkCodeList(JSONArray of parking lot codes)
Query bill summary information of a parking lot	`openydt data get-park-bill`	Read	parkCode, dimension(0 day/1 month/2 year), startTime, endTime, pageNum, pageSize
Get real-time parking lot data	`openydt data get-real-time-park-info`	Read	parkCode
Get daily vehicle exit counts and transaction counts of a parking lot	`openydt data get-realtime-leave-and-charge-num`	Read	parkCode
Get per-minute traffic flow of a single parking lot	`openydt data get-traffic-flow`	Read	parkCode, startTime, endTime(interval ≤ 1 day, format yyyy-MM-dd HH:mm)
Get parking space usage data	`openydt data parking-place-used`	Write(requires `--yes` )	parkCode, startDate, endDate(yyyyMMddHHmmss), minuteInterval(10 or 240)
Get parking space usage data (echart heatmap)	`openydt data parking-place-used-for-echart`	Write(requires `--yes` )	parkCode, startDate, endDate(yyyyMMddHHmmss), minuteInterval(10 or 240)
Get parking duration analysis data of a parking lot	`openydt data parking-time-analyse`	Write(requires `--yes` )	parkCode, startDate, endDate(yyyyMMddHHmmss), vipType(1 temporary vehicle/2 monthly rental vehicle), hourArea

Note:
parking-place-used
,
parking-place-used-for-echart
, and
parking-time-analyse
are marked as write in the platform contract. Must include
--yes
for confirmation when calling, otherwise they will be intercepted by the write operation confirmation. Other commands are read-only and do not require
--yes
.

Business Process

All operations in the Data Analysis Domain are parking lot-level read-only/statistical queries, with the core parameter being

parkCode

(parking lot ID/code). A typical analysis process is as follows, emphasizing using fields from the response of previous commands as parameters for subsequent commands:

Determine the target parking lot parkCode:
```
parkCode
```
comes from response fields of parking lot domain commands (such as
```
openydt park
```
/
```
openydt parking
```
list/query interfaces), or from users/upstream systems. Obtain parkCode first, then fill it into
--park-code
of all commands in this domain.
Quick Health Check (Real-time Overview): Use
```
get-real-time-park-info
```
(real-time present vehicles/parking spaces) +
```
get-realtime-leave-and-charge-num
```
(daily vehicle exit counts, transaction counts) to get the daily overview, confirm that the parking lot has data and the code is correct.
Traffic Flow Analysis:
- Per-minute curve for a single parking lot:
```
get-traffic-flow
```
  , note that the interval between
```
startTime
```
  /
```
endTime
```
  cannot exceed one day (format
```
yyyy-MM-dd HH:mm
```
  ).
- Top license plate distribution for multiple parking lots:
```
get-car-traffic-flow-analysis
```
  , pass multiple parking lot
```
parkCode
```
  as a
```
parkCodeList
```
  array.
Bill Analysis: First use
```
get-park-bill
```
to view bill summary indicators (select day/month/year by dimension), then use
```
get-bill-summary
```
(dimension supports 3 custom time periods) when itemized details are needed. Both support pagination (
```
pageNum
```
/
```
pageSize
```
, maximum pageSize is 1000 entries).
Parking Space and Duration Analysis (Requires Write Confirmation, Needs
--yes
):
- Parking space usage:
```
parking-place-used
```
  (list) /
```
parking-place-used-for-echart
```
  (heatmap coordinate data),
```
minuteInterval
```
  only supports 10 or 240.
- Parking duration distribution:
```
parking-time-analyse
```
  , split by
```
vipType
```
  (1 temporary vehicle / 2 monthly rental vehicle) and
```
hourArea
```
  duration intervals (in the format like
```
0-1,1-4,4-7,7-10,10-12,12-0
```
  ).
- The time parameters of the above commands use the compact format
```
yyyyMMddHHmmss
```
  , which is different from the
```
yyyy-MM-dd
```
  format in steps 3/4, please note the distinction.

Key Points for Field Transfer:
parkCode
from upstream parking lot domain responses →
--park-code
of all commands in this domain; total count/pagination information from pagination query responses → adjust
--page-num
/
--page-size
for the next query; collect
parkCode
of each parking lot into the
parkCodeList
array in
--body
for multi-parking-lot analysis.

Examples

bash

# 1) Query bill summary of a parking lot (year dimension, read-only, no --yes required)
openydt data get-park-bill \
  --park-code 2KKN6112 --dimension 2 \
  --start-time "2019-08-17 00:00:00" --end-time "2019-08-17 23:59:59" \
  --page-num 1 --page-size 10

# 2) Get top license plate distribution of traffic flow (multiple parking lots, pass parkCodeList array via --body, read-only)
openydt data get-car-traffic-flow-analysis \
  --body '{"parkCodeList":["765OB49GJ","765MQK2TX"]}'

# 3) Get parking duration analysis data of a parking lot (write operation, must include --yes)
openydt data parking-time-analyse \
  --park-code 2KKN885S \
  --start-date 20190910000000 --end-date 20190910235959 \
  --vip-type 1 --hour-area "0-1,1-4,4-7,7-10,10-12,12-0" \
  --yes