This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 8%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
I can't get the map tile to show my GPS location on the view. I have setup my JSON as per the image below:
When i check the raw data i can see that the data is coming in and sitting against the right capability but the map still shows "Waiting for data".
Can someone tell me what i'm doing wrong?
Hi @Joshua Bailey ,
If you are following a specific doc or tutorial can you share it with us?
The definition of a geopoint telemetry type should be like (note the schema needs to be "geopoint"): https://learn.microsoft.com/en-us/azure/iot-central/core/concepts-telemetry-properties-commands#complex-types
{
"@id": "<element id>",
"@type": "Telemetry",
"displayName": {
"en": "GeopointTelemetry"
},
"name": "GeopointTelemetry",
"schema": "geopoint"
}
A device client should send the telemetry as JSON that looks like the following example (your example above looks to be correct):
{
"GeopointTelemetry": {
"lat": 47.64263,
"lon": -122.13035,
"alt": 0
}
}
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello @Joshua Bailey , What is your IoT Central app's deployed region? is it the Central US?
I ended up starting again and deleting the IoT central app and the function that handles the message webhook and it all worked perfectly so not sure why the first instance wouldn't work as i followed exactly the same steps and sent exactly the same information but this time it worked.
Thanks for leting us know the workaround @Joshua Bailey ,
Please reach out if you face the same issue and we can look at internal logs of your IoTCentral Application before deleting it.