Edie Punt - Esri Supportdownloads2.esri.com/MappingCenter2007/resources/... · 2010. 9. 14. · Edie Punt. Slide 2 . ... •A rule will always consist of at least one symbol layer

Technical Workshops

Advanced Cartography in ArcGIS

Robert JensenEdie Punt

Overview

• Using representations to manage symbology• Solving graphic conflicts• Geoprocessing for cartography in ArcGIS 10

A good map communicates by: depicting data effectively reflecting the relative importance of features reducing distraction and conflict

Representation Symbology


Representations are:• A way to symbolize features to solve common

cartographic challenges• A storage model that stores symbols with data• Part of a feature class, managed through a layer

Common cartographic challenges previously required complex workarounds Storing symbols in the geodatabase makes that information available for re-use and sharing


• Representations symbolize features cartographically

Representations follow a rule-based structure Red = dashes Blue = drop shadows Green = overpass Orange = rotation


• Representations can produce and draw dynamic geometry, which may differ from spatial geometry

Rivers are drawn smoother than the underlying geometry

Representation Field Mapping

• Representations can be data-driven to tailor symbols to feature attribution

Streets drawn with one symbol

Casing and fill width from attributes

When multiple rules share common aspects, it’s a good idea to consider a single rule A single rule is easier to interact with and thus more efficient Attribute information controls the way symbols are drawn Establish field mapping for gray layer to Road Casing Establish field mapping for orange layer to Road Fill


• Representations can store and display multiple symbols for each feature

TThhee ssaammee ddaattaa rreepprreesseenntteedd ttwwoo wwaayyss BBootthh vveerrssiioonnss aarree ssttoorreedd iinn tthhee ddaattaa,, nnoott iinn mmaapp ddooccuummeennttss oorr llaayyeerrss Allows for differing sets of symbology to be accessed from the same data source. A self contained solution.

Representation Rules

• Symbol layers• Geometric effects, marker placement styles

•Representation rules are a set of properties that describes a unique symbol •Stored as feature class attribute values •A rule will always consist of at least one symbol layer but may consist of a combination of many types of symbol layers Symbol layers

Marker Line Fill

Geometric effects Dynamically alter display geometry

Marker placement styles Place representation markers relative to input geometry

Marker Placement Styles

• Position representation markers- Along lines and polygon outlines- Within polygons- In relation to points

• Extensible: write your own

The way in which a marker or multiple markers are positioned in relation to the supporting geometry of the feature This geometry could be a shape override or the result from a geometric effect

Geometric Effects

• Dynamically change geometry before symbol applied- Affect all symbol layers, or just one - Can convert geometry type

• Can work sequentially• Extensible: write your own

May be applied individually to symbol layers or globally to all symbol layers Chained effects work in sequence from the top down The order can create different results The geometric effects applied to one symbol layer have no influence on other symbol layers in the rule.

Chaining Geometric Effects

Dashes + Dashes

Wave + Wave

• Creates unique symbols• Effects can be chained to themselves

Note on first bullet: These symbols/patterns are not available with a single effect Chaining effects builds the complexity of the rules. Dash example Dashes 1: Red Line = 0.5 pt, dashes 4 4, half pattern, offset 0.25 Blue Line = 0.5pt, dashes 4 4, dashes 2 2 half pattern, offset -0.25 Dashes 2: Red Line = 0.5 pt, dashes 4 4, half pattern, offset 0.25 Blue Line = 0.5pt, dashes 4 4, half pattern, dashes 2 2 half gap, offset -0.25 Wave example Wave 1: 6 6, square Wave 2: 4 4, sinus

Representation Geometry Logic

• The geometry made by the last effect in the chain must match the geometry type of the symbol layer

- Else a warning appears indicating a disconnect in geometry logic

- The symbol layer doesn't have geometry to symbolize

Geometric effects alter geometry and even, in some cases, geometry type, it is important to ensure that representation rules maintain geometric logic. Geometric effects operate sequentially. The output of one geometric effect becomes the input of the following one, so you can use a chain of geometric effects to achieve the appropriate geometry logic. Regardless of how the geometry is dynamically changed through the chain of geometric effects, the final output of the last effect must match the geometry type of the symbol layer. If a warning symbol appears on the heading of the symbol layer, there is a disconnect in the geometry logic. The symbol layer you just added doesn't have any geometry to symbolize. For example, adding a fill layer to a line representation rule would generate a warning because there is no polygon geometry to fill. To repair the logic, add a line-to-polygon geometric effect to either the fill layer or the global effects portion of the rule. However, the opposite scenario—adding a line symbol layer to a polygon representation rule—would not generate a warning, because the line symbol layer will symbolize the outlines of the polygon geometry.

Geometric Effects: Drop Shadows

• Simulate a 3-dimensional appearance

Move effect

Offset effect

Method = Rounded

Gradient pattern

Color 1 = white

Color 2 = black

Intervals = 50

Percentage = 50

D

-Demo script- Use Move and Offset on fill layers to show how polygons can have their location changed just like points are. Move: X offset = 0.5, Y offset = -0.5 Offset: Offset = 0.5, method = rounded Gradient: color 1 = 100% white, color 2 = 100% black, style = buffer, intervals = 50, percentage = 50, angle = 0 Bonus = create rounded corners for buildings: Offset = -0.5, Buffer = 0.5 Opposite order will create square corners again

Geometric Effects: Using Markers

Offset: -10

Placement: Inside polygon

Offset: -7

Placement: Along outline

Offset: -3

Placement: Along outline

The polygon shows a feature where the middle of the feature is the highest part. Use a representation symbol to emphasize this. Its representation has four symbol layers: a stroke layer symbolized with dark blue; and three marker layers, each a dark blue dot of a different size. Each marker layer has its own placement style and geometric effect. The desired cartographic effect is a depth perspective effect where the dots stand out more along the slopes at the edges of the feature. To make the feature look like a hill, change the marker sizes and placement styles for the inside and outside layers. a) The placement style on the smallest dot is "Inside polygon." These dots fill the polygon interior. They do not fill it to the edge because of the Offset curve effect with a -10 value. For this marker layer, the polygon is shrunk by 10 points in all directions. b) The placement style on the medium dot is "Along outline." Without a geometric effect, this would cause one row of medium-sized dots to be placed along the polygon boundary. Because of the Offset curve and its negative value, the boundary is shifted seven points inward. c) The placement style on the big dot is also "Along outline," and the effect is the same as with the medium dot except that a different offset value is used.

Geometric Effects: Tapered Streams

• Organic, artistic look• Use Wave and Tapered Polygon geometric effects

Rivers drawn from line geometry

Rivers drawn from dynamic polygon geometry

D

-Demo script- The first goal is to show a river dynamically changing width to give the impression that water is flowing downhill. The second goal is to give the river symbols a more natural look instead of the straight line geometry of the feature. Tributary rule: add a new fill layer (see warning) and move it below the stroke – note that the fill layers attempts to draw something (might be OK for some features). Add Tapered Polygon effect (no warning), click apply to see poly draw. Move the fill layer above the stroke layer. Change To width to 2 - apply, change length to 45 – apply, change color to Cretean Blue (3rd from top/right) – apply. Now add wave effect above taper, period = 12 – apply, width = 4 – apply, style = random – apply. Note the difference between the fill and the stroke layers. Remove the stroke layer. click apply to finish with this rule. Body rule: Add the wave effect, period = 15, width = 5, style = sinus.

Representation Overrides

• Exceptions to the rule- Customize individual features- Made while editing

• Property overrides- Change any property of the rule

• Geometry overrides- Store alternate geometry

Representation Licensing

• Representations recognized by all ArcGIS products

• ArcView license: - View representations and properties

• ArcEditor license: - Create and edit representations - Some geoprocessing for representations

• ArcInfo license:- View, create, edit representations- All geoprocessing tools

•To use the representation geoprocessing tools, you must have an ArcInfo license. •It’s still useful to be aware of and understand representations if you’re working with an ArcView license because although you can’t create or edit them you will still be able to view them and their properties. •Recognized by all ArcGIS products

ArcView, ArcEditor, ArcInfo ArcGIS Server ArcGlobe, ArcScene ArcGIS Explorer ArcReader

Resolving Graphic Conflicts


• Features compete for map space- More prevalent as scale decreases- Retain representative character- Automate where possible

• Techniques to solve graphic conflicts:- Mask portions of features- Spread clustered features- Use contextual generalization

•• CCoonnssiiddeerraattiioonnss:: –– SSoommee ffeeaattuurreess mmuusstt sshhaarree tthhee ssaammee mmaapp ssppaaccee –– BBaallaannccee bbeettwweeeenn sshhoowwiinngg eelleemmeennttss aanndd lloossiinngg iinnffoorrmmaattiioonn –– OOtthheerrwwiissee rreeqquuiirreess ttiimmee ccoonnssuummiinngg mmaannuuaall iinntteerrvveennttiioonn

•• OOppttiioonnss ttoo ssoollvvee ggrraapphhiicc ccoonnfflliiccttss:: –– MMaasskk oonnllyy ppaarrttss ooff aa ssiinnggllee ffeeaattuurree –– SSpprreeaadd cclluusstteerreedd ppooiinntt ffeeaattuurreess aappaarrtt ffoorr vviissiibbllee ddiissttiinnccttiioonn –– AAppppllyy ggeenneerraalliizzaattiioonn tteecchhnniiqquueess iinn aa ccoonntteexxttuuaall ffaasshhiioonn


Vertical Coincidence

D

• Requirement: Symbolize vertical coincidence without altering the connectivity of associated data

• Solution: Create overpasses

GP tool automates a solution Find features where symbols intersect Build a mask at that location Create some bridges around those masks Use the masks to hide portions of a feature’s symbol Masking at the feature level, instead of the layer level


Symbol-level Masking

D

• Requirement: Show features clearly• Solution: Hide parts of a feature

Introduced at 9.3.1 Open Advanced Drawing Options Dialog Click “Draw using..” check-box Choose a layer from list of Masking Layers Choose a layer from list of Masked Layer – click apply Click “Enable to…” check-box Click on the Masked Layer, then click in Level section which is now available Type 1, 3 (the comma is needed but spaces are optional) – click enter Click apply to see result Click OK to close the dialog


Disperse Markers tool

• Requirement: Display clustered markers clearly• Solution: Spread markers apart with shape overrides

D

-Demo script- Open Disperse Markers tool Open help tab to learn about choice of patterns Choose input layer Choose 3 pts for the minimum spacing Choose ring for dispersal pattern Click OK to run tool Start editing and select features Open Representation properties dialog and see shape override button Click override button to remove it and see features returned to their original location


Detect Graphic Conflicts tool

• Finds areas where symbology overlaps, even if geometry does not

- Or find areas where symbology too close

• Compare two layers, or one layer to itself• New at ArcGIS 10: use non-representation layers too

The tool assesses conflicts among symbols, not geometry. The input layer and the conflict layer can be the same. Input layers can be symbolized with standard symbols or representation symbology. Input layers can include feature class annotation, including symbol substitution. Shapefile, coverage, and CAD layers are also acceptable inputs. The following inputs are not accepted by the tool: CAD, coverage, or VPF annotation, dimensions, charts, dot-density or proportional symbols, raster layers, network analyst layers, or 3D symbols. Use the Conflict Distance parameter to detect areas where input and conflict symbology is closer than a certain distance. The conflict calculation is based on a reference scale. Use the Line Connection Allowance parameter to disregard symbol overlaps where line ends meet. This is useful if you use line symbol end caps to ensure that lines connect visually, but you don't want each instance detected as a conflict.

Contextual Generalization with Geoprocessing

• Simplify data to display at smaller scales- Assess multiple layers contextually- Maintain representative pattern, density, and character- Resolve conflicts between symbolized features at scale

Traditionally the generalization tools we have released focus on geometry only. They work on individual feature geometries, or small groups of features. They didn’t consider symbology at all, and are useful for simplifying features, but not de-conflicting features. At 10 we released the next generation of generalization tools. These tools take into account that the: -Type of feature matters. Road networks are different from hydro networks, are different from pipeline networks -The relationships between layers matter. Moving Roads will affect how you need to move buildings. -The size of symbolized features at scale must be taken into account for de-conflicting features -Patterns need to be maintained. Road networks, building patterns -In a cartographic workflow it is often better modify the input layers, rather than creating new feature classes. Cartographic generalization takes place after the symbology has been applied and often after cartographic edits have taken place. For this reason the new tools will work with Representations. Generalization modifications can be written directly into the overrides without messing up the core geometry.


Thin Road Network tool

• Removes less significant roads from display• Retains representative pattern and connectivity• Visibility controlled by attribute, easy to modify

D

Maintain pattern and density while retaining connectivity Keep significant roads only

Balanced by road classification Retain specific features by locking

