Weatherscan Problems for Topeka, KS Unit

[kswx29]

I don't know much information except that the Weatherscan Unit is for Cox Communications in Topeka, KS.  It is on Channel 270.
There is a city incorrectly labled.  In the top ticker, it shows "Olathe" for the City of Junction City.  The two cities are very far apart.  Here is a picture.


Also, the "Estimated Precip" "Precip Forecast" and "Palmer Drought Severity" show up "Temporary Unavailable" and have been all day.  Also, the Doppler Radar shows "Temporary Unavailable" for Topeka and Manhattan, but not for for Junction City (Incorrectly stated "Olathe" in the top city ticker)

[Trevor]

IIRC, you usually will see that some things read "Temporarily Unavailable" for at least a couple of days after recieving WeatherScan.

[Zach]

I think the CC name could be different as there might not be a reporting station set up in Olathe yet, seeing how the unit is new.

[kswx29]

@Zach:  Well if that was so, I would think they would choose a city more close to Olathe, not a city about 140 miles away.  Olathe is about 60 miles East of Topeka while Junction City is about 60 West.  Also, I don't know how long we have had the unit, but a statement put out by cox says the channel would go into effect "On or After May 18th."

[Mike M]

I had a similar problem here back in 2006 were the title on the top said Gloucester City, but the forecasts were actually for Philadelphia. The issue was corrected a few days later. As for Garden, I agree with Trevor. When that segment made its debut in Philly, there were some products that were unavailable for a couple days.

[Zach]

@Zach:  Well if that was so, I would think they would choose a city more close to Olathe, not a city about 140 miles away.  Olathe is about 60 miles East of Topeka while Junction City is about 60 West.  Also, I don't know how long we have had the unit, but a statement put out by cox says the channel would go into effect "On or After May 18th."

Wow! Btw, I have seen worse. The FiOS Weatherscan in Tampa actually serves Tampa, Venice, and Winter Haven. Venice is about 100 miles south of Tampa and Winter Haven is about 50 miles east of Tampa.

[TWC STAR Team]

Corrected

[kswx29]

  Thank you!  The local radar for Topeka still isn't working though...but like people said maybe it takes time?

[KevOwensby]

I contacted TWC and Cox about both issues plus why we're getting Junction City and not a city like Lawrence instead. They fixed the Olathe/Junction City problem yesterday. The guy at Cox Tech Support emailed me back and said he'd forward the adding different cities issue to the engineers to see what could be done. A different guy with Cox Tech via phone told me all the Weatherscan Intellistars across the area were reading Temporarily Unavailable due to a "satellite alignment issue TWC is working on." Which I don't believe. Call Cox and report the problem. They see it as a "if only one person reports it then it's only happening with you." problem. If you call or email they're muchmore likely to correct it.

[kswx29]

I contacted TWC and Cox about both issues plus why we're getting Junction City and not a city like Lawrence instead. They fixed the Olathe/Junction City problem yesterday. The guy at Cox Tech Support emailed me back and said he'd forward the adding different cities issue to the engineers to see what could be done. A different guy with Cox Tech via phone told me all the Weatherscan Intellistars across the area were reading Temporarily Unavailable due to a "satellite alignment issue TWC is working on." Which I don't believe. Call Cox and report the problem. They see it as a "if only one person reports it then it's only happening with you." problem. If you call or email they're muchmore likely to correct it.

Do you live in Topeka too?  I was thinking that the weatherstar unit was serving both the Topeka and Manhattan/JC areas and that was why they had Junction City on there but I'm not completely sure. 

[Zach]

I contacted TWC and Cox about both issues plus why we're getting Junction City and not a city like Lawrence instead. They fixed the Olathe/Junction City problem yesterday. The guy at Cox Tech Support emailed me back and said he'd forward the adding different cities issue to the engineers to see what could be done. A different guy with Cox Tech via phone told me all the Weatherscan Intellistars across the area were reading Temporarily Unavailable due to a "satellite alignment issue TWC is working on." Which I don't believe. Call Cox and report the problem. They see it as a "if only one person reports it then it's only happening with you." problem. If you call or email they're muchmore likely to correct it.

The Galaxy-15 satellite is passing under the AMC-11 satellite and it failed to stop sending signals, which will cause interference. Source here:

[TWCToday]

I contacted TWC and Cox about both issues plus why we're getting Junction City and not a city like Lawrence instead. They fixed the Olathe/Junction City problem yesterday. The guy at Cox Tech Support emailed me back and said he'd forward the adding different cities issue to the engineers to see what could be done. A different guy with Cox Tech via phone told me all the Weatherscan Intellistars across the area were reading Temporarily Unavailable due to a "satellite alignment issue TWC is working on." Which I don't believe. Call Cox and report the problem. They see it as a "if only one person reports it then it's only happening with you." problem. If you call or email they're muchmore likely to correct it.

The Galaxy-15 satellite is passing under the AMC-11 satellite and it failed to stop sending signals, which will cause interference. Source here:

No! The AMC-11 satellite is only used for legacy STAR systems. TWC is not broadcast on that satellite for satellite, Intellistar, and WeatherScan users but rather AMC-10. The video you linked to was taken from a feed using the AMC-11 feed.

[KevOwensby]

Yes, I live in Topeka too.