Latest Contributions by JonMorris

Hi David, What you need is key number labeling, which we have just added to Maplex for ArcGIS 10.1. The initial implementation places labels in a list near the features, with a key number on the feature, but in the future we would also like to allow the labels to be added to the legend instead of a list. ... View more

Hi Alexander, Maplex goes through a number of stages when placing labels, and label priorities have an influence in more than one place. First, lots of trial positions are generated, in priority order - higher priority layers will be tackled first - then later on the trial positions are scored according to how well they fit various criteria. When the best trial positions are chosen, Maplex looks for overlaps with other labels. In the case of a conflict (overlap), the label with the lower priority will be removed - the next best trial position will be used instead. So, Maplex does not ignore symbol levels, just that there are more factors in play. Label priorities are more of a preference than an absolute requirement. When you say the top-level labels are moved, are they unplaced, or just moved to a different position so other labels can also be placed? If you want your highest priority labels to always be placed in the same zone of the polygon, you could use the fixed position option. Otherwise, you may be best converting these layers to annotation first, then labelling the remaining layers. ... View more

Sorry, Katherine, our development cycle is too long for us to have made any progress on this yet. When I said I would add it to the future enhancement list, back in September, new development had finished for 10.1 and we were entering the stabilisation phase. Hopefully we can look at it when we start development on the next release, although at this stage I've no idea when that will be released. Or even what number it will be! ... View more

Hi Frederic, It's on the list! Hopefully we'll manage to get this in a future release. ... View more

No problem. Don't forget to mark the post as answered if you are happy 🙂 ... View more

Hi Paul, I don't know exactly how SLE determines if a label overlaps the polygon, but I think it is some kind of vector test (Maplex rasterises the label and the feature and looks for overlaps between the two). In any case, the test will fail if the label cannot be placed within the polygon. I don't know if this includes the boundary/casing, but it should be quite easy to find out by setting the boundary width to a large value and alter the font size until you have a label that fits. It won't be possible to tell the label engine to place your label, via a formula or otherwise. As possible workarounds, you will have to either allow the label to place outside or reduce the font size. What is the problem you have with Maplex? Is it licensing? Or is there a bug? ... View more

Hi Jeremy, Crashes are serious and should always be reported, so we can get to work on a fix. If you submit a support request to your local distributor or to ESRI Support Services an analyst such as myself will be happy to investigate the issue with you. Providing a sample of your data would be helpful, especially if you can narrow down the problem to a single layer or feature. http://support.esri.com/en/ ... View more

Would you like to share it with us? 🙂 For those that are interested, one way to label both ends of a polyline is to set up two label classes, and under 'Label Offset', set 'Position Label' to 'Along line from Start' in one label class and 'Along line from End' in the other. ... View more

Hi Matthew, You need to use the 'Fixed position within polygon' option (assuming you are not placing curved labels - it is only available for horizontal or straight). Set the center zone to priority 1, and all other zones to zero. Then labels will only place if the center of the polygon is within the visible extent. As you are labeling grid squares, this should work ok -  the label will go unplaced if the geometric center of the polygon is outside the polygon bounds (e.g. Florida). ... View more

Hi Frédéric, Boundary labeling is designed to place pairs of labels wherever two polygons are coincident, and spends most of its time trying to find these boundary pairs. Single-sided placement was an enhancement added to ensure a single label is still placed where there is no neighboring polygon. Remove duplicates will not work in the way you are trying to use it, as the label engine is looking for duplicates of each pair of polygon labels. The placement you are after is really a line placement style, so you will have to use the Polygon to Line GP tool (Data Management toolbox) to convert your boundaries into line features and label them using line placement rules. Alternatively, you could use offset curved polygon placement, although this can only place labels on the outside of each polygon. [ATTACH=CONFIG]11601[/ATTACH] ... View more

Hi Christi, If you are getting the "general label error", it is probably due to a bug with the software. If you submit a support request to your local distributor or to ESRI Support Services an analyst such as myself will be happy to investigate the issue with you. Providing a sample of your data would be helpful, especially if you can narrow down the problem to a single layer or feature. http://support.esri.com/en/ ... View more

Unfortunately we don't have that capability at the moment. I'll add it to the list of future enhancements though. Possible workarounds (not ideal, I know) include aligning labels to the graticule, rotating the dataframe and labelling horizontally, or generating points to use as label place markers. Sorry, I can't offer any better solutions at the moment. ... View more

This sounds like a problem with map series, exporting or your code, not Maplex, so this post is probably in the wrong forum. Having said that - maybe the / is being interpreted as an escape character. Try using // instead. The "Object variable or With block variable not set" error means you are trying to use an uninitialized variable, but without seeing your code, I can't help you any more. ... View more

Crashes are bad news and we need to be informed if you have experienced one. Thanks for sending in the crash dump - that will help us to get to the bottom of the problem. If you could submit a support request to your local distributor or to ESRI Support Services with a sample of your data, that would be even more help. That way we can try to reproduce the problem in ArcMap and get a better idea of what has gone wrong. Have you got the latest service pack? At the moment, 10 SP2 is the most recently released service pack. The mxd bloat issue could be caused by GP tool history. See this KB article. ... View more

This is a known issue that we have not been able to completely fix. What version of ArcGIS are you using? We made some improvements to leader lines at 10.0 and hope to resolve the issue in the near future. ... View more