Longitude truncation & Missing Heatmap Data At Different Precision

[popwarfour]

Two issues here

1. As you can see from the logs I exported we're still getting that old longitude truncation bug. I don't think its really a big deal, other than the bug I'm about to mention I don't think its causing us any problem. but I figured I'd mention it just incase it has to do with the real issue here. Heres an example:

{
latDegrees = "44.2068";
lonDegrees = "-72.92270000000001";
secondsWorked = 49;
}

2. Take a look at the screen shots first at the bottom of the page. The lowest number is the highest precision (the numbers don't mean anything, just to keep order). Depending at what altitude I'm looking at I request a different precision level. I had never seen this happen before until I added a bunch of sample heat map data. Depending on the precision I found a random section of heat map data is not being given by the API, its just missing from the response. I would give you the url request I'm making but apparently I'm not logging it, whoops. But I do log all the data you would need to rebuild the request if you'd like as found at the top of "LowerLevel":

4 09:04:10:204 GreenUpVt[38680:1547] --- Data - Map: Current Precision = 4.000000
2014-04-24 09:04:10:205 GreenUpVt[38680:1547] --- Data - Map: Current Lat = 44.202366
2014-04-24 09:04:10:205 GreenUpVt[38680:1547] --- Data - Map: Current Lon = -72.945259
2014-04-24 09:04:10:205 GreenUpVt[38680:1547] --- Data - Map: Current Lat Delta = 0.122815
2014-04-24 09:04:10:205 GreenUpVt[38680:1547] --- Data - Map: Current Lon Delta = 0.109863

I'll just point out the place of interest is at the end of the "LowerLevel" log file. This is what the end of the heat map array looks like. We are missing that entire longitudinal section from -72.957678 to -72.936435 which again you can see from some of the images.

},
    {
    latDegrees = "44.2135";
    lonDegrees = "-72.9355";
    secondsWorked = 39;
},
    {
    latDegrees = "44.2134";
    lonDegrees = "-72.9354";
    secondsWorked = 27;
},

//*********************************************
//NOTICE THIS HUGE JUMP IN LONGITUDE RIGHT HERE!
//*********************************************

    {
    latDegrees = "44.2164";
    lonDegrees = "-72.9589";
    secondsWorked = 44;
}

Log Exports
Lower Level (Contains Missing Data - Seen in image 2)
https://drive.google.com/file/d/0B8Q2EtU9zgjCTTVZNjl2Ry1JcUk/edit?usp=sharing

Higher Level (Contains All Data - Seen in image 3)
https://drive.google.com/file/d/0B8Q2EtU9zgjCZ1AyeVlWOS00X3M/edit?usp=sharing

Image 1
https://drive.google.com/file/d/0B8Q2EtU9zgjCTEstLXB2Y3Nielk/edit?usp=sharing
Image 2
https://drive.google.com/file/d/0B8Q2EtU9zgjCNUFGMEJVLW4yVXc/edit?usp=sharing
Image 3
https://drive.google.com/file/d/0B8Q2EtU9zgjCWWlETXlFS2V2dFk/edit?usp=sharing
Image 4
https://drive.google.com/file/d/0B8Q2EtU9zgjCODlpdG53ZmR5em8/edit?usp=sharing

[EdgeCaseBerg]

So in the highlevel view (image 3) it looks like we've hit the entire road, but then on zooming in (image 2) the precision gets better and we can see that it's only part of the road right? That seems correct to me.
Image 4 looks like the data is more precise here... perhaps there is truncation of one of the axes? not sure.
I'll try to investigate this later but might not get to it today.

[popwarfour]

Backwards from that. The whole road should have heat map points everywhere
along it. I noticed that depending on the precision / altitude of the map
that section is just not being returned. I'll see if I can hard code the
precision and repeat the bug and give you some definitive url to test with
On Apr 25, 2014 2:21 PM, "Ethan Joachim Eldridge" [email protected]
wrote:

So in the highlevel view (image 3) it looks like we've hit the entire
road, but then on zooming in (image 2) the precision gets better and we can
see that it's only part of the road right? That seems correct to me.
Image 4 looks like the data is more precise here... perhaps there is
truncation of one of the axes? not sure.
I'll try to investigate this later but might not get to it today.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/173#issuecomment-41423743
.

[popwarfour]

It's not 100% critical at this point, I'm more worried about why the web
app is only showing a couple heat map locations
On Apr 25, 2014 2:21 PM, "Ethan Joachim Eldridge" [email protected]
wrote:

So in the highlevel view (image 3) it looks like we've hit the entire
road, but then on zooming in (image 2) the precision gets better and we can
see that it's only part of the road right? That seems correct to me.
Image 4 looks like the data is more precise here... perhaps there is
truncation of one of the axes? not sure.
I'll try to investigate this later but might not get to it today.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/173#issuecomment-41423743
.

[EdgeCaseBerg]

The data might be within the next page of the API response.

[EdgeCaseBerg]

Right now we're mitigating the issue by increasing the page size of the
heatmap page returned to the client, but really the way to fix this is to
have the client implement paging.

So we'll keep this in mind for 2.0