Atch_02_-_Database_Design_Requirements.pdf
PDF 40 KB Posted
- Attached to
- KDAM ATARS Federal contract opportunity
- Solicitation number
- FA8621-15-R-6328
About this file
DRAFT RFP DATABASE DESIGN REQUIREMENTS
View the file
Other files for this federal contract opportunity
Show all 50
KDAM ATARS has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Section J, Attachment 02 –Draft Database Design Requirements
FA8621-15-R-6328
6-Apr-15, Page 1 of 2
ATTACHMENT 02
DATABASE DESIGN REQUIREMENTS
All work shall include database documentation
1. Geocells
The geocell areas shall be designed to meet the following requirements:
1 geocell =~ 60nm x 60nm area
a. 1.0m textel/pixel resolution imagery or high quality generic imagery where the eye can detect mountains, valleys, ridgelines, and slopes
b. Level I DTED (approx. 90m post)
c. Feature data equal to Joint Operation Graphic (JOG) 1:250k detail
d. Feature data matched only to geocell boundaries
e. Microtexture on all non-high resolution textures
f. Natural vegetation scatter
g. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights.
2. Targets
The target areas shall be designed to meet the following requirements:
1 target = 30nm x 30 nm area around target + 6nm x 6nm area around target
a. 30nm x 30nm square around target
i. .625 textel/pixel resolution imagery or best available within 30nm x 30nm area*
ii. Level II DTED (approx. 30m post) or best available within 30nm x 30nm area*
iii. Feature data equal to Topographic Line Map (TLM) 1:50k detail or best available within 30nm x 30nm area*
b. 6nm x 6nm square around target
i. .3125m textel/pixel resolution imagery or best available within 6nm x 6nm area*
ii. Level III DTED (approx. 10m post) or best available within 6nm x 6nm area*
iii. Feature data equal to TLM 1:24k detail or best available within 6nm x 6nm area*
c. Microtexture on all non-high resolution textures
d. Natural vegetation scatter
e. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights
3. Objectives
The objective areas shall be designed to meet the following requirements:
1 Objective = 6nm x 6nm square around area of interest
a. .3125m textel/pixel resolution imagery or best available within 6nm x 6nm area*
b. Level III DTED (approx. 10m post) or best available within 6nm x 6nm area*
c. Feature data equal to TLM 1:24k detail or best available within 6nm x 6nm area*
d. Microtexture on all non-high resolution textures
e. Natural vegetation scatter
f. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights.
4. Airfields
The airfields shall be designed to meet the following requirements:
Section J, Attachment 02 –Draft Database Design Requirements
FA8621-15-R-6328
6-Apr-15, Page 2 of 2
1 airfield = 30nm x 30nm area + 6nm x 6nm area + actual airfield
a. 30nm x 30nm square around airfield
i. .625 textel/pixel resolution imagery or best available within 30nm x 30nm area*
ii. Level II DTED (approx. 30m post) or best available within 30nm x 30nm area*
iii. Feature data equal to TLM 1:50k detail or best available within 30nm x 30nm area*
b. 6nm x 6nm square around airfield
i. .3125m textel/pixel resolution imagery or best available within 6nm x 6nm area*
ii. Level III DTED (approx. 10m post) or best available within 6nm x 6nm area*
iii. Feature data equal to TLM 1:24k detail or best available within 6nm x 6nm area*
c. Microtexture on all non-high resolution textures
d. Natural vegetation scatter
e. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights
f. Include all taxiways, runways, parking ramps, etc. accurate to real-world locations, widths and lengths
g. Include all taxiway and runway markings
h. Include all airfield detail included in real-world approach plates and FLIP data
i. Include geotypical models of the same size and shape appropriate for the airfield buildings. Models must be placed in real-world positions
j. Control tower must be placed in real-world location
k. Include accurate airfield lighting
i. All airfield lighting shall have multiple levels of control and appropriate directionality.
Individual runway lighting shall have separate controls (i.e. approach lights, VASI, PAPI, runway lights, end lights).
l. Beacons and navaids must be placed in real-world positions.
5. Routes
The routes shall be designed to meet the following requirements:
a. Route based on Black Diamond - Kirtland AFB to Pueblo
b. Feature data equal to Joint Operation Graphic (JOG) 1:250k detail
c. Match feature data 5 miles on either side of route
d. Assumes no geospecific imagery
6. Models
a. Low Fidelity Models - 1 to 500 polygons
b. Medium Fidelity Models - 501 to 1300 polygons
c. High Fidelity Models - 1301 to 3000 polygons
7. Radar/CTDB
a. Any change made to the visual database will require an update to both the radar and CTDB databases unless otherwise specified.
*Or best available - sometimes in areas there is not high resolution imagery or map data because it doesn't exist or there is an additional charge to acquire it or create it from a third party vendor.
File details come from the government source that posted it. Updated .