To Create a new marker, at a minimum the following columns must be provided:

• Name
• Location or an Address.

You can supply marker address data in raw or structured format. For details, see the Address data type documentation.

When only the Name and Location are provided, then the ShapeType defaults to Circle, and the Radius defaults to 500 feet. If the Name, Location, and Radius are provided but not the ShapeType, then the ShapeType is set to Circle. If you provide the Name and Location and set the ShapeType to Polygon, then the Yard column is also required on Create.

To Update or Delete a marker, only the Id is required.

When you write templates that access this table, follow these requirements:

1. Specify the Symbolic Name for the table version to use:

   Copy

   TableID = Site-1.0

2. Specify an Intent that this table supports:

   • Retrieve
   • Create
   • Update
   • CreateOrUpdate
   • Delete

3. Input templates: In your [Output] section, be sure to map an input value to every table column that is flagged as being a primary key or required.

4. Retrieve templates: This table does not require the use of a fetcher. However, the following fetchers are available to optimize your query and are listed from most efficient to least:
   1. Id (Equals/In)
      Copy

      [Filter]
      Id(ExtId) = Equals(Id1)   # You can filter on literals or on variables from the [User] or [Calculated] sections.

      Copy

      [Filter]
      Id(ExtId) = In(["Id1","Id2","Id3"])

   2. UserId (Equals)
      Copy

      [Filter]
      UserId = Equals("ABC123")   # You can filter on literals or variables from the [User] or [Calculated] section.

   3. UpdateTime (GreaterThan)
      Copy

      [Filter]
      UpdateTime = GreaterThan(StartTime)   # Filter on literals or variables from the [User] or [Calculated] section.

   4. UpdateTime (Between)
      Copy

      [Filter]
      UpdateTime = Between(StartTime,EndTime)   # Filter on literals or variables from [User] or [Calculated]

   5. Name (Equals)
      Copy

      [Filter]
      Name = Equals("SiteName")    # You can filter on literals or variables from [User] or [Calculated]

   6. Yard (ContainsPoint(Latitude,Longitude))

      This fetcher filters by whether the boundary of a marker's yard contains a location, identified by latitude and longitude. If you filter on literals (Example 1), then you must define a default unit of measure for the Angle data type in the [Defaults] section. If you filter on input from the [User] section, then you can either define the unit of measure in the [Defaults] section or for each line in the [User] section as shown in Example 2.

      Example 1

      Copy

      [Defaults]
      Angle=Degree     # Sets the default unit of measure for the Latitude and Longitude literals in the [Filter] section
      
      [Filter]
      Yard = ContainsPoint(30.39761,-97.72958)  # Filters markers by literal values

      Example 2

      Copy

      [User]     # Sets the Latitude and Longitude by query string, for example: &Latitude=30.39761&Longitude=-97.72958
      Latitude(Angle,Degree) = “latitude”        # Sets the data type and unit of measure for Latitude
      Longitude(Angle,Degree) = “longitude”      # Sets the data type and unit of measure for Longitude
      
      [Filter]
      Yard = ContainsPoint(Latitude,Longitude) # Filters markers by input from the [User] section

This table supports the following option, which can be set in the [TableOptions] section.

• LocationAddressSync - This table option is Boolean and can be omitted. This option controls how the Location and primary address (Addresses[0]) are assigned during a Create or Update operation. The following tables describe the behavior of this option for the Create intent and Update intent.

  Create Intent

  Value	Description
  Not set	The default behavior will be the following: Location provided/Addresses[0] empty: Will assign the Addresses[0] value. Addresses[0] provided/Location empty: Will assign the Location value. Both provided: Will use the values as provided.
  True	The default behavior will be the following: Location provided/Addresses[0] empty: Will assign the Addresses[0] value. Addresses[0] provided/Location empty: Will assign the Location value. Both provided: Will use the values as provided.
  False	The default behavior will be the following: Location provided/Addresses[0] empty: An error is thrown. Both the Location value and the Addresses[0] value must be set during Create since values will not be synced. Addresses[0] provided/Location empty: An error is thrown. Both the Location value and the Addresses[0] value must be set during Create since values will not be synced. Both provided: Will use the values as provided.

  Update Intent

  Value	Description
  Not set	The default behavior will be the following: Location provided/Addresses[0] empty: Will update the Location value only. Addresses[0] provided/Location empty: Will update the Addresses[0] value only. Both provided: Will update the values as provided.
  True	The default behavior will be the following: Location provided/Addresses[0] empty: Will update the Addresses[0] value to the reversed geocode of the Location value. Addresses[0] provided/Location empty: Will update the Location value to the geocode of the Addresses[0] value. Both provided: Will update the values as provided.
  False	The default behavior will be the following: Location provided/Addresses[0] empty: Will update the Location value. Addresses[0] provided/Location empty: Will update the Addresses[0] value. Both provided: Will update the values as provided.

This list includes each column's name, which you use in expressions to retrieve or create data, and data type, which defines how the data is retrieved and set.

Note
If a column of data type Id is a primary key OR if it refers to other tables (Id <OtherTable>), then you can map it to an external key or, in some cases, a Telogis key.

Additional columns: