An agency may have a need to create a URL that directly launches the Lucity Web Map to display an asset, without having to navigate through the Lucity Web interface. For example, a Sewer department supervisor might want to embed a link to a mapped sewer line into a Crystal report.
Use the following URL as a template for jumping directly into the Lucity Web Map to view a feature:
http://[myserver]/LucityWeb/Public/Routing.aspx?RouteTarget=Internal&RouteSubTarget=MapWindows&RouteAction=ShowInMap&RouteParam1=[moduleid]&RouteParam2=0&RouteParam3=[{id:autoNumber}]
Three parts of the template must be specified:
[myserver] |
The name of the server that hosts Lucity Web. |
[moduleid] |
The identifying number of the Module in which the Asset is stored. To zoom to a specific Sewer Pipe, the module ID should be that of the Sewer Pipes module. To zoom to a Work Order, this value should be the module ID for the Work Order module. All module IDs are stored in the GBAUser.dbo.Modules table as KeyIDs. The module ID is used in the WKWOASSET table to specify which Module the Asset comes from. |
[{id:autoNumber}] |
This is a json list of feature IDs to select in the Web Map. This ID represents the module's database record number. For the GBASewer.dbo.SWNET table, the ID would be NT_ID.
|
Examples
The following URL will open the Web Map and select the sewer pipe with the ID 33293.
http://EXAMPLESERVER/LucityWeb/Public/Routing.aspx?RouteTarget=Internal&RouteSubTarget=MapWindows&RouteAction=ShowInMap&RouteParam1=2&RouteParam2=0&RouteParam3=[{id:33293}]
This URL will open the Web Map without selecting a feature:
http://EXAMPLESERVER/LucityWeb/Public/Routing.aspx?RouteTarget=Internal&RouteSubTarget=MapWindows&RouteAction=ShowInMap&RouteParam1=0&RouteParam2=0&RouteParam3=[]