Advanced Elevation Series (AES)

4m and 2m - Ground Control Required. Added cost unless customer supplied. If customer supplied there is a customer supplied data form that the sales engineer needs to complete-link added. 1. See if DG has needed control. 2. Engage VM for a GCP feasibility and pricing from Compass Data and KP Geo for any other control needs

Can be ordered with DTM only. Meant to be provide more detail that is captured but not to infer accuracy. 16m for 8m AES, 8m for 4m AES, 4m for 2m AES

Performed by vendor or ETP team. Process unclear since it is not an option on order form.

Digital Surface Model (DSM) Products are a reflective, or ‘first return’, surface representation that includes the terrain and cultural and vegetative features on the surface of the earth.

Digital Terrain Models (DTM) Products are a bare earth surface representation. All cultural and vegetative features on the surface of the earth are removed to represent the ground underneath

GeoTIFF, NITF2.1NCDRD

GeoTIFF, NITF2.1NCDRD

Top Directory <BaseName>DSM/DTM Directory PRODUCT_FILESGIS directory GIS_FILES

<Manifest FTP Metadata Files><BaseName><Manifest Metadata Files>GIS_FILES<Shapefile Files>PRODUCT_FILES<DSM or DTM Files><Shaded Relief Files> (if ordered)<Contour Files> (if ordered with DTM)<Product Metadata Files>

DVD

USB 2.0eSATAFirewire 400

FTP Pull

AES products will be consistent for industry standards and will be supported by common COTS but may not meet all AES standards (such as ISO 19115 metadata compliance) in Phase 1

100 km2

One geocell (defined as an area bounded by one degree of latitude and longitude. The earth-orb has 64,800 geocells. Most are quadrilaterals, but the 360 surrounding each pole are trilateral. Their length is constant; their width varies.)

Base Name<hddmmssHDDDMMSS>_<yyyy>_<mm>_<dd>_<productLev el>_<productType>_<increment id><hddmmHDDDMM>: coordinate of lower left minimum bounding rectangleh: hemisphere (N or S),dd: degrees latitude,mm: minutes latitude,ss: seconds latitude,H: hemisphere (E or W),DDD: degrees longitude,MM: minutes longitude,SS: seconds longitude.<yyyy>: 4 digit year of oldest image<mm>: 2 digit month of oldest image<dd>: 2 digit day of oldest image<product Level>: 2 character code for productL3 – 8 meter Vertical AccuracyL4 – 4 meter Vertical AccuracyL5 – 2 meter Vertical Accuracy<productType>: name of product typeDSM – Digital Surface ModelDTM – Digital Terrain Model<increment id>: A two digit number indicating the delivery number ‘01’ if not an incremental delivery.DSM<hddmmssHDDDMMSS>_<yyyy>_<mm>_<dd>_<productLevel>_DSM_<increment id>.TIFDTM <hddmmssHDDDMMSS>_<yyyy>_<mm>_<dd>_<productLevel>_DTM_<increment id>.TIF Tiled DSM or DTM<BaseName>_R<RowNum>C<ColNum>.TIF<RowNum>: the row number of the tile<ColNum>: the column number of the tileThe RowNum and ColNum fields will be left-padded with zeros to ensure that the values are as many characters as the highest value in the order. This will allow the product to line up conveniently in an alphabetized directory layout.Shaded Relief<BaseName>_SHADE.TIF

***These shapefiles may or may not be delivered based on product content or requirements***Contours<BaseName>_CONT.DBF<BaseName>_CONT.PRJ<BaseName>_CONT.SHP<BaseName>_CONT.SHXCloud Shape<BaseName>_CLOUD_SHAPE.DBF<BaseName>_CLOUD_SHAPE.PRJ<BaseName>_CLOUD_SHAPE.SHP<BaseName>_CLOUD_SHAPE.SHX(See Table 7)Obscured Shape<BaseName>_OBSCURED_SHAPE.DBF<BaseName>_OBSCURED_SHAPE.PRJ<BaseName>_OBSCURED_SHAPE.SHP<BaseName>_OBSCURED_SHAPE.SHX(See Table 7)Tile Shape<BaseName>_TILE_SHAPE.DBF<BaseName>_TILE_SHAPE.PRJ<BaseName>_TILE_SHAPE.SHP<BaseName>_TILE_SHAPE.SHX(See Table 7)Order Shape<BaseName>_ORDER_SHAPE.DBF<BaseName>_ORDER_SHAPE.PRJ<BaseName>_ORDER_SHAPE.SHP<BaseName>_ORDER_SHAPE.SHXThe order shape file shows the vertexes of the elevation AOI polygon.Product Shape<BaseName>_PRODUCT_SHAPE.DBF<BaseName>_PRODUCT_SHAPE.PRJ<BaseName>_PRODUCT_SHAPE.SHP<BaseName>_PRODUCT_SHAPE.SHXThe product shape file shows the vertexes for all products that make up the order item.Strip Shape <BaseName>_STRIP_SHAPE.DBF<BaseName>_STRIP_SHAPE.PRJ<BaseName>_STRIP_SHAPE.SHP<BaseName>_STRIP_SHAPE.SHXThe strip shape file shows the vertexes for all the strips or substrips included in the order item and will also show the catalog ID for each strip or substrip.

