-
Notifications
You must be signed in to change notification settings - Fork 168
Image_Registration
Rebecca Leggett edited this page Aug 30, 2019
·
2 revisions
Image Registration ¶
There two alternative paths to automatically creating a tie-point control network.
-
Autoseed Path
- This path will distribute and establish tie-points based on polygon overlaps of a collection of images.
- The image coordinates for each point are immediately measured with the autoseed application.
- The footprintinit and findimageoverlaps are required by autoseed
-
Seedgrid Path
- A gridded pattern of tie-points are established based on specified latitude/longitude values and spacing.
- The image coordinates for each "seeded" point are measured with the cnetadd application.
Creating a Tie-Point Control Network ¶
autoseed Path | seedgrid Path |
---|---|
spiceinit | spiceinit |
footprintinit | |
findimageoverlaps | seedgrid |
autoseed | cnetadd |
cnetref | cnetref |
pointreg | pointreg |
Related ISIS3 Applications ¶
spiceinit
footprintinit
findimageoverlaps
autoseed
seedgrid
cnetadd
cnetref
pointreg
- Building
- Writing Tests
- Test Data
- Start Contributing
- Public Release Process
- Continuous Integration
- Updating Application Documentation
- Deprecating Functionality
- LTS Release Process and Support
- RFC1 - Documentation Delivery
- RFC2 - ISIS3 Release Policy
- RFC3 - SPICE Modularization
- RFC3 - Impact on Application Users
- RFC4 - Migration of ISIS Data to GitHub - Updated Information 2020-03-16
- RFC5 - Remove old LRO LOLA/GRAIL SPK files
- RFC6 - BLOB Redesign
- Introduction to ISIS
- Locating and Ingesting Image Data
- ISIS Cube Format
- Understanding Bit Types
- Core Base and Multiplier
- Special Pixels
- FAQ