test/bdd/api/reverse/queries.feature

   1 @APIDB
   2 Feature: Reverse geocoding
   3     Testing the reverse function
   4
   5     @Tiger
   6     Scenario: TIGER house number
   7         When sending jsonv2 reverse coordinates 45.3345,-97.5214
   8         Then results contain
   9           | osm_type | category | type |
  10           | way      | place    | house |
  11         And result addresses contain
  12           | house_number | road            | postcode | country_code |
  13           | 906          | West 1st Street | 57274    | us |
  14
  15     @Tiger
  16     Scenario: No TIGER house number for zoom < 18
  17         When sending jsonv2 reverse coordinates 45.3345,-97.5214
  18           | zoom |
  19           | 17 |
  20         Then results contain
  21           | osm_type | category |
  22           | way      | highway  |
  23         And result addresses contain
  24           | road            | postcode | country_code |
  25           | West 1st Street | 57274    | us |
  26
  27     Scenario: Interpolated house number
  28         When sending jsonv2 reverse coordinates -33.231795578514635,-54.38682173844428
  29         Then results contain
  30           | osm_type | category | type |
  31           | way      | place    | house |
  32         And result addresses contain
  33           | house_number | road |
  34           | 1410         | Juan Antonio Lavalleja |
  35
  36     Scenario: Address with non-numerical house number
  37         When sending jsonv2 reverse coordinates 53.579805460944,9.9475670458196
  38         Then result addresses contain
  39           | house_number | road |
  40           | 43 Haus 4    | Stellinger Weg |
  41
  42
  43     Scenario: Address with numerical house number
  44         When sending jsonv2 reverse coordinates 53.580206752486,9.9502944945198
  45         Then result addresses contain
  46           | house_number | road |
  47           | 5            | Clasingstraße |