It would be nice if layouts had some sort of option to 'talk' to the map and tell it not to label things underneath layout graphics, at least in the particular data frame shown on the layout. I see this being implemented as additional tabs in the label weight ranking dialog - one for each data frame or layout in the project that the map is used in that has the setting turned on. From there, you could assign layout graphics a weight similar to how you can assign map graphics and features a weight on a data frame by data frame basis.
This would allow me to not have to convert my labels to manual annotation/graphics all the time or monkey with the placement settings so much.
ENH-000134871 mentioned here seems to be talking about map graphics, not layout graphics; the original poster does seem to be asking about layout graphics, though.
The conflict between “Extent indicator” and labels.
How to avoid the conflict between the “Extent indicator” and labels wherever possible?
Thank you
Regards
Jamal
I would like the Maplex engine to view any other dataframe as a conflict and not place labels such that they are infringed upon by another dataframe. This comes into play when you need to enhance details on the map, which can be accomplished by placing a tiny, larger-scaled dataframe over the feature of interest. But this doesn't look so good when your I-80 shield is cut in half by the inset dataframe.
I have a lot of maps with cadastre labels in them, which can amount to a lot of labels. One of the recurring problems is that if the north arrow and scale is inside the bounds of the map, very often it will overlap with multiple labels, creating a messy and confusing impression:
This is not only a problem with cadastre labels, though it does happen with them a lot.
It would be nice if we could give graphic elements a sort of "bounding box" (not sure what else to call it), which - for example - could then be weighted similar to "Label Weight". The only idea I have to do it at the moment would be to draw a polygon on each page, which can be quite time-consuming with lots of pages in data driven pages.
Here's an idea that admittedly requires a bit of extra setup, but might be worth it if you have a lot of pages in your Map Series. The steps below apply to Pro.
Same as this idea from 2011, and still an issue, I think?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.