earth 0.3.11 → 0.3.13

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    earth (0.3.10)
+    earth (0.3.12)
       activerecord (~> 3)
       cohort_scope (>= 0.0.7)
       conversions (>= 1.4.5)
@@ -65,6 +65,7 @@ GEM
     falls_back_on (0.0.3)
       activerecord
     fast_timestamp (0.0.4)
+    fastercsv (1.5.4)
     gemcutter (0.6.1)
     geokit (1.5.0)
     gherkin (2.2.9)
@@ -94,7 +95,7 @@ GEM
     rake (0.8.7)
     rcov (0.9.9)
     rdiscount (1.6.5)
-    rdoc (3.2)
+    rdoc (3.3)
     remote_table (0.2.32)
       activesupport (>= 2.3.4)
       escape (>= 0.0.4)
@@ -130,7 +131,7 @@ GEM
     sinatra (1.0)
       rack (>= 1.0)
     slither (0.99.4)
-    sniff (0.4.11)
+    sniff (0.4.12)
       aaronh-chronic (~> 0.3.9)
       activerecord (~> 3.0.0)
       activesupport (~> 3.0.0)
@@ -145,6 +146,7 @@ GEM
       rocco
       rspec (~> 2.0.0)
       sqlite3-ruby (~> 1.3.0)
+      timecop
       timeframe (~> 0.0.8)
     spreadsheet (0.6.5.0)
       ruby-ole
@@ -157,6 +159,7 @@ GEM
       sinatra (~> 1.0.0)
       sqlite3-ruby (~> 1.2)
     term-ansicolor (1.0.5)
+    timecop (0.3.5)
     timeframe (0.0.8)
       activesupport (>= 2.3.5)
     tzinfo (0.3.23)
@@ -174,6 +177,7 @@ DEPENDENCIES
   data_miner (~> 0.5.6)
   earth!
   falls_back_on (>= 0.0.3)
+  fastercsv
   geokit (>= 1.5.0)
   loose_tight_dictionary (>= 0.0.8)
   sniff (~> 0.4.11)

data/features/automobile_fuel_type.feature

@@ -3,19 +3,14 @@ Feature: Data import for AutomobileFuelType
   I want to import AutomobileFuelType data
   So that I can perform fuel type-based calculations
 
-  Scenario: Successfully verifying that annual distance > 0
+  Scenario: Successfully verifying that annual distance and emission factor > 0
     Given a "AutomobileFuelType" data import fetches results listed in "automobile_fuel_type_good"
-    When a data import verifies "Annual distance should be greater than zero"
+    When a data import verifies "Annual distance and emission factor should be greater than zero"
     Then the verification should be successful
 
-  Scenario: Successfully verifying that annual distance units are never missing
+  Scenario: Successfully verifying that annual distance units are kilometres
     Given a "AutomobileFuelType" data import fetches results listed in "automobile_fuel_type_good"
-    When a data import verifies "Annual distance units should never be missing"
-    Then the verification should be successful
-
-  Scenario: Successfully verifying that emission factor >= 0
-    Given a "AutomobileFuelType" data import fetches results listed in "automobile_fuel_type_good"
-    When a data import verifies "Emission factor should be zero or more"
+    When a data import verifies "Annual distance units should be kilometres"
     Then the verification should be successful
 
   Scenario: Successfully verifying that emission factor units are never missing
@@ -23,19 +18,14 @@ Feature: Data import for AutomobileFuelType
     When a data import verifies "Emission factor units should never be missing"
     Then the verification should be successful
 
-  Scenario: Failing to verify that annual distance > 0
-    Given a "AutomobileFuelType" data import fetches results listed in "automobile_fuel_type_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 annual distance units are never missing
+  Scenario: Failing to verify that annual distance and emission factor > 0
     Given a "AutomobileFuelType" data import fetches results listed in "automobile_fuel_type_bad"
-    When a data import verifies "Annual distance units should never be missing"
+    When a data import verifies "Annual distance and emission factor should be greater than zero"
     Then the verification should not be successful
 
-  Scenario: Failing to verify that emission factor >= 0
+  Scenario: Failing to verify that annual distance units are kilometres
     Given a "AutomobileFuelType" data import fetches results listed in "automobile_fuel_type_bad"
