Right now the bridge_processor calls gdalwarp to align and also explicitly reproject everything to EPSG:5070. If the reprojection wasn't necessary then we wouldn't need gdalwarp in the bridgeprocessor since the DEM and bridge VRT's could be aligned when the VRT is constructed using gdalbuildvrt from the underlying rasters.
Currently the only reason the projection is necessary is because of uncertainty surrounding the ripple1d terrain DEMs consistently being in 5070. If this is resolved we could remove gdalwarp
Right now the bridge_processor calls gdalwarp to align and also explicitly reproject everything to EPSG:5070. If the reprojection wasn't necessary then we wouldn't need gdalwarp in the bridgeprocessor since the DEM and bridge VRT's could be aligned when the VRT is constructed using gdalbuildvrt from the underlying rasters.
Currently the only reason the projection is necessary is because of uncertainty surrounding the ripple1d terrain DEMs consistently being in 5070. If this is resolved we could remove gdalwarp