Getting Data In

JSON Parse error while uploading .kmz - 7.2.0

m_newman
New Member

Having some issues trying to upload a .kmz file.. It's working fine on the 7.3.1 sandbox I have myself, but trying to add it to a 'proper' server running 7.2.0 (to which I have power user access, but am not an admin) I'm receiving the following error (in Chrome):

Your entry was not saved. The following error was reported: SyntaxError: Unexpected token < in JSON at position 0.

or under IE:

Your entry was not saved. The following error was reported: SyntaxError: Invalid character.

It's a reasonably sizeable data source (31MB compressed as a KMZ, 115 in the underlying KML), I'm wondering if that has anything to do with it. I've also asked an admin to try it as well and he replicated the result. I'm wondering if there's anything I can do (outside of the obvious but essentially impossible 'upgrade') to get this working?

I Don't have the Karma to link the file directly.. it is however a KMZ exported from Google Earth, sourced from a shapefile import of Australian area (SA3) boundaries - publicly available & from a .gov source at:

https://www.abs.gov.au/AUSSTATS/[email protected]/DetailsPage/1270.0.55.001July%202016?OpenDocument
("Statistical Area Level 3 (SA3) ASGS Ed 2016 Digital Boundaries in ESRI Shapefile Format " )

(This was imported into Google Earth, then saved out to the KMZ file)

KMZ file in question can be downloaded from http://www.filedropper.com/sa3 <- as noted, I'm new and can't be trusted with links, so please ensure you take the relevant precautions before opening... 😉

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Self-Healing Pipeline Is Now Generally Available: AI-Powered CIM Compliance

Maintaining data integrity across security and analytics pipelines is an ongoing challenge. Data ...