@Dave
I tried to figure out the latest status of the json implementation -> Azure. Same issue I guess with my elektrons:
Asset tracker should send
{ time,
location:{lat,long}
alt,
spd,
sat,
dop}
so basically the NMEA vis the publish function to an iot hub. There a stream analysis shall sort them in to colomns:
SELECT
data.ts as time,
data.location.lat as latitude,
data.location.lng as longitude,
data.alt as altitude,
data.spd as speed,
data.sat as stellites,
data.dop as hdop,
published_at as ptime,
coreid as trackerid
and PowerBi sahll be able to access the value separately. But I cannot get it to work.
So far I package all in one statement and it works fine when using:
String json = String::format("{\"ts\":\"%u\",\"lat\":\"%f\",\"lng\":\"%f\",\"alt\":\"%f\",\"spd\":\"%f\",\"sat\":\"%u\",\"dop\":\"%i\"}",
gps.time.value(),
gps.location.lat(),
gps.location.lng(),
gps.altitude.meters(),
gps.speed.kmph(),
gps.satellites.value(),
gps.hdop.value()
);
Particle.publish("sendpos", json,PRIVATE);
and select * as stream analysis.
But as you might know the PowerBI sees then simply one object that is called ‘data’.
Any update or doc how to send the json correctly? O will I need to setup SEND CUSTOM JSON at the particle integration. ? Is this CUSTOM JSON as described here by @svelde the only solution ?
Thanks for any hint!