Implementation of sparseness (generalization) of settlements signatures

When signatures are placed automatically, the position for the created signatures is selected for the base scale of the map. Therefore, at the base scale, all signatures are displayed correctly, «without interfering» with other signatures. However, when zooming out on the map, the image of signatures may overlap with other signatures.

The rules for performing generalization are written into the general import parameters file .osm2map.

In a line beginning with the character sequence _OSMGEN| the key of the object-title to be processed is placed.

The object keys are listed in descending order of their importance.

For example:

//--------------------------------------------------

//Generalization table

//--------------------------------------------------

_OSMGEN|t_city_2

_OSMGEN|t_city_3

_OSMGEN|t_city_4

_OSMGEN|t_admin-6

_OSMGEN|488-100-T

During the sparseness (generalization) procedure, signatures are not removed from the map, but by setting the hierarchy of importance of signatures by setting the upper visibility limit, in each of the scales only those signatures are visible that «do not interfere» with more important signatures and signatures of a similar rank, processed previously.

During processing, the object is set to the maximum possible («until it does not interfere with others») upper visibility limit, but not higher than that specified in the classifier.

If necessary, signatures can be generated on a separate map or added to the main one.

There is a possibility of generating «simplified» signatures.