Documenting was done using Doxygen and every .cpp and .h were separatly documented and pushed to my forklink
Fix some branching issues
What will I be working on next week?
Wrap up the work and discuss future strategy with the mentor
Did I meet with any stumbling blocks?
Nope
Report 11
My initial plan:
Clean the code
Read the documentation manual
Start the documentation
What did i do this week?
Pull the current code and stated cleaning it.
Cleaning was done using cpplint.py and every .cpp and .h were separatly branched out and merged
Start reading doxygen manual for documentation.
Fix some branching issues
What will I be working on next week?
Work on documenting the code
Did I meet with any stumbling blocks?
Nope
Report 10
My initial plan:
Work on existing task.
Work on issues on the page.
Work on other tasks as instructed by the mentor.
What did i do this week?
Compiled and merged the code on master branch.
Read the task given by mentor on cost column bug.link
Read the code and marked all possible places which could have caused the bug.
Tried working on it and ask my doubts.
Coded and merged to the upstream branch.
What will I be working on next week?
I have got chicken pox so I might not able to work a lot , but I will work on the same task.
Did I meet with any stumbling blocks?
Yes, I am diagnosed with chicken pox so couldnt work much this week, The infection is travelling down my throat, so the condition could get worsen this week
Report 9
My initial plan:
Merge the code with the master branch
Read and understand the tasks by the mentor.
Complete the tasks and pass the evaluation
What did i do this week?
Compiled and merged the code on master branch.
Read the documentation of boost.geomtery.
Read the task given by my mentor
Tried working on it and ask my doubts
What will I be working on next week?
Work on existing task.
Work on issues on the page.
Work on other tasks as instructed by the mentor.
Did I meet with any stumbling blocks?
Yes, the communication channel had some issues due to which there was some misunderstanding which is resolved now.
Report 7 8
My initial plan:
Much better wiki for tags, creating tables for each profile
add issue on issues page regarding cordinate system.
start filling the wiki about osm tagsfocusing on the tags osrm uses here
Yet to be decided
Did I meet with any stumbling blocks?
Not as of now, some of them were posted as issue
Report 3
My initial plan:
To understand how boost works.
Fork osm2pgrouting repo.
To work on issues created on osm2pgrouting repo.
Understanding the osm2pgRouting architecture.
What did i do this week?
I was busy this week with FOSS4G India conference so contribute much to GSOC
Here is the abstract of the paper presented at the conference : With the increased shift towards GeoSpatial Web Services on both the Web and mobile platforms especially in the user-centric services, there is a need to improve the query response time.
This paper attempt to evaluate the performance of an existing NoSQL database and SQL database with respect to LineIntersection problem across a range of databases.
SQL databases face scalability and agility challenges and fail to take the advantage of the cheap memory and processing power available these days. While NoSQL databases can handle the rise in the data stored and frequency at which it is accessed and processed which are essential features needed in a multiple geospatial data where we do not need a fixed schema(geometry) and fixed data size.
For this comparative study, MongoDB is the NoSQL engine while the PostGIS is the chosen SQL engine. The dataset consisted of two independent layers of horizontal lines and vertical lines with incremental lengths and their size varied from ten lines to ten thousand lines in each layer. All the data in the analysis was processed using In-memory and no secondary memory was used.
Initial results suggest that MongoDB performs better by an average factor of 25x which increases exponentially as the data size increases in both indexed and non-indexed operations. Given these results NoSQL databases may be better stated for simultaneous multiple-user query systems including Web-GIS and mobile-GIS. Further studies are required to understand the full potential of NoSQL databases across various geometries and spatial query types.
What will I be working on next week?
start filling the wiki about osm tagsfocusing on the tags osrm uses here
Meeting with mentor on monday, tuesday and wednesday
start to code the program::options
start filling the wiki about osm tagsfocusing on the tags osrm uses here
Thursday and Friday work on the wiki
Did I meet with any stumbling blocks?
Boost is new to me so I have implementation doubts which I will ask my mentor after full research.
Report 2
My initial plan:
To understand how boost works.
Fork osm2pgrouting repo.
To work on issues created on osm2pgrouting repo.
Understanding the osm2pgRouting architecture.
What did i do this week?
90 mins meeting with the mentor discussing on implementation details and issues already raised