I haven't used the MapTextLabeller all that much, but I have used the same text placement engine in another software package rather extensively.

If you take the unfiltered port of the GeometryFilter and enter that in to the MapTextLabeller as well you can use those features as obstacles. That means that the labels will not overlap them.

And then configure the MapTextLabeller like this:

Another thing you may want to try is allowing font size reduction in the Etiquette rule, this means that if it can't place the label it will reduce the font size by half a point and try again, up to a maximum number of steps you specify (speaking from experience: make sure the number of steps you specify is not so great you can end up with negative font sizes... also the behaviour for labelling points becomes a bit iffy when your labels are less than 1 pt in size)

It is important to keep in mind though that while the MapTextLabeller does a very good job there are certainly situations where it will not be able to label everything and I'm afraid the screenshot you posted is one such situation: a lot of points close to eachother with a lot of obstacles too.

---

Thanks for your answer.

However, I don't want to reduce them (anyway this option doesnt work !
), I just want to moove them on the other side the network for example.

---

Thanks for your answer.

However, I don't want to reduce them (anyway this option doesnt work !
), I just want to moove them on the other side the network for example.

The point is that the MapTextLabeller may not be able to find a solution where all labels are placed, they're not interfering with eachother and they're not overlapping any of the other features. Sometimes it's simply not possible.

 

 

By setting more lenient rules, specifically the font reduction and leader lines, you may improve the results.

 

 

---

Thanks for your answer.

However, I don't want to reduce them (anyway this option doesnt work !
), I just want to moove them on the other side the network for example.

But here we could see an overlapping...I don't undestand what you said...Sorry

 

 

---

But here we could see an overlapping...I don't undestand what you said...Sorry

 

 

First of all: are you sure that's the output of the MapTextLabeller you're viewing and not the original text? When I tried it it did manage to place some, but not all, labels correctly. There were no overlaps though.

 

 

What the MapTextLabeller does is it tries to label the features you enter, within the rules you specify and keeping in mind the obstacles you enter. Depending on those rules and your source data this may or may not result in a good solution.

 

 

---

Ok.

To sum up, the first picture is the init stage :

You can see the labels superpositions.

The second picture is the maptextLabeller result :

We can see easilly the result...Some points are disappeared.

My question is why the points disappeared while I thought they would be relocated? And in a second time why the police reduction doesnt work too ?

Thanks again

---

Ok.

To sum up, the first picture is the init stage :

You can see the labels superpositions.

The second picture is the maptextLabeller result :

We can see easilly the result...Some points are disappeared.

My question is why the points disappeared while I thought they would be relocated? And in a second time why the police reduction doesnt work too ?

Thanks again

Aha, that second image didn't show up earlier.

 

 

The points are "disappearing" because with the rules you have set within the MapTextLabeller it could not find a good solution for them.

 

 

They're actually not disappearing. Per labelling rule the MapTextLabeller has 2 output ports, one for the text (...TXT) and one for the features that could not be labelled (...UNL). So if you check that port you can still see those features.

 

 

Note that the MapTextLabeller will not relocate features! If you want to do that, and it may be that that will increase your chance of succes, you can try the Displacer before the MapTextLabeller.

 

 

It is my experience that to get a good result out of the labelling engine you'll need to experiment with the rules. It hardly ever works right the first time. And, as I've said earlier, there may not be a solution at all.

 

 

So that is my advice: try the Displacer, take a look at the MapTextLabeller rules, try and change them and then run the workspace again.

 

 

---

I'm in the same situation as @njbhvg but I don't have MapTextLabeller. This transformer isn't free.

Any idea how I could clean my labels without buying it?

---