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/abs@.nsf/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
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...