earth 0.3.15 → 0.4.0

data/Gemfile

@@ -5,6 +5,7 @@ gemspec
 
 gem 'data_miner', :path => ENV['LOCAL_DATA_MINER'] if ENV['LOCAL_DATA_MINER']
 gem 'sniff', :path => ENV['LOCAL_SNIFF'] if ENV['LOCAL_SNIFF']
+gem 'roo', '1.9.3'
 
 if RUBY_VERSION =~ /^1\.8/
   gem 'fastercsv'

data/earth.gemspec

@@ -4,8 +4,8 @@ require "earth/version"
 
 Gem::Specification.new do |s|
   s.name        = "earth"
-  s.version = "0.3.15"
-  s.date = "2011-01-28"
+  s.version = Earth::VERSION
+  s.date = "2011-02-17"
   s.platform    = Gem::Platform::RUBY
   s.authors = ["Seamus Abshere", "Derek Kastner", "Andy Rossmeissl"]
   s.email = %q{andy@rossmeissl.net}
@@ -32,10 +32,10 @@ Gem::Specification.new do |s|
   s.add_runtime_dependency 'errata'
   s.add_runtime_dependency 'falls_back_on', '>= 0.0.3'
   s.add_runtime_dependency 'geokit', '>= 1.5.0'
+  s.add_runtime_dependency 'geokit-rails'
   s.add_runtime_dependency 'cohort_scope', '>= 0.0.7'
   s.add_runtime_dependency 'conversions', '>= 1.4.5'
   s.add_runtime_dependency 'weighted_average', '>= 0.0.4'
   s.add_runtime_dependency 'loose_tight_dictionary', '>= 0.0.8'
-  s.add_development_dependency 'sniff', '~> 0.5.3'
-  s.add_development_dependency 'bueller'
+  s.add_development_dependency 'sniff', '~> 0.6.1'
 end

data/features/automobile_fuel.feature

@@ -0,0 +1,44 @@
+Feature: Data import for AutomobileFuel
+  As a data user
+  I want to import AutomobileFuel data
+  So that I can perform fuel-based calculations
+
+  Scenario: Successfully verifying that base fuel name is never missing
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_good"
+    When a data import verifies "Base fuel name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that distance key is never missing
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_good"
+    When a data import verifies "Distance key should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that ef key is never missing
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_good"
+    When a data import verifies "Ef key should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that blend portion is from 0 to 1 if present
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_good"
+    When a data import verifies "Blend portion should be from 0 to 1 if present"
+    Then the verification should be successful
+
+  Scenario: Failing to verify that base fuel name is never missing
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_bad"
+    When a data import verifies "Base fuel name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that distance key is never missing
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_bad"
+    When a data import verifies "Distance key should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that ef key is never missing
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_bad"
+    When a data import verifies "Ef key should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that blend portion is from 0 to 1 if present
+    Given a "AutomobileFuel" data import fetches results listed in "automobile_fuel_bad"
+    When a data import verifies "Blend portion should be from 0 to 1 if present"
+    Then the verification should not be successful

data/features/automobile_type_fuel_age.feature

@@ -1,3 +1,4 @@
+# DEPRECATED - use AutomobileTypeFuelYearAge
 Feature: Data import for AutomobileTypeFuelAge
   As a data user
   I want to import AutomobileTypeFuelAge data
@@ -18,7 +19,7 @@ Feature: Data import for AutomobileTypeFuelAge
     When a data import verifies "Age percent and total travel percent should be from zero to one"
     Then the verification should be successful
   
-  Scenario: Successfully verifying that age annual distance and vehicles are greater than zero
+  Scenario: Successfully verifying that annual distance and vehicles are greater than zero
     Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_good"
     When a data import verifies "Annual distance and vehicles should be greater than zero"
     Then the verification should be successful

data/features/automobile_type_fuel_year.feature

@@ -3,9 +3,19 @@ Feature: Data import for AutomobileTypeFuelYear
   I want to import AutomobileTypeFuelYear data
   So that I can perform type fuel year-based calculations
 
-  Scenario: Successfully verifying that type name and fuel common name are not missing
+  Scenario: Successfully verifying that type name is not missing
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
-    When a data import verifies "Type name and fuel common name should never be missing"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that fuel common name is not missing
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "Fuel common name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that type year name is not missing
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "Type year name should never be missing"
     Then the verification should be successful
 
   Scenario: Successfully verifying that year is from 1990 to 2008
@@ -13,24 +23,59 @@ Feature: Data import for AutomobileTypeFuelYear
     When a data import verifies "Year should be from 1990 to 2008"
     Then the verification should be successful
 
-  Scenario: Successfully verifying that total travel, fuel consumption, and emission factors are greater than zero
+  Scenario: Successfully verifying that total travel is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "Total travel should be greater than zero"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that fuel consumption is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "Fuel consumption should be greater than zero"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that ch4 emission factor is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "Ch4 emission factor should be greater than zero"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that n2o emission factor is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "N2o emission factor should be greater than zero"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that total travel units are kilometres
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "Total travel units should be kilometres"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that fuel consumption units are litres
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
-    When a data import verifies "Total travel, fuel consumption, and emission factors should be greater than zero"
+    When a data import verifies "Fuel consumption units should be litres"
     Then the verification should be successful
 
-  Scenario: Successfully verifying that HFC emissions are zero or more
+  Scenario: Successfully verifying that ch4 emission factor units are kilograms per litre
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
-    When a data import verifies "HFC emission factor should be zero or more"
+    When a data import verifies "Ch4 emission factor units should be kilograms per litre"
     Then the verification should be successful
 
-  Scenario: Successfully verifying that units are correct
+  Scenario: Successfully verifying that n2o emission factor units are kilograms per litre
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
-    When a data import verifies "Units should be correct"
+    When a data import verifies "N2o emission factor units should be kilograms per litre"
     Then the verification should be successful
 
-  Scenario: Failing to verify that type name and fuel common name are not missing
+  Scenario: Failing to verify that type name is not missing
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
-    When a data import verifies "Type name and fuel common name should never be missing"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that fuel common name is not missing
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "Fuel common name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that type year name is not missing
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "Type year name should never be missing"
     Then the verification should not be successful
 
   Scenario: Failing to verify that year is from 1990 to 2008
@@ -38,17 +83,42 @@ Feature: Data import for AutomobileTypeFuelYear
     When a data import verifies "Year should be from 1990 to 2008"
     Then the verification should not be successful
 
-  Scenario: Failing to verify that total travel, fuel consumption, and emission factors are greater than zero
+  Scenario: Failing to verify that total travel is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "Total travel should be greater than zero"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that fuel consumption is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "Fuel consumption should be greater than zero"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that ch4 emission factor is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "Ch4 emission factor should be greater than zero"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that n2o emission factor is greater than zero
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "N2o emission factor should be greater than zero"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that total travel units are kilometres
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "Total travel units should be kilometres"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that fuel consumption units are litres
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
-    When a data import verifies "Total travel, fuel consumption, and emission factors should be greater than zero"
+    When a data import verifies "Fuel consumption units should be litres"
     Then the verification should not be successful
 
-  Scenario: Failing to vefify that HFC emissions are zero or more
+  Scenario: Failing to verify that ch4 emission factor units are kilograms per litre
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
-    When a data import verifies "HFC emission factor should be zero or more"
+    When a data import verifies "Ch4 emission factor units should be kilograms per litre"
     Then the verification should not be successful
 
-  Scenario: Failing to verify that units are correct
+  Scenario: Failing to verify that n2o emission factor units are kilograms per litre
     Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
-    When a data import verifies "Units should be correct"
+    When a data import verifies "N2o emission factor units should be kilograms per litre"
     Then the verification should not be successful

data/features/automobile_type_fuel_year_age.feature

@@ -0,0 +1,94 @@
+Feature: Data import for AutomobileTypeFuelYearAge
+  As a data user
+  I want to import AutomobileTypeFuelYearAge data
+  So that I can perform type fuel year age-based calculations
+
+  Scenario: Successfully verifying that type name is not missing
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that fuel common name is not missing
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Fuel common name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that type fuel year name is not missing
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Type fuel year name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that year is 2008
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Year should be 2008"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that age is from zero to thirty
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Age should be from 0 to 30"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that total travel percent is from zero to one
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Total travel percent should be from 0 to 1"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that annual distance is greater than zero
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Annual distance should be greater than zero"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that vehicles is greater than zero
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Vehicles should be greater than zero"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that annual distance units are kilometres
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_good"
+    When a data import verifies "Annual distance units should be kilometres"
+    Then the verification should be successful
+
+  Scenario: Failing to verify that type name is not missing
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that fuel common name is not missing
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Fuel common name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that type fuel year name is not missing
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Type fuel year name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that year is 2008
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Year should be 2008"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that age is from zero to thirty
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Age should be from 0 to 30"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that total travel percent is from zero to one
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Total travel percent should be from 0 to 1"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that annual distance is greater than zero
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Annual distance should be greater than zero"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that vehicles is greater than zero
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Vehicles should be greater than zero"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that annual distance units are kilometres
+    Given a "AutomobileTypeFuelYearAge" data import fetches results listed in "automobile_type_fuel_year_age_bad"
+    When a data import verifies "Annual distance units should be kilometres"
+    Then the verification should not be successful

data/features/automobile_type_fuel_year_control.feature

@@ -3,9 +3,29 @@ Feature: Data import for AutomobileTypeFuelYearControl
   I want to import AutomobileTypeFuelYearControl data
   So that I can perform type fuel year control-based calculations
 
-  Scenario: Successfully verifying that type name, fuel common name, and control name are not missing
+  Scenario: Successfully verifying that type name is not missing
     Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
-    When a data import verifies "Type name, fuel common name, and control name should never be missing"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that fuel common name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
+    When a data import verifies "Fuel common name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that control name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
+    When a data import verifies "Control name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that type fuel control name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
+    When a data import verifies "Type fuel control name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that type fuel year name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
+    When a data import verifies "Type fuel year name should never be missing"
     Then the verification should be successful
 
   Scenario: Successfully verifying that year is from 1990 to 2008
@@ -18,9 +38,29 @@ Feature: Data import for AutomobileTypeFuelYearControl
   #   When a data import verifies "Total travel percent for each type fuel year should sum to one"
   #   Then the verification should be successful
   # 
-  Scenario: Failing to verify that type name, fuel common name, and control name are not missing
+  Scenario: Failing to verify that type name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that fuel common name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
+    When a data import verifies "Fuel common name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that control name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
+    When a data import verifies "Control name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that type fuel control name is not missing
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
+    When a data import verifies "Type fuel control name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that type fuel year name is not missing
     Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
-    When a data import verifies "Type name, fuel common name, and control name should never be missing"
+    When a data import verifies "Type fuel year name should never be missing"
     Then the verification should not be successful
 
   Scenario: Failing to verify that year is from 1990 to 2008

data/features/automobile_type_year.feature

@@ -1,7 +1,7 @@
 Feature: Data import for AutomobileTypeYear
   As a data user
   I want to import AutomobileTypeYear data
-  So that I can perform type fuel year control-based calculations
+  So that I can perform type year-based calculations
 
   Scenario: Successfully verifying that type name is never missing
     Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
@@ -13,14 +13,24 @@ Feature: Data import for AutomobileTypeYear
     When a data import verifies "Year should be from 1990 to 2008"
     Then the verification should be successful
 
-  Scenario: Successfully verifying that HFC emissions are zero or more
+  Scenario: Successfully verifying that HFC emissions is zero or more
     Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
-    When a data import verifies "HFC emissions should be zero or more"
+    When a data import verifies "Hfc emissions should be zero or more"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that HFC emission factor is zero or more
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
+    When a data import verifies "Hfc emission factor should be zero or more"
     Then the verification should be successful
 
   Scenario: Successfully verifying that HFC emissions units are kilograms CO2e
     Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
-    When a data import verifies "HFC emissions units should be kilograms CO2e"
+    When a data import verifies "Hfc emissions units should be kilograms co2e"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that HFC emission factor units are kilograms CO2e per litre
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
+    When a data import verifies "Hfc emission factor units should be kilograms co2e per litre"
     Then the verification should be successful
 
   Scenario: Failing to verify that type name is never missing
@@ -33,12 +43,22 @@ Feature: Data import for AutomobileTypeYear
     When a data import verifies "Year should be from 1990 to 2008"
     Then the verification should not be successful
 
-  Scenario: Failing to verify that HFC emissions are zero or more
+  Scenario: Failing to verify that HFC emissions is zero or more
     Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
-    When a data import verifies "HFC emissions should be zero or more"
+    When a data import verifies "Hfc emissions should be zero or more"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that HFC emission factor is zero or more
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
+    When a data import verifies "Hfc emission factor should be zero or more"
     Then the verification should not be successful
 
   Scenario: Failing to verify that HFC emissions units are kilograms CO2e
     Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
-    When a data import verifies "HFC emissions units should be kilograms CO2e"
+    When a data import verifies "Hfc emissions units should be kilograms co2e"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that HFC emission factor units are kilograms CO2e per litre
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
+    When a data import verifies "Hfc emission factor units should be kilograms co2e per litre"
     Then the verification should not be successful