Skip to main content

Elaborate Hack for Transparency

ArcGIS supports transparency*.
* Some restrictions apply.

But if you really want to do anything with transparency you quickly learn that the functionality available is completely inadequate.

I work with a number of layers that rather than resembling a stain glass window with neatly segmented regions, come closer to resembling the outcome of tossing said window down a flight of stairs. The smashed bits all laying in a pile overlapping each other sometimes seven or eight layers deep.

But how to represent this mess? In ArcGIS you really can't because ArcGIS only draws the top most layer. Take a yellow piece of stained glass and drop it on top of a blue one and in the overlap you don't get green, but blue. Even when you set transparency!

The only way to complete our Glad bag analogy is to make two independent layers with transparency applied. Not bad when there's only two. But what if there's 582? That would take a while. And what if the layer with 582 is constantly growing so we'd have to make new definition queries or static shapefiles every single time we appended a record. Not doable.

However while ArcGIS does not support transparency properly, it occurred to me that ArcIMS does.

With that idea, I present:

Hacking ArcGIS - Lesson 1: True Transparency


Step 1: Author a new map .AXL in which includes transparency (0.6 works well) and displays by unique value.
NOTE: I don't use Author at all in more, but it works great for building a unique values display.


Step 2: In ArcIMS Administrator create a new image service using the .AXL

Step 3: Add the new image service to your ArcGIS map.

Step 4: Use a copy of the layer with display set to transparent to label.

That's it! You can now print and export a map with true transparency.

Comments

Popular posts from this blog

ArcGIS One-to-Many Labeling

ArcGIS is just plain lousy at dealing with any relationship that isn't one-to-one. We all have a slew of hacks just to deal with this limitation. I for one regularly am creating temporary cross-tab queries so I can represent multiple sample results at a collection point, fish surveyed at a cross-section and a host of other relationships. The classic example for mapping comes from the cadastral community and condominium lots. It's an odd situation where more than one person has title to the same piece of ground. How do you represent this? I've got a new trick thanks to Mohammed Hoque's article in ArcUser Magazine. We're going to do a database query inside a label expression, loop through the results and output the entire list to label. For our example we'll use Outfitting Areas in Idaho and we'll label them with the Outfitters and Guide License Numbers and Outfitter Names. 1.) Open ArcGIS and add your spatial layer with the unique identifier shared with...

Simple HTTP Redirect with Querystring in IIS7

HTTP Redirect seems simple enough. Always was in IIS6 and in IIS7 there's even a button labeled HTTP Redirect that promises relative redirects.  It looks like it'll be as easy Apache finally.  That is until you try to redirect a querystring.  Then everything bombs. Turns out it still is relatively easy, except you have to know that Microsoft changed $S$Q to $V$Q. Why? $Ss and $Gs I suspect. And How. In our example we'll redirect all pages under http://olddomain.com/content to http://mydomain.com/content. Pick the virtual directory you want to redirect. e.g. http://olddomain.com/content Click HTTP Redirect under IIS in the IIS management console. In the HTTP Redirect Dialog: Check Redirect requests to this destination Enter your new path ending with $V$Q.  e.g. http://mydomain.com$V$Q Counter-intuitively check Redirect all request to exact destination (instead of relative destination) Choose the appropriate Status Code (Permanent or Temp...

Simple Record-Level Auditing in SQL Server & ArcSDE

I've had simple auditing set up in my databases for years thanks to our old DBA. This is not robust transaction logging, it just answers the questions "Who created this?", "When was this created?", "Who last edited this?" and "When was this last edited?". After witnessing a brand new table audit itself without triggers, I set about to understand the setup. This seemed curious to me, so I thought it might also be curious to you. It turned out to be a two step system which rendered my insert triggers superfluous (at least I think so, tell me if I'm missing something and I need insert triggers after all). Our solution uses a combination of two methods. For inserts we are going to tie our audit fields to User Defined Data Types which inherit Defaults we have specified. For updates we will build a trigger to log the changes. We will use the following fields in our tables to track inserts and updates: AUD_NUser - Creator AUD_NDate - Creati...