Opened 14 years ago
Last modified 14 years ago
#387 assigned task
generateKMLforPI.py
Reported by: | knpa | Owned by: | knpa |
---|---|---|---|
Priority: | alpha 4 medium | Milestone: | |
Component: | PML utilities | Keywords: | |
Cc: | Other processors: |
Description (last modified by knpa)
Script to generate a .kml google earth file for inclusion with deliveries. Currently includes eagle/hawk and photographs.
Note here any improvements that need to be made or major changes.
Change History (4)
comment:1 Changed 14 years ago by knpa
- Owner changed from mggr to knpa
- Status changed from new to assigned
comment:2 Changed 14 years ago by knpa
- Description modified (diff)
comment:3 Changed 14 years ago by knpa
Todo:
- Eagle and Hawk lines currently appear as VNIR/SWIR*hdr. We want them to be listed as something more like "h154a02".
- All eagle/hawk lines that have a header file in "eagle" or "hawk" appear in kml. This is not desirable when files are present for lines which are not being delivered (because they were 'voided' on logsheet or there is something wrong with that line). Need to find a better way to determine whether a line is included, perhaps from hs delivery. Perhaps raw files for void lines should be moved into a subdirectory at an earlier stage.
comment:4 Changed 14 years ago by mggr
Suggest that we use the hyperspectral config file to determine which lines are processed and what their "official" names are. If this file doesn't exist, fall back to the current behaviour (we want this script to work automatically every time and just become less detailed when less info is available).
Note: See
TracTickets for help on using
tickets.
T