Open IanMayo opened 7 years ago
Here is a KNIME workflow that handles the first part of the issue (date conversion). KNIME_UPWORK_processing_frequently_orrcuring_encodings.zip
Now I have a question about the data. I saw that the lines for DYNAMIC_REC include locations like these: "21 10 0 N 21 03 0 W 21 00 0 N 20 53 0 W" I suppose these are two locations written behind each other. What exactly should be done in the workflow? Should only the first location be converted to a new column with a new format? Or should both locations be converted to two new columns with a new format?
Hadn't noticed that :-)
Let's just process the first location.
Alright, I did so. So here is a workflow that handles both parts of this issue.
We're re-using the multiple messages file again here.
The file contains examples of two sets of frequently occurring structures in my data:
951212 050000.000
or951212 050000
(without milliseconds)22 12 10.58 N 21 32 2.98 W
In this task I'd like you to parse the
DYNAMIC_REC
messages, and output a series of dates & locations. The dates should be in ISO_8601 format (e.g.1995-12-12T05:00:00Z
), and the locations should be in floating point degrees lat/long (e.g.22.15 -21.544
).shapes.rep.zip