von jdonato » 09 Mär 2010, 16:45
Hi bodo
In response to 1:
As far as I can see, the channel number is expressed in Schedules Direct Data as "channel" (in the lineup--map section of the data), but you need to get "station id" first. Looking at my data, fccChannelNumber only applies to over-the-air (OTA) channels. Let's follow two channels, WAPADT and HBO. For example, WAPADT, an OTA channel:
<station id='63389'>
<callSign>WAPADT</callSign>
<name>WAPADT (WAPA-DT)</name>
<fccChannelNumber>27</fccChannelNumber>
<affiliate>Independent</affiliate>
</station>
And HBO, a not OTA channel (from Dish Network):
<station id='10240'>
<callSign>HBO</callSign>
<name>Home Box Office</name>
<affiliate>PAY</affiliate>
</station>
So fccChannelNumber won't help, because it refers only to OTA channels.
To correctly select the channel number, the data that needs to be retrieved first is "station id". This is so, because later we will find this code in the xml (in the lineup section):
<map station='63389' channel='4' channelMinor='1'/>
This will be channel "4.1" (you need to add the dot between "channel" and "channelMinor" combined)
And:
<map station='10240' channel='300' from='2004-08-02'/>
This will be channel "300"
So, "station id" 63389 will lead us to "channel" 4.1, and "station id" 10240 will lead us to "channel" 300, those are the real channel numbers (4.1, 300)
About number 2:
I am only one user, but if you ask me, I would prefer [number] [Channelname]. No dots, because this will confuse users, since the digital over-the-air channels have sub-channels (as in 4.1, 4.2, that is, channel 4 have two channels, the main channel 4.1, and another, 4.2, which could be a 24-hour weather station, sports, etc.).
Example, combining what we have now with the channel number:
"4.1 WAPADT (WAPA-DT)"
"300 Home Box Office"
Sorry for the long-winded explanation. I also think this should be easy to implement for the plugin author.
Thanks for such a great application.
Hi bodo
In response to 1:
As far as I can see, the channel number is expressed in Schedules Direct Data as "channel" (in the lineup--map section of the data), but you need to get "station id" first. Looking at my data, fccChannelNumber only applies to over-the-air (OTA) channels. Let's follow two channels, WAPADT and HBO. For example, WAPADT, an OTA channel:
<station id='63389'>
<callSign>WAPADT</callSign>
<name>WAPADT (WAPA-DT)</name>
<fccChannelNumber>27</fccChannelNumber>
<affiliate>Independent</affiliate>
</station>
And HBO, a not OTA channel (from Dish Network):
<station id='10240'>
<callSign>HBO</callSign>
<name>Home Box Office</name>
<affiliate>PAY</affiliate>
</station>
So fccChannelNumber won't help, because it refers only to OTA channels.
To correctly select the channel number, the data that needs to be retrieved first is "station id". This is so, because later we will find this code in the xml (in the lineup section):
<map station='63389' channel='4' channelMinor='1'/>
This will be channel "4.1" (you need to add the dot between "channel" and "channelMinor" combined)
And:
<map station='10240' channel='300' from='2004-08-02'/>
This will be channel "300"
So, "station id" 63389 will lead us to "channel" 4.1, and "station id" 10240 will lead us to "channel" 300, those are the real channel numbers (4.1, 300)
About number 2:
I am only one user, but if you ask me, I would prefer [number] [Channelname]. No dots, because this will confuse users, since the digital over-the-air channels have sub-channels (as in 4.1, 4.2, that is, channel 4 have two channels, the main channel 4.1, and another, 4.2, which could be a 24-hour weather station, sports, etc.).
Example, combining what we have now with the channel number:
"4.1 WAPADT (WAPA-DT)"
"300 Home Box Office"
Sorry for the long-winded explanation. I also think this should be easy to implement for the plugin author.
Thanks for such a great application.