Archives for posts with tag: lines of code

I decided it is time to have a minor version increase, so the new package version is 0.2. I want to represent the maturity the software has reached and show (or convince myself ­čÖé ) of the stability it has. A new cheat sheet comes with it, too. Apart from little fixes the most important addition for users is probably the function sosCreateTime(...) which allows creating event time lists for GetObservation requests very easily based on character strings:

# Using :: and / as seperators for start and end time:
sosCreateTime(sos = aqe, time = "2007-08-01 08:00::2007-08-05 15:00")
sosCreateTime(sos = aqe, time = "2007-08-01 15:00/2007-08-05 20:00")

# Creating time instants with a relative spatial operator, i.e. TM_Before (first example) or TM_After (second example):
sosCreateTime(sos = aqe, time = "::2007-08-05")
sosCreateTime(sos = aqe, time = "2007-08-05/")

The first count of the lines of code was done when the first presentation of sos4R was given, adding up to 9.213.

In release 0.2, it is 15.636. Not bad.

The changes:

* Bugfix in coordinate order in coercion function for SpatialPointsDataFrame
* Added function sosCreateTime(...)
* Removed require(rgdal) from sosGetCRS(...) and replaced it with a check and potential warning as done in sp:::CRS
* Replacing potentially critical characters from data.frame column names (function .cleanupColumnName(...))
* Added function sosUOM(...) to extract the unit of measurement from objects
* Added summary methods for OmObservation and OmObservationCollection

The project presentation is on next Monday – I hope that explains the lack of entries in the last week(s). I managed to get quite a lot of stuff done, even tested several SOS instances. As a little proof (I know, counting empty lines and comments is cheating): I am up to 9.213 lines of code!

The invitation to the presentation, times et cetera are listed below. I’d sure be happy about a lot of interested guests! Read the rest of this entry »