id	summary	reporter	owner	description	type	status	priority	component	version	resolution	keywords	cc
90	Apparently wrong update rates for RTCM message type scanning of BNC	stuerze	stoecker	"The message type scanning in BNC delivers sometimes one message type twice per epoch (for example: 1064 every 10 seconds). But the real update rate is 5 seconds. Hence, it looks like the epoch before and / or behind it is missing. 
But the two data sets have different epochs (difference is 5 secons)
 
Please note, the stream content is correct but the issue is related to the buffering in the BKG Ntrip Caster. Hence, it has to be solved there. BNC delivers correct values in connection with other Casters."	task	closed	normal	Professional Caster		fixed		stuerze