Comments (9)
In the MALA header data file I have (".rad") there is no date (contrary to the Sensors&Software header data file). Therefore, I had decided to take the date of the file reading as the survey data, which is not quite correct.
Now I changed that. If there is no date in the header file, the following is done:
x@date <- character(0)
When typing x
(your current object of the GPR
class) in the command console, the survey date is not shown if it is character(0)
.
You can set the date by yourself using the new svDate()
function:
svDate(x) # get the survey date (return NULL if there is no date
svDate(x) <- as.Date("2014-03-02")
svDate(x)
# or
svDate(x) <- as.Date(format(Sys.time(), "%Y-%m-%d"))
svDate(x)
One alternative (for later) would be to check if there is a coordinates file (".cor") and extract in this file the survey date... I add this alternative on my todo list.
from rgpr.
An alternative would to be extract the date and time information from the rd3 file, rather than the header:
file.mtime("YourFile")
Or if you want just the date:
as.Date(as.character(file.mtime("YourFile")))
This, of course, assumes that the date modified is the collection date.
from rgpr.
That's a possible alternative. It should be first checked, how the file.time()
changes when the .rd3 file is copied at another place: does the date and time information stay the same? In other words: does the date and time information of the .rd3 file always reflect the survey date and time?
from rgpr.
I just completed a two week time lapse survey using Mala gear. All the dates and times relative to when I collected that data are intact. I copied and pasted those files to different places on my computer and it did not change anything. However, this information is likely to change if that data were downloaded, or transferred to another computer, as the original files would no longer be used.
from rgpr.
Thank you for testing. I prefer to not use the date of the data file for the survey date. I will explore another option: extract the date from the coordinate file ".cor" (this date would really correspond to the survey date). I will first check if all .cor files have the same structure/format...
from rgpr.
Yeah, that was the best thing I could think of, because going through all of my ancillary Mala files (.mrk, .em, .cor, .add, .rad) none of them have survey acquisition time and date. Maybe that is something to bring up with Mala? I noticed that not having this information generates an error when trying to use the GPS survey functions, because they require that bit of info. I was going to look into that code a bit later before adding it to an issue.
from rgpr.
Strange... do you know if there is an official documentation on the MALA file format?
from rgpr.
I'm asking some of the geophysicists that manage the equipment for the project I'm working on. Maybe they'll have some ideas. I may contact Mala directly to see if they have any insights.
from rgpr.
It sounds like Mala doesn't actually record that information in a metadata file; that metadata is not recorded in a specific file.
from rgpr.
Related Issues (20)
- package ‘rgpr’ is not available for this version of R (4.0.x) HOT 1
- I can't import data HOT 5
- Error While Reading .DZT File HOT 18
- Hope to know more about the algorithm behind the hyperbola fitting
- Error While Fitting Hyperbola HOT 4
- Error on bits2volt function: using argument "nbits" while it says it was supposed to be "nBytes" HOT 3
- Can't read .rd7 files. HOT 3
- Kirchhoff migration with 2D velocity model
- Slice Interpolation Issue HOT 2
- Error in initialize(value, ...) : object 'velocity' not found HOT 2
- Topography and time to depth conversion HOT 5
- Import GPR data link is broken HOT 1
- Read/import GPR data in DT1 format HOT 4
- Plot contrast settings HOT 3
- Changing axes from time to distance HOT 6
- Horizontal resolution HOT 2
- Can't read .dt1 files HOT 3
- plot `SGY` error HOT 3
- Request for Support: Adding Support for Easy Radar USA's .gpr Format HOT 6
- Is the dielectric value in dzx files used? HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rgpr.