Skip to content

check which use of gfzrnx is done in header#236

Open
plutonheaven wants to merge 1 commit into
mainfrom
202607_finer_gfzrnx_processing_check
Open

check which use of gfzrnx is done in header#236
plutonheaven wants to merge 1 commit into
mainfrom
202607_finer_gfzrnx_processing_check

Conversation

@plutonheaven

Copy link
Copy Markdown
Collaborator

closes #235

Check that both "gfzrnx" and "FILE PROCESSING" are in the header to decide whether to reprocess a file with gfzrnx.

This is due because some old files used gfzrnx to merge NAV files, but not check/repair them.

@plutonheaven plutonheaven requested a review from jtec July 3, 2026 15:57
Comment thread src/prx/util.py
if "gfzrnx" in f.read():
logging.warning(f"File {file} already contains 'gfzrnx', skipping repair.")
return file
def _check_gfzrnx_processing(file):

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure this needs to be a nested function since it's called only once? If it needs to be a function, I'd make a it a module-level function so that it can be unit tested. If not, I'd just place it's code before the if _check_gfzrnx_processing(file):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Some NAV file processed by old gfzrnx versions are buggy

2 participants