{'fraction_non_alphanumeric': 0.02585604472396925, 'fraction_numerical': 0.005590496156533892, 'mean_word_length': 4.917355371900826, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Requirements For Space-Sensed Oceanographic Data

In 1978 the United States launched the oceanographic satellite SEASAT. Although the satellite operated successfully for only one hundred days in space, it was a monumental event. In the years that followed, atmospheric and oceanographic scientists revealed the true potential of such a system. Following SEASAT there was a NASA proposal for SEASAT B, and the interagency (NASA, NOAA, NAVY) oceanographic satellite NOSS. Unfortunately for those of us who rely on accurate forecasts of ocean conditions, neither system became a reality. However, reiterating the operational requirement for such a system, in April 1981 the Director, Naval Oceanography Division, Office of the Chief of Naval Operations formulated the proposal for N-ROSS, the Navy Remote Ocean Sensing System. From the beginning, one thing was obvious, Navy could not afford to go it alone. It was true that the Defense budget was larger, but money needed to build N-ROSS was also required to build ships, aircraft and weapons systems. We approached NASA and NOAA informally with the N-ROSS proposal. Could they help? Although neither agency was in a position to make a firm commitment, we were encouraged to determine the Navy's willingness to commit itself to such an undertaking. In addition we asked the Air Force to help with the launch, command and control phases. They too gave us the encouragement to proceed.