Data Preparation - Seismic 2D line - with shotpoints displayed as labels
Source - SeismicLineGeometry and/or NotionalSeismicLine
Typical input is from SegP1, UKOOA or even some csv/text files.
Commonly a “Navigation ingestion” program either expects standard format (SEGP1, UKOOA) or allows user to define format/syntax (‘n’ lines of header’, column ‘n’ has shotpoint….), also parses information from header of SegP1/UKOOA.
When ingesting, shows user a quick QC (ex: to catch if Canadian navigation appears in South America, because of wrong CRS input by user), also allows the user to ‘link’ the navigation data to an existing Master data entry of Seismic 2D.
There is often an additional QC to verify by converting lat/long (from input) to X/Y (from input), check if values are within tolerance.
Later, with work product component (SegY file), there may also be a requirement of matching up SP-CDP (1 to 1, 1 to 2 or non linear) as navigation data speaks ‘SP’ whereas SegY data speaks ‘CDP’ in most cases.