Tag Info

New answers tagged

0

a possible solution : export from the composer the map in a raster format, with only the labels being activated (everything else being hidden, including the line vector) add the raster from the composer in your view, assign a transparent value (likely white) Place this raster layer below the vector ... The problem may be that your raster file will ...


0

Not sure if you have already tried this but you can edit the placement of your labels: Layer properties > Labels > Placement Select Offset from centroid and choose the whole polygon and the centre quadrant. Unless you also edit the Scale-based visibility in the Rendering section (Layer properties > Labels > Rendering), the labels will constantly appear ...


0

I often have the same problem and I mostly solve it with following vendor options <VendorOption name="goodnessOfFit">0.1</VendorOption> <VendorOption name="conflictResolution">false</VendorOption> <VendorOption name="spaceAround">-1</VendorOption> I hope it helps.


0

By default GeoServer tries very hard to not overlap your labels (as this generally what the user wants). You can change this behaviour by setting the vendor option conflictResoloution to false. <VendorOption name="conflictResolution">false</VendorOption>


4

You can use 'Weighting labels and features' which is different to Priority in Maplex "This weight is to be used only when there is a conflict, that is, an overlap between a label and a feature." Forces ArcMap to consider alternate positions for labels. Do this by increasing feature weight to a higher number. ...


0

The only way I know to do this would be union or intersect all three of your layers to one. If you have an Advanced license this could be done in one step, otherwise you are limited to two inputs at a time. This should create a single layer that looks like the district polygons, but each polygon would have a country and division attribute. The problem is ...


2

This was determined to be the issue to this problem. It will be marked as the answer soon. When using format tags make sure they close from inside out. Thanks to @kenbuja for clarifying that. "<bol><clr green='255'>"+lab4+"</clr></bol>" NOT "<bol><clr green='255'>"+lab4+"</bol></clr>"


0

Try using the ampersand as you suggested and use vbcrlf instead of \n. I don't think \n works "" + [PARCEL] & vbcrlf & "TEXT" & "" something like this


3

I think you might be somewhat along the right lines, but, what about something more along the lines of: lab1 = line's value lab2 = line's value ... if line 1 condition >= 90 lab1 = bold and green + lab1 + end bold and green if line 2 condition >= 90 lab2 = bold and green + lab2 + end bold and green ... label = bold and underline + header ...


2

You have to expand the default.style of osm2pgsql to import the local name as well. The file is a simple text file, which you can edit with any text editor. You will find a line node,way name text linear inside. This will import only the international readable name. For local names, add node,way name:ja text linear ...


2

You need to remove the trailing colon on the last line. return myText: should be return myText I don't see anything else that jumps out, but that's definitely the cause of the current error you're seeing.


1

There is an existing ArcGIS Idea titled Circular callout backgrounds to: Add circular text callout backgrounds in addition to the default rectangular box callout backgrounds. If you have not already done so, I recommend that you add your vote to that.


2

This is not possible in the current release of ArcGIS Online. You can add multiple fields to the label, but they will be drawn right to each other. You can of course add custom text by typing it into the text field, for instance.: ID:{OBJECTID} // NAME:{NAME}


0

I'm guessing the parser was not changed to python, '\n' does work to force new lines within python label expressions.


5

Right click your feature class and choose Properties... Browse to the Labels tab. "Label features in this layer" should already be checked. If it isn't, check it. Choose your voting block field in the "Label Field" Text string box.


2

Create multiple annotation classes for each scale you are using. I did that for the maps in this publication and it worked out pretty well.


1

using maplex is the only fix for this I have found. since these are polygons (points work much easier) the workaround I have found is to... there are several maplex settings that will help like eroded center always within polygon. Which is in the anchor setting. interior feature weight. then choosing place at fixed postion and setting the internal ...


0

More of a Hack, but I would simply add a cartridge return after the field for parcel service, and a cartridge return before the the field future land use, in there respective label expression. Here an example in Python For Parcel Service [parcel_num] + '\n' For Future Land Use '\n' + [future_land_use_num] This should offset them one on top of the ...



Top 50 recent answers are included