ArcReader: Difference between revisions

From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs)
mNo edit summary
 
Brian Wilson (talk | contribs)
mNo edit summary
Line 1: Line 1:
Generally speaking, ArcReader looks just like ArcMap, TOC on the left, map on the right, toolbars at the top, layers can be turned off or on. Properties are locked down; for example, you can't change Display transparency or Symbology or Labels.
== What is it? ==


If you want to publish a map therefore you might want to include several layers that have different settings. For example, a street layer might be included twice, once with and once without labels.
* Create a map in ArcMap.
* Save it to a PMF (= "Portable Map Format") using the Publisher extension.
 
Now you can give PMF files to your friends and clients and they can view them in  ArcReader, which is free. So the cost to you is just the $2500 Publisher extension.
 
== What features does it have? ==
 
This [http://downloads.esri.com/support/whitepapers/ao_/arcgis91-functionality-matrix_0606.pdf giant feature matrix PDF] tells you exactly what features can be found in each ESRI product.
 
Generally speaking though, ArcReader looks just like ArcMap. TOC on the left, map on the right, toolbars at the top, and layers that can be turned off or on. But it's just a map viewer, not a GIS system.


You can zoom in and out and pan around and you can print.
You can zoom in and out and pan around and you can print.
Line 7: Line 16:
You can do searches and you can use the identify tool.
You can do searches and you can use the identify tool.


There are still data and layout views.
All properties of a 'published' map are locked down; for example, you can't change Display transparency or Symbology or Labels.
 
If you want to publish a map from ArcMap therefore you might want to include several layers that have different settings. For example, a street layer might be included twice, once with and once without labels.
 
As in ArcMap, there are data and layout views. You can control which are available as a Publisher property.
 
You can put a password onto the PMF file
 
=== Customizing ArcReader ===
 
Things start to take off when you create customized versions of ArcReader.
There is a component in Publisher to allow creating customized ArcReaders.
(That's what ESRI says, I have not found it yet.)
 
=== Using PMF files in other applications ===
 
You can open up the PMF file by unchecking the "ArcReader only" boxes in Publisher properties.
 
== Managing data sources ==


The age-old problem of packaging the shapefiles / datasources with the map still exists. For example, my MXD project shapefiles are on a server, so my PMF (ArcReader) file still references the very same server files. If I hand you a copy of the PMF, it won't work for you unless I give you a copy of my server, too.
The age-old problem of packaging the shapefiles / datasources with the map still exists. For example, my MXD project shapefiles are on a server, so my PMF (ArcReader) file still references the very same server files. If I hand you a copy of the PMF, it won't work for you unless I give you a copy of my server, too.
About the only property available for you to change is the data source location for each layer. So if you have the files, you can hook them up.
About the only property available for you to change is the data source location for each layer. So if you have the files, you can hook them up.


Line 15: Line 43:


If the server is Internet-based and all the references in my ArcMap project are to those published Web services instead of to shapefiles tucked away on a file server, the PMF would work for you too. If your Internet connection is fast enough. Vector files, good. Raster files, bad.
If the server is Internet-based and all the references in my ArcMap project are to those published Web services instead of to shapefiles tucked away on a file server, the PMF would work for you too. If your Internet connection is fast enough. Vector files, good. Raster files, bad.
== Punch list for producing a good ArcReader Map ==
'''Who is the end user?''' Design the map for your user, not yourself.
Export only the layers needed by your user.
How will the map be distributed? You probably want to package all layers.
=== Publisher settings ===
'''Set a 'freshness' date.''' Make the map expire so that the user will download a newer copy when the data is old and stale.
'''Set the comments field.''' Promote yourself, not ESRI, by editing the comments field.

Revision as of 18:57, 1 September 2006

What is it?

  • Create a map in ArcMap.
  • Save it to a PMF (= "Portable Map Format") using the Publisher extension.

Now you can give PMF files to your friends and clients and they can view them in ArcReader, which is free. So the cost to you is just the $2500 Publisher extension.

What features does it have?

This giant feature matrix PDF tells you exactly what features can be found in each ESRI product.

Generally speaking though, ArcReader looks just like ArcMap. TOC on the left, map on the right, toolbars at the top, and layers that can be turned off or on. But it's just a map viewer, not a GIS system.

You can zoom in and out and pan around and you can print.

You can do searches and you can use the identify tool.

All properties of a 'published' map are locked down; for example, you can't change Display transparency or Symbology or Labels.

If you want to publish a map from ArcMap therefore you might want to include several layers that have different settings. For example, a street layer might be included twice, once with and once without labels.

As in ArcMap, there are data and layout views. You can control which are available as a Publisher property.

You can put a password onto the PMF file

Customizing ArcReader

Things start to take off when you create customized versions of ArcReader. There is a component in Publisher to allow creating customized ArcReaders. (That's what ESRI says, I have not found it yet.)

Using PMF files in other applications

You can open up the PMF file by unchecking the "ArcReader only" boxes in Publisher properties.

Managing data sources

The age-old problem of packaging the shapefiles / datasources with the map still exists. For example, my MXD project shapefiles are on a server, so my PMF (ArcReader) file still references the very same server files. If I hand you a copy of the PMF, it won't work for you unless I give you a copy of my server, too.

About the only property available for you to change is the data source location for each layer. So if you have the files, you can hook them up.

There does not appear to be any way for you to SAVE the new PMF file though! So you'd be forced to repeat the updates each time you open the PMF, probably cursing me all the while.

If the server is Internet-based and all the references in my ArcMap project are to those published Web services instead of to shapefiles tucked away on a file server, the PMF would work for you too. If your Internet connection is fast enough. Vector files, good. Raster files, bad.

Punch list for producing a good ArcReader Map

Who is the end user? Design the map for your user, not yourself.

Export only the layers needed by your user.

How will the map be distributed? You probably want to package all layers.

Publisher settings

Set a 'freshness' date. Make the map expire so that the user will download a newer copy when the data is old and stale.

Set the comments field. Promote yourself, not ESRI, by editing the comments field.