... | @@ -449,13 +449,13 @@ Step 3 completed. |
... | @@ -449,13 +449,13 @@ Step 3 completed. |
|
### 3.2: Converting .csv into .kml
|
|
### 3.2: Converting .csv into .kml
|
|
|
|
|
|
.....
|
|
.....
|
|
The conversion into a '.kml' file required some research about
|
|
|
|
|
|
|
|
**Time Stamp**
|
|
**Time Stamp**
|
|
|
|
|
|
After some initial [research](https://developers.google.com/kml/documentation/kmlreference#timestamp) into typical kml conform time stamps and comparing them to the tweets.csv, we identified chose to aim for a time stamp that was already in most parts given in the .csv, but with a few differences:
|
|
After some initial [research](https://developers.google.com/kml/documentation/kmlreference#timestamp) into typical kml-conform time stamps and comparing them to "created_at" column in the tweets.csv file, we chose to aim for a time stamp that was already mostly given in the .csv, but with a few differences:
|
|
|
|
|
|
> kml time stamp: 1997-07-16T10:30:15+03:00
|
|
> kml time stamp: 1997-07-16T10:30:15+03:00
|
|
|
|
|
|
> tweets.csv time format: 2012-11-05 15:47:16+01
|
|
> tweets.csv time format: 2012-11-05 15:47:16+01
|
|
|
|
|
|
We therefore concluded that we needed to add in the "T" where the blank space is and add ":00" at the end.
|
|
We therefore concluded that we needed to add in the "T" where the blank space is and add ":00" at the end.
|
... | | ... | |