EXOR MapCapture Interface User Guide...EXOR MAPCAPTURE INTERFACE USER GUIDE ASSET SHAPEFILES...

Version: 4.7 i

CONFIDENTIALITY STATEMENT

The contents of this document, including system ideas and concepts, are confidential and proprietary in nature and are not to be distributed in any form without the prior written consent of Bentley, Inc.

EXOR

MapCapture Interface User Guide

February 2014

Version: 4.7

Submitted by:

Bentley Systems (UK) Ltd.,

9th Floor,

20 Gracechurch Street,

London

EC3V 0BG

EXOR

MAPCAPTURE INTERFACE USER GUIDE

DOCUMENT TRACKER

EXOR MapCapture Interface User Guide

Trademark

Bentley and the "B" Bentley logo are either registered or unregistered trademarks or service marks of

Bentley Systems, Incorporated, or one of its direct or indirect wholly-owned subsidiaries.

Other brands and product names are trademarks of their respective owners.

Copyright

Copyright © 2013 Bentley Systems, Incorporated.

All Rights Reserved.

Including software, file formats, and audiovisual displays; may only be used pursuant to applicable

software license agreement; contains confidential and proprietary information of Bentley Systems,

Incorporated and/or third parties which is protected by copyright and trade secret law and may not be

provided or otherwise made available without proper authorization.

Restricted Rights Legend

If this software is acquired for or on behalf of the United States of America, its agencies and/or

instrumentalities ("U.S. Government"), it is provided with restricted rights. This software and

accompanying documentation are "commercial computer software" and "commercial computer software

documentation", respectively, pursuant to 48 C.F.R. 12.212 and 227.7202, and "restricted computer

software" pursuant to 48 C.F.R. 52.227-19(a), as applicable. Use, modification, reproduction, release,

performance, display or disclosure of this software and accompanying documentation by the U.S.

Government are subject to restrictions as set forth in this Agreement and pursuant to 48 C.F.R. 12.212,

52.227-19, 227.7202, and 1852.227-86, as applicable.

Contractor/Manufacturer is Bentley Systems, Incorporated, 685 Stockton Drive, Exton, PA 19341-0678.

Unpublished - rights reserved under the Copyright Laws of the United States and International treaties.

EXOR


DOCUMENT TRACKER

Document Tracker

Document Details

File:

MapCapture Interface User Guide V4.7.docx

Prepared by:

Ade Edwards

Manual Name:

MapCapture Interface User Guide

Reviewed by:

Rob Coupe, Julian Earnshaw

Version:

4.7

Approved for issue by:

Date of Issue:

Feb 2014

Product Manager:

Rob Coupe

File Name:

Document Centre/Exor/Product Manuals/4.7 Product Manuals/4.7 completed documentation/MapCapture Interface User Guide v4.7.doc

Document Version Control

Revision Date By Chapter/Page Description

1 11-May-2010 Ade Edwards Initial Version

2 Nov 2010 Ade Edwards Updated to 4.3

3 May 2011 Ian Skinner No changes to 4.4

4 Nov 2011 Ian Skinner No Changes to 4.5

5 Oct 2012 Ian Skinner Document reviewed for 4.6 release

6 Feb 2012 Ian Skinner Changes made to make the document more generic.

7 Feb 2014 Brad Atwell All Reformatting to Bentley template for 4.7 release

EXOR


TABLE OF CONTENTS

Table of Contents

1 Introduction ........................................................................................................................................... 1

2 Asset Shapefiles .................................................................................................................................... 2

2.1 Files ............................................................................................................................................... 2

2.2 Naming convention ....................................................................................................................... 2

2.3 Attribute mapping ......................................................................................................................... 3

2.4 Network locations ......................................................................................................................... 3

3 FTP Transfers ........................................................................................................................................ 4

4 Asset Shapefile Extract ......................................................................................................................... 5

4.1 Locator Extract .............................................................................................................................. 5

4.2 Bulk Download Extract ................................................................................................................. 7

5 Asset Shapefile Editing ....................................................................................................................... 13

5.1 Shapefile Format ......................................................................................................................... 13

6 Asset File Loader ................................................................................................................................ 19

6.1 Bulk Upload ................................................................................................................................ 19

7 Process Automation ............................................................................................................................ 22

7.1 Automated Asset Downloads ...................................................................................................... 23

7.2 Automated Asset Loading ........................................................................................................... 25

7.2.1 Polling FTP Process ............................................................................................................ 25

7.2.2 Spawned Loading process ................................................................................................... 26

8 Issues and FAQ ................................................................................................................................... 28

EXOR


INTRODUCTION

Version: 4.7 1



1 Introduction

MCi was originally based on the Mapcapture loader which is used at Larimer. The main difference is that the Larimer

loader uses CSV files and MCI uses Shapefiles.

There are two main areas of functionality – an Asset Shapefile Extract and an Asset Shapefile Loader.

In general a customer would tend to run a bulk job each night to download all of their shapefiles into areas on their FTP

site(s) for users to pickup. They take these files and either load them into Mapcapture, or into another 3rd party

application like ArcMap, and perform edits on the assets.

These are then saved and deposited back onto an FTP site. These files will then be picked up via the application and load

them into the main database.

EXOR


ASSET SHAPEFILES

Version: 4.7 2



2 Asset Shapefiles

2.1 Files

The shapefile and associated files are typically of the form:

DBF file contains the Attribute data.

LOG file is produced from the MCi process.

PRJ file is a Projection file, and will only be present if the layers are using a SRID.

SHP is the binary shapefile.

SHX is the shapefile index file.

At the very least MCi requires a DBF, SHP and SHX file to load.

2.2 Naming convention

The shapefile and associated files MUST be named in the following way otherwise you will have difficulties when it

comes to loading.

20100513085447_TFL_NI_HIGHWAYS

The first part of the filename is the date and time and is set at the time of extract out of Highways or MapCapture itself:

20100513 < Date element

085447 < Time (with seconds)

The second part is the Admin Unit code and this is based on the user logged into the system when extracting.

TFL .

The third part is the 2 character Asset Type.

NI, CW, SB etc

The final part is the Username

HIGHWAYS

Followed by the file extension.

EXOR


ASSET SHAPEFILES

Version: 4.7 3



2.3 Attribute mapping

To allow compatibility with later versions of Esri SDE (i.e., 9.2 and 9.3.1) attribute mapping files are needed during the

upload and download process to map certain column names (i.e., SECTION, OWNER, LINK) which are deemed to be

Oracle keywords and rejected by the Esri loading utilities which MCi plugs into. To reduce the impact and to maintain

the same file specification across MCi and MapCapture client, the attribute mapping files are generated during the extract

and loading process automatically.

2.4 Network locations

A network location on the shapefile is now an optional field. You can load and extract files without a network reference,

however you will need to perform a Refresh of the Layer (using MCP0300 – Maintain Layers module) to ensure the

extract view is compatible.

EXOR


FTP TRANSFERS

Version: 4.7 4



3 FTP Transfers

When Shapefiles are extracted and loaded into the system, then can be transferred to and from one or many FTP site

locations if required. If you do not want to use this functionality it can be switched off by using the MCP product option

“DOMCPFTP”.

The files can be FTP transferred to a location after the Extract process (for external contractors to pickup) and they can

also be deposited on FTP sites for the Load process to pick them up.

The FTP metadata can be maintained via HIG0200 using an FTP type of “MCP”.

Full details are in the “MapCapture Interface Configuration Guide”.

Figure 1 - FTP Connections

EXOR


ASSET SHAPEFILE EXTRACT

Version: 4.7 5



4 Asset Shapefile Extract

The shapefiles can either be downloaded from Locator (NM0572) from within Asset Manager or Bulk Download

(MCP0100) from within MapCapture product.

4.1 Locator Extract

Select assets for download, and use the “Select To” box to send the assets to the download function (defined via Theme

functions)

Figure 2 - Download Assets

EXOR



Version: 4.7 6



This is an example of downloading multiple Assets into a shapefile. Assuming the configuration is correct, the files are

then FTP’d onto the desired location.

Figure 3 - Download Assets into Shapefile

This asset shapefile can then be picked up by the contractor. The shapefiles are also archived into the archive directory as

defined in the FTP metadata (see configuration guide for full details) –

Figure 4 – Shapefile Archive

EXOR



Version: 4.7 7



4.2 Bulk Download Extract

The user can download many different asset types in bulk using MCP0100. The can optionally add a basic ROI condition.

This module is found under the MapCapture product on the Launchpad –

Figure 5 – Bulk Download Menu Option

EXOR



Version: 4.7 8



Here is an example of Bulk Download. Performance will vary depending on the ROI (or lack of) and the number of asset

items.

Figure 6 – Bulk Download

EXOR



Version: 4.7 9



A log is available for each file extracted, and this is based on the output of the Esri SDE2SHP command executed on the

server.

Figure 7 – Bulk Download Log

EXOR



Version: 4.7 10



The output files will be available on the FTP site (or database server if FTP is not configured).

Figure 8 – Output Files

EXOR



Version: 4.7 11



If archive locations are defined, copies of the files will also be there.

Figure 9 – Archive Files

EXOR



Version: 4.7 12



This is a diagram to represent the process flow of an Export using MCI. The end user (inspector) would have to connect to

the FTP to manually find the files and download them to his/her device.

1. Select Assets for

Download

2. Downloaded to Database Server 3. Transferred to FTP Site

4. Inspector picks up the Shapefiles

Figure 10 – Process Flow Diagram

EXOR


ASSET SHAPEFILE EDITING

Version: 4.7 13



5 Asset Shapefile Editing

Once the contractors have picked up the shapefiles, they can go ahead and edit them using either MapCapture, or an

application like ArcMap.

5.1 Shapefile Format

Here is a typical example of the format of an Asset shapefile. There are a number of fixed attributes, i.e., Asset ID, XSP,

Start Date, Asset Type, Network Location and Shape.

The Asset flexible attributes are defined as ATR_<n>. This may appear a little confusing, but we are restricted to 10

character attribute names in DBF files, so this method produces valid attribute names.

EXOR



Version: 4.7 14



Figure 11 - BS - Bus Shelters Asset

EXOR



Version: 4.7 15



The shapefile can be dragged into ArcMap and edited (to mimic what MapCapture does).

Once the file is opened, locate your asset and highlight it. Use the Editor menu to start editing the shape and attributes.

Figure 12 – Shapefile Edit Tools

EXOR



Version: 4.7 16



Perform a reshape if desired.

Figure 13 - Reshape

EXOR



Version: 4.7 17



Figure 14 - Attributes

From the image above, the following key columns have to be set -

1. EDITMODE – must be either ‘M’ – modification (with Asset History), ‘C’ – Correction (without Asset History)

or ‘I’ for insert.

2. SUR_DATE – must be set to the Survey Date i.e., today or whenever the Asset was surveyed.

3. SUR_TIME – must be set to the Survey Time i.e., the time in which it was surveyed.

4. Modifying the ATR_<n> must be done with care – domain values and lookups are only available in MapCapture

by virtue of the PEDIF file.

5. If you are doing an ‘I’ – Insert, you must set INV_ID to -1.

EXOR



Version: 4.7 18



Once you have finished editing the feature and attributes, save the edits.

Figure 15 – Save popup

This is the editing complete.

EXOR


ASSET FILE LOADER

Version: 4.7 19



6 Asset File Loader

6.1 Bulk Upload