-    When a data import verifies "Emission factor should be zero or more"
+    When a data import verifies "Annual distance units should be kilometres"
     Then the verification should not be successful
 
   Scenario: Failing to verify that emission factor units are never missing

data/features/automobile_make_fleet_year.feature

@@ -3,9 +3,9 @@ Feature: Data import for AutomobileMakeFleetYear
   I want to import MakeFleetYear data
   So that I can perform year-based calculations
 
-  Scenario: Successfully verifying that year is between 1978 and 2007
+  Scenario: Successfully verifying that year is from 1978 to 2009
     Given a "AutomobileMakeFleetYear" data import fetches results listed in "automobile_make_fleet_year_good"
-    When a data import verifies "Year should be between 1978 and 2007"
+    When a data import verifies "Year should be from 1978 to 2009"
     Then the verification should be successful
   
   Scenario: Successfully verifying that fuel efficiency is greater than zero
@@ -23,9 +23,9 @@ Feature: Data import for AutomobileMakeFleetYear
     When a data import verifies "Fuel efficiency units should be kilometres per litre"
     Then the verification should be successful
   
-  Scenario: Failing to verify that year is between 1978 and 2007
+  Scenario: Failing to verify that year is from 1978 to 2009
     Given a "AutomobileMakeFleetYear" data import fetches results listed in "automobile_make_fleet_year_bad"
-    When a data import verifies "Year should be between 1978 and 2007"
+    When a data import verifies "Year should be from 1978 to 2009"
     Then the verification should not be successful
   
   Scenario: Failing to verify that fuel efficiency is greater than zero

data/features/automobile_make_model_year.feature

@@ -3,9 +3,9 @@ Feature: Data import for AutomobileMakeModelYear
   I want to import MakeModelYear data
   So that I can perform model year-based calculations
 
-  Scenario: Successfully verifying that year is between 1985 and 2010
+  Scenario: Successfully verifying that year is from 1985 to 2010
     Given a "AutomobileMakeModelYear" data import fetches results listed in "automobile_make_model_year_good"
-    When a data import verifies "Year should be between 1985 and 2010"
+    When a data import verifies "Year should be from 1985 to 2010"
     Then the verification should be successful
 
   Scenario: Successfully verifying that fuel efficiences are greater than zero
@@ -18,9 +18,9 @@ Feature: Data import for AutomobileMakeModelYear
     When a data import verifies "Fuel efficiency units should be kilometres per litre"
     Then the verification should be successful
 
-  Scenario: Failing to verify that year is between 1985 and 2010
+  Scenario: Failing to verify that year is from 1985 to 2010
     Given a "AutomobileMakeModelYear" data import fetches results listed in "automobile_make_model_year_bad"
-    When a data import verifies "Year should be between 1985 and 2010"
+    When a data import verifies "Year should be from 1985 to 2010"
     Then the verification should not be successful
 
   Scenario: Failing to verify that fuel efficiences are greater than zero

data/features/automobile_make_model_year_variant.feature

@@ -3,9 +3,9 @@ Feature: Data import for AutomobileMakeModelYearVariant
   I want to import MakeModelYearVariant data
   So that I can perform variant-based calculations
 
-  Scenario: Successfully verifying that year is between 1985 and 2010
+  Scenario: Successfully verifying that year is from 1985 to 2010
     Given a "AutomobileMakeModelYearVariant" data import fetches results listed in "automobile_make_model_year_variant_good"
-    When a data import verifies "Year should be between 1985 and 2010"
+    When a data import verifies "Year should be from 1985 to 2010"
     Then the verification should be successful
 
   # FIXME TODO
@@ -24,9 +24,9 @@ Feature: Data import for AutomobileMakeModelYearVariant
     When a data import verifies "Fuel efficiency units should be kilometres per litre"
     Then the verification should be successful
 
-  Scenario: Failing to verify that year is between 1985 and 2010
+  Scenario: Failing to verify that year is from 1985 to 2010
     Given a "AutomobileMakeModelYearVariant" data import fetches results listed in "automobile_make_model_year_variant_bad"
-    When a data import verifies "Year should be between 1985 and 2010"
+    When a data import verifies "Year should be from 1985 to 2010"
     Then the verification should not be successful
 
   # FIXME TODO

data/features/automobile_make_year.feature

@@ -3,9 +3,9 @@ Feature: Data import for AutomobileMakeYear
   I want to import MakeYear data
   So that I can perform year-based calculations
   
