ArcReader: The Good, the Bad, and the Ugly

by Nate 9. August 2006 22:45
I've been working with ArcReader a lot lately, using it as a simple client access interface to connect intranet users to an enterprise GIS built on ArcSDE 9.1 and Microsoft SQL Server 2005. Generally speaking, I've been happy with the product and the publisher extension (which allows you to publish map documents to ArcReader-accessible .pmf files). I have, however, discovered many shortcomings in the application. This entry outlines both the strengths and weaknesses of ArcReader, as I see it, specifically when using it to access data served over a network (Local Area (LAN) or Wide Area (WAN)).

Strengths
  • Simple way to publish data quickly.
  • Has an accessible user interface that is easy to learn.
  • Provides a no risk read-only interface to your GIS - this eliminates the need to worry about forgetting to add the data into ArcMap from a SDE geodatabase as a non-editing user.
  • As long as joins and relates are applied before the .pmf file is created, all necessary attribute fields are searchable - even if related tables have not been explicitly added to the .pmf.
  • Can drill down into related (via a geodatabase relationship class) feature class and stand-alone tables using the identify tool, even if the related tables are not explicitly added to the .pmf and the relationship only exists in the geodatabase and hasn't been established in the ArcMap project.
  • Capability of using both data and landscape views, meaning that you can make sure that all printed products meet your guidelines and standards.
  • If accessing data that are stored in a spatial data engine (sde) or served via web services, the end user will always have the best data. This helps reduce the need to send out "updated" datasets or .pmf projects.
  • Custom macros can be used to extend the abilities of your application. (Corrected in comment below. Thanks!)
Weaknesses
  • I haven't yet tried to create custom ArcReader applications, but the ArcReader Configuration tool is very limiting.
  • If using an ArcReader Template (.art) file to customize an ArcReader application using the ArcReader Configuration tool, it is difficult and very cumbersome to link the .art file with the .pmf file.
    • Question: why not just set the default path of the .art to the location of the .pmf?
    • Note: I have just read that this issue is being addressed in the impending 9.2 release. You will be able to package .art files with .pmf files when publishing the project.
  • Cannot add non-spatial tables to ArcReader application (the workaround is to, like mentioned above, explicitly apply joins and relates before the map file is published).
  • Cannot query feature classes or tables that are linked via a geodatabase relationship class (unless you perform the joins in the ArcMap project before publishing to a .pmf file. Even then you have to either hide extraneous fields before you publish the map document or settle for a bloated, confusing attribute table).
  • During an identify, attribute field names are sorted in alphabetical order.
    • Question: Why not have the fields listed in the order that they are presented in the table schema, as this is the order defined by the data owner?
    • Note: A workaround, although it should be more efficient than this: While performing an identify in ArcReader, you can right-click in the right-hand side of the identify box and unselect "Sort Fields". This will turn off the automatic sort. Why is this turned on by default?
Overall, ArcReader is a nice packaged solution. It allows for greater accessibility to an organization's GIS, and is easy to use - for both the administrator and the end user. You can customize some aspects of an application using the ArcReader Configuration tool, but will need to create a fully customized ArcReader project to gain access to advanced customization options. With the release of ArcGIS Explorer scheduled for later this calendar year, it will be interesting to see where ESRI takes ArcReader in the 9.2 release. My prediction: ArcReader will always have its "niche" as an easy-to-use and deploy client access solution. As more advanced applications come along - whether traditional or web-based - ESRI will have to continue to fine-tune the ArcReader interface and open it up to simpler customization by administrators.

Note: ArcReader is available for the Linux, Solaris, and Windows platforms and is available for download at the ESRI site.

Listening to Christopher O'Riley - True Love Waits: Christopher O'Riley Plays Radiohead...

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

ArcReader

E-mail | Kick it! | DZone it! | del.icio.us
Permalink | Comments (1) | Post RSSRSS comment feed

Comments

Comments are closed

Powered by BlogEngine.NET 1.4.5.0
Theme by Mads Kristensen
GeoURL