Getting more than 24 hours of Guide Data

[scJohn]

I am requesting 23:59:00 of guide data at a time by channelId. So 00:00:00 - 23:59:00 using:
/services/service?method=channel.listings&channel_id=7216&start=1526184000&end=1526270340&format=json

So for the current day(the 13th), everything is okay. But when I request tomorrow's guide (the 13th, or the 14th), I also get the 11:00 PM - 11:59 PM from the 12th. This results in 2 entries for the 12th at 11:00PM - 11:59 PM.

Is this the correct response? Is there an adjustment I can make to the parameter(s) so I do not get the last hour of the previous day?

Thanks.

[shspvr]

I am requesting 23:59:00 of guide data at a time by channelId. So 00:00:00 - 23:59:00 using:
/services/service?method=channel.listings&channel_id=7216&start=1526184000&end=1526270340&format=json

So for the current day(the 13th), everything is okay. But when I request tomorrow's guide (the 13th, or the 14th), I also get the 11:00 PM - 11:59 PM from the 12th. This results in 2 entries for the 12th at 11:00PM - 11:59 PM.

Is this the correct response? Is there an adjustment I can make to the parameter(s) so I do not get the last hour of the previous day?

Thanks.

I take that your using the tuner EPG ? then maybe you should signup for Schedules Direct there EPG good for 14 day

[mvallevand]

I take that your using the tuner EPG ? then maybe you should signup for Schedules Direct there EPG good for 14 day

This is a developer sub forum question nt an end user issue.

The actual problem is that epg gude data start time equals the stop time of the previous listing.. The developer is left to deal with the nuance, not sure if sub should deal with it in the API or not. I figure adding one second to the start time would get the proper listng

Martin

[shspvr]

I know it developer sub forum
Usely this happing when pull the EPG from tuner because they only give you about 24 hour of data and sometime it dose odd things I seen this happing with just about every DVR software that pull data off the tuner out there which is why I recommend to use 3rdparty EPG like Schedules Direct
I don't how EPG is done in Canada but here USA is not done very well that only get address when start rolling ATSC 3.0 then we will start long time EPG data 7 days or more directly off the tuner.

[sub]

I am requesting 23:59:00 of guide data at a time by channelId. So 00:00:00 - 23:59:00 using:
/services/service?method=channel.listings&channel_id=7216&start=1526184000&end=1526270340&format=json

So for the current day(the 13th), everything is okay. But when I request tomorrow's guide (the 13th, or the 14th), I also get the 11:00 PM - 11:59 PM from the 12th. This results in 2 entries for the 12th at 11:00PM - 11:59 PM.

Is this the correct response? Is there an adjustment I can make to the parameter(s) so I do not get the last hour of the previous day?

Thanks.

This call finds any listings that overlap with the start-end range specified. It effectively does this SQL query:

select * from EPG_EVENT where channel_oid=@channel_oid end_time >= @range_start_time and start_time <= @range_end_time

As Martin suggested, you could probably avoid including a show that ends exactly at the range start time by adding a second.