Questions that I have about the scope of the coverages in CDB:
Coverages in CDB 1.x included things that were more or less static (imagery, elevation), but it did include periodic temporal (time-based) items like quarterly and monthly imagery. It did not include things that change on a short time scale, like water temperatures or weather properties, and it did not store multiple versions of long term temporal coverages like imagery that change slowly over time (I am assuming that higher-order constructs can handle this). Is this still a good assumption to work from?
Are there any missing data layers from CDB 1.x that are needed to support SOCOM's needs in "land, sea, and air, cyber, electromagnetic spectrum, space and critical infrastructure"? I know that some of these are likely changing during a mission and don't fit CDB's focus on the unchanging datasets (see previous question), but there is probably some data types I am not aware of that would fit well here.
The current CDB 1.x coverages are:
Elevation - Point based elevation posts
Minimum and Maximum Elevation for an area (for optimizing line of sight calculations)
Maximum height of culture for an area (for optimizing line of sight calculations)
Imagery - Consists of year-round, quarterly, and monthly imagery, plus emissive light maps for the terrain
Multi-spectral Imagery - same categories as in Imagery, but with different wavelengths in Near Infrared and Short-wave Infrared that are primarily reflected (for NVG simulation/stimulation and newer SWIR sensors)
Raster Materials - semantic composite material per texel of imagery, used primarily for thermal/emissive Infrared (medium and long wave IR) and radar simulation. This is not a PBR (Physically Based Rendering) material for visual rendering.
Questions that I have about the scope of the coverages in CDB:
Coverages in CDB 1.x included things that were more or less static (imagery, elevation), but it did include periodic temporal (time-based) items like quarterly and monthly imagery. It did not include things that change on a short time scale, like water temperatures or weather properties, and it did not store multiple versions of long term temporal coverages like imagery that change slowly over time (I am assuming that higher-order constructs can handle this). Is this still a good assumption to work from?
Are there any missing data layers from CDB 1.x that are needed to support SOCOM's needs in "land, sea, and air, cyber, electromagnetic spectrum, space and critical infrastructure"? I know that some of these are likely changing during a mission and don't fit CDB's focus on the unchanging datasets (see previous question), but there is probably some data types I am not aware of that would fit well here.
The current CDB 1.x coverages are: