In order to facilitate the user to retrieve the historical track uploaded to the Eagle Eye platform, the history search function is added. This function can query the terminals that appear in a certain space range in the past. For example, search for terminals in a geographical range from 2:00 pm to 3:00 pm yesterday. Note: This service is an advanced payment service. You can use Apply for trial or purchase Activate the service permission.

The methods of using this type of interface are:
Step 1: Create a task using the createjob interface
Step 2: Use the getjob interface to view all tasks of the current service
Step 3: Use the deletejob interface to delete tasks according to job_id

When creating a new historical track retrieval task, pay attention to:

1. Only tracks 6 hours before the current time can be retrieved. For example, tasks created at 10:00 on 2021-11-15 can only retrieve tracks generated before 4:00 on 2021-11-15.
2. The search time interval shall not exceed 24 hours, that is, the difference between the end time and the start time shall be within 24 hours.
3. A developer can only have 10 unfinished tasks at the same time. If there are more than 10 unfinished tasks, creation failure will be returned. Please wait until the existing tasks are processed before creating new tasks.

 {
 "status" :  zero ,
 "message" :  Success ,
 "job_id"  :  one
 }

Query the tasks in the task pool, which includes the following types of tasks:

1. The task has been created and has not been started
2. Tasks in progress
3. Completed tasks, but the completion time does not exceed 48 hours (note: completed tasks will be automatically cleaned up after 48 hours). Completed tasks will return file_url, paste the address to the browser or use other download methods to obtain the result file. When file_url displays no result, it indicates that no entity has been queried.

1. The format of the exported file name is: service_id _ job_id . zip (for example: 135252_10. zip)
2. Use the zip decompression tool to extract the file: service_id _ job_id . json (example: 135252_10. json)
3. Each line of text in the file represents a track data in json format, where:

 https : / / yingyan . baidu . com / api / v3 / historysearch / getjob ? ak = < User ak > & service_id = < User service_id >

 {
 "status" :  zero ,
 "message" :  Success ,
 "total" :  two ,
 jobs :  [ {
   "job_id" : one , "service_id" : two hundred and thirty thousand one hundred and forty-four , "start_time" : one billion six hundred and thirty-nine million four hundred and eleven thousand and two hundred ,
   "end_time" : one billion six hundred and thirty-nine million four hundred and twenty-two thousand , "around" : { "center" : { "longitude" : one hundred and nineteen point four nine three three two eight , "latitude" : forty point four six seven six three nine } , "radius" : one hundred } , "coord_type"
   : "gcj02" , "create_time" : "20211215192540" , "modify_time" : "20211215192552" , "job_status" : "done" ,
   "file_url" : "no result" } ] ,
 }

Delete task according to job_id

 {
 "status" :  zero ,
 "message" :  Success ,
 }