The files must be deposited on the FTP site for the MCP0200 module to pick up. This can load a single Asset shapefile, or

a batch of many shapefiles. The shapefiles must be consistent in terms of Admin Unit code, and there is security in the

form to prevent users from loading files they have no permission to load.

Once loaded, the status of the Batch can be checked –

Figure 16 – MCI Batches

This output shows the SDE upload log on the bottom left panel, and the Asset loader on the bottom right panel.

If the SDE upload fails, the Asset loader will not start.

From this example it shows the 1 Asset edited in a shapefile being processed, and the other 33 left in the holding table

unprocessed.

EXOR


ASSET FILE LOADER

Version: 4.7 20



The asset can then be queried and checked in the Map to ensure the edit has gone through OK.

Figure 17 – View edit

EXOR


ASSET FILE LOADER

Version: 4.7 21



Here is a simple diagram to show the process flow of the Upload.

3. Downloaded to Database Server

2. FTP Site

1. Inspector carried out survey, deposits

files onto the FTP Site

4. Shapefile(s) picked up and loaded

into Exor

Figure 18 – Upload Process Flow

EXOR


PROCESS AUTOMATION

Version: 4.7 22



7 Process Automation

In 4.0.5.2 the Extract and Upload of Asset shapefiles were trigger by users in Highways running the processes from the

forms.

From 4.2.1.0 the process can be fully automated.

Here is a simple diagram to show the changes in terms of Uploading Asset shapfiles –

FTP Site “Drop Box”

Shapefile

Loader Asset Loader

Inspectors PC

Process Automation Framework

Alert Manager

Provides feedback to the

user at various stages

Files from FTP site are picked up at a regular

interval and a load process is spawned.

Exor Highways

Upload of Asset Shapefiles via Automated MCi

MCi Loader

User drops files onto FTP

Site

Figure 19 – Process Automation

EXOR


PROCESS AUTOMATION

Version: 4.7 23



7.1 Automated Asset Downloads

A MCi Extract process type is shipped with MCi at 4.2.1.0. This is a process that will call a package to extract ALL asset

types at a set interval – likely to be once a day (midnight).

This is shipped as metadata, so it will need submitting as a process to kick it off.

Figure 20 – MCI File Extract Process

EXOR


PROCESS AUTOMATION

Version: 4.7 24



The Process Monitor can be used to check the processes have executed OK, and some high level feedback is provided.

To check on the download process in detail, press the “More Details” button for each Process Execution – this will launch

the “Bulk Download” module in MCi.

Figure 21 – Bulk Download

The files will either be deposited on the FTP site or the database server depending on settings. The process will ONLY

run as the Highways owner.

EXOR


PROCESS AUTOMATION

Version: 4.7 25



7.2 Automated Asset Loading

This is a slightly more complicated process which involves –

7.2.1 Polling FTP Process

A process called “MCi File Move” will run at a certain interval and will poll the incoming FTP areas.

Figure 22 – Polling FTP Process

If files are found, they are FTP’d to the Upload area on the DB server, and a Load process is automatically spawned. If no

files are found, the FTP process will simply do nothing.

EXOR


PROCESS AUTOMATION

Version: 4.7 26



7.2.2 Spawned Loading process

If the parent FTP “MCi File Move” process finds files and transfers them successfully, a Loader process will be spawned.

Figure 23 – Spawned Loading Process

EXOR


PROCESS AUTOMATION

Version: 4.7 27



The load process is logged at a high level in the Monitor Processes form. The “More Details” button will take you to the

MCP0200 module for more information –

Figure 24 – More Details

EXOR


ISSUES AND FAQ

Version: 4.7 28



8 Issues and FAQ

Date post:	27-Jun-2020
Category:	Documents
Upload:	others
View:	15 times
Download:	0 times

EXOR MapCapture Interface User Guide...EXOR MAPCAPTURE INTERFACE USER GUIDE ASSET SHAPEFILES...

Documents