-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Data Quality and Radius Functionality in FastMode #105
Comments
(1) the radius function works only in fastmode about (2) extra work needs to be done. |
Thank you for clarifying the current behavior of FastMode and the radius functionality. I appreciate your detailed response. I have a few follow-up questions and requests:
I understand extra work is needed for improving the modes and that radius support in Standard Mode may not be straightforward. Your guidance or insights would be greatly appreciated as I explore potential solutions! Thanks again for your time and effort! |
all your questions can be answered by taking a look at the code: https://github.com/gosom/google-maps-scraper/blob/main/gmaps/searchjob.go |
When activating FastMode, the returned data is significantly limited, with many data points missing. Additionally, the
radius
property does not function as expected when FastMode is inactive.The current behavior creates the following challenges:
FastMode: Returns a small amount of data, which is often incomplete or of poor quality.
Standard Mode: Provides richer data but does not restrict results to the specified radius, making it unreliable for targeted queries.
The desired functionality is to:
Obtain rich, complete data within a specified radius.
Ensure that the radius property works consistently, regardless of whether FastMode is active or not.
This improvement would greatly enhance data accuracy and usability for targeted searches.
Thank you!
The text was updated successfully, but these errors were encountered: