Techniques for providing proprietary tile-based and/or non-tile-based graphics processing to an open-source infrastructure modeling platform
In example embodiments, a proprietary implementation of tile-based and/or non-tile-based graphics processing is provided at run-time as a binary for use in an open-source infrastructure modeling platform. An open-source repository from which the infrastructure modeling platform is built includes a backend module and definitions of the interface of a visualization module from a private repository that implements the tile-based and/or non-tile-based processing. The open-source repository lacks code for the underlying implementation of the visualization module. The implementation of the visualization module is instead maintained in a private repository and built therefrom. In operation, the backend module calls an exposed function of a DLL that returns a pointer to a binary implementation of the visualization module. When graphics of an infrastructure model are required, the backend module utilizes the defined interface with the pointer to request tile-based and/or non-tile-based processing from the visualization module.
1 . A method for rendering an infrastructure model within an open-source infrastructure modeling platform, comprising:
calling, by a backend module of an open-source infrastructure modeling platform executing on a client device or one or more cloud computing devices, a function of a dynamically loaded module (DLL) to obtain a pointer to an implementation of a visualization module built from a private repository that implements tile-based graphics processing;
determining a need to render graphics for at least a portion of the infrastructure model, wherein the determining the need to render graphics comprises:
receiving, by the backend module from the frontend module, an initial request for the description of a tile tree to which a tile belongs,
calling, by the backend module, the visualization module to obtain the description of the tile tree,
receiving, by the backend module from the frontend module, a subsequent request to generate graphics for a tile in the tile tree;
utilizing, by the backend module, an interface of the visualization module with the pointer to request tile-based processing of graphics by the implementation, wherein the request includes an identification of a set of elements that intersect a volume of the tile; and
receiving processed graphics produced by the visualization module at a frontend module of the open-source infrastructure modeling platform for display to a user.
2 . The method of claim 1 , wherein the graphics are received into a local cache at the backend module, and the providing the graphics to a frontend module further comprises:
enqueueing and returning status of the request for processing graphics;
upon completion of the request for processing graphics, providing an indication the graphics are in the local cache to the frontend module; and
fetching, by the backend module, the graphics for the tile from the local cache.
3 . The method of claim 1 , wherein the graphics are received into an external cache separate from the backend module, and the providing the graphics to a frontend module further comprises:
enqueueing and returning status of the request for processing graphics;
upon completion of the request for processing graphics, providing an indication the graphics are in the external cache to the frontend module; and
fetching, by the frontend module, the graphics for the tile from the external cache.
4 . The method of claim 1 , wherein the request for processing graphics requests non-tile-based processing and includes identification of a set of elements, or identification of a symbology and geometric primitives, and the determining the need to render graphics further comprises:
receiving, by the backend module from the frontend module, identification of the set of elements or identification of the symbology and geometric primitives.
5 . The method of claim 4 , wherein the graphics are received by the backend module and provided by the backend module to the frontend module.
6 . A method for rendering an infrastructure model within an open-source infrastructure modeling platform, comprising:
calling, by a backend module of an open-source infrastructure modeling platform executing on a client device or one or more cloud computing devices, a function of a dynamically loaded module (DLL) to obtain a pointer to an implementation of a visualization module built from a private repository that implements tile-based graphics processing and non-tile-based graphics processing;
determining a need to render graphics for at least a portion of the infrastructure model;
utilizing, by the backend module, an interface of the visualization module with the pointer to request tile-based and/or non-tile-based processing of graphics by the implementation, wherein the interface of the visualization module includes a primary interface for tile-based graphics processing and a supporting interface for non-tile-based graphics processing, and the request includes at least one of an identification of a set of elements that intersect a volume of a tile, identification of a set of elements, or an identification of a symbology and geometric primitives; and
receiving processed graphics produced by the visualization module at a frontend module of the open-source infrastructure modeling platform for display to a user.
7 . The method of claim 6 , wherein the primary interface includes one or more types selected from the group consisting of:
an Error type for an indication of kinds of errors that may occur during processing of a request by the visualization module;
a Tile Content type for storing the graphics;
a Pole State type for an indication of results/status of the request for processing graphics;
a Tile Content Source type for an indication of a method by which the frontend module may retrieve graphics returned by the visualization module;
a Tile Tree type for a description of a tile tree to which the tile belongs;
a Tile Tree Identifier type for information used to interpret the description of the tile tree in order to identify a particular tile tree; and
a Tile Content Identifier type for information used to describe the graphics to be produced from the tile within the tile tree.
8 . The method of claim 7 , wherein the primary interface includes one or more operations selected from the group consisting of:
a Get Current Version Format operation that provides a maximum version of graphics format understood by the visualization module;
a Set Use Tile Cache operation that enables or disables use of a local cache at the backend module;
a Get Tile Tree operation that obtains a current description of a tile tree;
a Purge Tile Tree operation that removes extant tile trees from memory;
a Pole Tile Content operation that returns results/status of the request for processing graphics;
a Get Tile Content operation that fetches graphics for a specific tile or produces graphics for the specific tile;
a Cancel Content Requests operation that cancels the request for processing graphics;
a Set Tracking Geometry operation that toggles tracking of changes to geometry contained within the infrastructure model; and
an Add Changes operation that updates state to record addition, deletion and/or modification of elements with the infrastructure model.
9 . The method of claim 7 , wherein the supporting interface includes one or more types selected from the group consisting of:
a Request type for description of source of geometry, a unique request ID and parameters specifying how the geometry is to be converted into graphics; and
a Results type for an object that resolves asynchronously to the graphics or an error.
10 . The method of claim 7 , wherein the supporting interface includes one or more operations selected from the group consisting of:
an Enqueue operation that adds the request for processing graphics to a queue awaiting processing;
a Cancel operation that cancels the request for processing graphics; and
a Terminate operation that cancels all requests in the queue.
11 . The method of claim 6 , wherein the request for processing graphics requests tile-based processing and includes identification of a set of elements that intersect a volume of a tile, and the determining the need to render graphics further comprises:
receiving, by the backend module from the frontend module, an initial request for the description of a tile tree to which the tile belongs;
calling, by the backend module, the visualization module to obtain the description of the tile tree; and
receiving, by the backend module from the frontend module, a subsequent request to generate graphics for a tile in the tile tree.
12 . The method of claim 11 , wherein the graphics are received into a local cache at the backend module, and the providing the graphics to a frontend module further comprises:
enqueueing and returning status of the request for processing graphics;
upon completion of the request for processing graphics, providing an indication the graphics are in the local cache to the frontend module; and
fetching, by the backend module, the graphics for the tile from the local cache.
13 . The method of claim 11 , wherein the graphics are received into an external cache separate from the backend module, and the providing the graphics to a frontend module further comprises:
enqueueing and returning status of the request for processing graphics;
upon completion of the request for processing graphics, providing an indication the graphics are in the external cache to the frontend module; and
fetching, by the frontend module, the graphics for the tile from the external cache.
14 . The method of claim 6 , wherein the request for processing graphics requests non-tile-based processing and includes identification of a set of elements, or identification of a symbology and geometric primitives, and the determining the need to render graphics further comprises:
receiving, by the backend module from the frontend module, identification of the set of elements or identification of the symbology and geometric primitives.
15 . A non-transitory electronic device readable medium having instructions stored thereon for an open-source infrastructure modeling platform, wherein the instructions when executed by one or more processors of one or more computing devices are operable to:
call a function to obtain a pointer to an implementation of a visualization module built from a private repository that implements tile-based graphics processing;
determine a need to render graphics for at least a portion of the infrastructure model by:
receiving an initial request for the description of a tile tree to which a tile belongs,
calling the visualization module to obtain the description of the tile tree, and
receiving a subsequent request to generate graphics for the tile in the tile tree;
utilize an interface of a visualization module with the pointer to request tile-based processing of graphics by the implementation, wherein the request includes at least an identification of a set of elements that intersect a volume of the tile; and
receive graphics for display.
16 . The non-transitory electronic device readable medium of claim 15 , wherein the graphics are received into a local cache, and the instructions when executed are further operable to:
enqueue and return status of the request for processing graphics;
upon completion of the request for processing graphics, provide an indication the graphics are in the local cache; and
fetch the graphics for the tile from the local cache.
17 . The non-transitory electronic device readable medium of claim 15 , wherein the graphics are received into an external cache, and the instructions when executed are further operable to:
enqueue and return status of the request for processing graphics;
upon completion of the request for processing graphics, provide an indication the graphics are in the external cache; and
fetch the graphics for the tile from the external cache.
18 . The non-transitory electronic device readable medium of claim 15 , wherein the implementation of the visualization module also implements non-tile-based graphics processing of graphics, and the instructions when executed are further operable to:
utilize the interface of the visualization module with the pointer to request non-tile-based processing of graphics by the implementation, wherein the request for non-tile-based processing of graphics includes identification of a set of elements, or identification of a symbology and geometric primitives; and
receive additional graphics for display.
19 . The non-transitory electronic device readable medium of claim 15 , wherein the interface of the visualization module includes a primary interface for tile-based graphics processing, and the primary interface includes one or more types selected from the group consisting of:
an Error type for indication of kinds of errors that may occur during processing of a request by the visualization module;
a Tile Content type for storing the graphics;
a Pole State type for an indication of status of the request for processing graphics;
a Tile Content Source type for an indication of a method by which the frontend module may retrieve graphics returned by the visualization module;
a Tile Tree type for a description of a tile tree to which the tile belongs;
a Tile Tree Identifier type for information used to interpret the description of the tile tree in order to identify a particular tile tree; and
a Tile Content Identifier type for information used to describe the graphics to be produced from the tile within the tile tree.
20 . The non-transitory electronic device readable medium of claim 15 , wherein the interface of the visualization module includes a primary interface for tile-based graphics processing, and the primary interface includes one or more operations selected from the group consisting of:
a Get Current Version Format operation that provides a maximum version of graphics format understood by the visualization module;
a Set Use Tile Cache operation that enables or disables use of a local cache at the backend module;
a Get Tile Tree operation that obtains a current description of a tile tree;
a Purge Tile Tree operation that removes extant tile trees from memory;
a Pole Tile Content operation that returns status of the request for processing graphics;
a Get Tile Content operation that fetches graphics for a specific tile from or produces graphics for the specific tile;
a Cancel Content Requests operation that cancels the request for processing graphics;
a Set Tracking Geometry operation that toggles tracking of changes to geometry contained within the infrastructure model; and
an Add Changes operation that updates state to record addition, deletion and/or modification of elements with the infrastructure model.
21 . The non-transitory electronic device readable medium of claim 18 , wherein the interface of the visualization module includes a supporting interface for non-tile-based graphics processing, and the supporting interface includes one or more types selected from the group consisting of:
a Request type for description of source of geometry, a unique request ID and parameters specifying how the geometry is to be converted into graphics; and
a Results type for an object that resolves asynchronously to the graphics or an error.
22 . The non-transitory electronic device readable medium of claim 18 , wherein the interface of the visualization module includes a supporting interface for non-tile-based graphics processing, and the supporting interface includes one or more operations selected from the group consisting of:
an Enqueue operation that adds the request for processing graphics to a queue awaiting processing;
a Cancel operation that cancels the request for processing graphics; and
a Terminate operation that cancels all requests in the queue.