Fixed Structure of Certain Meta Fields (location)

When adding cameras manually via the API, there are a few fields that have a specific structure. These fields should either be omitted or filled according to that structure so as to not interfere with the expected behavior of the web client. One such field is location.

Location is set up as a hierarchy/tree with the following structure

Province → City → Zone → Circuit → Subcircuit

In order for the frontend code to understand the placement of a camera in the tree and to be able to perform searches, the location meta is structured the following way

"meta": {
  "Province": "Ontario",
  "province_Ontario": "",

  "City": "Toronto",
  "city_Toronto": "",
  
  "Zone": "Kensington Market",
  "zone_Kensington_Market", "",
  
  "Circuit": "Augusta Ave",
  "circuit_Augusta_Ave": "",
  
  "Subcircuit": "12 Baldwin Street",
  "subcircuit_12_Baldwin_Street": "",
  
  "location": "12 Baldwin Street"
}

Every location type has 2 fields, where “LocationType” can be any of the 5 location types listed above. In the second field “locationType_” the location name is included in the key with any spaces replaced by an underscore.

"LocationType": "Location Name",
"locationType_Location_Name": ""

Cameras do not need to have all 5 levels of location, but if a location is included it must have all higher levels of that location type. For example, if a camera has a “Zone” field, it also MUST have “City” and “Province” fields. It does NOT however require “Circuit” and “Subcircuit”.

The field “location” is the lowest level of location the camera has.

If a camera doesn’t have any location, do not include these fields in the meta at all.