|
|
Post by psuteam on Jun 4, 2017 21:49:16 GMT -7
When testing the iridium tracking, I noticed that the website stopped updating the coordinates of the iridium payload but all movement had still been recorded in the archive. The archive date for the recording that was given was for *tomorrow*. Any insights would be appreciated!
|
|
|
|
Post by irowe on Jun 5, 2017 7:55:03 GMT -7
The only thing I can think of is that since the times are stored in UTC on the archive. I'm guessing you're from Portland State, and Oregon is UTC -7 hrs during daylight savings time. The only track logged for today so far is this one, which I assume was yours. The UTC time stamps for that are between 1 and 2 am, which would be between 6 and 7 pm your local time (at least I think so. I'm in EST and time zones are weird). That means in terms of UTC, you would be in the next day. |
|
|
|
Post by psuteam on Jun 5, 2017 15:06:34 GMT -7
Ah, that makes sense! And the tracking finally did update today to the location that the iridium payload was at yesterday. Is it common for there to be such a huge lag in the tracking? Thanks!
|
|
|
|
Post by irowe on Jun 6, 2017 8:29:59 GMT -7
Back on the old server, we saw delays of ~40 minutes some times. Now, we can usually see the Iridium tracker move every 30 seconds without much discrepancy from the real location. Some times if we lose connection to the Iridium satellites, from building interference, etc, the data will not appear until we resume connection.
|
|
|
|
Post by David MSGC on Jun 17, 2017 14:56:44 GMT -7
It is not a lag in updates. The data is in the database but not displayed on the map of the landing page, you have to go to the archive or click on your balloon. If you are looking at your balloon's page and not the landing page you can see the updates come in as they are received.
If the current time is past midnight UTC the data will be put into "tomorrows" data. The web page will only show icons for balloons flying during local time. If it is past midnight UTC you will have to find the data in the archive.
We might be able to change this in the future, dates are stored as strings and not dates. If we can change it to a date we can do date math and only display flights from local time much easier. Right now we have to do it this way so that it does not clutter the map with all flights ever recorded on the database.
If there is any delay it is that the server has not received a packet. The "old" server worked the same way, the improvement in latency from Feb 2017 to now is due to changes in the Iridium/NAL network.
|
|
|
|
Post by David MSGC on Jun 17, 2017 15:01:15 GMT -7
It is not a lag in updates. The data is in the database but not displayed on the map of the landing page, you have to go to the archive or click on your balloon. If you are looking at your balloon's page and not the landing page you can see the updates come in as they are received. If the current time is past midnight UTC the data will be put into "tomorrows" data. The web page will only show icons for balloons flying during local time. If it is past midnight UTC you will have to find the data in the archive. We might be able to change this in the future, dates are stored as strings and not dates. If we can change it to a date we can do date math and only display flights from local time much easier. Right now we have to do it this way so that it does not clutter the map with all flights ever recorded on the database. If there is any delay it is that the server has not received a packet. The "old" server worked the same way, the improvement in latency from Feb 2017 to now is due to changes in the Iridium/NAL network. If you do not have an Iridium or GPS connection it will not send a packet, if no packet is received by the database it will not show on the map. If it is past midnight UTC it will not be displayed on the map until after midnight local time. If it is past midnight UTC you can find the data in the archive. Note: the archive is the same exact page and data as if you were to click on your balloon opening the page with just your balloons data. The best way to see if your data is being received is to open the page with your data and look at the table below the map, incoming packets will update to the table as they are received. |
|
|
|
Post by markshancock on Jul 19, 2017 6:58:06 GMT -7
|
|
|
|
Post by David MSGC on Jul 19, 2017 14:53:38 GMT -7
I am open to any suggestions but in this case It is not relevant to javascript, it is how the database is setup and will not be changed before the eclipse. If you are doing any testing after midnight UTC you will have to go to the archive instead of the landing page. The page you view from the archive is the same exact page you view from clicking on the balloon on the landing page. |
|
|
|
Post by markshancock on Jul 19, 2017 18:25:46 GMT -7
I am open to any suggestions but in this case It is not relevant to javascript, it is how the database is setup and will not be changed before the eclipse. If you are doing any testing after midnight UTC you will have to go to the archive instead of the landing page. The page you view from the archive is the same exact page you view from clicking on the balloon on the landing page. David, The main screen is uniquely helpful as it assists in knowing what other balloons are in-flight in our space. Oregon is the first to see the Eclipse; so, we are expecting to have quite a few balloons in the space - some of which will be launching ahead of us. I was responding to your comment "... dates are stored as strings and not dates. If we can change it to a date we can do date math". I am open to helping; but, I have no visibility as to how your server app works. - Who created the tracking map?
- What is it written in?
- What/who filters what data to display?
|
|