End of Transfer File<BaseName>_EOT.TXTThe appearance of this file on the FTP site indicates that DG has completed transferring all product files. It is a zero length file. This file is described in section 3.2.1 of the DigitalGlobe Medial Layout Guide.Manifest File<BaseName>.MANThis file contains data associating the elevation product with the order fulfilled by the product. This file is described in section 3.2.2 of the DigitalGlobe Medial Layout Guide.

Top-level Delivery Index (XML) File <BaseName>_README.XMLThis file is described in section 3.2.4 of the DigitalGlobe Medial Layout Guide.Layout JPG<BaseName>_LAYOUT.JPGThis file is described in section 3.2.5 of the DigitalGlobe Medial Layout Guide.

Product Component Index (subdirectory readme) File<BaseName>_LIC_README.TXTSee section 5.3 for file contents.ISO19115 Metadata<BaseName>_ISO19115.XMLThis file is described in section 3.2.7.15 of the DigitalGlobe Medial Layout Guide.Browse Image<BaseName>_BROWSE.JPGThis is a low resolution shaded relief image. This file is described in section 3.2.7.2 of the DigitalGlobe Medial Layout Guide.License Text FileLICENSE.TXTDEMONSTRATION.TXTThis file is described in section 3.2.7.4 of the DigitalGlobe Media Layout Guide.

GeoTIFF 32-bit signed floating point

GeoTIFF 8-bit unsigned integer

ESRI line shapefile – any line type can be usedAttributes: elevation, Contour_TypeElevation: floating point number in meters, xxx.xxContour_Type: Index, Intermediate, SupplementAn index divisible by 5 will have Index=TRUEOther indies will have Index=FALSE

Customers will be able to order products in DG supported projections (See Table 10). Product files will be delivered in the ordered datum and projection. GIS files will be delivered in geographic.

Customers will be able to order products in the following datums:·        EGM96 [Default]Ellipsoid associated with projection (See Table 10)

·        Orders greater than 1,000km2 in area will be fulfilled within 90 days of completion of any required tasking and receipts of any required Ground Control Points.·        2 meter Vertical accuracy orders less than 1,000km2 will be fulfilled within 45 days of completion of any required tasking and receipts of any required Ground Control Points.·        8 meter Vertical Accuracy and 4 meter Vertical Accuracy orders less than 1,000km2 in area will be fulfilled within 30 days of completion of any required tasking and receipts of any required Ground Control Points.

The overlap of stereo models match within the tolerance of the product

When more than one stereo model is used to make an AES product, the elevation values between the models will be matched to the neighboring model. This will reduce elevation shifts between stereo models. In this example, the stereo models overlap between the yellow lines. Note the breaks in the contour lines where one stereo model ends, and the next begins. After Edge Matching, the elevation values are continuous from one stereo model to the next. There are no breaks in the contour lines.

Spikes, wells, and blunders will be removed to aesthetically meet product quality

Spikes, wells and blunders are usually caused by errors in correlation between stereo images. These errors can be caused by changing conditions between the images such as a moving vehicle, or changed ground conditions like a plowed field. In this example, there are small blunders that show as features in the elevation data that are not in the imagery. The operator will interpolate elevation values over the blundered region based on the imagery available.

Regions outside of the order polygon are classified as NULL value. This example illustrates null values outside the area of interest (AOI). Null values are set to a -32,767 default elevation.

Water along coastlines • Elevation of 0m for products referenced to MSL • This is N/A for Ellipsoid projections

Example represents a flattened coastline with a default elevation of 0.0 meters.