-  Scenario: Successfully verifying that year is between 1985 and 2010
+  Scenario: Successfully verifying that year is from 1985 to 2010
     Given a "AutomobileMakeYear" data import fetches results listed in "automobile_make_year_good"
-    When a data import verifies "Year should be between 1985 and 2010"
+    When a data import verifies "Year should be from 1985 to 2010"
     Then the verification should be successful
   
   Scenario: Successfully verifying that fuel efficiency is greater than zero
@@ -18,9 +18,9 @@ Feature: Data import for AutomobileMakeYear
     When a data import verifies "Fuel efficiency units should be kilometres per litre"
     Then the verification should be successful
   
-  Scenario: Failing to verify that year is between 1985 and 2010
+  Scenario: Failing to verify that year is from 1985 to 2010
     Given a "AutomobileMakeYear" data import fetches results listed in "automobile_make_year_bad"
-    When a data import verifies "Year should be between 1985 and 2010"
+    When a data import verifies "Year should be from 1985 to 2010"
     Then the verification should not be successful
   
   Scenario: Failing to verify that fuel efficiency is greater than zero

data/features/automobile_size_class_year.feature

@@ -0,0 +1,34 @@
+Feature: Data import for AutomobileSizeClassYear
+  As a data user
+  I want to import AutomobileSizeClassYear data
+  So that I can perform size class year-based calculations
+  
+  Scenario: Successfully verifying that year is from 1975 to 2010
+    Given a "AutomobileSizeClassYear" data import fetches results listed in "automobile_size_class_year_good"
+    When a data import verifies "Year should be from 1975 to 2010"
+    Then the verification should be successful
+  
+  Scenario: Successfully verifying that fuel efficiencies > 0
+    Given a "AutomobileSizeClassYear" data import fetches results listed in "automobile_size_class_year_good"
+    When a data import verifies "Fuel efficiencies should be greater than zero"
+    Then the verification should be successful
+  
+  Scenario: Successfully verifying that fuel efficiency units are kilometres per litre
+    Given a "AutomobileSizeClassYear" data import fetches results listed in "automobile_size_class_year_good"
+    When a data import verifies "Fuel efficiency units should be kilometres per litre"
+    Then the verification should be successful
+  
+  Scenario: Failing to verify that year is from 1975 to 2010
+    Given a "AutomobileSizeClassYear" data import fetches results listed in "automobile_size_class_year_bad"
+    When a data import verifies "Year should be from 1975 to 2010"
+    Then the verification should not be successful
+  
+  Scenario: Failing to verify that fuel efficiencies > 0
+    Given a "AutomobileSizeClassYear" data import fetches results listed in "automobile_size_class_year_bad"
+    When a data import verifies "Fuel efficiencies should be greater than zero"
+    Then the verification should not be successful
+  
+  Scenario: Failing to verify that fuel efficiency units are kilometres per litre
+    Given a "AutomobileSizeClassYear" data import fetches results listed in "automobile_size_class_year_bad"
+    When a data import verifies "Fuel efficiency units should be kilometres per litre"
+    Then the verification should not be successful

data/features/automobile_type_fuel_age.feature

@@ -0,0 +1,54 @@
+Feature: Data import for AutomobileTypeFuelAge
+  As a data user
+  I want to import AutomobileTypeFuelAge data
+  So that I can perform type fuel age-based calculations
+  
+  Scenario: Successfully verifying that type name and fuel common name are not missing
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_good"
+    When a data import verifies "Type name and fuel common name should never be missing"
+    Then the verification should be successful
+  
+  Scenario: Successfully verifying that age is from zero to thirty
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_good"
+    When a data import verifies "Age should be from zero to thirty"
+    Then the verification should be successful
+  
+  Scenario: Successfully verifying that age percent and total travel percent are from zero to one
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_good"
+    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
+    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
+  
+  Scenario: Successfully verifying that annual distance units are kilometres
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_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 and fuel common name are not missing
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_bad"
+    When a data import verifies "Type name and fuel common name should never be missing"
+    Then the verification should not be successful
+  
+  Scenario: Failing to verify that age is from zero to thirty
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_bad"
+    When a data import verifies "Age should be from zero to thirty"
+    Then the verification should not be successful
+  
+  Scenario: Failing to verify that age percent and total travel percent are from zero to one
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_bad"
+    When a data import verifies "Age percent and total travel percent should be from zero to one"
+    Then the verification should not be successful
+  
+  Scenario: Failing to verify that annual distance and vehicles are greater than zero
+    Given a "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_age_bad"
+    When a data import verifies "Annual distance and 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 "AutomobileTypeFuelAge" data import fetches results listed in "automobile_type_fuel_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_control.feature

