Difference between revisions of "EclipseLink/Examples/Radar"
m (New page: ==Radar Application== ===Requirements== ====R1: Determine layered GIS data for rainfall distribution at 1km resolution @ 200 km range=== ====R2: Provide historical data==== =====R2.1: Prov...)
Revision as of 16:54, 13 September 2011
- 1 Radar Application
- 2 =Requirements
- 2.1 =R1: Determine layered GIS data for rainfall distribution at 1km resolution @ 200 km range
- 2.2 Design Issues
- 2.3 References
=R1: Determine layered GIS data for rainfall distribution at 1km resolution @ 200 km range
R2: Provide historical data
R2.1: Provide volumentric data per GPS position
R3: Provide 30 min prediction window
R3.1 Extend prediction window by including surrounding area weather
R4: Provide present status per GPS position
DI1: Database: Derby or Oracle GIS/SDO aware?
I2: Database Expected Volume
- There are 14 levels of rainfall represented by color bands from purple to light blue. If we include the ground color (green-grey), rivers (navy) and borders (black) we have 17 levels. We also want to encode (null/unset/no-data) as white or -1 - this gives us 18 levels which fits in a single 8 bit byte.
- There are approximately 500x480 pixels at 1km resolution which works to 234Kb decoded.
- We expect 24 x 6 = 144 images / site / day, which comes to 234Kb x 144 = 34Mb / day / site.
- We therefore need 12 Gb storage / year / site. A standard 2Tb drive which is around the effective limit of most databases will hold 169 years of data (disregarding compression gains and error handling losses). We should be able to hold our goal of 10 years of radar data for 16 sites comfortably.
- This assumes we store raw data without gps coordinates, we may want to only store colored pixels.