We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File name is composed of:
txt = to indicate it is ascii BE = Belgium 61 = Zaventem VOL = ? NA = ? 201304052202 = datetime
@leijnse can you figure out if this complies with OPERA file name practice and if we should rename files (e.g. drop txt_ at beginning).
txt_
The text was updated successfully, but these errors were encountered:
Proposed new directory and file structure (verify with OPERA file name convention, e.g. drop PPI_?
PPI_
/ppi - 6260_20130405.zip - 6260_201304052202.txt - 6260_201304052207.txt - 6260_20130406.zip - ... /position - 6260_lat.txt - 6260_lon.txt - ...
Sorry, something went wrong.
Position data added in 6fd7ae3
There is no official OPERA file naming convention. I've adopted the naming conventions suggested above. Files have been uploaded to Google Drive.
Reflectivity data has been uploaded: https://github.com/enram/case-study/tree/master/data/reflectivity-ppi
leijnse
No branches or pull requests
File name is composed of:
txt = to indicate it is ascii
BE = Belgium
61 = Zaventem
VOL = ?
NA = ?
201304052202 = datetime
@leijnse can you figure out if this complies with OPERA file name practice and if we should rename files (e.g. drop
txt_
at beginning).The text was updated successfully, but these errors were encountered: