Carto Questions – Answers

To make a backup archive of an ArcGIS Pro project folder (including geodatabase(s), .aprx file, etc.):

• Close ArcGIS Pro
• Open Windows Explorer (or My Computer) (not Internet Explorer)
• Browse to the location of your project folder (the one with the geodatabase(s), .aprx file, etc. in it)
• Right-click on the project folder and choose Send To / Compressed (zipped) Folder
• This should create a .zip file (a ‘zipped’ file) that contains a compressed (zipped) version of your entire project folder (with the geodatabase(s), .aprx file, etc.)
• Recommended: Rename this file so that the name of the zip file has the date in in (i.e., instead of smith_caribbean.zip it is 2020_04_30_smith_caribbean.zip)

THEN, you can open and continue working with your original .aprx file in your original project folder. So the answer to your second question is you do not (can not) use the backup zip file with ArcGIS Pro – you have to keep using the .aprx file in your original project folder. The backup is only for if something goes wrong with your original project folder.

IF you need to restore / return to / use a backup version you would need to Unzip it (uncompress it), which would create a new copy of the your project folder, with geodatabase(s), .aprx file, etc. that you could open and use.

INFO:

One of the ‘clever’ things about Labels (which are automatically placed) is that if there are too many labels (i.e., the map area is too crowded) then Pro will only display some of the Labels. One downside of this is that if you convert your Labels to Annotation it will likewise (by default) only convert those labels that are being displayed – and you end up not having annotation for the features that weren’t being labeled… But you don’t have to accept this default behavior (of course).

So if you find that your Annotation feature class is missing text for some of the features you can either:

• Simply add the missing annotation manually
• Re-do the Convert Labels to Annotation process and change the default settings

For the detailed write-up on this, see: https://huxley.wwu.edu/sal/tut-pro-labels-anno (specifically the section on ALL of the Labels to Annotation).

Here’s the quick version:

To convert ALL of the labels to annotation (even if they weren’t being displayed on the map):

• In the Convert Labels to Annotation pane CHECK the box for Convert unplaced labels to unplaced annotation
• These ‘unplaced’ annotation features still won’t be visible (by default) but at least they will be in the database…

To ‘Place’ annotation that is ‘Unplaced’ (i.e., make it visible on the map):

• Open the Attribute table for the Annotation feature class
• Select an annotation text string and change the value of the Status field from Unplaced to Placed

To ‘Place’ ALL of the ‘Unplaced’ annotation at once:

• Open the Attribute table for the Annotation feature class
• Right-click on the Status field to choose Calculate Field
• In the Calculate Field pane, enter 0 for the value to be calculated (for the Status field)
  • i.e., Status = 0

INFO:

Labels (which are generated directly and dynamically from feature attributes and placed on the map dynamically) can be converted to Annotation Features in an Annotation Feature Class. Annotation features can be edited – both in what they say and where they are located. You can also modify the font / size / color / style of annotation features individually (as opposed to changing the Label style for an entire group of labels).

EDITING Annotation Features:

• To edit annotation features use the Edit ribbon (from either a Map View or a Layout View with the Map Frame Activated)
• On the Edit ribbon there is a Select tool and a Clear button (which are similar to the Select / Clear tools on the Map ribbon)
• If you select a piece of annotation text you can reposition it using the Move tool (also from the Edit ribbon)
• (Use the Finish icon on the Edit toolbar to complete the edit)
• Also, with a piece of annotation text selected, you can open the Attributes pane from the Edit ribbon
• In the Attributes pane you can change the wording, stack the text, change the font size, color, symbol, etc.
• Once you are done editing the annotation you can use Clear to unselect
• Use the Save icon (on the Edit ribbon) to save your edits

INFO:

When you create a new annotation feature class it should be created / stored (by default) in the Project’s Default Geodatabase (similar to when you create new data via any Geoprocessing tool). You can override this if you want, and store the new data in whatever geodatabase you wish, but for most projects using the Default Geodatabase is a good place. However, when you open your geodatabase in Catalog your new feature class may, or may not, appear to be there. If it’s not listed, the most common reason is that the geodatabase display needs to be refreshed. (Why you would have to manually do this is a mystery…)

SOLUTION:

• Open the Catalog pane
• Open / expand the Databases folder
• Open / expand the Default geodatabase (the main project geodatabase)
• Right-click on the Default geodatabase and choose Refresh
• All of the feature classes in the geodatabase should now be displayed…

NO. You should not need to re-project any of the data for Labs 1, 2, 3 or 4. Instead, you will be setting the Coordinate System / Projection properties for the Map view. This controls how the data is displayed.

You can set whatever coordinate system / projection you want for the display of the map view and ArcGIS Pro will do a virtual re-projection of the data on-the-fly from whatever system the data is in to whatever system you are choosing for the display of the map.

One method is to open the Fields table for the layer. In the Fields table you can modify the Alias for the field. Click Save and close the Fields table when you are done. This should change the field heading in the layer’s attribute table as well as how it appears in the Symbology pane and the Contents pane. If you have already applied the symbology using the original field name (before you set an alias) you may need to refresh your symbology (change to some other field temporarily and then choose your newly aliased field again to refresh the display).

You can also modify the text directly in in the Contents pane: first click on the field name in the Contents to select it. Then click it again to shift it to edit mode. You can then type whatever you want to use as a label for that field.

Both methods should be reflected in the Legend.

INFO

Labeling lat-long lines is important, especially for large-scale maps (for small-scale maps it may be less important if the purpose is just to show the curved shape of the planet). On a large-scale map the lat-long lines are meaningless (just lines on the page) unless they are labeled.

OPTIONS:

A. One method of showing lat-long lines is to Insert a Grid for a map frame in a layout. These grids are created as a property of the map frame and are drawn on top of the rest of the map (so they are shown on top of any feature symbology or text in the map itself). You can set the units and the spacing increment for a Grid as well as how the lines and the labels are shown. Because these labels are a property of the map frame they are shown at the edges of the map (just outside the frame) which removes clutter from the map itself. One of the downsides of this method is that the because the Grid lines are drawn on top of the map you can’t create a figure-ground effect by placing the lat-long lines behind/below the land…

B. A second method is to use a lat-long line feature class to show the lat-long lines. Many of these exist, and often the have attributes to enable the use of all lines or just the lines in certain increments (every 5 degrees vs. every 20 degrees, etc.). You can adjust the symbology of the lines as desired, and as a feature class these lines can be drawn above or below the land (for figure-ground, etc.). Like any other line feature class, lat-long lines can be labeled. Because they are features in the map the labels and/or annotation are likewise in / on the map itself (i.e., they can’t be placed outside the map frame on the layout).

C. A third option is a hybrid of A & B above. In this method one uses a lat-long feature class to show lines on the map (symboloized and arranged above/below land as desired) without labels. Then, to add labels, you can Insert a Grid (in the layout) for the map frame and show only the labels (i.e., do not show the Grid lines themselves). This method allows you to customize the symbology of the lines as you like (in the map) but still have labels that are outside of the map frame (at the edges). This requires first getting the Grid increments to match those used for the Lat-Long lines, and then turning off the Gridlines so that only the labels are shown. To create a Grid with labels only:

• Insert Grid / Black Horizontal Grid (or other template as desired)
• Open the Format Map Grid properties pane (right-click on the Grid in the Layout Contents)
• Under Map Grid / Options UNCHECK the box for Automatically Adjust
• Under Map Grid / Components select the Interval for Longitude and Latitude (to match your lat-long line feature class)
• Under Map Grid / Components select and the Remove (using the x) any Ticks or Gridlines Components (leaving ONLY the Labels)
• Under Map Grid / Components format the Appearance of the Labels as desired….
• Choose Labels from the Format Map Grid drop-down menu to set other display properties… (font, offset, color, halo, etc.)

• Select your scale bar
• Right-click to choose Properties to open the Format Scale Bar pane (not the ribbon)
• In the Format Scale Bar pane:
• Scale Bar (drop down menu)
• Display tab
• Border: X gap and Y gap settings
• Background: X gap and Y gap settings

You can use whatever font you like. Just make sure it supports the overall goal of communication.

Comic Sans requires slightly more room than something like Arial or Verdana, so you make your job more difficult, but it’s up to you.

When creating a new feature class (for annotation or for geographic features) you need to
1. Create a new feature class (in Catalog)
2. Add the feature class to the current map view you are using (using Add Data or drag to the map view)
3. Go to the Edit tab of the ribbon and choose your edit tool of choice (Create Features, Move, etc.)

• In ArcGIS Pro:
  • Select the layer being labeled in the map view Contents
  • From the Labeling tab of the ribbon, set the desired scale thresholds for the Visibility Range (allowing you to control at what scales the labels are drawn or not drawn)
  • See also: https://pro.arcgis.com/en/pro-app/latest/help/mapping/text/label-classes.htm (note that the scale ranges settings work even if you aren’t using multiple label classes)
• In ArcGIS Online (Map Viewer):
  • Select the layer being labeled in the Layers contents panel (left side of the map)
  • On the right side of the map, open the Labels pane
  • Adjust the Visible Range sliders to set the scale thresholds
  • (note that the black triangle below the slider bar indicates the current map scale)
  • See also: https://doc.arcgis.com/en/arcgis-online/create-maps/configure-labels-mv.htm

Note: With very few exceptions you should not be using ESRI Basemaps for ANY of the static maps in this class. The only exception might be for a hillshade (or some other ESRI base data), being added to one of the later lab assignments.

By default, ESRI adds data credits onto map frames that use their Basemaps (and some other data layers from ArcGIS Online). These credits remain on the map even if you can’t see their data, and you cannot turn these off (unless you turn off the ESRI base layers). But you can modify the credits, or even replace them. Note that if you are using ESRI data you need to acknowledge this on the map, but if you don’t like the way their default credits look you can modify the credit text.

First, we need to change the map frame basemap credits to a Dynamic Text string:
– In the Layout view, open the Insert tab of the ribbon
– From the Dynamic Text drop-down menu, choose Service Layer Credits (from the Layout section)
– Drag/draw a box on the page where you would like to relocate the credit text
– This adds a text box to your layout, with the credit text. The advantage of this is that you can now move the text box, change the font size or color, etc.
– Note that if you delete the text box it will reappear as the default map credits (on the map frame)

Ways to improve or ‘remove’ the Service Layer Credits
– You can make the text smaller, or a lighter color
– You can position them to the edge of the page (or wherever they are out of the way)
– You can move the text box off of the page, or place it under some other map element… (but if you do this you need to replace their credits with credits of your own wording)

Things to try:

Try a different DPI (resolution) for the Export (and/or change some other export setting(s)

Export to jpg vs. tif vs. pdf (and then convert to different format after exported, if necessary)

Take a screenshot of the Layout View and submit that (especially if just for a Draft)

See General Questions / response / links above…:

INFO:

When labels are converted to Annotation the software places the annotation in the middle of each polygon (i.e., in the middle of India) – not where the label was.

Label placement uses an algorithm to place the label in the ‘best’ location; Annotation puts the text feature in the middle of the polygon so that you can place it where you want it. Automatically generated and placed labels are easy, but annotation gives you far more power in terms of control. However, with great power come great responsibility (neither Peter Parker nor Voltaire)

SOLUTION:

Zoom out and/or Pan the map to where you can see the middle of India. Using the Edit tools, Select the India annotation text and Move it to where it will be visible in the layout.

INFO:

A feature class can contain graphic features (points, lines or polygons) or annotation features. To create / add features you need to use the Edit tools to create new features. The process is essentially the same for annotation as for creating new lines or polygons.

SOLUTION:

First create the empty Feature Class: Catalog / Databases / <yourGeodatabase>.gdb / <right-click> / New / Feature Class Name… Feature Class Type = Annotation Coordinate System… Reference Scale = Set this to approximately the finished scale that you will be using for your final map / layout- this is important Do NOT just use the default setting as it is unlikely that it will be what you want

Once you have your new annotation feature class you can add text string features: Zoom your map to the region where you wish the text string to be Scale your map view to approximately the MAP SCALE of your FINAL MAP (the map view in the layout) Edit ribbon Create (which should open the Create Feature pane) Select the feature class that you want to add features to (from the Create Features pane) Enter the text you wish to use for the annotation into the text box Click on the map at the location you wish to place the text string

You can then use the other Edit tools (move, rotate, etc.) to relocate the text string as desired.

INFO:

A Legend itself does not have a Gap setting – but there are Gap settings for the Border, the Background and the Shadow. (note that before you can see these changes on the Layout you will have to make sure that the Border, Background and/or Shadow have a symbol color (i.e., aren’t transparent).

SOLUTION:

Format Legend (pane, not Ribbon) / Legend (drop-down menu) / Display (tab): X and Y Gap settings for Border, Background and Shadow

Note: The black box (w/white corner handles) that is shown when you have a Legend item selected does not reflect any of this. It is simply the (un-gapped) Legend item.

For Maps 1-A and 1-B: ESRI, 2005

For Map 1-C: ESRI, 2005, 2014 (in addition to (minimal) credit for any online data that you use (see below)

For Map 1-I: Washington State Dept. Of Ecology, 2019
(along with ESRI for the basemap and optionally other data layers if used…)

For online data sources (from ArcGIS Online, the Living Atlas, etc.) you can list either “ArcGIS Online” or “ESRI Living Atlas” along with the agency that created / hosts the data (if there is one) or the owner name (if an agency isn’t listed). If you can find a publication date for the data you should include that as well (but you don’t need a full citation, URL, etc.)

Web Apps should have a specific section for Data Credits (sources and dates) included as part of the About or Info section.

The maps will also have the ESRI Basemap Service credits (by default) on the map itself, so you don’t need to list the basemap in your Data Credits (though you can if you want).

Also in the About / Info section (and maybe also in a Splash Screen) would be:

• NAME of the CARTOGRAPHER
• NAME of the​ ORGANIZATION responsible for the map (often including a Logo and/or URL)
  • This can be either WWU or Huxley or ENVS… or some combination
• DATE of the MAP / APP creation/publication
• DATE of the map DATA 
• SOURCE(s) OF DATA
• SOURCE(s) OF PHOTOS (if photos are used)
• NOTES on the purpose / intent of the map
• NOTES on how to use the map (technical aspects if not intuitive)

A Splash Screen is a good place for some of this info, but most of it should ALSO be in an About or Info section so that it is available to the user as they are using the map (without having to reload the map to get to it). Thus, a Splash Screen is a good place for the overall / general information but is not, typically, a replacement for an About or Info section.

Refer to the instructions in the lab write-up for the different dates and sources of the various data layers.

Yes.

Make sure that any/all ESRI basemaps are turned OFF (or removed entirely). Not only are these basemaps forbidden for our static maps in this class, but they fill the entire map view and block any potential symbology changes you make to the Map Frame Background (if that is how you are symbolizing the ‘ocean’).

You could also use a data layer to symbolize the ocean (i.e., one of the Feature Classes in the geodatabases, instead of trying to symbolize the background of the map). Feature classes can be symbolized as you like (with more options than the Background) and can be quickly turned ON/OFF as you like (which can improve draw times). They can also be arranged where you want in the Contents draw order (i.e., on top of the ESRI basemap, which should be turned off anyway).

In your project Default geodatabase (the main geodatabase for the project).

An ArcGIS Pro Project folder should contain at least one ‘project geodatabase’ that has the same name as the main .aprx file and as the project folder itself. This is (by default) the Default Geodatabase where newly create data (annotation or other feature classes) are created and stored. You can change where you want to store data but in general the project Default Geodatabase is a pretty good place.

BACKGROUND

In the Chart Frame Properties choose: Only show chart data visible in the map frame AND Within the map series shape. By doing this the chart should only show data for the geographic area as defined by the particular feature in the Map Series Index layer (i.e., just the data for a specific island or country that is being used to define the map series page). The issue is that sometimes the Chart Frame doesn’t seem to do what it’s supposed to (i.e., these settings don’t always work and the Chart shows data for adjacent geographic areas as well).

A few students ran into this last quarter, with no real satisfactory answer as to why (or how to fix, once it happens). As best I can figure, it has something to do with the order of events (i.e., Inserting the Chart Frame before or after the Map Series or something like that)… We were never able to figure out exactly why some students ran into this but most did not… So, if this happens to you:

TWO OPTIONS:

1) Just ignore it and post a comment when you submit your maps saying “Chart Property for ‘Within Map Series Shape’ Not Working” (and we’ll know that you tried and we’ll not worry about it)

2) Try again, with a different chart and/or different layout. Here are some options:

Quick Trial # 1 (and if this works you can proceed to rebuild the map series as required):

• Insert a new Chart Frame (into the Layout with the Map Series already created)
• Set the Chart Frame properties as specified (if needed – I think the default for a Chart Frame in a what we want)

This should only take a few seconds – and if it works then you can re-set the other Chart Frame properties in terms of size, etc.

Quick Trial # 2 (if #1 doesn’t work)

This took me less than a minute – and if it works, then you can copy / paste other Layout elements from your original layout to your new layout)

• Insert new layout
• + Map Frame
• + Map Series
• + Chart

Not so Quick # 3...

Return to the Map View and create a new chart – and insert this into your Layout. If this works, continue with the layout…

And for the record, here is what worked for me in terms of the specific order of events:

• In the Map View
• Create the Chart and get all of the properties set properly
• Add Layout
• Insert Map Frame
• Create Map Series (using the Index Layer)
• Insert Chart
• Specify ‘Within map series shape‘ for Chart Frame Properties

Full question: “I’ve worked with R and graphing and was taught to not put a title on graphs, instead we would have the caption below. For cartography is it preferred to have a title on the chart / graph? I feel like it is because it gives a brief descriptor to the graph where there is nothing else, besides the axis labels, to describe what the reader is looking at. And it seems with GIS we’re a little more closer to the general public and having to make things simple and understandable versus the science realm.”

RESPONSE:

I don’t think it matters nearly as much for Cartography, as long as the information is there. As with most things in cartography there aren’t any real rules, just guidelines. And yes, cartography is much more about communication with the general public and less constraints by a particular science or journalistic style.

R is more typically used to produce charts that will go in a publication, thus the tendency towards having the chart captioned below like a figure. I think ArcGIS Pro tends to favor the title within or above the chart partly because it’s easier to program the chart item as a block (with title, etc.). Depending on how much, and what else, you have on the page, I think it also helps unite the various chart elements (title, axis, etc.) with each other. If there are a lot of other elements (as there often are on a map and less so in an article) then keeping the title within a chart border helps keep everything clear.

If the map were going into an article it might have the chart separate (with both the map and the chart having their individual captions) or it might be a map with a chart, and a single caption at the bottom for both…

“ESRI, US Census 2010”

If you duplicate a Layout view and still use the same Map view, then any changes made to that Map view will be reflected in all of your Layout views. If you want completely separate Layouts you would need to also duplicate your Map view as well. So for 5 different maps you would need 5 Map views and 5 Layout views…

Alternatively, you can just use one Map view and duplicate the key data layer multiple times. In this strategy you would only have one Map view but might add your State Census data layer 5 times (once with graduated colors, once with dot density, etc.). Then you can either have one Layout (and turn the appropriate layers On/Off along with appropriate text boxes and titles) or you could have 5 different Layout views (each with a unique title and text box) and all you would need to do is turn the appropriate layer On (and the other copies of the layer Off).

Good question. With kind of a long answer.

First off “NAD 1983” is a DATUM, not a Coordinate System. It’s easy to get confused, as many Coordinate Systems include the name of a Datum in the name of the Coordinate System. So, for example, “UTM NAD 1983” is a Coordinate System, that uses UTM (Universal Transverse Mercator) using the NAD 1983 Datum. 

What a Datum? In simple terms it can be thought of as a model of the earth. NAD stands for North American Datum and NAD 1983 is the best model / fit that was developed in 1983, and is better than NAD 1927 which, you guessed it, was the North American Datum of 1927…

Anyway, when you specify a Coordinate System, there is usually something more than just “NAD 1983”. Like ‘State Plane…’ or ‘UTM…’ or ‘Albers Conic…’

Unless you are using a “Geographic Coordinate System.” A “Geographic” coordinate system is Unprojected (or spherical). The most common Geographic Coordinate System is Lat-Long, but there are others, like ‘NAD 1983’ (which could more fully be described as a “Geographic Coordinate System using NAD 1983” – the NAD 1983 part is still the Datum, not the Coordinate System). These unprojected (“Geographic”) coordinate systems are usually NOT what we want for static maps. Since we are heading for a flat, static map (i.e., on a piece of paper or a flat screen) we want a “projected” (i.e., flattened) coordinate system. You will note that when choosing a Coordinate System the first choice is between “Geographic Coordinate Systems” and “Projected Coordinate Systems”. You want to be looking in the Projected Coordinate Systems.

So…, if I were looking for a Projected Coordinate System for a map of the United States (especially the lower 48) I’d be looking in the Projected Coordinate Systems / Continental / North America / folder.

For a more local or regional map I would look in Projected Coordinate Systems / State Plane / or Projected Coordinate Systems / UTM /.

~ ~ ~

So that should get you a Coordinate System for the lower 48.

For Alaska and Hawaii, you could either use a new Map View, with a Coordinate System that fits AK or HI, or you could (perhaps) find a Coordinate System that looks OK for the lower 48 and AK and HI. Or you could find a Coordinate System that looks good for the lower 48 and then (for your inset maps of AK and HI) simply rotate the map frames (on the layout) as needed to ‘look’ right.

First off, map text will be the focus of Lab / Module 3, so you don’t have to get too carried away with it for the Lab 2 maps, but great to be thinking (and struggling) with these issues now.

Ideally, we’d like to use state names rather than abbreviations and we’d also like to be consistent across the map (i.e., use names or use abbreviations for all and use the same font size / style / color for all)… But that isn’t always possible.

Probably the first (easiest) option is to switch from full names to abbreviations. You could use some names (where they fit) and some abbreviations, but this is generally frowned on (the preference being for consistency). Still, it’s an option and you’ll find maps that do this.

Another option is to make some of the text a smaller font. Again, not ideal (inconsistent), but a fairly common solution. Sometimes you’ll see that the smaller text is in bold so that it ‘appears’ slightly bigger than it actually is. Or you can keep the font size the same but reduce the gap between the letters (making the words smaller). All of these, however, make the text harder to read and produce a map with inconsistent text (different text style for similar features). Another option, of course is just to make all of the text smaller (even for the bigger states that have room for bigger text). This in unfortunate, as much of the text is unnecessarily hard to read, but it does maintain consistency… 

Another option is to use leader lines. Leader lines are a way of ‘moving’ the text from the crowded area (where it doesn’t fit) to a less crowded place (like out in the ocean) where there is room. The downside of leader lines is that they add more ink (lines) to the map, which can create other issues and they move the text further away from the feature (which is always undesirable). As with using a smaller font size, sometimes a cartographer will opt to use leader lines for all of the text (even the features that don’t really need leader lines) to maintain consistency and just decide that that is the ‘style’ of the map…

Another option is to use halos for the text, allowing the text to still be close to the feature but ‘overcome’ the lack of room and the conflicts with map features.

Or you could use a lookup key: on the map you place a 1, 2, 3, 4… (or A, B, C…) and then have a ‘key’ somewhere that says “1 Vermont, 2 New Hampshire, 3 Rhode Island,” etc. This greatly reduces the conflict issues on the map (very minimal text to fit) but moves the text even further away from the feature it is supposed to be associated with…

You could also use a “detail” inset map (adding another map frame to the layout page where you could zoom in further and thus have more room for text)…

~ ~ ~

And, of course, you can combine multiple options: for example using a slightly smaller font size, with a halo, or abbreviations with a lookup key to list the full name, or an inset map with leader lines, etc.

~ ~ ~

What’s ‘best’? Unfortunately, there isn’t a ‘best.’ What it boils down to is that you, as the cartographer, want to have multiple options available and will have to choose which one(s) works / looks best for a given map. This will depend on the scale of the map (how crowded the text is) as well as how much other text is on the map as well as the audience and purpose (does the map ‘need’ full state names or are abbreviations okay?). And yes, it quickly becomes very subjective. 

I know that’s not the most satisfying answer, but from my perspective it’s Great that you are thinking about it and this is exactly the process that almost every cartographer ends up going through for almost every map.

The Heatmap layer should be ON when the map is zoomed OUT.

As you zoom in it should eventually turn OFF (and remain off for the more local scales of the map). Be sure your map has layers that turn on / off as the scale changes.

WHY we’d want this:

As one zooms in the heatmap style of symbology is less effective and less useful. Once you can no longer see the larger pattern of the ‘heatmap’ you only see a few colors. Not only is this harder to interpret without the rest of the pattern, but these colors are actually somewhat misleading in that they aren’t drawn from a particular data layer (they look like polygons but are simply drawn between and around points). For these reasons, one might choose (as I have) to NOT show the heatmap when zoomed in.

The desired result is a map that shows the cool heatmap pattern when zoomed out. And shows the more precise point data when zoomed in.

Point data, on the other hand, is hard to interpret when zoomed out and there are lots of overlapping/conflicting points. Thus the use of Cluster technique is appropriate for when the map is zoomed IN.

Full question: “Do you want all towns to be labeled within the extent of Abbotsford, Colwood, and La Conner, or would you only like those specific Towns being labeled?”

ANY town with a population greater than 30,000 that is shown on the map should be labeled. The towns of Abbotsford, Colwood and La Conner are listed purely to define the spatial extent of the map. But any large town shown should be labeled.

What we want to show is the NATIONAL capital for each and every country. So if we have 13 countries we should have exactly 13 capitals. In the database these are referred to as National capitals (as opposed to State or Provincial capitals).

Some cities serve as BOTH the capital for the country AND for the capital of the local province. Since these are National capitals they need to be included (as one of our ‘capital cities’). These are listed as National and Provincial Capitals, and YES they need to be included on your map (since they are the capital of the nation).

Each country (polygon) should have one and only one capital city.

Using the cntry08_line feature class (not the country polygon layer), choose Unique Values for the BND_TYPE field.

I assume by ‘changes’ you mean things like edits to Annotation.

A Map View, or a Map Frame in a Layout use data layers. Data can be features (points, lines, etc.) or annotation. These data layers are, by design, separate from the layout or the map view. They are data and are stored in the geodatabase. If you EDIT the data (the points, lines, annotation) in a data layer it is changed in the geodatabase. And then ANY other Map View / Layout that uses the data layer will likewise reflect the change.

For example, imagine that I have a feature class of city points for Washington. I can add that data layer to as many maps as I like. But if I edit the data and move the point for Seattle out into the water than ANY and ALL of the maps that use that data layer will now show Seattle as being out in the water. Because I edited the DATA. Likewise if I change the name of Bellingham to Stefanham it will be changed on all of the maps (and any labels that are being created from that point layer). Or if I edit an annotation string, it will be changed in every map that uses that annotation.

The advantage of using feature classes (points, lines OR ANNOTATION) is that it can be reused. So you don’t have to recreate text for each map you make. But this becomes a disadvantage if you want to customize / tweak the features for one map without effecting other maps (and again, this comes up most often for annotation). You may want to just tweak the data for one map, but you CAN’T. If you tweak the annotation is will be changed in all or your maps… (just like if you had moved Seattle out into the bay).

HOW TO AVOID THIS…

If you need to tweak / customize annotation (or anything else) for a particular map you need to have a feature class that ISN’T being used for your other maps. So you could either Copy / Paste your annotation feature class (in the CATALOG PANE, not the Map Contents) OR you can simply create a new annotation feature class. And then you tweak the new annotation layer, leaving the one you had alone so that the old map isn’t altered.

There are, of course, more sophisticated ways of creating multiple versions of certain features within a single annotation feature class, some of which could be used for one map and others for other maps… but for now, simply creating multiple annotation feature classes is probably the way to go. So you might have Cities_Anno_Map2a and Cities_Anno_Map_3, etc.

