X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 08 Jul 2016 03:03 PM by  anon
Reading Push-Broom sensor row/frame coordinate data
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
08 Jul 2016 03:03 PM
    I'm working with a push-broom style hyperspectral imager that outputs separate coordinate and aircraft yaw/pitch/roll information for each row (frame) of the generated image. That information is contained in a separate "Navigation" text file. The header file (below) which accompanies the image does not provide any coordinate information. Can anyone give me any general tips on how to pass the row coordinates, and yaw/pitch/roll information to ENVI so I can get the image to display correctly? I have pasted the contents of an example header file, followed by a single frame from the accompanying Navigation data file below. If it can't readily be done, I'd like to know. If it will require some advanced programming skills, that would be helpful too. I'm fairly new to ENVI still. ============================== Header file contents: ENVI description = {Generated using ENVIFileOut pipeline service module. Sensor: vnir. Frame rate: 67.0 hz. Exposure: 2000 us.} data type = 12 lines = 10000 samples = 680 bands = 60 interleave = bip byte order = 0 wavelength units = Nanometers wavelength = {401.67, ...} ============================== Navigation file excerpt: FRAME_ID 10002 PACKET_SIZE 012979 START_TIME 1149609328.389214 REQUEST_TIME 1149609328.389214 ANGULAR_UNITS degrees GROUND_SPEED_UNITS meters/sec GROUND_SPEED 0.414 CAM_LOC_LAT 35.33483512 CAM_LOC_LON -120.76240358 CAM_LOC_ALT 113.507 CAM_LOC_ALT_ELLIPSOID 78.185 VELOCITY_EAST -0.205402 VELOCITY_NORTH 0.359797 VELOCITY_UP 0.238916 PLATFORM_ATT_YAW 138.62106 PLATFORM_ATT_PITCH -0.25222 PLATFORM_ATT_ROLL 5.59221 SENSOR_ATT_YAW -30.48000 SENSOR_ATT_PITCH -87.41000 SENSOR_ATT_ROLL 30.48000 LOS_ATT_YAW 64.67447 LOS_ATT_PITCH -82.81715 LOS_ATT_ROLL 0.00000 CENTER_LAT 35.33489027 CENTER_LON -120.76226136 CENTER_ALT 0.000 UPPER_LEFT_LAT 35.33524299 UPPER_LEFT_LON -120.76176857 UPPER_LEFT_ALT 0.000 UPPER_RIGHT_LAT 35.33457678 UPPER_RIGHT_LON -120.76269935 UPPER_RIGHT_ALT 0.000 REGPOINTS 23,1,0035.3352429896,-120.7617685657,000000000.00000,32,0035.3352089058,-120.7618161873,000000000.00000,63,0035.3351752153,-120.7618632582,000000000.00000,94,0035.3351419036,-120.7619097996,000000000.00000,125,0035.3351089645,-120.7619558204,000000000.00000,156,0035.3350763917,-120.7620013294,000000000.00000,187,0035.3350441792,-120.7620463351,000000000.00000,218,0035.3350123209,-120.7620908457,000000000.00000,249,0035.3349808111,-120.7621348693,000000000.00000,280,0035.3349496441,-120.7621784140,000000000.00000,311,0035.3349188143,-120.7622214875,000000000.00000,342,0035.3348883162,-120.7622640974,000000000.00000,373,0035.3348581446,-120.7623062511,000000000.00000,404,0035.3348282943,-120.7623479561,000000000.00000,435,0035.3347987600,-120.7623892193,000000000.00000,466,0035.3347695369,-120.7624300478,000000000.00000,497,0035.3347406200,-120.7624704484,000000000.00000,528,0035.3347120045,-120.7625104278,000000000.00000,559,0035.3346836857,-120.7625499926,000000000.00000,590,0035.3346556591,-120.7625891491,000000000.00000,621,0035.3346279202,-120.7626279038,000000000.00000,652,0035.3346004645,-120.7626662627,000000000.00000,680,0035.3345767789,-120.7626993543,000000000.00000

    MariM



    Veteran Member


    Posts:2396
    Veteran Member


    --
    11 Jul 2016 11:29 AM
    ENVI does not have a correction for roll, pitch and yaw although they are similar to omega, phi and kappa. You have some map information in the navigation data, so you could do a 'rough' georeference using: UPPER_LEFT_LAT 35.33524299 UPPER_LEFT_LON -120.76176857 by populating the map info and coordinate system in the header (Edit ENVI Header in classic or View Metadata->Edit Metadata). However, this will not really correct for distortions and it isn't really 'projected'. I would suggest using the Build RPCs tool possibly using the 'reg points' at the bottom but I don't really understand the format of those points. However, if you can use Build RPCs and collect some good ground control points (along with elevations), you could then use the generic RPC Orthorectification on your dataset to get an accurate georeferencing.
    You are not authorized to post a reply.