[ANSWERED] JSON Parser Beta and nested square brackets
mark last edited by mark
Smis, small integers.
(Apparently our version of v8 knows about BigInts because I didn't get a syntax error, but something else went wrong. I'll have to look into that.)
Let me get clear on what you mean by "unix timestamps" -- do you mean the number of seconds since midnight Jan 1, 1970? I guess not since these do not include milliseconds. What do you mean?
But what if you simply divided your millisecond integer values by 1000.0 to get seconds instead? Does that address the problem?
Well, I think I need an example patch or something to answer this more effectively.
For example when I check the web api I am using I get the first timestamp as : 1585207161600, but this element is output from the JSON parser as 364071376, if I use another method to see the results and search them there is nowhere that I find 364071376 (just to check if I made a mistake parsing).
I have made a very simple sample patch based on the example above, if I change any of the values of a JSON attribute to 1585207161600, it will output 364071376 from the parser.JSON Parse timestamp error.izz
@mark Any word on this or should I put it in a bug report- I understand this might not be high priority.
I've confirmed the issue, and have added it to the issue tracker.
mark last edited by
@mark works like a charm thanks.
The data comes from the US government and this site: https://www.usgs.gov/products/data-and-tools/real-time-data/earthquakes
a way to rotate a globe map to the latitude and longitude of each earthquake if anyone knows how..
Here is the demonstration patch I am working on - not even close to completed. I have reduced the resolution of the texture maps to fit into under 3mb download .zip.
It uses API data sources from VirusTracker and the WorldBank. I am also looking at accessing earth texture maps from NASA API to associate with times of day. but at the moment just have two texture maps that swap out including an example of average temperature and night. The data updates every day based on the availability of current Covid19 statistics through VirusTracker. It is set to minus 3 days because of the uncertainty of availability of daily data over weekends etc. The WorldBank API data provides, country broad individual wealth position, world coordinates and capital city.
I would say the patch system needs a way to capture the data with a single pass of the API URL's rather than continuously using the TCP GET method over and over. I haven't yet got the single pass TCP GET method into a Data Array configured, but I think that would be best practice.