Mapping and Charting Solutions 10.5.1 Patch 1 (Desktop | Server)
This patch is obsolete. All fixes have been incorporated into Mapping and Charting Solutions 10.5.1 Patch 2 for (Desktop | Server).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
- Login with a Windows Administrator account.
- Select and download the Mapping and Charting Solutions file.
- Double-click the msp file to start the install process.
- When Setup starts, follow the instructions on your screen.
ArcGIS for Maritime: Server, additional installation instructions:
Maritime Chart Service
- Login as a Server Manager by launching https://localhost:6443/arcgis/manager.
- Click Services.
- Stop the map service with Maritime Chart Service capabilities configured.
- Move the controlfiles folder from <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\maritimechartservice\controlfiles to a backup location.
- Copy the new controlfiles folder from <ArcGIS Server installation drive>\MaritimeServer\Server<version>\maritimechartservice to <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\maritimechartservice.
- 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.
- 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.
- 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.
- Repeat steps 1 through 8 for each map service with the Maritime Chart Service capabilities configured.
- Login as an administrator by launching https://localhost:6443/arcgis/admin.
- Click Uploads.
- Click Upload.
- Click Choose File and browse to the MaritimeService.soe file located in <ArcGIS Server installation drive>\MaritimeServer\Server<version>\Bin.
- Click Upload to add the SOE to the site.
- Copy the Item ID for use in the Update step.
- Click Home.
- Click Services.
- Click Types.
- Click Extensions.
- Click Update and paste the Item ID.
- Click Update.
- Navigate to Server Manager https://localhost:6443/arcgis/manager.
- Click Services.
- Click the map service for which you want to enable the Maritime Chart Service.
- Click Capabilities.
- 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.
- Click Save and Restart to make the Maritime Chart Service available.
- 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.
- 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.
- Ensure Maritime Chart Service has been upgraded, see Maritime Chart Service steps above.
- Backup the productsondemand folder at <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\productsondemand.
- Copy the productsondemand folder installed by this patch at <ArcGIS Server installation drive>\MaritimeServer\Server<version>\ to <ArcGIS Server installation drive>\arcgisserver\directories\maritimeserver\.
- 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
- 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.
- 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.
Configuring the Maritime Server: Products on Demand web application
- 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.
- Move the pod web application folder to a backup location. For IIS it would be the C:\inetpub\wwwroot\pod folder.
- 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.
- Optionally rename the folder pod. The folder name will be the name of the application you access over the web.
- Consolidate any modifications from the backup pod web application with the new pod web application.
- 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.
ArcGIS for Aviation
- BUG-000102762 : ImportAixm51 is not importing aixm:SignificantPointInAirspace.
- TFS98098: Parent clientkey value is populated for embedded table objects.
- TFS98217: NavaidComponent WorkHour_code value not importing.
- TFS101836: Import AIXM 5.1 will not run sequentially.
- TFS101870: AirportHeliportAvailability attribute information is not populating.
- TFS101873: ADHPUSageLim does not populate operationalstatus attribute.
- TFS101876: AirportHeliportUsage is not found for airports with a timesheet component.
- TFS101888: Export is missing multiple related records for AirportHeliport.
- TFS102319: Navaidcomponent related availability information is not imported.
- TFS102343: Add mapping for importing related unit information.
- TFS102354: More obstaclestructures are linked to obstacle area.
- TFS102378: SUA Line tool is always running with VFR logic.
- TFS102386: Exporting a features with null geometry fails to import.
- TFS102435: Export template verticalestructurepart for line and polygon is incorrectly placed.
- TFS102458: Export OrganisiationAuthority is missing some of the fields.
- TFS102551: Editor Tracking using the UTC confuses the Permdelta export.
- TFS102934: Update Anno is not scaling outline width parameter when annotation is generated for other scales.
- TFS103238: Add Scalebar option to not round the values.
- TFS103347: VFR UA and MOA Tables do not allow multiple tables.
- TFS103477: Windturbine group features are not getting annotation if the group geometry is complex.
- TFS103679: ImportAixm45: Apply policy on NavaidSystem creation.
- TFS103680: ImportAixm45: Some ILS NavaidSystem features are not integrated.
- TFS103681: ImportAixm45: NavaidAssociation NavaidComponent_ID of nonexistant NavaidComponents.
- TFS103682: ImportAixm45: NavUsageLimit is missing rows.
- TFS103713: SUA Renderer is generalizing airspace geometries.
- TFS103035: The Export Points geoprocessing tool now has an option to include all fields from the source datasets in the output feature class.
- TFS102602: AML 2.1 to 1.0 conversion should modify all necessary values for the typewk attribute.
- TFS102355: Features are out of order when a Collection is deleted in an ER.
- TFS102359: S-58 check 28 (Record count incorrect, e.g. NOMR/NOCN/NOED/etc) is not working correctly with ER present.
- TFS102507: S-58 check 1673a not returning as an Error.
- TFS103046: S-58 check 1522b is returned when the ER is actually valid.
- TFS102167: Data is not displayed when opening a 10.5 MCSTPK project in 10.5.1.
- TFS102341: Enhancement: Returning a blank transparent image when a MCS export request returns no data.
- TFS103525: Hebrew localization error in PoD export due to date value.
- Information on enhancements and new features can be found in the What’s New for ArcGIS for Maritime: Server help topic.
- TFS102563: Enhancement: Create Rapid Graphic GP tool should have an optional contour interval parameter.
- TFS96137: JOG Location Diagram AOI should expand to the full range.
- BUG-000099410: Data Reviewer: The Symbolize Reviewer Feature Records button fails with non-database owner connections to an enterprise geodatabase.
- TFS102558: Data Reviewer: Error “The property
is not set” may be encountered when validating shapefiles using the Geometry on Geometry check.
ArcGIS for Maritime: Bathymetry
ArcGIS for Maritime: Charting
ArcGIS for Maritime: Server
Esri Defense Mapping
Desktop and Server
Esri Production Mapping
Check the Patches and Service Packs page periodically for the availability of additional patches. New information about this patch will be posted here.
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.
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.