Resolved Still having time zone import issues

[pcohen]

I reported this a while ago and was told it would be fixed. For this month's schedule, I still have to adjust all the times for trips that change time zones. This is true in both APDL and the logbook pro importer app. (I call it the logbook pro importer app, because to call it logbook pro mobile is really a stretch.) I have local time set in APDL settings. All pairings in Flica are in local time.

 

[pcohen]

 

[pcohen]

So on APDL in the first image, the scheduled flight time is 2:53. Because of the time zone change, it is actually 3:53. I have had have to adjust almost every leg of my schedule. Is this a daylight savings thing?

 

[pcohen]

Maybe I am doing something wrong.

 

[pcohen]

 

[Neal Culiner]

Your Flica schedule image shows 0615 to 0908 yet your leg view shows 0808 for IAH. Can you paste this trip data from flica into a reply so I can paste it into the schedule importer on APDL.net. Login to Flica and copy the trip please, paste into a reply.

 

[pcohen]

L7633 : 05MAYEXCEPT SUN SATBSE REPT: 0530LOperates: May 4-May 31
Base/Equip: LGA/EM7CA01EXCEPT ON May 9, May 10, May 11, May 13, May 17, May 19, May 20, May 26, May 30
DYDDDHCFLTNODPS-ARSDEPLARRLBLKTGRNTOA TBLKTDHD TCRDTDUTY/FDPLAYOVER
TH05 3299LGA-IAH06150908 035300468868
TH05 3345IAH-LGA09541434 0340 8868 0733 07330919/0904
D-END: 1449L T.A.F.B.: 0919

 

[pcohen]

 

[pcohen]

Screenshot easier to read I think

 

[Neal Culiner]

Phil, I can't process the trip data as you pasted because of the format probably from this forum'ware, however, I think I know what the problem is. The times the schedule importer is using and going into APDL are correct and should not be modified. I believe the confusion is "Device Local" in Logbook Pro Mobile and "Local" in APDL:

Device Local in Logbook Pro Mobile is the timezone of your device's location, i.e. when you input the times you can use the local time of where you are standing

Local in APDL is local AT THAT DESTINATION regardless of where your device is physically located. So your IAH time should be as shown on the Flica trip info as 0908 and if you are changing it to 0808 that is incorrect as it's local AT IAH.

 

[pcohen]

I'm not changing it in APDL. It is importing as 808. I have to change it to 908 to get correct block time. ORD is also doing this.

 

[Neal Culiner]

How exactly are you processing your trip data? APDL Toolkit automatic? APDL Toolkit copy/paste? Pasting it into the Schedule/Calendar view view the + button, or on APDL.net directly?

Please send the entire trip to me via email to sales@nc-software.com so I can try to reproduce the issue and ensure the time zone conversions are correct.

Also, is your device's clock automatically getting its time from the network or have you set it to a manual time?

 

[pcohen]

Device is set to automatic

 

[pcohen]

That is the entire trip above. It is a 1 day trip. Just a LGA-IAH turn

 

[pcohen]

L7633 : 06MAYEXCEPT SUN SATBSE REPT: 0530LOperates: May 4-May 31
Base/Equip: LGA/EM7CA01FO01EXCEPT ON May 9, May 10, May 11, May 13, May 17, May 19, May 20, May 26, May 30
DYDDDHCFLTNODPS-ARSDEPLARRLBLKTGRNTOA TBLKTDHD TCRDTDUTY/FDPLAYOVER
FR06 3299LGA-IAH06150908 035300468860
FR06 3345IAH-LGA09541434 0340 8860 0733 07330919/0904
D-END: 1449L T.A.F.B.: 0919

 

[pcohen]

I think I pasted it to APDL.net because only the prelim schedules were available, , so it was too early in the month for the automatic download.

 

[Neal Culiner]

Try pasting it into APDL.net again and make sure the time zone option is set to LOCAL. You can also paste it into the app by tapping the + button on the top right of Schedule/Calendar views.

 

[pcohen]

Ok. That works. Looks like APDL.net might have been set to custom time zone. M

 

[pcohen]

Thanks.

 

[Neal Culiner]

It will remember whatever you set...glad you have it resolved.