Closed swapnalshahil closed 3 years ago
“gmm_storage.db" database stores search terms and possible navigation history amongst other proprietary content in BLOB data records. So even after converting to tsv some remains encoded. But we can see there searched terms, and links there which may be sufficient for us.
"gmm_myplaces.db" stores saved places,labelled places,etc. We can get links to those locations with other data also in savedlocation.tsv.
@shivanshu1333 sir! Please review! 🙂
@swapnalshahil either we've to find a way to extract proprietary content if it is possible or we have to keep only the useful information in tsv file which is readable by humans, in this case we need to parse the tsv file to extract only readable strings.
Now it stores all bundles.
@swapnalshahil we'll setup a meeting to discuss this
@swapnalshahil we'll setup a meeting to discuss this
ok, sir!
Description
Extraction of location data. Implementation from the command line to extract location data directly. Creating API which will give the Location data(this will help in frontend). API : /data//location
this will provide path to open 1) savedlocation.tsv 2)searchedlocation.tsv
Fixes #186
Type of change
How Has This Been Tested?
POSTMAN and CMD
CMD
savedlocation.tsv(above)
searchedlocation.tsv(above)
Extraction using POSTMAN (above)
API (above)
Checklist: