Details of request “Hong Kong Shapefile Data

Event history

This table shows the technical details of the internal events that happened to this request on accessinfo.hk. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on accessinfo.hk. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type created_at described_state last_described_at calculated_state link
2034  sent  2018-12-03 11:16:54 +0800  waiting_response  2018-12-03 11:16:55 +0800  waiting_response  outgoing  
2054  followup_sent  2018-12-17 11:56:11 +0800        outgoing  
2057  response  2018-12-20 12:02:15 +0800        incoming  
2059  response  2018-12-20 15:11:07 +0800    2018-12-21 06:26:15 +0800  waiting_clarification  incoming  
2062  status_update  2018-12-21 06:26:15 +0800  waiting_clarification  2018-12-21 06:26:15 +0800  waiting_clarification   
2063  followup_sent  2018-12-21 07:06:03 +0800  waiting_response  2018-12-21 07:06:03 +0800  waiting_response  outgoing  
2064  response  2018-12-21 19:23:59 +0800        incoming  
2071  response  2018-12-27 14:44:27 +0800        incoming  
2075  response  2019-01-01 11:27:01 +0800    2019-01-07 08:34:34 +0800  waiting_clarification  incoming  
2085  status_update  2019-01-07 08:34:34 +0800  waiting_clarification  2019-01-07 08:34:34 +0800  waiting_clarification   
2086  followup_sent  2019-01-07 08:39:30 +0800  waiting_response  2019-01-07 08:39:30 +0800  waiting_response  outgoing  
2092  response  2019-01-08 15:22:42 +0800    2019-01-10 07:14:40 +0800  waiting_clarification  incoming  
2099  status_update  2019-01-10 07:14:40 +0800  waiting_clarification  2019-01-10 07:14:40 +0800  waiting_clarification   
2100  followup_sent  2019-01-10 07:19:44 +0800  waiting_response  2019-01-10 07:19:44 +0800  waiting_response  outgoing  
2105  response  2019-01-14 10:48:35 +0800    2019-01-22 15:31:57 +0800  waiting_clarification  incoming  
2122  status_update  2019-01-22 15:31:56 +0800  waiting_clarification  2019-01-22 15:31:57 +0800  waiting_clarification   
2123  followup_sent  2019-01-22 15:35:32 +0800  waiting_response  2019-01-22 15:35:33 +0800  waiting_response  outgoing  
2125  response  2019-01-23 15:27:01 +0800        incoming  
2126  response  2019-01-23 16:02:42 +0800    2019-01-24 06:07:40 +0800  waiting_clarification  incoming  
2127  status_update  2019-01-24 06:07:40 +0800  waiting_clarification  2019-01-24 06:07:40 +0800  waiting_clarification   
2128  followup_sent  2019-01-24 06:11:55 +0800  waiting_response  2019-01-24 06:11:55 +0800  waiting_response  outgoing  
2130  response  2019-01-24 17:01:37 +0800        incoming  
2753  edit  2019-07-25 11:45:07 +0800         
2754  edit  2019-07-25 11:45:07 +0800         
2755  edit  2019-07-25 11:45:07 +0800         
2756  edit  2019-07-25 11:45:07 +0800         
2757  edit  2019-07-25 11:45:07 +0800         
2758  edit  2019-07-25 11:45:08 +0800         
2759  edit  2019-07-25 11:45:08 +0800         
2760  edit  2019-07-25 11:45:08 +0800         
2761  edit  2019-07-25 11:45:08 +0800         
2762  edit  2019-07-25 11:45:08 +0800         
2763  edit  2019-07-25 11:45:08 +0800         
2764  edit  2019-07-25 11:45:08 +0800         
2765  edit  2019-07-25 11:45:08 +0800         
2766  edit  2019-07-25 11:45:08 +0800         
2767  edit  2019-07-25 11:45:08 +0800         
2768  edit  2019-07-25 11:45:08 +0800         
2769  edit  2019-07-25 11:45:08 +0800         
2770  edit  2019-07-25 11:45:08 +0800         
2771  edit  2019-07-25 11:45:08 +0800         
2772  edit  2019-07-25 11:45:08 +0800         
2773  edit  2019-07-25 11:45:08 +0800         
2774  edit  2019-07-25 11:45:08 +0800         

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by accessinfo.hk for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.