Once the aliases are set up and imported into the geodatabase configuration, an agency must publish any maps that it wants to use. The Lucity Webmap and the Lucity Mobile application support both .mxd, and .msp map services. After the services are published, Lucity must be configured to use the services.
Fill out the Order field. (Map services are layered based on this field. A lower number is a lower layer. Zero is the bottom layer.)
Note:Lucity Mobile and Mobile Work Maps only query data out of the top-most layer. Therefore, make sure the layer that contains Lucity assets has the highest number in the Order field.
Check the Base Map? box if this layer is used as a base map.
Check the Tiled? box if this layer is a tiled service.
Fill out other fields as needed.
Click Save.
Click Test if the map service has Lucity features in it. Doing so will show a list of all of the feature classes that the map will recognize as being connected to Lucity.
After steps 1 and 2 have been completed for all map services, go to the Lucity Administration Tool, and navigate toSystem > Settings > GIS Web tab.
In the Operational Data Spatial Reference WKID field, fill in the Spatial Reference number. This topic was covered in step 1.h (for Arc 10 setup) or 1.g (for Arc 10.x).
The WKID that is used here must be the the WKID that the operational data is referenced against. Lucity uses this spatial reference to record x-y coordinates and any other spatial data.
In the URL for Geocoding Service... field, provide the URL for what will be the default geocoding service used by the web map or Lucity mobile app.
This URL can be found in the same way that it is found for map services in step 1. Be sure to include the rest/ before the word services in the URL.
It is highly suggested that agencies use a Geometry Service. If an agency has a geometry service, it should provide the URL in the URL for Geometry Service field. Be sure to include the rest/ before the word services in the URL.