Best Practices for Processing Multi-Year GNSS Data with pdp3 [Error: time span too long (>108 days)

[mirzawaqar]

I’m currently working on processing GNSS data from a single station spanning the past 10 years. However, when I try to process even a single year of data using the pdp3 script, I encounter the following error:

"Time span too long (>108 days)"

It seems that pdp3 has a hard-coded limitation where it can only process up to 108 days of data in a single run.

For those of you who have worked with long-term GNSS time series, how do you typically handle this?

Do you:

Split the data into chunks (e.g., quarterly)?

Merge the output ENU files after processing?

Use any custom automation or post-processing scripts to stitch the results together?

I’d really appreciate any advice or workflow recommendations for efficiently processing and managing long-term GNSS data with pdp3.

Thanks in advance for your guidance!

pdp3 -m P -s 2024/1 -e 2024/366 SUWN0010.24o
===> CheckExecutables ...
===> CheckExecutables done
:: Processing time range: 2024-01-01 00:00:00.000 <==> 2024-12-31 23:59:30.000
:: Processing interval: 30
:: Site name: suwn
:: Positioning mode: P:300
:: AR switch: A
:: Frequency combination: G12 R12 E15 C26 J12
:: Configuration file: /home/max/.PRIDE_PPPAR_BIN/config_template
:: RINEX observation file: /home/max/hdd1/GNSS/SUWN/RINEX/2024/Daily/ppp_project/SUWN0010.24o
error: time span too long (> 108 days): from 60310 to 60675