UCOSP code sprint day #3
Monday, January 18, 2010
Today both the Geotools and Ingres group continued to explored the unanswered questions in their heads. We also had an hour of wrap up after lunch on what's good/bad about this meeting up.
I found the code sprint well-organized and yet elastic to different needs for different groups. I have also learnt more about the different curriculum from different schools, their strength and weakness. I am also able to get most of the discussion about sync'ing the knowledge among the team, the flow of the term, contacts, communication channel and job allocation done at this code sprint, which will definitely ease my work for the rest of the term.
Schedule of this term total = 11 weeks
Meeting: Every Friday
Where: GTalk/Skype/Google Wave
Blogs: Update 1 summarized blogpost to UCOSP per week after the meeting
Week 1(22 Jan 2010): Eva: figure out how to debug the code, and complete the 1st patch: isEmpty. See Ingres in debugging mode in action(attach gcc and run on top of Ingres?). Sara: figure out how to add test cases, how the connections are made in between the test_suite and the ingres geospatial code base, structure of the test suite for geospatial, what are the files that are needed to be modified in order to test the functions that Eva writes.
Week 2(29 Jan 2010): the 2nd patch: IsEmpty
Week 3(5 Feb 2010): testing of the first 2 patches
Week 4(12 Feb 2010): the 3rd patch: Overlaps
Week 5(19 Feb 2010): the 4th patch: NumPoints
Week 6(26 Feb 2010): testing of the 3rd, 4th patches
Week 7(5 Mar 2010): ----
Week 8(12 Mar 2010): the 5th patch: X
Week 9(19 Mar 2010): the 6th patch: Y
Week 10(26 Mar 2010): testing of the 5th, 6th patches
Week 11(2 Apr 2010): Video of seeing the SQL running in action
Posted byA nerdy girl at 12:23 PM 0 comments
Labels: code sprint, Geospatial, Ingres, UCOSP, winter 2010
UCOSP code sprint day #2
Saturday, January 16, 2010
Today we continue to explore the unanswered questions left over from yesterday. These are the things that I have explored
OGC stands for opengeospatial consortium, and GEOS is an implementation of the OGC specification. It is formed by a set of companies who have invested their time to have set out a standard for geospatial information systems and databases. GEOS implements part of the SFS standard and Ingres uses it for geospatial manipulation and calculation. The patch Alex sent sends me extends GEOS to support more of the standard so that Ingres can use the GEOS.
Functions instances to implement:
- IsSimple,
- IsEmpty,
- Overlaps,
- X(on points only),
- Y(on points only),
- NumPoints (on linestring only)
Files to change:
- adgoptab.roc
- fi_defn.txt
- aduint.h
- adfops.h
- adupoint.c
- adffiids.h
Following the standard that is quoted from OpenGIS Implementation Specification for Geographic information - Simple feature access:
Organization: Open Geospatial Consortium Inc.
Date: 2005-11-22
Reference number of this document: OGC 05-134
Version: 1.1.0
Category: OpenGIS® Implementation Specification
Editor: Keith Ryden
SQL functions on type Geometry
IsEmpty(g Geometry) : Integer
The return type is Integer, with a return value of 1 for TRUE, 0 for FALSE, and –1 for UNKNOWN corresponding to a function invocation on NULL arguments.
TRUE if this geometric object corresponds to the empty set
IsSimple(g Geometry): Integer
The return type is Integer, with a return value of 1 for TRUE, 0 for FALSE, and –1 for UNKNOWN corresponding to a function invocation on NULL arguments.
TRUE if this geometric object is simple, as defined in the Geometry Model
SQL functions that test spatial relationships
Overlaps(g1 Geometry, g2 Geometry) : Integer
The return type is Integer, with a return value of 1 for TRUE, 0 for FALSE, and –1 for UNKNOWN corresponding to a function invocation on NULL arguments.
TRUE if the intersection of g1 and g2 results in a value of the same dimension as g1 and g2 that is different from both g1 and g2 Integer
SQL functions on type Point
X(p Point) : Double Precision
return the x-coordinate of Point p as a double precision number
Y(p Point) : Double Precision
return the y-coordinate of Point p as a double precision number
SQL functions on type LineString
NumPoints(l LineString) : Integer
return the number of Points in the LineString
Posted byA nerdy girl at 12:23 PM 0 comments
Labels: code sprint, Geospatial, Ingres, UCOSP, winter 2010
UCOSP code sprint day #1
Friday, January 15, 2010
Today Andrew started off the day with explaining to the group of Ingres UCOSP students the general overview picture of how a user at the browser level, Tomcat, GEOServer/Map Server, Geotools and Ingres DMBS fit together. It's decided that the 4 students from University of Waterloo and University of British Columbia work on the Geotools communication with the Ingres DBMS, and that me working on the implementation of SQL functions while Sara test them out.
We have also decided the goal of the code sprint for the Geotools group to figure out where the code that need to be modified sit, what are the road blocks, and what is the schedule of the work for the rest of the team. It's clear for the Ingres SQL group what need to be done, so the goal of the code sprint will be having 1 patch completed and if not, what is the road block to it and the schedule fo the work for the rest of the team.
We had pizza lunch and I met with some sponsors who is those that support us financially. I have also talked in person to some other graduate students and professors who I have been talking to on IRC/mailing list in previous term, and they are working on the analysis of the performance of Ingres. Hope that I can learn more from them/together for this semester!
Posted byA nerdy girl at 12:19 PM 0 comments
Labels: code sprint, Geospatial, Ingres, UCOSP, winter 2010
UCOSP code sprint: day 3, wrap up and thoughts
Sunday, September 27, 2009
Today is the last day of code sprint and everyone is wrapping up and give their thoughts. I agreed with our project head Andrew Ross that communications is really important in collaborations. To the very least, "let the community know what you are doing". On top of that, the community itself is a very useful place to get help from and responses to very specific technical questions. Moreover, this way you also can let the community knows more about you, your interest and ability and put you in the right place to contribute. Afterall, coding should be fun!
Another side note, the most rewarding experience from the code sprint is to "pass it on". It feels so excellent to get them up to speed about their tools and technologies sets needed, such as using version controls, IDE, and how to tackle a problem. I saw myself in the past from my teammates, and wished that only if there had been someone in the past who could have told me all these.
Great experience, great people, great talks, great connections, great food... The only bad point that I can come up with is that at the start of the code sprint, the students should have been "sync-ed" with the tools that they need, regardless if they are familiar with them or not, such that they can spend the time more usefully on things that would be valuable to be done face to face.
Posted byA nerdy girl at 3:50 PM 0 comments
Labels: code sprint, UCOSP
UCOSP code sprint: day 2
Saturday, September 26, 2009
Today our task was to let the CMS, Drupal, to know about the following modules: GMap, Location, OpenLayers. I am new to Ingres and find it would be helpful if there is an "all in a page step by step tutorial" out there for newbies like me. So there you go!
Tutorial for newbies to start working on Ingres Geospatial on Windows XP 32 bit
- Every step in the following should be done with the latest update/release
- Step through the guide in the movie to download and install Ingres. If you are using home edition, make sure that the Windows'user name that you are logged in with does not contain any space.
- Get Xampp - A tool with PHP, Apache, etc and all the necessary configurations in one package.
- Note that "//xampp/htdocs/" is the root of your "website".
- Get and install Drupal.
- Know more on how to use Drupal.
- Get the following modules: OpenLayer, Location, and GMap, and let Drupal know these modules exists by following these configurations.
- After the modules, checkout the code from repository at http://code.ingres.com/ingres/main.
- Build the code that you have checked out by following this here.
Posted byA nerdy girl at 9:47 AM 0 comments
Labels: build, code sprint, CSC494, Drupal, Geospatial, GMap, Ingres, installation, Location, OpenLayers, tutorial, UCOSP, Windows XP
UCOSP code sprint: day 1
Friday, September 25, 2009
We started off 9am in the morning, with a demo by Andrew Ross about Ingres and valuable advices for our later career. After the lunch, our task for today is to get Apache, PHP, and configured them to work with each other, as well as to get Drupal installed.
I already have the first three on my machine from a all in one package that I have for quite a while: XAMPP. I went smooth myself for the installation back then, but there are various problems encountered by my teammates.
On top of the issue that I had with installation of Ingres. I found that the usability of installation process also has room to be improved for newbies. I would prefer myself not to spend 3 straight days at the code sprint to get every plugin and features into their own place, but use my time more usefully with everyone else. Nevertheless, I had a good time with them!
Posted byA nerdy girl at 6:43 AM 0 comments
Labels: code sprint, CSC494, day 1, UCOSP