t.vect.list: Added support for JSON, YAML and CSV#7051
t.vect.list: Added support for JSON, YAML and CSV#7051gulshan-123 wants to merge 10 commits intoOSGeo:mainfrom
Conversation
|
One thing I am sorry about :( and the motivation for this PR: #7004 , While testing more rigorously, I found this: Currently, #7004 refactored the code to use We missed this during review as there is no any tests related to vector time datasets in pytest of timeseriesmap_test.py , only raster dataset was being used. Thus, my next step will be to add tests corresponding to vector space time datasets too in the pytest, so that similar error do not occur in future in timeseriesmap. Thank You |
|
While we use the data-metadata split in v.db.select, is that something we want to use here where the columns are fixed? Did you use it in the other temporal tool? |
Yes. we are using the similar data metadata split in For {'data': [{'end_time': '2001-02-01 00:00:00',
'mapset': 'PERMANENT',
'name': 'precipitation_1',
'start_time': '2001-01-01 00:00:00'},
{'end_time': '2001-03-01 00:00:00',
'mapset': 'PERMANENT',
'name': 'precipitation_2',
'start_time': '2001-02-01 00:00:00'},
{'end_time': '2001-04-01 00:00:00',
'mapset': 'PERMANENT',
'name': 'precipitation_3',
'start_time': '2001-03-01 00:00:00'},
{'end_time': '2001-05-01 00:00:00',
'mapset': 'PERMANENT',
'name': 'precipitation_4',
'start_time': '2001-04-01 00:00:00'},
{'end_time': '2001-06-01 00:00:00',
'mapset': 'PERMANENT',
'name': 'precipitation_5',
'start_time': '2001-05-01 00:00:00'},
{'end_time': '2001-07-01 00:00:00',
'mapset': 'PERMANENT',
'name': 'precipitation_6',
'start_time': '2001-06-01 00:00:00'}],
'metadata': {'column_names': ['name', 'mapset', 'start_time', 'end_time']}} |
The tests and idea are taken from t.rast.list.
I have added the tests too.
plain
json
yaml
CSV