This is the workflow for copying the geometry and (optionally) attributes from a ‘parent’ feature to ‘child’ feature.
Select the parent polygon using the edit tool (small pencil) or the identify tool
Select the copy features button
Select the desired 'Target Feature Layer' from the drop-down list.
Uncheck fields that should not be copied over to the child (the default is to have all fields with matching names copy attributes from parent to child) and copy
Point features can be copied with an offset distance and direction (available at MobileMap release 4.3.61). To apply an offset, from the copy feature window for a point feature:
Check the box next to Apply Offset
Enter a Distance and Degrees for the offset
*Please note, in ability to copy Plot features can be turned on or off by the Enable Copying of Plots setting found in Settings > MobileMap Cruise > Plots. If this setting is turned off, copying of plots is disabled.
Selecting Coincident Geometries
Because copying facilitates the creation of coincident geometries, MobileMap has the ability to choose a specific feature when multiple are selected during query or edit operations.
Use the edit tool to select the desired feature type (small pencil)
Select the desired feature on the map
If the feature is coincident with another feature of the same type, MobileMap will notify the user of how many overlapping features were selected and display the attributes of all features in a window. Pan to the right to see each feature’s attributes and select the desired one.
Notes on Symbology
Features of different types that are likely to overlap should have symbology that makes it as easy as possible to distinguish them. To accomplish this, it is recommended that ‘base’ features (those that should appear below others) be given a higher line weight than other feature types. We typically use a line width of 3 or 4 for a base feature and then change the color and line width for other features that will be drawn on top of the base feature(s). Dashed lines can also be used for higher level features. Below is an example of symbology that could work well for multiple polygons in a feature service that will likely overlap on the map.
In this symbology it is assumed the Location Polygon is the feature that should be drawn below all other polygon types (with the exception of generic polygons).