Visibility controlled by attribute, easy to modify Level of 0 can be used in all the new tools as a lock. You can set up multiple visibility fields for multiple scales… no overhead… lots of different ways to view same feature class. This tool lowers the density of a displayed street network by eliminating smaller, less significant roads while maintaining the overall connectivity and character of the street network. The Thin Road Network tool eliminates road features from display to create a simplified arrangement of roads that maintains connectivity along with the representative pattern and density of the original arrangement. Flexibility is provided in that significant features can be forced to remain visible, and the visibility of any feature can be easily switched. No data is moved or deleted in the processing of this tool. Use a definition query to show the results – zero = visible, one = invisible


Merge Divided Roads tool

• Create a single highway feature from multiple lanes• Create a single road from a boulevard• Merge only equal-class roads together

D

This tool generates a line feature class whose features follow the course of divided road features to display a simpler network of single lines. The Merge Divided Roads tool creates a single road from a matched pair of parallel-trending, equal classification roads. This is particularly useful when data has been collected as separate lanes in a highway, or for multiple lane boulevards but should be depicted as a single feature at reduced scales. Pictures: 1 = original roads, 2 = thinned roads, 3 = merged roads at 10K, 4 = merged roads at 24K


Resolve Road Conflicts tool

• Adjust roads to show visual separation- multi-lane highways, boulevards, dead-ends, roundabouts

• Less significant roads moved to accommodate more significant roads

D

Symbolized roads tend to coalesce at smaller scales Spread parallel-trending roads apart, Adjust roads to show visual separation

multi-lane highways, boulevards, dead-ends, roundabouts Displacement can be saved as polygons

visual check, or input for Propagate Displacement tool to maintain spatial relationships

Enhance dead-end spacing This tool resolves symbol conflicts among roads by slightly displacing features while retaining connectivity and character of the road network. Input features are hierarchically categorized to ensure that less significant parts of the network are moved to accommodate more important features. The Resolve Road Conflicts tool separates roads that graphically conflict when symbolized at scale. Road classification is defined through attribution and used to dictate which features will remain in place (or move a relatively small amount) at the expense of others which must be moved and reshaped somewhat to accommodate them. This tool separates multiple highway lanes and boulevards, exaggerates roundabouts, and widens gaps between highways and exit ramps. The degree and direction of displacement can be stored in polygons which can be used to propagate this movement to spatially related features.

Resolving Line Conflicts

• Comparing Resolve Road Conflicts tool and Merge Divided Roads tool

Coalescing

Displace

Merge


Propagate Displacement tool

• Conflict resolution may introduce spatial discrepancy- Adjust adjacent features to reestablish relationships

• Use displacement output from other tools- Merge Divided Roads tool- Resolve Road Conflicts tool

D

Propagate displacement to points, lines, polygons solid: entire feature moves as a block, i.e. building elastic: feature can be warped slightly to fit, i.e. forest auto: tool decides for each feature, based on geometry (default)

This tool evaluates the displacement that was made to a road network and propagates the shift to nearby features to ensure that their original spatial relationships are retained. The Propagate Displacement tool preserves the spatial relationship between features by propagating the displacements made in conflict resolution to proximate features. Movement can be either solid, where the entire feature is translated to a new location, or elastic, where a large complex feature is reshaped proportionally to account for the positional changes. An automatic option allows the tool to make this choice dependent on the morphology of each feature.


Resolve Building Conflicts tool

• Separate buildings from each other and from barriers- Retain relative density and pattern- Adjust visibility, size, and spacing, orientation

D

This tool resolves symbol conflicts among a collection of buildings with relation to one or more linear barriers. Minimum building size is enforced and placement in relation to barriers can be controlled. The Resolve Building Conflicts tool seeks to eliminate graphic conflicts between buildings and between buildings and specified barrier features through elimination and transformation when they are symbolized at scale. The characteristic pattern arrangement and density is preserved. Small buildings can be increased to a minimum size and multiple barrier layers can be considered simultaneously. Barriers typically include roads and streets, but can also include other layers like rail, hydrography, utilities, or administrative boundaries. Point and polygon building geometry can be assessed together. Buildings can be optionally oriented and positioned relative to the barrier features.

ESRI Mapping Centerwww.esri.com/mappingcenter

Documents

Edie Punt - Esri Supportdownloads2.esri.com/MappingCenter2007/resources/... · 2010. 9. 14. · Edie Punt. Slide 2 . ... •A rule will always consist of at least one symbol layer