Add permanently_closed field to maps result
complete
s
shadwell
Hi Milos Djurdjevic, I noticed some places don't have open_state provided (for example, see this data id which is temporarily closed: !4m5!3m4!1s0x89d4cd72212ab4f7:0xa1209ca8cddb77cf!8m2!3d43.736683299999996!4d-79.3446361). Any help would be greatly appreciated!
Milos Djurdjevic
shadwell: Hi. I have opened a separate issue for this that you can follow: https://serpapi.canny.io/admin/feedback/bugs/p/some-google-maps-place-results-do-not-extract-openstate?boards=bugs
We will look into it!
Milos Djurdjevic
complete
Milos Djurdjevic
in progress
s
shadwell
Hi - this is pretty important to my team so was just wondering if there was any news related to this? Appreciate any updates
Milos Djurdjevic
shadwell: Hi shadwell. We have been working on this feature. The ideal way to handle this is to have a
"permanently_closed": true
response. But unfortunately, there is no way for us to distinguishes between open states (Permanently closed, Temporarily closed, Open, Closed,...).The proposed solution to this would be to introduce a
open_state
field. For example:"open_state": "Permanently closed"
"open_state": "Temporarily closed"
"open_state": "Closed ⋅ Opens 9:30AM"
"open_state": "Open ⋅ Closes 5:30PM"
Would this be of help to you and your team?
s
shadwell
Milos Djurdjevic: Really appreciate the response! That would work for us and would also likely help others parse based on their use case
Illia Zub
planned
Illia Zub
under review