PS – locking a map frame (in a layout) prevents it from being panned / zoomed / moved / etc. – but does not lock the data (because, again, the data is separate from the map so that it can be used in other maps…

Having set the properties for the Leader Lines (for the Labels) and then converted the labels to annotation, try editing / moving one piece of annotation to see if the leader line appears.

Leader line are kind of weird in ArcGIS Pro. See: https://huxley.wwu.edu/sal/tut-pro-leader-line

You can either choose a label style that is curved to begin with (in which case all of the annotation that is created will have a curve ‘potential’ built into the text string. Or you can add the ability to curve an existing (straight) annotation text string by changing the underlying line segment (that the annotation text follows) from a straight line to a Bezier Curve:

• From the Edit ribbon, select a piece of annotation
• Click the Edit Vertices option in the ribbon (this should show the line upon which the anno is drawn)
• Right-click on the anno’s baseline (the line under the letters) and choose Change Segment / To Bezier Curve
• You can now tweak the curves using the vertex ‘handles’
• Add (or remove) vertices as needed… (I find that often having just two vertices, one at each end of the line, is best)
• See also: https://huxley.wwu.edu/sal/tut-pro-curved-anno

No, you should not.

It’s true. Some of the features you want (i.e., are required) to label on a map may not be included in the data set that you happen to have… (the same is true for features like the Panama Canal or the mountains).

How you solve this is up to you, but I wouldn’t skip it just because it’s not in the data you have… If your boss asks you to label something for a map would you just not bother if your data didn’t include that feature??

Sure, you’re welcome to choose whatever you want for a topic and to create your own data if needed.

As for data creation, there are two options. One is to create a feature class in Pro and Share that to a web layer. I’d recommend creating a new Map View that has only the one layer in it and Sharing that to a web layer (otherwise Pro wants to export everything else in the Map view also). Once it’s uploaded to your ArcGIS Online account (as a Feature Service) you can add it to whatever maps (in Pro or ArcGIS Online) that you want.

The other option would be to start your ArcGIS Online Web Map (pre-StoryMap) in the old Map Viewer. In the old Map Viewer you can create Map Notes (points or text) that are saved as part of your Map. You then would need to Save that map and then Open it in the new Map Viewer Beta for further development. You can’t create Map Notes in the new Viewer, but if you open an existing map that has Map Notes the display just fine.

Either way should work. And the final results would be similar. Creating a feature class in Pro is slightly more work, but gives you more flexibility (and you would be able to edit the data later if you needed to).

You can add text to labels by using a Label Expression (not to be confused with a Label SQL Query Expression). The basic idea is to add a text string to whatever attributes that are being used in the label.

Having added labels (using whatever field you wish) click on the Expression icon to the right of the Field drop-down-menu box in the Labeling ribbon. This should open the Label Properties pane to the Label Expression sub-tab.

In the label expression, instead of using just a field name
something like: $feature.NAME
you can add a text string to the field. For example:
$feature.NAME + ” Island”
This will add the word Island after each label. Note the use of the + sign to add a text string and the ” ” marks for the text string. Note also the inclusion of the space before the word Island (so you get Orcas Island instead of OrcasIsland).

These examples use the Arcade Language. See Help files for more information or for creating label expressions in other languages…

You can change the color / size / font / style / etc. of a single annotation text string by selecting it with the Edit ribbon Select tool and then opening the Attributes pane (from the Edit ribbon). Choose the Annotation tab (as opposed to the Attributes tab) and then make symbology changes as desired. Click the Symbol button for more properties.

If you want to change the color of more than one text string (or all of the text strings) select those that you want (using the Edit ribbon Select tool or by opening the anno Attribute table, etc.). With multiple text strings selected, open the Attributes pane (as above).

In the Attributes pane, you should see a list of all of the text strings you that are selected. Either select them all in the list (select the top one, scroll down and use Shift-click to select the last one and all in between) OR click on the layer name above the list (which will then apply changes to the full list). Make changes to the Symbology as desired, which will be applied to all of the text strings in the list.

Save your Edits.

For some reason, editing annotation seems to bring some computers to a crawl. I’m not sure why, but here are some things you can try to (perhaps) lessen the pain:
– Turn off any hatch, speckle, pattern, gradient or picture fills or symbology (while editing)
– Turn off any layers that you don’t need to see for the editing
– Break your anno feature class into multiple, smaller feature classes (so you can turn off most of your anno while you edit just a few pieces of text at a time) – later you can turn them all on for printing, etc.
– Try editing from within the Map View (as opposed to from the Layout View with the Map Frame being Activated)
– Try using a Graphics Layer instead of an annotation feature class (you can right-click on a layer in the Contents and choose to Convert Labels to a Graphics layer instead of to Annotation – you then use the Graphics tab on the ribbon to edit the text instead of the Edit tools)

Screen refresh / redraw speed is based on the amount of data and the symbology being applied to the data vs. the computer’s RAM, video / graphics card, etc. Larger files (lots of points or lines and/or lots of polygons with complex geometry) can slow the draw time, as does raster data. Annotation can be especially problematic. Symbology choices (pattern fills, hatching, picture fills, transparency, layer blending, etc.) can also slow the process. Displaying data in a projection other than the projection of the data (especially for large data layers) can slow the process.

See notes below for how to improve the refresh speed…

Things to try that might improve the performance:
– Get a bigger, better, faster computer
– Turn Off any layers that you don’t need (at the moment)
– Simplify the symbology (for the moment – i.e., you can make your ocean a simple blue fill while you are working on the map and then later change it to a speckle pattern)
– Use Labels instead of Annotation (at least for the moment)
– Apply Definition Queries or Selection Layers to data layers so you are only displaying the data you need for the map
– Clip your data (so that you only have data for the area you need to see in the map)
– Simplify your data (using Generalization tools to reduce the complexity of the geometry – but note that this degrades your data…)
– Locate data that is more appropriate for you map (smaller extent, different scale, etc.)

– FLATTEN your map (or certain layers of your map) – see notes below – Note that even if the Flattened version of the map isn’t high enough quality to use for the final map, you can use a Flattened version (of the larger, slower files) while you are working on the rest of the map elements, and then go back to the full (unflattened) data files for the final export / printing.

Most printers are not able to print to the very edge of the page…

Different printers are have different limits as to how close to the edge of the page they can print. ArcGIS Pro does not seem to do a very good job of knowing these limits ahead of time.

To avoid losing parts of your map, export the map to a .pdf file (or .jpg) file and print that. In the printer settings, choose “Fit to Page” (or similar options) to insure that the full map is printed. Note that this will reduce the size of your printed map slightly. This is why using a scale bar is better than using a representative scale fraction.

Probably the issue is file size (as related to computer memory and/or printer cache). Of course, you could find a bigger computer and/or a bigger printer and/or wait a looonnng time… But if that’s not possible:

– One option is to reduce the resolution of the file (see notes on Exporting below).
– Another option is to print the file using a browser: For example, if you have a .pdf file, rather than opening it from Adobe, open the file using the Chrome browser and try to print that (the browser will often reduce the file size).
– Another option is to export the file (from Pro) using a lower resolution DPI.
– Another option is to export the file (from Pro) to a different file format (.jpg vs. .pdf vs. tif).

Maps with a lot of data (especially intricate polygons with lots of vertices) and/or lots of text (annotation and/or graphic text) can create very large files when exported. Likewise, gradient, speckle, picture or hatched fill patterns can create very large files.

See below for notes on how to reduce the file size…

Options for reducing files size:
– The simplest method is to reduce the resolution in the Export (150 DPI instead of 300 DPI, for example. – Of course, this won’t look / print as crisp…
– You can also change the symbology, etc. (see notes above on Slow Refresh speeds)
– Export a high-resolution .jpg file (i.e. 300 DPI or better) and then convert the .jpg to a .pdf (most windows computers will let you ‘print’ to a .pdf file, or there are online applications that will create a .pdf from a .jpg, or you can use Adobe software). These will typically be much smaller files than the original .pdf exported from ArcGIS Pro.
– Replace some of the base layers in the map with a ‘Flattened’ image (see notes below)

The concept here is to ‘Flatten’ a bunch of data layers into a single, simple image file. Essentially, you are making your own basemap. Typically, you wouldn’t do this for all of the data layers in the map. Instead, just flatten the big / base layers (like the ocean, land, raster data, imagery…). To create a flattened image of a complex map:
– Working in a MAP view (not a Layout view)…
– Turn off layers you don’t want / need to flatten (smaller files, things you are still working with, etc.)
– Zoom in / out to the full extent of the area you need mapped (or out a little more)
– From the Share tab of the ribbon, choose Export Map (again, this is exporting a map from a Map View, not a Layout view)
– Choose JPEG for the file type and high (Max) quality for the output
– Check the box for Write World File (this will create a geo-referenced .jpg file)
– Click Export
– This will create a geo-referenced image of the map (like a screenshot with coordinates)
– Turn Off the data layers that were used to create the Flattened image
– Use Add Data to bring in the Flattened image (which should look about the same, but draw much faster)
– Turn on the other data layers (not in the image) to continue working with them…
– If the Flattened image isn’t good enough for the final map, you can use it for working on the map, and then turn off the Flattened image and turn on all of the original data files when you are ready for the final export / printing…

Something like… 

• Skills:
  • Static mapping
  • Interactive / web mapping
  • Cartographic Topics:
    • Symbology (Quantitative and Qualitative)
    • Color 
    • Text
    • Layout
    • Charts
    • Map Series
  • Web maps & apps & StoryMaps using ArcGIS Online
  • Working with Spatial data

ENVS-418 is an upper-division (400-level) course in cartography and communication of spatial information. It includes both static and interactive (online) mapping using qualitative and quantitative methods within the broader context of page layout and graphic design. The class is a hands-on (lab-style) course including review and critique of maps.

At WWU, ENVS-418 is a “BCOM GUR” course (Block B, Communications Studies, General University Requirement), addressing the Quantitative, Scientific, & Technological Literacies and the Communicative & Interpretive Literacies.

You may want to save all of your project and data files. But you should also export / save both .jpg and .pdf versions of your final maps (in 300 DPI). In general, the .pdf files should print a little better, but the .jpg files are easier to use in web pages, PowerPoint slideshows, etc. You might also print out a hard copy (note that you can print an 11×17 map on 8×11 paper but scaling the file to fit the page – not only does this make it easier to save / file / insert into a portfolio, but somehow the reduced size maps often look cooler than the original… great trick for that hoped-for job interview some day…)

Your online content (data, maps, apps) will all continue to exist in the cloud indefinitely. However, once you leave WWU you won’t have access to editing the files if you need to update anything. See https://huxley.wwu.edu/sal/leaving-wwus-arcgis-online-organization for more information.