How do I configure my Saved Views tool?

The Open Saved View tool opens a map document in the mobile application.  This tool can be found in the toolbar in Mapbook:

Saved Views are selected in the Open Saved View dialog.

How to use Saved Views buttons:

1) Click on the ‘Open Saved View’ tool.  The Open Saved View dialog opens, displaying available maps.  The first saved view in the list is automatically selected.

2) To select a different saved view in the list, tap/click the Saved View or the ‘Move Up/Move Down’ tools to move the selection cursor in the list.

3) To open the selected Saved View in the map display, tap/click the ‘Open Document’ tool or double-tap/click the Saved View in the list.

Configuring Saved Views:

For SavedViews, verify that you have this tag enabled in the <Paths> section of your GoSyncMobileConfiguration.xml:

<SavedViewXMLPath>$data\MobileConfiguration\SavedViews.xml</SavedViewXMLPath>

For Saved Views, there are two options for configuration.  The 1st option allows you to pick from a list of predefined MXD documents, as shown in the above Saved Views UI.  This method is ideal for user’s to quickly access commonly used map views.  If this is the preferred method, the below configuration can be used in the GoSyncMobileConfiguration.xml:

<!– Saved Views tool, replaces Open File if used –>

<Tool name=”CommandNewFile_NewFile”>

<caption>Open File</caption>

<category>Command</category>

<image>Open</image>

<image_large>Open_large</image_large>

<style>image</style>

<tag>ControlsOpenDocCommand2</tag>

<Assembly>Tadpole.GoSync.Mapbook.SavedViews.dll</Assembly>

<TypeName>Tadpole.GoSync.Mapbook.SavedViews.OpenSavedView</TypeName>

</Tool>

The second option allows you to browse to a specific MXD versus using the Saved Views window.  This is done by commenting out the Saved Views tag and uncommenting out the Open File tool tags also contained in the GoSyncMobileConfiguration.xml:

<!– Open File tool, replaces Saved Views if used –>

<Tool name=”CommandNewFile_NewFile”>

<caption>Open File</caption>

<category>Command</category>

<image>Open</image>

<image_large>Open_large</image_large>

<style>image</style>

<tag>ControlsOpenDocCommand</tag>

<progID>esriControlToolsGeneric.ControlsOpenDocCommand</progID>

</Tool>

Posted in Configuration, GO! Sync, Mobile GIS | Tagged , | Leave a comment

How do I change the color of my GPS arrow?

If your field crew is requesting to change the color of your GPS arrow, this can be done by:

Locating your GoSyncMobileConfiguration.xml file – this is found in your $serverdata\MobileDownloads\Default\MobileConfiguration folder

Inserting the following tags in your <GPS> section:

<GpsColor>

<GpsColorRed>255</GpsColorRed>

<GpsColorGreen></GpsColorGreen>

<GpsColorBlue></GpsColorBlue>

</GpsColor>

The above set of tags renders a red arrow, but you can change the color to be any combination of Red, Green & Blue.

After you have color values specified in the above GPS tags, save your GoSyncMobileConfiguration.xml and run a sync from your client machines.  The next time your user’s start GPS in Mapbook, they will be able to see the new color.

Posted in Configuration, GO! Sync, Mobile GIS | Tagged , | Leave a comment

Our IT department installed GO! Sync on a client machine and licensed it but now I can’t run a sync.

  • This happens occasionally when IT logins in with Admin privileges to install a machine, then does not set them as below for all Users.
  • Verify permissions have been set for the $data folder:
  • $data – Read / Write / Modify for all Users (typically User group), not just Admins

  • Verify permissions have been set for the $app folder:
  • $app – Read / Write / Modify / Execute for all Users (typically User group), not just Admins

Posted in Uncategorized | Leave a comment

What kind of geodatabases are supported as connection files in InspectServerConfiguration.xml?

The InspectServerConfiguration.xml is the GO! Sync Server inspection configuration file used to process incoming inspections.  The key to this file are that inspection names have to match with what is being used in the InspectionClientConfiguration.xml, multiple connection files are supported.

Acceptable database types can be SDE ‘*.sde’ connection files, pGDB ‘*.mdb’ or fGDB ‘*.gdb’ databases.  SDE connection files should be located in the [ServerDataRoot]\ServerConfiguration\ConnectionFiles folder.

Posted in Configuration, GO! Sync, Inspections | Leave a comment

Alternate display fields through identify window

In Mapbook, if you want to display different fields for your user’s when they identify particular features in the field, this can be accomplished by changing the “Primary Display Field” type in ArcMap for the MXD being used by your project.

