Commits on Aug 6, 2014
  1. @tamird

    Merge pull request #7 from square/rbx

    cleanup and test on more rubies
    tamird committed Aug 5, 2014
  2. @tamird

    Update tested Rubies

    tamird committed Aug 5, 2014
Commits on Aug 5, 2014
  1. @tamird

    RuboCop

    tamird committed Aug 5, 2014
  2. @tamird

    Convert specs to RSpec 3.0.3 syntax with Transpec

    This conversion is done by Transpec 2.3.6 with the following command:
        transpec -b true,false -f
    
    * 51 conversions
        from: obj.should
          to: expect(obj).to
    
    * 12 conversions
        from: be_true
          to: be true
    
    * 9 conversions
        from: be_false
          to: be false
    
    * 7 conversions
        from: == expected
          to: eq(expected)
    
    * 7 conversions
        from: obj.should_not
          to: expect(obj).not_to
    
    For more details: https://github.com/yujinakayama/transpec#supported-conversions
    tamird committed Aug 5, 2014
  3. @tamird

    remove cruft

    tamird committed Aug 5, 2014
Commits on Dec 12, 2013
  1. Merge branch 'Predpol-master'

    * Predpol-master:
      fix rubocop offenses
      So it doesn't blow up every time I try to reload this file in an irb session
      Add a friendly inspect output
      Add "lon" as a helpful alias as well
      derp. `self.`
      rspec's nested format is nicer
      Better Bundler setup
      Use newer version of RSpec. 2.6 doesn't want to auto-find the spec folder.
      Add helper method for roughly determining the central point in a bounding box.
      Extract Polygon#bounding_box into a method that can be shared
      add aliases so it's easier to pick out the lat / lng values
      extract Point into its own file
      move requires to the top
      added specs for placemark name parsing
      simplified placemark_name_for_polygon logic a bit
      added placemark name parsing support
    Zach Brock committed Dec 12, 2013
  2. fix rubocop offenses

    Zach Brock committed Dec 12, 2013
  3. Fix merge conflicts

    Zach Brock committed Dec 12, 2013
Commits on Dec 7, 2013
  1. @tamird

    Bundler is stupid

    tamird committed Dec 6, 2013
  2. @tamird

    Merge pull request #5 from square/shave-yaks

    Modernize the gem
    R: @rudle
    tamird committed Dec 6, 2013
  3. @tamird

    Modernize the gem

    RSpec, Rubocop, Travis, go!
    tamird committed Dec 6, 2013
Commits on Apr 30, 2013
  1. @sgonyea
  2. @sgonyea

    Add a friendly inspect output

    sgonyea committed Apr 30, 2013
  3. @sgonyea
  4. @sgonyea

    derp. `self.`

    sgonyea committed Apr 30, 2013
  5. @sgonyea

    rspec's nested format is nicer

    sgonyea committed Apr 30, 2013
  6. @sgonyea

    Better Bundler setup

    sgonyea committed Apr 30, 2013
  7. @sgonyea
  8. @sgonyea
  9. @sgonyea
  10. @sgonyea
  11. @sgonyea

    extract Point into its own file

    sgonyea committed Apr 30, 2013
  12. @sgonyea

    move requires to the top

    sgonyea committed Apr 30, 2013
Commits on Apr 6, 2013
  1. @omarqazi
  2. @omarqazi
  3. @omarqazi
Commits on Mar 5, 2013
  1. update date and bump version

    Zach Brock committed Mar 5, 2013
  2. add contributing section

    Zach Brock committed Mar 4, 2013
  3. @zbrock

    Merge pull request #2 from sgonyea/support_all_standard_kml_files

    Support standard kml files
    zbrock committed Mar 4, 2013
Commits on Mar 3, 2013
  1. @sgonyea

    Bump the MINOR version to 2.

    sgonyea committed Mar 3, 2013
Commits on Feb 23, 2013
  1. @sgonyea

    The xmlns of the kml shouldn't matter

    The majority of tools that output kml use the xmlns of "http://www.opengis.net/kml/2.2". Regardless, support them all!
    sgonyea committed Feb 22, 2013
  2. @sgonyea

    Split block of coords by whitespace, not by \n

    Lots of programs / tools output coordinates separated only by a space, and not by newlines.  The standard states that coordinates should not have any whitespace within it, so this change will not break things.
    sgonyea committed Feb 22, 2013
  3. @sgonyea

    Don't support the parsing of non-standard KML files

    The KML standard states that the coordinates must contain "Four or more tuples, each consisting of floating point values for longitude, latitude, and altitude. The altitude component is optional. Do not include spaces within a tuple."
    sgonyea committed Feb 22, 2013
Commits on Jun 20, 2012
  1. @abrons

    Merge pull request #1 from cheister/patch-1

    Do not freeze version string so that it does not error out when trying to strip! it during evaluation
    abrons committed Jun 20, 2012
  2. @cheister

    Update master

    cheister committed Jun 20, 2012