Common Questions
You can create a .NET Web application with the Web ADF controls that utilize an ArcIMS Route Server service for displaying Smart Data Compression (SDC) data directly, without the need for custom code. In order to incorporate routing and SDC geocoding functionality into the application, you must program against the Route Server ArcXML API. A sample application is included with Route Server 9.2 that illustrates how to do this.
ArcIMS Route Server includes a sample DHTML client viewer application that is installed along with the software. (The default location is $AIMSHOME/RouteServer/Sample_Viewer/DHTML_Sample). In addition, a set of Active Server Pages (ASP) samples is currently available from the ESRI Online Support Center. As new samples are developed, they will also be made available through the Support Center.
Yes. As an ArcIMS extension, Route Server is distributable. However, some factors, such as slow network connections and large numbers of simultaneous hits to your Web site, will cause reduced performance.
ArcIMS Route Server can use commercial datasets from NAVTEQ, Tele Atlas, Tele Atlas GDT, and DMTI that have been optimized to perform routing and geocoding within the ArcIMS Route Server extension. Data is currently available from these vendors covering North America and Europe. It is possible to introduce additional datasets for use with ArcIMS Route Server. This requires custom data preparation in Smart Data Compression format by ESRI Professional Services for an additional cost. Upon request, ESRI can work with third-party data vendors to optimize their data for use with ArcIMS Route Server.
Editing, subsetting, appending, or altering of the data isn't possible due to optimizations made for the SDC format.
No. Unlike RouteMAP IMS, ArcIMS Route Server is integrated with ArcIMS and requires no custom coding to be used within an ArcIMS server. Although built using RouteMAP technology, ArcIMS Route Server follows the standards of ArcIMS. It has many unique components including its data, application programming interfaces, and methods.
RouteMAP IMS is designed as a dealer locator—an easy way to find the nearest location (dealer, hotel, etc.) and get driving directions to the location.
ArcIMS Route Server is the routing answer for those who already have ArcIMS or have need for the GIS functionality that ArcIMS provides, with the added need of routing.
| RouteMAP IMS | ArcIMS Route Server | |
|---|---|---|
| Data |
|
|
| Data Formats |
|
|
| Projection Formats | North America level: Albers (As you zoom in, it becomes cylindrical.) | Geographic coordinates by default (Maps can be customized to support any projection available in ArcIMS.) |
| Customization | ActiveX, Java, .NET API | ArcXML directly in HTML viewers, ArcXML using the ArcIMS connectors (ColdFusion, ActiveX, AppServerLink), .NET |
| Scalable | Yes | Yes |
| Routing | Point-to-point and optimized (Traveling Salesman Problem) | Point-to-point and optimized (Traveling Salesman Problem) |
| Map Control and Editing | Only via the Map Author, not Web browser | Yes, but not on SDC layers (You can edit SDC layer properties in ArcXML.) |
| Palm Support | Download to Palm using Palm database (PDB) format; map is static | Custom HTML solution for Palm served through Palm Query Application (PQA) using a custom ArcIMS server-side solution (using one of the connectors); maps are live |
No. The ArcIMS Route Server extension must be installed and licensed in order to work with SDC data in ArcIMS, including geocoding and routing with SDC data.
RouteServer and SDCGeocodeServer are private Virtual Servers, and thus do not show up in the Virtual Server drop-down list. These servers must be specified with the EXTENSION tag in the map configuration (.axl) file. The RouteServer and SDCGeocode functionality can only be accessed through an ArcIMS Image Service.
