RidgeStar
About
Locations
Manual
Preface
Introduction
Versions
Concepts
Construction
Usage
Operations
Questions
Features
Settings
Album
Alerts
Assignments
AssignmentMeter
Assignor
Audit
Availability
BulkLoad
BulkMail
Calendar
Chapter
Chart
Criteria
Evaluation
Exams
GeoCode
GoogleAPI
iCalendar
IPMapping
JavaNames
KeyTranslation
Lists
Locations
Mail
MinorAuth...
Misconducts
NACHA
News
Notification
Notify
NWS
PageHeader
Paperwork
Password
PhotoUse
Questions
Request
Reset
RestClients
RestServer
RMA.WSYSA
Rules
Save
ScheduleMeter
SoapClients
SoapServer
SRC
Tickets
Timeout
TouchLine
Translate
UserName
Internals
Appendices
Reference
Service
Logon
RidgeStar

Manual: Settings-GoogleAPI

Logonfindtranslate
Get Started |Calendar |Locations

The GoogleAPI Settings specifies the Google Key that should be used when contacting the corresponding Google Service, as follows:

Directions
Establishes the Google API Key used to identify any requests issued to the Google Maps Directions API. This is used on the Site when contacting Google to compute the Travel Duration for a Referee to move from one Location to another.
Geocoding
Establishes the Google API Key used to identify any requests issued to the Google Maps Geocoding API. This is used on the Site to determine the precise Longitude and Latitude associated with a Location defined in the Locations table.
JavaScript
Establishes the Google API Key that will be used to identify any requests issued to the Google Maps JavaScript API. This is used in the Client machine request that Google Maps draw a "visual map" of the area around a Location.
reCAPTCHA
Identifies the unique API Key that identifies the Site to Google for the purposes of reCAPTCHA confirmation.
Travel
Specifies the time of day used to determine the Arrival Time for API calls to the Directions API calculating Travel Time. Default is "12:00".
SiteVerify
Establishes the Google API Key that will be used to verify the reCAPTCHA data returned from a reCAPTCHA form via Google siteverify.

Unspecified operands (or if the entire setting is undefined) will cause the system to operate as if there is NO Google API Key in effect. Thus, the system will not identify itself to Google when contacting it for service. In most cases, this means Google will "track" activity by IP Address (either the Web Server or the Client/Browser system).