Frequently Asked Questions (FAQs)
The following is a list of frequently asked questions, answers, and links to more information:
Most modern web browsers like; Chrome, Firefox, Safari, and IE9+. For optimal performance, the product team recommends using the application in the most up to date versions of these.
Road Analyzer’s Notify function allows users to directly email notifications of problems, and it automatically captures and includes key characteristics and metrics about the current Road Analyzer session. This Notify tool can be configured to route the emails as needed; directly to the Road Analyzer Support team and/or to the customer’s administrative or IT team.
Additionally customers or external users can be setup to use the Road Analyzer repository and collaboration toolset, and this allows them to open new defects, track defect resolution progress, and to communicate with Road Analyzer's Support team. Issues that come to Transcend via the above mentioned Notify tool are also logged and assigned using this same repository.
Online support is also available, and request tickets initially go to Transcend’s Support team. Every request ticket is logged into the repository mentioned in the previous paragraph, and assigned to the appropriate Support team member.
Road Analyzer performance depends on a number of factors, like; how many layers are configured to be loaded by default, the type of symbology configured for each layer, database tuning, etc. The biggest factor to performance in Road Analyzer is the performance of the ArcGIS Server map service that is driving the application. Under most normal circumstances Road Analyzer can query and render the SLD in under 5 seconds. See “Scalability and Performance” for more details.
Road Analyzer does provide a visual representation of application load time, query time, and render time metrics. These metrics can be easily viewed in the application to determine what layers and processes in the application take the most time.
Road Analyzer can be “replicated” to multiple application servers and function in a load balanced environment. See “Scalability and Performance” for more details.
Yes, the application requests/transactions can be encrypted by running over HTTPS (SSL).
Yes. Road Analyzer is built with a responsive design so that it can look good and operate well on devices that range from small to large (phone to desktop).
Yes, every service endpoint and functionality in the application has an assigned privilege. Roles can be created dynamically and privileges can be assigned to, or removed from, any role. See the Roles topic in App Manager's User Guide for more details.
Road Analyzer’s Draw Tools (Redline) provide the ability to draw and edit lines, ellipses, rectangles, paths, and text to both the Stick Panel and Bar Panel areas of Road Analyzer. For each of these drawing items color, size and placement is set by the user. Drawing items can be saved and recalled, with the capability to share and/or overwrite at save time. See the Manage Drawings (Redlines) topic for more details.
Road Analyzer easily integrates with most current third party video log viewers. Typically the required input for launching these video log viewers is a combination of ROUTE ID and MEASURES. Road Analyzer parses this information for the active SLD route and builds a URL string, and launches the viewer using this string.
Other applications can be launched from Road Analyzer using the URL string method mentioned above, and Road Analyzer has a Links function for easy user selection and configuration for such integration.
Road Analyzer includes a Scale function that is displayed on the Divider (Route Information) Bar, and the user can change the scale value as needed. Also the Application Configuration toolset in Road Analyzer provides the ability to set the default scale. As scale is changed, the SLD stick diagram refreshes accordingly, equivalent to zooming in and out on the stick diagram.
If the layer (underlying data) has an equivalent “modified” date field, than Road Analyzer can display that “last updated” date.
You can change the "configuration database" destination by using the Data Sources component within the application. You'll want to change the "Default Connection" - that is the connection used for the configuration database. Once you save this and load the "TDS" splash page again it will start pointing to the new database that you configured (the connection must have read & write permissions to the DB). Any configurations you have made within the application will need to be re-configured (such as the Map Service URL, etc). An alternative method, is by changing the "DefaultConnection" Connection String in the Web.Config at the root of the TDS application. You can read more about this in the Profile Configuration topic.
Road Analyzer does not need to be installed on the same server as ArcGIS Server, it can sit on any "application server". Cross-origin/domain issues should not be an issue as long as you have installed the CORS component for ESRI's ArcGIS Server Web Adapter, and have Road Analyzer's Map Service URL configured to go through Web Adapter. See the Application Architecture topic for more details. One other common thing is to make sure your SSL certificate is valid and trusted by your browser. You can do this by clicking the "Test URL" link next to where you entered the map service URL and verify it works. Also, you typically want to use a protocol-less URL.
Example: //my-ags-server/arcgis/etc rather than http://my-ags-server/arcgis/etc.
You will need to have geography services enabled on your browser and operating system for the "My Location" option to work. However, if you are using the Google Chrome browser and your site is HTTP, it will be blocked as Google Chrome not allow using browser location on non-secure sites (HTTP) sites. You will need to add an SSL certificate to your server (this would make the site use HTTPS) in order to use that functionality there.
Yes it does and you can learn more about how to add them in the Application Integrations topic. However, a Google license is mostly likely required unless you are running the Road Analyzer application on a site that is available to the public. For more information, please visit Google Maps' Get a Key/Authentication page
Yes; if your map service is LRS-enabled and published with ESRi's Roads & Highways data, that information is included in the map service, which Road Analyzer reads. If your map service is not LRS-enabled, but you have added the network layers as networks in App Manager's LRS Metadata section, then Road Analyzer can pick it up that way as well. In the Route Selection View, you will see a LRM/Network Selection Network (LRM) dropdown menu to select the network you wish to use for your session. Also, in the Straight-Line Diagram (SLD) View, you can switch the currently loaded route to another network from the Route dropdown menu found in the top navigation bar.
With answer: Transcend's tools, as well as ArcGIS Server, include security options to protect data access and help prevent SQL injection attacks. Please see the Application Security topic in the App Manager user guide for more information.