Water bodies with a width or length greater than 50m and Rivers, Streams, Canals, etc with an average width of 50m or more are flattened to the visual surface of the water.Optional for all products

The first example illustrates a drain bed where it is not flattened. The second example has a DLD (double line drain) depicted after determining it met capture criteria. The DLD has a monotonic flow, maintaining a constant elevation throughout.

Flattened to the surrounding terrain.

Road flattening is an option for the DSM product only. The first example is a city block location where both buildings and trees are shown. The “before edited” picture below shows that this area has not yet been edited to remove unwanted artifacts.

Flattened to the surrounding Cloud areas will be delineated by the Cloud Shapefile and filled using SRTM, interpolation, or other DG content. terrain.

Cloud areas are captured after reviewing all possible imagery coverage solutions. A cloud shapefile is depicted to outline only the locations where stereo coverage is not visible and the DEM may not maintain its accuracy within the cloud shapefile limits.

Regions obscured by heavy vegetation (DTM only), steep terrain, cloud shadow, or other features will be delineated by the Obscured shapefile in both DTMs and DSMs. Up to 50% of the AOI can be designated as ‘Obscured Areas’. Obscured Areas are processed using a ‘best effort’ methodology and may not meet designated product accuracy. The following attributes will be included within the obscured shapefile: cloud shadow, vegetation, collection geometry, other (using the field, “names”).

Features that are to be captured in a DSM or DTM can be obscured for reasons such as dense vegetation (DTM only), steep terrain, building lean, cloud shadow, etc. This makes accurate determination of the height of bare ground difficult, and in some cases, impossible. In these areas, the best determination of the ground height will be made. Up to 50% of the AOI can be designated as ‘Obscured Areas’. Obscured Areas are processed using a ‘best effort’ methodology and may not meet designated product accuracy. Obscured regions greater than ½ square kilometer will be captured in the Obscured Area shape file and delivered with the product.

When the AOI is tiled, the Tile shapefile will define the limits of the products tiles.

Required editing seems like the same except for the omission of the Obscured shape file in the 4m DTM. Should we only list once and only highlight differences?

Contours are intended to represent the elevation at ground level. Contours are only offered on DTMs. DTMs represent bare earth, or ground level features. Contour products also represent ground level elevations, and therefore contour products are able to be made from DTMs.DSMs include features such as buildings and bridges. These features have steep (vertical) faces, and are therefore difficult to represent with contour products. DSMs also represent the height of the vegetation, and not ground level. For these reason, contours are not offered with a DSM product.

Contour intervals are based on the absolute vertical LE90 of the product that the contours are generated from. This allows a user who only has access to the contour product to infer an accuracy of the vertical data represented by the contours.The contour intervals shall be twice the absolute vertical LE90 of the data that the contours are generated from.  

Contours are classified as Index Contours and Intermediate Contours for cartography purposes. Index Contours are represented as Bold line.Intermediate Contours are represented as thin lines. Supplemental ContoursElevation models that are generated from Satellite imagery usually have a high level of relative detail. These Elevation models capture details that would normally not be represented with the Index and Intermediate Contours. In order to represent this detail, Supplemental Contours are also delivered in the Contour Product.For the AES Product, Supplemental Contours will have an interval of half the absolute vertical LE90 of the data they are derived from, and be evenly spaced between the Index and Intermediate Contour lines.Supplemental Contours are contour lines that are drawn between the Index and Intermediate Contours to densify the contours and show relative detail. They are not intended to represent or infer absolute accuracy.Display of Supplemental Contours is optional. Terrain detail, ground conditions, and the intent of the project will impact the need for their display.When Supplemental Contours are represented, they are shown as dashed lines.

The elevation value of an Index or Intermediate Contour shall be a multiple of the contour interval. This ensures that the contours at sea level or ellipsoid height will have a value of 0 (zero).For the AES products, there are four Intermediate Contours between each Index Contour, resulting in every fifth contour line (excluding the optional Supplemental Contour) being an Index Contour. And, there are three Supplemental Contours between the Index and Intermediate Contours. Refer to Table 16 for an example of the relationship of Index, Intermediate, and Supplemental Contours in the AES products.

Contour lines are classified into three categories; Index, Intermediate, and Supplemental. Each line has an elevation associated to the line.Typically, the Index lines are plotted as a bold line, and the intermediate contour lines are plotted at a thinner weight