Use rougher polygon cost calculation based on closest border or obstacle
Differentiate between x and y resolution for polygon coordinate positions -> fewer candidate positions
Merge pull request #640 from mhugent/labeling_performance

Labeling performance