Abstract: Techniques are described for efficient label insertion and collision handling. A bounding geometry for a label to be graphically displayed on a display screen as part of an electronic map is determined, wherein the bounding geometry comprises a circle. The bounding geometry is inserted into a grid index, wherein the grid index represents a viewport of the electronic map. Disjoint regions of the grid index intersected by the bounding geometry are identified, wherein each disjoint region represents a different portion of the viewport. For each intersected disjoint region, it is identified whether there is at least one collision between the bounding geometry and one or more existing bounding geometries in the disjoint region; and responsive to identifying whether there is at least one collision in the intersected disjoint region, a target opacity of the label is set.

Abstract: Techniques are described for efficient duplicate label handling. A vector tile is added to a render tree of an electronic map, the vector tile comprising a first set of labels. A vector tile family of the vector tile is identified, each vector tile of the family comprising a second set of labels. For each label of the first set, for each vector tile in the vector tile family, second labels from the second set are identified, and for each identified label, coordinates of the label of the first set are compared to coordinates of the identified label to determine whether the coordinates are within a threshold similarity of each other. Responsive to the determination, the label of the first set of labels is associated with an identifier with which the identified label is associated.

Abstract: Techniques are described for efficient duplicate label handling. A vector tile is added to a render tree of an electronic map, the vector tile comprising a first set of labels. A vector tile family of the vector tile is identified, each vector tile of the family comprising a second set of labels. For each label of the first set, for each vector tile in the vector tile family, second labels from the second set are identified, and for each identified label, coordinates of the label of the first set are compared to coordinates of the identified label to determine whether the coordinates are within a threshold similarity of each other. Responsive to the determination, the label of the first set of labels is associated with an identifier with which the identified label is associated.

Abstract: Techniques are described for efficient label insertion and collision handling. A bounding geometry for a label to be graphically displayed on a display screen as part of an electronic map is determined, wherein the bounding geometry comprises a circle. The bounding geometry is inserted into a grid index, wherein the grid index represents a viewport of the electronic map. Disjoint regions of the grid index intersected by the bounding geometry are identified, wherein each disjoint region represents a different portion of the viewport. For each intersected disjoint region, it is identified whether there is at least one collision between the bounding geometry and one or more existing bounding geometries in the disjoint region; and responsive to identifying whether there is at least one collision in the intersected disjoint region, a target opacity of the label is set.

Abstract: Techniques are described for efficient duplicate label handling. A vector tile is added to a render tree of an electronic map, the vector tile comprising a first set of labels. A vector tile family of the vector tile is identified, each vector tile of the family comprising a second set of labels. For each label of the first set, for each vector tile in the vector tile family, second labels from the second set are identified, and for each identified label, coordinates of the label of the first set are compared to coordinates of the identified label to determine whether the coordinates are within a threshold similarity of each other. Responsive to the determination, the label of the first set of labels is associated with an identifier with which the identified label is associated.

Abstract: Techniques are described for efficient duplicate label handling. A vector tile is added to a render tree of an electronic map, the vector tile comprising a first set of labels. A vector tile family of the vector tile is identified, each vector tile of the family comprising a second set of labels. For each label of the first set, for each vector tile in the vector tile family, second labels from the second set are identified, and for each identified label, coordinates of the label of the first set are compared to coordinates of the identified label to determine whether the coordinates are within a threshold similarity of each other. Responsive to the determination, the label of the first set of labels is associated with an identifier with which the identified label is associated.

Abstract: Techniques are described for efficient label insertion and collision handling. A bounding geometry for a label to be graphically displayed on a display screen as part of an electronic map is determined, wherein the bounding geometry comprises a circle. The bounding geometry is inserted into a grid index, wherein the grid index represents a viewport of the electronic map. Disjoint regions of the grid index intersected by the bounding geometry are identified, wherein each disjoint region represents a different portion of the viewport. For each intersected disjoint region, it is identified whether there is at least one collision between the bounding geometry and one or more existing bounding geometries in the disjoint region; and responsive to identifying whether there is at least one collision in the intersected disjoint region, a target opacity of the label is set.

Abstract: A Policy- and Relevance-based User Interface (UI) for an enterprise suite Console provides a Console Operator access to information about systems on a network under management. By means of such UI, a user experience is dynamically constructed within product domains particular to the system under management using content elements that flow from content sites into the user environment, populating user interface and driving the Operator experience. Specifications distributed with the content determine how the local Console UI organizes and presents information. The UI is further determined by each Console operator's content access rights. The UI allows for re-flowing the Console UI without reinstalling or updating the Console application, seamlessly integrating new content in to the UI and targeting language to specific working areas.

Abstract: A Policy- and Relevance-based User Interface (UI) for an enterprise suite Console provides a Console Operator access to information about systems on a network under management. By means of such UI, a user experience is dynamically constructed within product domains particular to the system under management using content elements that flow from content sites into the user environment, populating user interface and driving the Operator experience. Specifications distributed with the content determine how the local Console UI organizes and presents information. The UI is further determined by each Console operator's content access rights. The UI allows for re-flowing the Console UI without reinstalling or updating the Console application, seamlessly integrating new content in to the UI and targeting language to specific working areas.

Abstract: A Policy- and Relevance-based User Interface (UI) for an enterprise suite Console provides a Console Operator access to information about systems on a network under management. By means of such UI, a user experience is dynamically constructed within product domains particular to the system under management using content elements that flow from content sites into the user environment, populating user interface and driving the Operator experience. Specifications distributed with the content determine how the local Console UI organizes and presents information. The UI is further determined by each Console operator's content access rights. The UI allows for re-flowing the Console UI without reinstalling or updating the Console application, seamlessly integrating new content in to the UI and targeting language to specific working areas.

Abstract: A policy-driven communication and management infrastructure may include components such as Agent, Server and Console, policy messages, and Relays to deliver security and system management to networked devices. An Agent resides on a Client, acting as a universal policy engine for delivering multiple management services. Relays, Clients additionally configured to each behave as though they were a root Server, Relaying information to and from other Clients, permit Clients to interact with the root Server through the Relay, enabling information exchange between Client and Server. Such information exchange allows Clients to gather information, such as new policy messages, from the Server, to pass status messages to the Server and to register their network address so that they can be readily located. Automatic Relay selection enables Clients and Relays to select their own parent Relays, thus allowing Clients and Relays to discover new routing paths through the network without administrator input.