Changeset 5609 in ntrip
- Timestamp:
- Jan 22, 2014, 12:30:04 PM (11 years ago)
- Location:
- trunk/BNC/txt
- Files:
-
- 1 added
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/txt/frankfurt.tex
r5608 r5609 193 193 194 194 \begin{frame} 195 \frametitle{ Kalman Filter}195 \frametitle{Algorithms -- Kalman Filter} 196 196 197 197 \begin{small} … … 297 297 \end{frame} 298 298 299 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 300 301 \begin{frame} 302 \frametitle{Data Transfer -- NTRIP} 303 304 In order to be useful data have to be provided in a well-defined \textcolor{blue}{format}. 305 RTCM (Radio Technical Commission for Maritime Services) messages are widely used for GNSS data in 306 real-time. 307 308 \vspace*{5mm} 309 310 In addition to a format the so-called \textcolor{blue}{protocol} has to be defined. Using a given 311 protocol the data user communicates with the data provider. 312 313 For GNSS data, the so-called \textcolor{blue}{NTRIP} streaming protocol is used. 314 \begin{itemize} 315 \item NTRIP stands for Networked Transport of RTCM via Internet Protocol. 316 \item NTRIP is in principle a layer on top of TCP/IP. 317 \item NTRIP has been developed at BKG (together with TU Dortmund). 318 \item NTRIP is capable of handling hundreds of data streams simultaneously delivering the data 319 to thousands of users. 320 \item NTRIP is world-wide accepted. 321 \end{itemize} 322 323 \end{frame} 324 325 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 326 327 \begin{frame} 328 \frametitle{NTRIP} 329 330 Efficiency of data transfer using NTRIP is achieved thanks to the GNSS Internet Radio / 331 IP-Streaming architecture: 332 333 \includegraphics[width=0.7\textwidth,angle=0]{ntrip.png} 334 335 \end{frame} 336 299 337 \end{document}
Note:
See TracChangeset
for help on using the changeset viewer.