Consider city location in input

[metalwarrior665]

Now that we know UULE works pretty well, what about making the next step to make this more usable for end-users? There are few ways to implement this (feel free to add more):

1. Parse + translate the city at runtime - Would be very try/fail but will just work for all major cities.
2. Provide simple external page (tool) like page analyzer to convert a city to UULE (with search completion)
3. Implement the same thing at 2) as a new INPUT_SCHEMA component. The question would be how would the big data (8 MB csv) be loaded into the client (or server-side?).

[jancurn]

In description of the uule parameter there is a link to a tool that generates it.

On Tue, 18 Feb 2020 at 18:06, Lukáš Křivka [email protected] wrote:

Now that we know UULE works pretty well, what about making the next step to make this more usable for end-users? There are few ways to implement this (feel free to add more):

1. Parse + translate the city at runtime - Would be very try/fail but will just work for all major cities.
2. Provide simple external page (tool) like page analyzer to convert a city to UULE (with search completion)
3. Implement the same thing at 2) as a new INPUT_SCHEMA component. The question would be how would the big data (8 MB csv) be loaded into the client (or server-side?).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/apifytech/actor-google-search-scraper/issues/31?email_source=notifications&email_token=ACQ7CBFEKSR7CR27HA26CPTRDQISDA5CNFSM4KXIV2AKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IOMILXA, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACQ7CBHNGAVZV6HEA2QR6XDRDQISDANCNFSM4KXIV2AA .