The example below shows the GLOBALID field on the left hand side being displayed as the current default value.  This window is produced by clicking on the “Identify” button in Mapbook.  

To perform a change to the field shown in Mapbook, open your current MXD and locate the same feature class that you identified in Mapbook.  Right click on that feature and choose properties.  Locate the “Fields” tab and change the “Primary Display Field” to the field you want to display.  We are going to change this field to “DESCRIPTION”:

From here, save your changes and run a sync from your client machine.  This time, clicking on Identify for the same feature yields a different result:

The Street CL feature class used for this example contained domain values with a “Residential” code and description for that particular street being identified as shown below:

Posted in GIS, GO! Sync | Tagged , | Leave a comment

Stopping FTP Service at log on – Edits to Tadpole.GoSync.FTP.Client.UI.exe.config

If you want to stop the GO! Sync FTP Service when clients log on, you would need to edit a tag on the GO! Sync Server.  This tag is located in the Tadpole.GoSync.FTP.Client.UI.exe.config file and needs to have a value of “True”: <add key=”StopServiceAtLogon” value=”True“/>

This file is located in the $serverdata\MobileDownloads\Default\AppUpdates\FTP, where $serverdata represents the drive where GO! Sync application was installed.

Once the above tag has been changed to “True”, on the GO! Sync Server you will have to recreate your Manifest.xml file.  This can be done by restarting the Tadpole.GoSync.AppStarter.CreateManifest.exe located in the $app\GO! Sync\Tools\Bin folder.

 

 

 

After the Manifest.xml has been recreated on the Server, sync from your client machine that you want to stop FTP Service at log on, then reboot to restart both GO! Sync Services.

Posted in Configuration, GO! Sync, TC Technology | Tagged , | Leave a comment

Setting the proper permissions for client machines

If ftp is running fine to your client machines but the data on the client machines are not being updated from what is on the server, then this could be due to:

1) The client machines may not have sufficient privileges to the $data folder.  To ensure the proper privileges are set correctly on client machines check that:

$data, normally C:\GISData has Read / Write / Modify for all Users (typically user group), not just Admin group

2) If you notice that Mapbook is not running the latest version, the $app folder also needs to have sufficient privileges.  To ensure the proper privileges are set correctly on client machines check that:

$app, normally C:\Program Files\GO! Sync has Read / Write / Modify / Execute for all Users (typically User group), not just Admin group.

To make the above changes, you will need to be logged in as an Administrator or have the proper Administrative rights to make these changes.  Your IT department may be required for assistance.

Posted in GO! Sync, TC Technology | Tagged , | Leave a comment

How to configure Sticky Values

One valuable tool Mapbook user’s can take advantage of is the use of Sticky Values.  With this tool, you can limit the amount of data input for your user’s by copying the values from your previous inspection and maintaining those same values into your new inspection.  Once these new values are part of your new inspection, any field values can be edited and saved.

Some things to note:

  • Sticky value field names visible in Mapbook will match the alias names assigned within your ArcMap MXD document.
  • User’s must click the Sticky Value tool prior to enabling Sticky Values
  • User’s must click on the Sticky Value button prior to creating a new inspection for the previous values to be visible
  • Once an inspection has been made with a Sticky Value, the user can easily create another inspection of the same type anywhere on the map
  • Toggling off the Sticky Values button removes any saved data from the previous Sticky Value inspection

Configuration – InspectionClientConfiguration.xml

  • To configure Sticky Values insert the Sticky Value extension tags and dll file within the ex.tensions portion of the InspectionClientConfiguration.xml (located near the bottom of the InspectionClientConfiguration.xml file).

<Extension>

<TypeName>TCTechnology.GoSync.Inspect.StickyValues.InspectionStickyValues,TCTechnology.GoSync.Inspect.StickyValues.dll</TypeName><ConfigurationInformation>$data\MobileConfiguration\StickyValuesInspectConfiguration.xml</ConfigurationInformation>

</Extension>

Configuration – StickyValueInspectConfiguration.xml

Verify that the StickyValueInspectConfiguration.xml file is located within your MobileConfiguration folder that is located in your $serverdata root folder.

Below is an example of what the StickyValueInspectConfiguration.xml should contain.  It should be noted that for each inspection type that you want to assign Sticky Values ensure that your inspection name matches your current inspections as specified in your InspectionClientConfiguration.xml.  Also, for any of the specific fields you want to enable a Sticky Value, ensure that these fields are noted within your  <FieldCopies></FieldCopies> tags as seen below.

<StickyValueInspectConfiguration xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”http://tctechnology.com/schemas/2008/Inspect/StickyValuesInspectConfiguration.xsd”>

