English

Mapping and Charting Solutions 10.6.1 Patch 4 (Desktop | Server)

Summary

This is a general cumulative maintenance patch for the Mapping and Charting Solutions including; ArcGIS for Aviation (Desktop), ArcGIS for Maritime: Bathymetry (Desktop), ArcGIS for Maritime: Charting (Desktop), ArcGIS for Maritime: Server, Esri Defense Mapping for (Desktop, Server), and Esri Production Mapping for (Desktop, Server). Please download and install this patch at your earliest convenience.

Description

We recommend Mapping and Charting Solutions customers with the following solutions download and install this patch to ensure the highest quality experience.

  • ArcGIS for Aviation
  • ArcGIS for Maritime: Bathymetry
  • ArcGIS for Maritime: Charting
  • ArcGIS for Maritime: Server
  • Esri Defense Mapping
  • Esri Production Mapping
Note: This patch is cumulative of all previously released Patches and Hot Fixes for Mapping and Charting Solutions 10.6.1.


Installing

  1. Login with a Windows Administrator account.
  2. Select and download the Mapping and Charting Solutions file.
  3.   Checksum (Md5)
    Desktop MappingandCharting1061Patch4.msp e4a0a950d3995dcb389723a7eb005161
    Server MappingandChartingServer1061Patch4.msp ca7fc7defa2e6cd04555bcdb2d4c1b52
  4. Double-click the msp file to start the install process.
  5. When Setup starts, follow the instructions on your screen.

ArcGIS for Maritime: Server, additional installation instructions:


Maritime Chart Service (MCS) for Maritime: Server

  1. Login as a Server Manager by launching https://localhost:6443/arcgis/manager.
  2. Click Services.
  3. Stop the map service with Maritime Chart Service capabilities configured.
  4. Move the controlfiles folder from <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\maritimechartservice\controlfiles to a backup location.
  5. Copy the new controlfiles folder from <ArcGIS Server installation drive>\MaritimeServer\Server<version>\maritimechartservice to <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\maritimechartservice.
  6. If modifications were made to the old control files, they will need to be made to the new control files. The backup control files can be used to consolidate modifications with the new control files. For example, Coordinate systems and AutoCellUpdate settings.
  7. If the map service was configured to read S-63 encrypted datasets, copy the S-63 user-permit.txt file from the backup controlfiles folder to the new controlfiles folder.
  8. Delete the .senc files from <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\maritimechartservice\sencs. The .senc files must be rebuilt after upgrading. Deleting them will significantly increase creation performance.
  9. Repeat steps 1 through 8 for each map service with the Maritime Chart Service capabilities configured.
  10. Login as an administrator by launching https://localhost:6443/arcgis/admin.
  11. Click Uploads.
  12. Click Upload.
  13. Click Choose File and browse to the MaritimeService.soe file located in <ArcGIS Server installation drive>\MaritimeServer\Server<version>\Bin.
  14. Click Upload to add the SOE to the site.
  15. Copy the Item ID for use in the Update step.
  16. Click Home.
  17. Click Services.
  18. Click Types.
  19. Click Extensions.
  20. Click Update and paste the Item ID.
  21. Click Update.
  22. Navigate to Server Manager https://localhost:6443/arcgis/manager.
  23. Click Services.
  24. Click the map service for which you want to enable the Maritime Chart Service.
  25. Click Capabilities.
  26. Verify that the datasetsDirectory, controlFilesDirectory, and workingDirectory properties point to the correct locations. For more information about these properties, see the 'Modifying Maritime Chart Service capabilities properties' section of Setting Maritime Chart Service properties.
  27. Click Save and Restart to make the Maritime Chart Service available.
  28. Confirm the Maritime Chart Service capabilities are working properly in the map service by verify that the .senc files in the sencs folder are current.
  29. Repeat steps 22 - 28 for each map service with Maritime Chart Service capabilities configured.


Products on Demand (PoD) for Maritime Server
This update is only required for existing Maritime PoD deployments. For a new deployment follow the Deploy Maritime PoD steps.

  1. Ensure Maritime Chart Service has been upgraded, see Maritime Chart Service steps above.
  2. Backup the productsondemand folder at <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\productsondemand.
  3. Copy the productsondemand folder installed by this patch at <ArcGIS Server installation drive>\MaritimeServer\Server<version>\ to <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\.
  4. Merge modifications made to the productsondemand files in the backup folder with the new productsondemand folder. This may include layout templates, etc.

Utilities.py file update for Maritime Server: Products on Demand

  1. Navigate to the Utilities.py file which is typically located at <ArcGIS Server installation drive>\arcgisserver\directories\ maritimeserver\productsondemand\Tools. This is the shared_products_path where productsondemand will be deployed.
  2. Edit the following variables:
    • shared_products_path and output_directory: update machine name, domain and the path if you did not use default settings.
    • output_url: Use localhost for testing only otherwise, update machine name, domain and the path if you did not use default settings.
  3. Save your updates.
  4. For the Calculator service copy the Utilities.py file to <ArcGIS Server installation drive>\arcgisserver\directories\arcgissystem\arcgisinput\POD\Calculators.GPServer\extracted\v101\tools.
  5. For the Gateway service copy the Utilities.py file to <ArcGIS Server installation drive>\arcgisserver\directories\arcgissystem\arcgisinput\POD\Gateway.GPServer\extracted\v101\tools.
  6. In ArcGIS Server Manager click Services and choose Manage Services.
  7. Click Folders and choose POD.
  8. Restart your Calculator and Gateway geoprocessing services.

Configuring the Maritime Server: Products on Demand web application
Prerequisites:

  • Updated layout templates.
  • Updated or published a new map service with Maritime Chart Service enabled.
  • Updated Utilities.py file and restarted the Calculator and Gateway geoprocessing services.
  1. Move the pod web application folder to a backup location. For IIS it would be the C:\inetpub\wwwroot\pod folder.
  2. Navigate to <ArcGIS Server installation drive>\MaritimeServer\Server\WebApplications and copy the folder called pod to C:\inetpub\wwwroot if using IIS to deploy your web application.
  3. Optionally rename the folder pod. The folder name will be the name of the application you access over the web.
  4. Consolidate any modifications from the backup pod web application with the new pod web application.
  5. Edit your podconfig.js file located under pod\js with your published POD service:
    • Update serviceURL to the location created in step 2 of Publishing Service Definition Files. If defaults were used, then the path is http://gisserver.domain.com:6080/arcgis/rest/services/POD.
    • Update the MCSURL path, which the pod web application will use for viewing, to the map service path used in your layout template. The default location is http://gisserver.domain.com:6080/arcgis/rest/services/SampleWorldCities/MapServer/exts/MaritimeChartService/MapServer. The layout template WMS service will be used by the print service to create the chart export.
    • Optionally change the basemap from the Esri Ocean Basemap by modifying the BasemapWithMCS variable.
  6. Save your changes to the podconfig.js file.
  7. You are now ready to use Products on Demand by browsing to http://<your server>/<web application name>.

Enhancements and Issues Addressed with this Patch

    ArcGIS for Aviation
  • BUG-000120717 ExportAixm51 should export ADHPUsageLim, ADHPUsageCon and FlightCharacteristic tables to AirportHeliportUsage.
  • BUG-000120781 ExportAixm51 xlink:href Need '#' added before uuid.
  • BUG-000120780 ExportAixm51 is creating annotation for features that do not have related Notes in AIS.
  • BUG-000120779 ExportAixm51 output has AIXM 5.1 nonconformities.
  • ENH-000120890 ExportAixm51 should not produce output for objects having all null values.
  • Git496 TOP Terrain and obstacle depiction issues for NPAS.

  • ArcGIS for Maritime: Bathymetry
  • Cumulative of previous 10.6.1 patches.

  • ArcGIS for Maritime: Charting
  • TFS116736: Update SCAMIN sample xml to latest UOC guidelines.
  • TFS116850 TOD VPF - Incorrect file name for NTI thematic index.
  • TFS116851 TOD VPF - The TSI file is missing for Ecrtext.
  • TFS116852 TOD VPF - NaN indices are not properly being written.

  • ArcGIS for Maritime: Server
  • TFS115327: Entitlement operation URL length causing 500 error.
  • TFS115380: LNDMRK point features not displaying correctly due to LNKMRK order in psymrefs.dic and psymreft.dic files.
  • TFS115380: Change CURVEL text group to 30.
  • TFS115380: Change indhlt display priority to 9.
  • TFS116050: Enhancement: Modified default ViewOverGroup to include three new layers. Low accuracy, Additional chart information, Overscale warning. All three are turned off by default to reduce clutter.
  • TFS116075: Enhancement: Added support for additional chart information according to S-52.
  • TFS116077: Enhancement: Added support for date dependency features according to S-52.
  • TFS116284: PoD PDF export does not return data for large scale chart when overlapped by a small scale chart.
  • TFS116435: VALSOU for isolated danger points not displaying when IsolatedDangersOff display parameter is used.
  • TFS116808: Corrected S-52 CHDATD01 symbol to display properly.

  • Esri Defense Mapping
    Desktop and Server
  • Git 711 : Update the MTM50, MTM100, TM25, TM50 and TM100 basemap layers label classes to use CMYK.
  • Git 776 : Elevation labels in JOGA products should be in units of feet not meters.
  • Git 786 : Label Expressions in meters to support JOG-G Product.
  • Git 791 : Add Symbol Level Settings for Roads in JOG-A template.
  • Git 820 : Two sets of AOIs are created in JOG_SHEETS_A in the Carto data set when running Location Diagram.
  • Git 871 : 10.x TDS 6.1 and TDS 7 Edit Template Issues.
  • Git 896 : TM TDS7 templates need updating.
  • Git 895 : MTM50 Template issues.
  • Git 902 : Add MGCP TRD 4.5 to Product.
  • Git 915 : Update TDS_7_JOG_VST for JOGs.
  • Git 916 : Add Buffer Zone ATY and FIPS Country Codes to AirspaceSrf in TDS 7 Schema.
  • BUG-000121164 : Create Contours script tool does not generate all contours when the Format on the Region properties dialog is set to a country that uses a comma for the decimal delimiter.
  • BUG-000121218 : Create Rapid Graphic does not output an MXD path for JOG_A.
  • Git 941 : VST/Style Issues TDS7 TM25, TM50, TM100.
  • Git 944 : TM TDS 7 map templates need to have label expressions updated.
  • Git 947 : Update Margin Notes in All MTM and TM Templates.
  • Git 951 : Create Rapid Graphic - JOG MEF Polygons not matching grid cells.
  • Git 952 : Create Rapid Graphic - Update JOG MEF output to new feature class for TDS7.
  • Git 961 : Update color to Distorted Surface symbol for MTM and TM style.

  • Server
  • Git911 : Update POD to export MXD's to 10.6.

  • Desktop
  • Git522 : ICM Create Streets index graphic is using incorrect MGRS grid.
  • Git690 : Incorporate Field Workflow updates to COTS 10.x production workflows.
  • Git908 : Add Support for multiple cell AOIs in VDP and Field Workflows.
  • Git934 : ICM number GNFs are not sorting the categories correctly.

  • Esri Production Mapping
    Desktop and Server
  • Cumulative of previous 10.6.1 patches.

  • Server
  • Cumulative of previous 10.6.1 patches.

Patch Updates

Check the Patches and Service Packs page periodically for the availability of additional patches. New information about this patch will be posted here.

How to identify which ArcGIS products are installed

To determine which ArcGIS products are installed, choose the appropriate version of the PatchFinder utility for your environment and run it from your local machine. PatchFinder will list products, hot fixes, and patches installed on your local machine.

Getting Help

Domestic sites, please contact Esri Technical Support at 1-888-377-4575, if you have any difficulty installing this patch. International sites, please contact your local Esri software distributor.