@@ -0,0 +1,34 @@
+Feature: Data import for AutomobileTypeFuelControl
+  As a data user
+  I want to import AutomobileTypeFuelControl data
+  So that I can perform type fuel control-based calculations
+
+  Scenario: Successfully verifying that type name, fuel common name, and control name are not missing
+    Given a "AutomobileTypeFuelControl" data import fetches results listed in "automobile_type_fuel_control_good"
+    When a data import verifies "Type name, fuel common name, and control name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that emission factors are greater than zero
+    Given a "AutomobileTypeFuelControl" data import fetches results listed in "automobile_type_fuel_control_good"
+    When a data import verifies "Emission factors should be greater than zero"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that emission factors units are kilograms per kilometre
+    Given a "AutomobileTypeFuelControl" data import fetches results listed in "automobile_type_fuel_control_good"
+    When a data import verifies "Emission factor units should be kilograms per kilometre"
+    Then the verification should be successful
+
+  Scenario: Failing to verify that type name, fuel common name, and control name are not missing
+    Given a "AutomobileTypeFuelControl" data import fetches results listed in "automobile_type_fuel_control_bad"
+    When a data import verifies "Type name, fuel common name, and control name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that emission factors are greater than zero
+    Given a "AutomobileTypeFuelControl" data import fetches results listed in "automobile_type_fuel_control_bad"
+    When a data import verifies "Emission factors should be greater than zero"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that emission factors units are kilograms per kilometre
+    Given a "AutomobileTypeFuelControl" data import fetches results listed in "automobile_type_fuel_control_bad"
+    When a data import verifies "Emission factor units should be kilograms per kilometre"
+    Then the verification should not be successful

data/features/automobile_type_fuel_year.feature

@@ -0,0 +1,54 @@
+Feature: Data import for AutomobileTypeFuelYear
+  As a data user
+  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
+    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"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that year is from 1990 to 2008
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    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
+    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"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that HFC emissions are zero or more
+    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"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that units are correct
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_good"
+    When a data import verifies "Units should be correct"
+    Then the verification should be successful
+
+  Scenario: Failing to verify that type name and fuel common name are 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"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that year is from 1990 to 2008
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    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
+    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"
+    Then the verification should not be successful
+
+  Scenario: Failing to vefify that HFC emissions are zero or more
+    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"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that units are correct
+    Given a "AutomobileTypeFuelYear" data import fetches results listed in "automobile_type_fuel_year_bad"
+    When a data import verifies "Units should be correct"
+    Then the verification should not be successful

data/features/automobile_type_fuel_year_control.feature

@@ -0,0 +1,34 @@
+Feature: Data import for AutomobileTypeFuelYearControl
+  As a data user
+  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
+    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"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that year is from 1990 to 2008
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
+    When a data import verifies "Year should be from 1990 to 2008"
+    Then the verification should be successful
+
+  # Scenario: Successfully verifying that total travel percent for each fuel type year sums to one
+  #   Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_good"
+  #   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
+    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"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that year is from 1990 to 2008
+    Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
+    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 percent for each fuel type year sums to one
+  #   Given a "AutomobileTypeFuelYearControl" data import fetches results listed in "automobile_type_fuel_year_control_bad"
+  #   When a data import verifies "Total travel percent for each type fuel year should sum to one"
+  #   Then the verification should not be successful

data/features/automobile_type_year.feature

@@ -0,0 +1,44 @@
+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
+
+  Scenario: Successfully verifying that type name is never missing
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should be successful
+
+  Scenario: Successfully verifying that year is from 1990 to 2008
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_good"
+    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
+    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"
+    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"
+    Then the verification should be successful
+
+  Scenario: Failing to verify that type name is never missing
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
+    When a data import verifies "Type name should never be missing"
+    Then the verification should not be successful
+
+  Scenario: Failing to verify that year is from 1990 to 2008
+    Given a "AutomobileTypeYear" data import fetches results listed in "automobile_type_year_bad"
+    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
+    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"
+    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"
+    Then the verification should not be successful