-
Notifications
You must be signed in to change notification settings - Fork 166
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
Is also the Google Maps information is in Protobuf #15
Comments
Hello, Yes, this is Protobuf serialized to JavaScript. The produced JSON array indexes just correspond to the field numbers of the original Protobuf message, and This serialization method is very much used in Google products, including in Google Search and other parts. AFAIK, there is no way to extract the original serialization structures because the Closure Compiler-transformed code that reads this usually indexes the generated JSON array fields directly by their indexes. However, by luck, it is not impossible that the fields of this format may match other messages used with other Protobuf-based serialization method (e.g, binary Protobuf sent by a mobile application) that may use similar message structures. Regards, |
@MusiCode1, you can extract data from it by accessing the nested arrays. According to elm-lang creator, Google never removes existing fields, but I haven't found an official statement about it. It works pretty stably for us for more than a year. I can't share the code of the parser but we have a paid API. |
Google Maps has a very strange format to convey the information to the customer.
This is a lot of nested arrays, which contain a lot of NULL values.
It looks like this:
Sample link: https://www.google.com/search?tbm=map&hl=en&q=white%20house&tch=1&ech=1
Is it also Protobuf?
And how do you decipher it?
The text was updated successfully, but these errors were encountered: