sk-zk
commented
1 year ago Nice, thank you
Not sure if the overlay_x and overlay_y should be converted to radians or degrees, for consistency?
Radians
place[1][0][0][2] is probably something to do with depth, but I'm not sure. Metres away from the middle of the panorama could be it, noting that the location of the overlay isn't 100% exactly where it is in real life.
Yeah, looks like it could be meters from the camera.
Feature ID or Client ID could in theory be used with the places API, or perhaps another internal thing, but that's another story.
The feature_id seems to be an internal ID for the place which appears in calls to internal APIs but can't be used for the official API.
The client_id is probably actually a map node ID (I guess not). If you look at the places for a pano and see an intersection in there, open the map editor in that spot and Ctrl+F the response from GeoUgcMapsRoadsEditorUi/data/batchexecute. The ID will show up in there as many times as the intersection has legs. I'm gonna comment this out for now until I have a better understanding of what this is for
Turns out toggle 5 does do something, it includes places (POIs? Locations? Features? I'm not sure what the correct wording is) in the response.
Useful for trekkers to find out what building/landmark it's for, though this also includes businesses that appear in Street View (I think the API calls them "overlays") (I guess you could also call them hotspots) as little icons on top of the building entrance that you can click on to give you a preview of that business, but also can have some other businesses that happen to be nearby and aren't clickable.
I suck at documentation and haven't slept well today, so hopefully I haven't missed anything important.
Not sure if the overlay_x and overlay_y should be converted to radians or degrees, for consistency? place[1][0][0][2] is probably something to do with depth, but I'm not sure. Metres away from the middle of the panorama could be it, noting that the location of the overlay isn't 100% exactly where it is in real life.
Feature ID or Client ID could in theory be used with the places API, or perhaps another internal thing, but that's another story.
The array at msg[5][0][9] also can contain some other things, like a single-element list containing another single-element list that contains something like
"/m/028vq2"for example. I'm not sure what that's about, I think it has something to do with the little text that appears underneath the name of important places on the map. Also, for some museum panos from Arts & Culture, it has hotspots of the actual artworks and things and their information/properties, which may be interesting.