Core Geolocation Support Location Parameters for defining a Location object Must be of type 'location'. Location specification type The location_info parameter must contain a comma separated list of IANA codes or synonyms describing the civicAddress of this location. The IANA codes and synonyms can be obtained by executing the CLI command geoloc show civicAddr_mapping. The location_info parameter must contain a comma separated list valid GML elements describing this location. The location_info parameter must contain a single URI parameter which contains an external URI describing this location. Location information The contents of this parameter are specific to the location format. location_info = country=US,A1="New York",city_district=Manhattan, A3="New York", house_number=1633, street=46th, street_suffix = Street, postal_code=10222,floor=20,room=20A2 location_info = Shape=Sphere, pos3d="39.12345 -105.98766 1920", radius=200 location_info = URI=https:/something.com?exten=${EXTEN} Fully qualified host name This parameter isn't required but if provided, RFC8787 says it MUST be a fully qualified host name. IP addresses are specifically NOT allowed. The value will be placed in a loc-src parameter appended to the URI in the Geolocation header. Location determination method This is a rarely used field in the specification that would indicate the method used to determine the location. Its usage and values should be pre-negotiated with any recipients. Level of confidence This is a rarely used field in the specification that would indicate the confidence in the location specified. See RFC7459 for exact details. Sub-parameters: One of: A percentage indicating the confidence. https://www.rfc-editor.org/rfc/rfc7459 Profile Parameters for defining a Profile object Must be of type 'profile'. PIDF-LO element to place this profile in Based on RFC5491 (see below) the recommended and default element is device. https://www.rfc-editor.org/rfc/rfc5491.html#section-3.4 Reference to a location object Reference to a location object Reference to a location object location specification type xxxx Notes to be added to the outgoing PIDF-LO document The specification of this parameter will cause a <note-well> element to be added to the outgoing PIDF-LO document. Its usage should be pre-negotiated with any recipients. Sets the value of the Geolocation-Routing header. Sets if empty Civic Address elements should be suppressed from the PIDF-LO document. Determine which profile on a channel should be used Use the incoming profile if it exists and has location information, otherwise use the configured profile if it exists and has location information. If neither profile has location information, nothing is sent. Use the configured profile if it exists and has location information, otherwise use the incoming profile if it exists and has location information. If neither profile has location information, nothing is sent. Discard any incoming profile and use the configured profile if it exists and it has location information. If the configured profile doesn't exist or has no location information, nothing is sent. Discard any configured profile and use the incoming profile if it exists and it has location information. If the incoming profile doesn't exist or has no location information, nothing is sent. Get or Set a field in a geolocation profile The profile parameter to operate on. The following fields from the Location and Profile objects are supported. Additionally, the inheritable field may be set to true or false to control whether the profile will be passed to the outgoing channel. Append provided value to the specified parameter instead of replacing the existing value. This only applies to variable list parameters like location_info_refinement. Before reading or after writing the specified parameter, re-resolve the effective_location and usage_rules parameters using the location_variables parameter and the variables set on the channel in effect at the time this function is called. On a read operation, this does not alter the actual profile in any way. On a write operation however, the effective_location and/or usage_rules parameters may indeed change and those changes will be passed on to any outgoing channel. When used to set a parameter on a profile, if the profile doesn't already exist, a new one will be created automatically. The ${GEOLOCPROFILESTATUS} channel variable will be set with a return code indicating the result of the operation. Possible values are: Success No or not enough parameters were supplied There was an internal error finding or creating a profile There was an issue specific to the parameter specified (value not valid or parameter name not found, etc.)