AWIPS NEXRAD ORPG Interface

1. AWIPS NEXRAD ORPG Interface Lowell Schaffert

2. Standalone ORPG • Host the ORPG software on a standalone system. • RSA ORPG to BDDS (level II data), refer to Figure 1 (a & b) • This is an internal NWS interface • This is a serial binary data stream using a TCP/IP socket • Constant socket connection with basically continuous data transfer, magenta line • ORPG initiates the socket connection to the BDDS, green line

3. Figure 1a

4. Figure 1b

5. Standalone ORPG, Cont. • DS-1 (AWIPS file server) to RSA ORPG (level III data) connection (the public side of the ORPG) refer to figures 2 (ER) and 3 (WR) • Need a well-known, agreed to port number • Protocol - raw TCP/IP socket • DS-1 initiates the socket connection to the ORPG system, green line • The data is transmitted between DS-1 and the ORPG system on this socket, magenta line • Data product requests from DS-1 to ORPG system • There is a listen port on the ORPG • Data products from ORPG system to DS1, level III data • This is a serial binary data stream using a TCP/IP socket, constant socket connection with basically continuous data transfer • You may also send a request for a one-time data product to the ORPG.

6. Figure 2

7. Figure 3

8. Standalone ORPG, Cont. • DS-1 to RSA ORPG (level II data for the model cluster), refer to figures 4 (ER) and 5 (WR) • Need a well-known, agreed to port number • Protocol - raw TCP/IP socket • DS-1 (BDDS Reader) initiates the socket connection to the ORPG system, green line • The level II data is transmitted from the ORPG system to DS-1 (BDDS Reader) on this socket, magenta line • Permanent connection after the initial request to send data products (RPS list) and alert request from DS1 to ORPG. • This is a serial binary data stream using a TCP/IP socket, with basically continuous data transfer • The Model Server gets the level II data from DS-1, blue line

9. Figure 4

10. Figure 5