Markers require location to be specified through one of these column sets:

• Lat and Lon

• EnvelopeAddress that includes the country specified in the string, like "20 Enterprise, Aliso Viejo, CA 92656 -- USA"

• EnvelopeAddress and Country

  Note
  If you specify the country both within the EnvelopeAddress string and with the Country column, then the value set for the Country column is used.

• StreetName and Country plus one of the following:

• PostalCode
• City and Region

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

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

   Copy

   TableID = Marker-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. Tag (Equals)
      Copy

      [Filter]
      Tag = Equals("MarkerName")     # You can filter on literals or on variables from the [User] or [Calculated] sections

   3. Shape (ContainsPoint(Latitude,Longitude))

      This fetcher filters by whether the marker contains a location, identified by latitude and longitude. For polygon markers, the fetcher checks for the location within the boundaries of the polygon Shape. For point markers, the fetcher checks for the location within the Radius of the marker. 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]                                   
      Shape = 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]
      Shape = ContainsPoint(Latitude,Longitude) # Filters markers by input from the [User] section

   4. UserId (Equals)
      Copy

      [Filter]
      UserId(ExternalIdName) = Equals("ABC123")  # or use Telogis Id: UserId = Equals("123456...")

   5. UpdateTime (GreaterThan)
      Copy

      [Filter]
      UpdateTime = GreaterThan(TimeStart)        # Timestamp variable from User or Calculated section

   6. UpdateTime (Between)
      Copy

      [Filter]
      UpdateTime = Between(TimeStart,TimeEnd)    # Timestamp variable from User or Calculated section

   7. PrimaryCategoryId (Equals)
      Copy

      [Filter]
      PrimaryCategoryId(Telogis, Name) = Equals("HQ")  # or use an External key or Telogis Id

   8. PrimaryCategoryId (In)
      Copy

      [Filter]                         # Tests whether external key value matches any in the set
      PrimaryCategoryId(Telogis, Name) = In(["HQ", "Customers", "Fuel Station", "Prohibited"])

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

• ResetAccessPathIntersection - This table option is Boolean and can be omitted. This option allows resetting the Intersection and Access Paths fields for a marker's associated site during an update operation. The following table describes the behavior of this option for the Update intent.

  Note
  Access Paths cannot be set through a Site table Create/Update.

  Update Intent

  Value	Description
  Not set	The default behavior will be the following: An update to a Marker will not clear the corresponding Site’s Intersection or Access Paths. If the customer option HasDefaultResetAccessPathIntersection is set to True, the default behaviour will be the same as True.
  True	The default behavior will be the following: Any update that causes the Marker to move more than 500 feet will remove the corresponding Site’s Intersection and Access Paths.  Caution Any Intersection or Access Paths “reset” cannot be recovered.
  False	The default behavior will be the following: An update to a Marker will not reset the corresponding Site’s Intersection or Access Paths.  Note This takes priority over the customer option HasDefaultResetAccessPathIntersection.

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: