A museum analytics service consumes Meraki Scanning POSTs. Which fields should the constructed consumer treat as the core location retrieve?
Select an answer to reveal the explanation.
Short Explanation
You are reading who was seen and where—the observation’s MAC (and maybe IP) plus coordinates when enough APs heard the client. Missing lat/lng is often a coverage fact, not a parse bug.
Full Explanation
The constructed Scanning consumer reads the observation array for client MAC (and optionally IP) and location fields (lat/lng or x/y when the cloud could compute them). Missing coordinates when too few APs heard the client is a data fact, not necessarily a parse error. SSID enable flags, FDM object types, and full RF survey artifacts are outside this retrieve task.