<StickyValueInspections>

<!– Inspect –>

<StickyValueInspection InspectionName=”Light Inspect – Mast Arm”>

<!–Path to the XML to write on the saveing of values–>

<XmlPath>$data\UserData\Light Inspect – Mast Arm.xml</XmlPath>

<FieldCopies>

<FieldCopy from=”PAL” to=”PAL”/>

<FieldCopy from=”METERED” to=”METERED”/>

<FieldCopy from=”FEED” to=”FEED”/>

<FieldCopy from=”WI_FI” to=”WI_FI”/>

<FieldCopy from=”VOLTAGE” to=”VOLTAGE”/>

<FieldCopy from=”WATTAGE” to=”WATTAGE”/>

</FieldCopies>

</StickyValueInspection>

</StickyValueInspections>

</StickyValueInspectConfiguration>

After you create a Sticky Value, an XML is automatically created in the $data\UserData folder.  The Sticky Inspection will assign itself the current inspection name.

Posted in Configuration, GO! Sync, Inspections | Tagged | Leave a comment

Default Map Tips vs MultiLineMapTips

Default Map tips that you see in Mapbook appear just as they would if you have map tips also enabled in your MXD document in ArcMap.  Map tips displaying this way are controlled by the checkbox below.  This field can be changed to whatever primary field you choose, also in the screen shot below.  In this example the primary field is set to display DisplayName.  The big limitation here is only 1 field can be displayed without having to create a custom script to see multiple fields.

Alternatively, MultiLineMapTips can be displayed per feature that will display label information without having you to hover over a particular feature, however you do have to click the MultiLineMapTip tool and then on your feature to see your label.

Multi Line Map tips configuration

Needed:

MultilineMapTip.xml

MultilineMapTip.xsd

MultilineMapTip xml path and button tags

Configuring MultilineMapTip.xml involves specifying the layer you want in between the <LayerName></LayerName> tags.  The layer name has to correctly match the layer name as it appears in the MXD under the table of contents, not how it appears when you navigate to the feature class in ArcCatalog.  Multiple lines are represented per field tag and specified between the following tags.  Concatenating fields on the same line requires you to change the tag for <Field Concat=”true”.  This way the first 2 fields are concatenated.  To achieve concatenation for 3 fields, values for the first 2 fields must be set to true.  The below example would read

Device Name, Driver

Capture Date

Here is the configuration typically found on MultiLineMapTips.xml

<Fields>
<Field Concat="true" Separator=", ">
<FieldName>DeviceName</FieldName>
</Field>
<Field Concat="true" Separator=", ">
<FieldName>Driver</FieldName>
</Field>
<Field Concat="false" Separator=", ">
<FieldName>CapturedDate</FieldName>
</Field>
</Fields>

I have tested against the above settings and discovered that some reserved words such as SHAPE or OBJECTID may pose problems and not display correctly for Map Tips.

No configuration is needed for the MultilineMapTip.xsd, however the MultilineMapTip xml path & button configuration should appear as shown below:

<MultiLineMapTipXMLPath>$data\MobileConfiguration\MultiLineMapTip.xml</MultiLineMapTipXMLPath>

<Tool name=”MapEngineTools_MultiLineMapTipTool”>

<caption>MapTip Tool</caption>

This functionality is available with your 9.3.72 release.  Please contact customer support at support@tctechnology.com for the latest version.

Posted in GO! Sync, Mobile GIS, TC Technology | Tagged , | Leave a comment

GO! Sync Mapbook Windows 7 64 bit compatibility?

We do support Windows 7 64 bit provided you are running a Mapbook version later than 9.2.69/9.3.69.  Version 9.3.72.X will work.  I have included additional information I was able to find from ESRI’s website, however, you may want to verify with ESRI for any updates:

Question:

Does ESRI support 64-bit processors with ArcGIS products?
Answer:

Support for 64-bit processors
ArcGIS on Windows is supported on 64-bit processors starting with ArcGIS 9.2 Service Pack 3 and higher.
At ArcGIS 9.2 Service Pack 3, the supported 64-bit Windows operating systems are Windows XP 64-bit and Windows 2003 Server 64-bit. Windows Vista 64-bit support begins at ArcGIS 9.2 Service Pack 4.

The above ArcGIS 9.2 Service Packs run as 32-bit applications on these 64-bit Windows platforms, taking advantage of some of the performance benefits of the 64-bit environment.

Support also includes the ArcGIS 9.2 Service Pack 3 or higher applications running on a 32-bit operating system, running on 64-bit hardware.

Posted in GO! Sync, TC Technology | Tagged , | Leave a comment