What s New in Plts for Arcgis Nautical Solution 9 2Slides

8/19/2019 What s New in Plts for Arcgis Nautical Solution 9 2Slides

1/74

What’s New in PLTS for ArcGIS Nautical Solution 9.2

Transcript

Copyright © 2007 ESRI

All rights reserved.

The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright

law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or

by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system,

except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts and Legal Services Manager,

ESRI, 380 New York Street, Redlands, CA 92373-8100, USA.

The information contained in this document is subject to change without notice.

@esri.com, 3D Analyst, ADF, AML, ARC/INFO, ArcAtlas, ArcCAD, ArcCatalog, ArcCOGO, ArcData, ArcDoc, ArcEdit, ArcEditor,

ArcEurope, ArcExplorer, ArcExpress, ArcFM, ArcGIS, ArcGlobe, ArcGrid, ArcIMS, ArcInfo Librarian, ArcInfo, ArcInfo-

Professional GIS, ArcInfo-The World's GIS, ArcLocation, ArcLogistics, ArcMap, ArcNetwork, ArcNews, ArcObjects, ArcOpen,

ArcPad, ArcPlot, ArcPress, ArcQuest, ArcReader, ArcScan, ArcScene, ArcSchool, ArcSDE, ArcSdl, ArcStorm, ArcSurvey, ArcTIN,

ArcToolbox, ArcTools, ArcUSA, ArcUser, ArcView, ArcVoyager, ArcWatch, ArcWeb, ArcWorld, Atlas GIS, AtlasWare, Avenue,

BusinessMAP, Database Integrator, DBI Kit, ESRI, ESRI-Team GIS, ESRI-The GIS Company, ESRI-The GIS People, FormEdit,

Geographic Design System, Geography Matters, Geography Network, GIS by ESRI, GIS Day, GIS for Everyone, GISData Server,

InsiteMAP, JTX, MapBeans, MapCafé, MapObjects, ModelBuilder, MOLE, NetEngine, PC ARC/INFO, PC ARCPLOT, PC

ARCSHELL, PC DATA CONVERSION, PC STARTER KIT, PC TABLES, PC ARCEDIT, PC NETWORK, PC OVERLAY, PLTS,

Rent-a-Tech, RouteMAP, SDE, SML, Spatial Database Engine, StreetEditor, StreetMap, TABLES, the ARC/INFO logo, the ArcCAD

logo, the ArcCAD WorkBench logo, the ArcCOGO logo, the ArcData logo, the ArcData Online logo, the ArcEdit logo, the

ArcExplorer logo, the ArcExpress logo, the ArcFM logo, the ArcFM Viewer logo, the ArcGIS logo, the ArcGrid logo, the ArcIMS

logo, the ArcInfo logo, the ArcLogistics Route logo, the ArcNetwork logo, the ArcPad logo, the ArcPlot logo, the ArcPress for

ArcView logo, the ArcPress logo, the ArcScan logo, the ArcScene logo, the ArcSDE CAD Client logo, the ArcSDE logo, the

ArcStorm logo, the ArcTIN logo, the ArcTools logo, the ArcView 3D Analyst logo, the ArcView Business Analyst logo, the ArcView

Data Publisher logo, the ArcView GIS logo, the ArcView Image Analysis logo, the ArcView Internet Map Server logo, the ArcView

logo, the ArcView Network Analyst logo, the ArcView Spatial Analyst logo, the ArcView StreetMap 2000 logo, the ArcView

StreetMap logo, the ArcView Tracking Analyst logo, the Atlas GIS logo, the Avenue logo, the BusinessMAP logo, the Data

Automation Kit logo, the ESRI ArcAtlas Data logo, the ESRI ArcEurope Data logo, the ESRI ArcScene Data logo, the ESRI ArcUSA

Data logo, the ESRI ArcWorld Data logo, the ESRI Digital Chart of the World Data logo, the ESRI globe logo, the ESRI Press logo,

the Geography Network logo, the MapCafé logo, the MapObjects Internet Map Server logo, the MapObjects logo, the MOLE logo,

the NetEngine logo, the PC ARC/INFO logo, the Production Line Tool Set logo, the RouteMAP IMS logo, the RouteMAP logo, the

SDE logo, The World's Leading Desktop GIS, Water Writes, www.esri.com, www.geographynetwork.com, www.gisday.com, and

Your Personal Geographic Information System are trademarks, registered trademarks, or service marks of ESRI in the United States,

the European Community, or certain other jurisdictions.

Other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners.


2/74

Presenter: Mary Mozingo

ESRI Redlands, California

What’s New in PLTSfor ArcGIS

Nautical Solution 9.2

Hello, my name is Mary Mozingo and I am an instructor with the Global Navigation Nautical

Team in Redlands, CA. I want to welcome you all to the "What's New in PLTS for ArcGIS

Nautical Solution 9.2” training seminar. For those of you who are unfamiliar with the acronym,

PLTS stands for Production Line Tool Set.

Copyright © 2007 ESRI. All rights reserved. 1


3/74

Copyright © 2004 ESRI. All ri ghts reserved.

Seminar overview

Topics What is PLTS Nautical Solution?

Nautical charting

ENC data production

Format

Each topic is followed by a software demonstration and review

A list of FAQ’s is included at the end of the seminar

In this training seminar, I will introduce you to the PLTS Nautical Solution extension and

demonstrate how these tools can help with chart and S-57 data creation. The topics presented in

this training seminar are, "What is the PLTS Nautical Solution?", then I will cover nautical

charting capabilities with the Solution, and we will end with the ENC data production tools and

functionality. Each of these topics will be followed by a software demonstration and review.

Also, I will go over a list of frequently asked questions regarding the Nautical Solution at the end

of this seminar.



4/74


What is PLTS

Nautical Solution?

Let's begin with our first topic: What is the PLTS Nautical Solution?



5/74


What is PLTS?

Production Line Tool Set

PLTS, again, stands for Production Line Tool Set. It is an extension to the ArcGIS Desktop

product. So what is the PLTS Nautical Solution, and how does it fit into the production process?



6/74


What is PLTS?

Production Line Tool Set Extends ArcGIS Desktop for production

The purpose of PLTS is to help with the overall production process within ArcGIS. PLTS extends

the ArcGIS Desktop for production interface.



7/74


What is PLTS?


Provides tools for tracking production workflow

With PLTS, you have tools that help to manage the production workflow.



8/74


What is PLTS?



Streamlines data creation and maintenance

There are also tools available to help streamline data creation and maintenance. These tools are

designed to provide an efficient editing and attribution environment.



9/74


What is PLTS?




Provides an environment for data review

Another component of PLTS has been specifically created for performing data review. This

includes visual and automated review tools as well as documentation of errors.



10/74


What is PLTS?




Provides an environment for data review

Creates high-quality cartographic products

PLTS also has tools designed to enhance the cartographic production process, including tools that

help you build and manage a map series or a map book.



11/74


PLTS framework

PLTS for

ArcGIS

Extension to ArcGISTwo tiers

As we start to explore the PLTS extension, you will see that there are two tiers to the product.



12/74


PLTS framework

PLTS

Foundation

FoundationTools

GIS DataReViewer

Map ProductionSystem-Atlas

Job Trackingfor ArcGIS

(JTX)

PLTS for

ArcGIS


The first tier is known as PLTS Foundation. This is the base tier, providing you with all the

workflow management data production, data review, and cartography tools. The components of

PLTS Foundation are…



13/74


PLTS framework

PLTS for

ArcGIS


PLTS

Foundation

FoundationTools

GIS DataReViewer



(JTX)

Job Tracking for ArcGIS, also referred to as JTX (this is the workflow management

component)...



14/74


PLTS framework

PLTS for

ArcGIS


PLTS

Foundation

FoundationTools

GIS DataReViewer



(JTX)

the Foundation tools–don't let this name confuse you. This component of the Foundation tier

contains the tools that streamline the editing and attribution environment.



15/74


PLTS framework

PLTS for

ArcGIS


PLTS

Foundation

FoundationTools

GIS DataReViewer



(JTX)

The GIS Data ReViewer contains tools for performing data QC. Checking the data quality is an

important part of the production process, and the GIS Data ReViewer provides a complete review

environment.



16/74


PLTS framework

PLTS for

ArcGIS


PLTS

Foundation

FoundationTools

GIS DataReViewer



(JTX)

Finally, the Map Production System-Atlas, or MPS-Atlas, is your cartographic aid. MPS-Atlas

contains the tools and functionality for producing a series of high quality cartographic maps.



17/74


PLTS framework

PLTS

Solutions NauticalSolution

Mapping Agenc ySolution

DefenseSolution

Aeron auticalSolution


PLTS

Foundation

FoundationTools

GIS DataReViewer



(JTX)

PLTS for

ArcGIS

The second tier of the PLTS product is termed the Solution tier. A solution provides users with

database production tools and cartographic templates that are geared towards meeting the

standards of your chosen industry.



18/74


PLTS framework

PLTS

Solutions NauticalSolution

Mapping Agenc ySolution

DefenseSolution

Aeron auticalSolution


PLTS

Foundation

FoundationTools

GIS DataReViewer



(JTX)

PLTS for

ArcGIS

In this training seminar, we'll be focusing on the PLTS Nautical Solution.



19/74


PLTS Nautical Solution

Solution for management ofnautical data and products

The PLTS Nautical Solution provides efficient management of nautical data and products.



20/74




Support for ci vilian and defense

nautical standards

The data and products supported are both for civilian and defense nautical standards. The solution

and its data models are enterprise-enabled.



21/74





nautical standards

Enterprise scalable and flexible

The solution is enterprise-scalable and flexible to provide, for instance, one central database for

both charting and S-57 data.



22/74





nautical standards

Enterprise scalable and flexible

Built on ArcGIS Desktop and

ArcGIS Server platform

As an extension, it is built on ArcGIS Desktop and in addition, can also be used on the ArcGIS

server platform.



23/74


Nautical products supported at 9.2

Vector (Data) Products Vector Product Format (VPF)

• Digital Nautical Chart (DNC)

S-57 – International Hydrographic Organization (IHO) standard

• ENC, AML, IENC

With the release of the PLTS for ArcGIS Nautical Solution 9.2, several products are supported.

With the VPF standard, or vector product format, the digital nautical chart (or DNC) production

is fully supported. This format is mainly used by the United States National Geospatial-

Intelligence Agency, or NGA for short. S-57 is the International Hydrographic Organization (or

IHO) transfer-standard for digital hydrographic data. The Nautical Solution supports several S-57

product specifications. ENC, or Electronic Nautical Chart production, is supported out of the box.

AML, also known as Additional Military Layers, and IENC, or Inland Electronic Navigation

Charts, are supported S-57 products as well. However, AML and IENC require some

configuration of the existing nautical data model.



24/74






• ENC, AML, IENC

Chart Products

IHO

• INT1, INT2, INT3

National

• NOAA

• US Department of Defense

Map books

Several nautical chart product standards are also supported with the Nautical Solution. Again, the

IHO specification for INT1 (International 1) is supported through provided symbols in the INT1

style file, provided with the Solution, as well as label expressions for abbreviations. The INT2

borders, graduation, grids, and linear scales are supported with XML files used in conjunction

with the PLTS Grid Manager. The combined support with the Nautical Solution of INT1 and

INT2 specifications also supports INT3 as well. For the domestic US, there are also symbols and

tools to support nautical chart production for civilian, commercial, and defense chart products,

such as NOAA and US Department of Defense. Functionality within MPS-Atlas enables the

creation of map books. This can be especially useful for inland waterways, such as navigating

along portions of the Mississippi River.



25/74






• ENC*, AM *, IEN *

*, IN *, IN *

*

*New at 9.2

L C

Chart Products

IHO

• INT1 T2 T3

National

• NOAA

• US Department of Defense

Map books

Many of these products are newly supported with the PLTS for ArcGIS Nautical Solution at 9.2.

The S-57 and IHO chart production is the main focus of what's new in the Nautical Solution, and

what we'll be discussing in this seminar.



26/74


What’s in the box?

Geodatabase templates ENC, DNC, and charting models

In addition to the foundation components, the Nautical Solution includes geodatabase templates

for ENC, DNC, and charting models.



27/74




Geoprocessing tools

There are several geoprocessing tools that are included with the Nautical Solution that provide for

more efficient data production.



28/74




Geoprocessing tools

Sample data and MXDs

A sample data CD is provided with the solution, including DNC, ENC, and nautical chart sample

data and MXDs.



29/74




Geoprocessing tools


Nautical cartographic too ls and elements

Nautical cartographic tools and elements are included, such as the magnetic calculator and PLTS

Grid Manager.



30/74




Geoprocessing tools



Symbology and grids (INT1, INT2, INT3)

The symbology and grids, provided with the Nautical Solution, are from the IHO INT1, INT2,

and INT3 specifications.



31/74




Geoprocessing tools




S-57 capabilit y and editing too ls

S-57 data production capabilities and editing tools make up another large portion of what's new in

the Nautical Solution at 9.2.



32/74




Geoprocessing tools





Unit conversion for depth and height

Unit conversion of S-57 and chart data for depth and height fields is automated through the use of

rules. For instance, the US produces ENC data in both meters, which is specified by the IHO

standard, and feet, which US mariners traditionally use.



33/74




Geoprocessing tools






SCAMIN configuration and assignment

SCAMIN, or minimum scale, is the scale below which a feature is no longer visible on a ship's

electronic chart display and information system. The assignment of SCAMIN values is based on

initial configuration.



34/74




Geoprocessing tools






SCAMIN configuration and assignment

Sounding management

The management of sounding groups in S-57 data is necessary in order to reduce the file size.

Soundings are the most abundant feature that is collected. Soundings are grouped based on

similar attribution and there are several tools to help us select sounding groups, create groups, as

well as appending to existing sounding groups.



35/74


Software

demonstration

Let's go to our first software demonstration. What I'm going to do is activate the PLTS extension

and explore the foundation tools’ editing and attribution environment. I have some ENC data here

from Florida and what we want to do is make some edits. Now the first thing that I need to do

with PLTS is to ensure that the extension is activated. I'll do that just like any other extension

from ArcGIS by going to Tools and Extensions. We will see here each of the individual

components that I've just talked about with the PLTS Nautical Solution. We have the Nautical

Solution extension as well as MPS Atlas, GIS Data ReViewer, and PLTS Foundation Tools for

editing and attribution. Now that I know that my extensions are activated, I can start using PLTS.

Let's first take a look at the ArcMap interface with PLTS installed and activated. One thing you'll

notice right away are the additional tabs and the table of contents. The PLTS Selection and PLTS

Target tabs are very useful for feature attribution and feature creation.

PLTS also has several toolbars for more efficient data creation and maintenance.

Some tools, you'll notice, are the same as ArcGIS core functions, but they reduce the number of

clicks with the mouse. For instance, I've already started my edit session with a single click of the

PLTS Start Editing button, which is on the PLTS Editing and Environment toolbar as shown here.

The edit session has already been started, so let's take a look at how I can create features. First, I



36/74

need to set my target layer. With the PLTS Target tab, this is accomplished with a single click.

Notice how the Target tab lists all of the feature classes that are loaded into ArcMap in our

Display tab in the table of contents. I'm going to set my target here to create a

BuoySpecialPurpose feature. If I add this feature right now, you'll notice that the attribution

associated with it is default, and all of these values are set to null. But I remember that I also have

loaded a Favorites database. A PLTS Favorites database contains preattributed combinations that

allow for more efficient feature creation. By expanding the BuoySpecialPurpose subtype, I can

see my Favorite that has been created for me already. This is actually shared by a coworker.

These are saved in a geodatabase and can be distributed throughout your organization. By

selecting this favorite, in this lower portion within the PLTS Target tab, I can see the attributes

that are associated with it. This happens to be a pillar buoy, which is not what I want to add.

While the PLTS Target tab is used to select the target for features that I want to create, the PLTS

Selection tab is used to view the attribution of already-existing and selected features. So from the

PLTS Selection tab, I see a tree view of my currently selected which happens to be this beacon

right here. In the lower part of the tab, we again see the fields and attributions for the selected

feature. You'll notice that some of the fields are bold while others are grayed-out and some appear

normal. These bold fields designate the use of mandatory attributes and provide a visual cue to

anyone editing attribution of this data. I'm going to remove the attribution for the mandatory

attribute CATLAM, or Category of Lateral Mark field. Changing this to Null, you'll notice that

this field value has changed, and we now see that it has a blue tint, and the check box next to it is

checked. To commit this attribution change to the feature, I need to click the Apply button.

Remembering that this is a mandatory attribute that I have now changed to Null, I expect to see

this error message popping up. It ran certain conditions that have already been preconfigured with

this model, and it lets me know that the Category of Lateral Mark is a mandatory attribute and

that it must not be Null. Okay, I notice that the attribute here on the check box is still blue and

checked on, meaning that these changes have not been made to my feature yet. I'll change this

back to the value of 1, which it originally was. It's still blue, and the box is checked. Now when I

click Apply, it performs the same validation, but it does not find that there is a mandatory

attribute, null.

Now that this value has been changed, I've applied it and it's ran through and passed the

conditions that are set up to check for it. It has now applied my attributes, which are valid, to the

features. If I would like to add this new attribute combination to my Favorites database, I can

simply right-click on it and say "Create Favorite." My input Favorite name's going to be a "Pile



37/74

porthand lateral mark." Now when I go back to my PLTS Target tab and go to my BeaconP

lateral beacon subtype, I notice that there's a new Favorite underneath it for my Pile porthand

lateral mark.

You've now seen the PLTS interface in ArcMap and a sampling of some of the efficient editing

tools that are available. I'm going to save my edits.



38/74


Review

PLTS Nautical Solut ion i s an extension of ArcGIS forefficient:

Geodatabase creation

Data extraction and attribution

QC and data review

Cartographic production

Workflow management

New products are supported wi th PLTS Nautical

Solution 9.2

Let's review what we've covered so far.

When it comes right down to it, PLTS really is a combination of geodatabase creation, data

extraction and attribution, quality control and data review, and cartographic production and

workflow management tools. With the Nautical Solution, we build on top of this foundation with

nautical and hydrographic industry-specific data models, validation, and symbology.



39/74


Nautical charting

Let's continue with a look at nautical charting with the PLTS Nautical Solution.



40/74


Nautical chart production

Cartographic editing

N

a

u

t

i

c

a

l

The nautical chart production process begins with cartographic editing such as generalization,

edge-matching, and so on.



41/74




Grids and borders

N

a

u

t

i

c

a

l

G

r

i

d

s

b

o

r

d

e

r

s

Each chart can be stored in an individual geodatabase. The underlying nautical data is contained

within its own feature dataset. The grids and borders are contained within the same geodatabase,

but in a separate feature dataset. They all are corresponding to the same nautical chart.



42/74




Grids and borders

Page layout

N

a

u

t

i

c

a

l

S

o

u

r

c

e

d

i

a

g

r

a

m

G

r

i

d

s

b

o

r

d

e

r

s

If the source diagram is required for the chart, it also has its own feature dataset, and in this

example we see one layout which is actually comprised of data from three separate geodatabases,

one for each panel, that have been combined in ArcMap in separate data frames to form one hard

copy nautical chart output.



43/74




Grids and borders

Page layout

Exporting

N

a

u

t

i

c

a

l

S

o

u

r

c

e

d

i

a

g

r

a

m

G

r

i

d

s

b

o

r

d

e

r

s

When a chart addition is ready for QC or perhaps publication, there are many different formats

available to export from ArcMap into. We will discuss these shortly.



44/74



Symbology INT1 specifications

Representation rules

Label expressions

Masking

Symbolizing nautical data with the PLTS Nautical Solution is aided by the INT1 style file

included with the Solution. Here we see examples of INT1 symbols that are included in that style

file. The symbols are displayed by representation rules within the geodatabase. In addition, INT1

contains specifications for labeling features, such as lights. Label expressions have been created

and included with the Nautical Solution according to INT1 spec. And with any cartographic

production, masking is a very important part and is included within the Solution as well.



45/74



Symbology INT1 specifications

Representation rules

Label expressions

Masking

Geoprocessing framework

World Magnetic Model

Light sectors

Align topmarks

The geoprocessing framework for nautical charting includes tools for calculating the World

Magnetic model, as well as generating light sectors, lines and areas representing those light

sectors based off of original point features, as well as aligning topmarks to their respective

navigational aids.



46/74


Grids and borders

INT2 IHO specifications suppl ied 14 scale range dependent formats

Most hydrographic agencies use customized

versions of INT2

Once our data has been symbolized, we need to add grids and borders. The INT2 IHO

specifications for grids and borders are supplied with the Nautical Solution. They include the 14

scale range dependent formats. Although most hydrographic agencies will take those formats and

customize them to their own versions of INT2, which of course is easily done with the Nautical

Solution.



47/74


Grids and borders



versions of INT2

Managed and created w ith PLTS Grid

Manager

INT2 borders and grids delivered

as XML files

Created over specified chart

extents using wizard

The grids and borders are managed and created with the PLTS Grid Manager. The INT2 borders

and grids are delivered and included with the Nautical Solution as XML files. The grids and

borders can be created over a specified chart extent using the PLTS Grid Manager wizard.



48/74


Grids and borders



versions of INT2

Managed and created w ith PLTS Grid

Manager

INT2 borders and grids delivered

as XML files

Created over specified chart

extents using wizard

Borders/grids created as

series of feature classes ingeodatabase

Customized grids styles

created with designer tool

Here we see an example of grids and borders that were created. The Grid Manager uses those

XML files and the wizard to create our grids and borders, which are a series of feature classes

within our geodatabase. Because they are a series of feature classes, all we need to do to

customize them is to start an edit session and use the designer tool to customize them to our

individual hydrographic agency’s proprietary border styles.



49/74


Page layout

Guidelines Snapping

Graphics

Text

Logos

Neatline

Once our data has been symbolized and we've done our cartographic editing, and our grids and

borders have been added, we need to be concerned about our page layout. That includes our

guidelines as well as snapping to them, any graphics that need to be included. For instance,

specific text on the chart number or chart name, logos. For here, we see an example of the

National Geospatial-Intelligence Agency (or NGA) chart logo as well as the NOAA chart logo.

We also have the ability to add specific graphics such as neatlines around our data as well.



50/74


Page layout

Guidelines Snapping

Graphics

Text

Logos

Neatline

Surround elements

Graphic tables

Scale bars

Element Manager

• Creating

• Adding• Loading

In addition, on our page layout, there are certain surround elements, or marginalia, that need to be

added. For instance, we see here an example of a tide table. We've used something called the

Graphic Table Elements tool that's included with PLTS, or GTE tool. It looks similar to Excel,

with its columns and rows that allow us to customize and create individual tide tables or scale

bars to be included with our nautical charts. You can see here that this is an example of a

somewhat complex tide table and it's easily created with the GTE tool. We can not only create

these and add them to individual charts, we can load them from saved tide tables with the GTE

tool as well.



51/74


Exporting

Vector EPS

PDF

Color Separations

• SPOT/Pantone

SeeSpotColor

Process color/CMYK

Once we have symbolized our data, we've also added our grids and borders, and we've laid out

our page. Next thing that we'd like to do is export. There are several options available for

exporting from ArcGIS. For instance, if we'd like to export as a vector, we can export to EPS

files, PDF, we can make color separations of SPOT/Pantone SeeSpotColor, as well as processing

the colors into CMYK.



52/74


Exporting

Vector EPS

PDF

Color Separations

• SPOT/Pantone

SeeSpotColor

Process color/CMYK

Raster

GeoTIFF

TIFF

Color Separations

• Separated TIFF

To export rasters, we have the ability to export TIFFs, GEOTIFFs, as well as color separations

and separated TIFFs. Here we see an example of exporting color separated TIFFs of our chart.



53/74


Software

demonstration

In the second software demonstration, I will expose the compass rose's representation rules, and

correspondingly use the World Magnetic Model calculator to rotate the compass rose to magnetic

North. I'm already in an edit session, and I'd like to switch my view to an existing compass rose.

So one very important element of a nautical chart is the compass rose which include designating

true North, pointing here, as well as magnetic North, within a specific location. True North is

where all of the longitude lines meet at the North Pole of Earth, whereas magnetic North can vary

by your location, altitude, and the day of the year. The magnetic field is constantly shifting over

time, and the angular difference between true North and magnetic North is the declination which

we'll see depicted on nautical charts with the compass rose. In this example here, our compass

rose is pointing magnetic North, uh, is actually pointing true North because we have not made our

World Magnetic Model calculations yet. I have here the same ENC S-57-based data from Florida,

which I want to make a chart of. You'll see again how this compass rose only points to true North.

I'm going to use the magnetic calculator to populate the declination to a field called the

VALMAG, or Value of Magnetic Pull field, for the MagneticP feature class. The representation

for the compass rose has multiple layers.

Let's take a look at these properties right now. For MagneticP, I want to look at the properties for

each of these features within the layer. We're looking at one specific MagneticP point right now,



54/74

and its corresponding representation. So here's our representation. I notice that it has different

layers which we can see the marker styles here, and I happen to know that this layer is the

outermost circle that we see pointing to true North, whereas this layer here, I happen to know, is

the inner circle which is supposed to point towards magnetic North. Because this symbol is

actually divided into these separate layers, I can choose to rotate the magnetic North circle layer

individual from the true North-pointing circle. I can set the angle of rotation to a specific field in

my database, and I see here that the angle of rotation is on my VALMAG field. This is exactly

what I want to have happen. Now I'll clear my selected features.

Now I could do the complex calculations myself to determine the magnetic declination. However,

nautical charts can have more than one compass rose per chart, and for anyone managing several

charts, this is a very time-consuming task. I'm going to open the Magnetic Calculator GP tool

now through ArcToolbox. It is located within the PLTS Foundation Tools Magnetic toolset. My

Magnetic Calculator is here. Again, the magnetic declination has many determining factors, so

first I'm going to put in my XY location which is my Point feature class. MagneticP is my input

feature class.

Altitude is another determining factor. The linear units listed here refer to the units in the Altitude

field. Now I'm gathering data for a nautical chart. The data is always based on nautical charts at

sea level; thus, my altitude is going to be zero. And because I'm providing an altitude, I need to

provide a linear unit, which I know if I did have an altitude other than zero, would be in meters.

Now that we know our XY location as well as altitude, we need to input a date. The date must be

between the years of Jan 1, 2005 and December 31, 2010. I'm going to use today's date. In this

example, I'd also like to populate this calculated value to that VALMAG field that I referred to

earlier, which I'm going to select here from a pull-down list. So the magnetic declination of

features at these XY locations in this feature class, at an altitude of zero meters, on today's date,

will be calculated into the VALMAG field. Now once I click OK, I want you to watch the

compass rose very carefully. So the calculations are going to be computed and what you'll see

here is a slight rotation of the compass rose. It's automatically rotating to the correct number of

calculated degrees of declination that we've calculated with our Magnetic Calculator. I'm actually

going to stop and save my edits.

So now that you've seen the use of representations for the compass rose and the functionality of

the Magnetic Calculator, let's review what we've covered so far.



55/74


Review

Core ArcGIS and PLTS tools used for feature editing

PLTS Grid Manager creates grids from INT2 XML files

Included with PLTS Nautical Solution 9.2

Efficient surround element (marginalia) creation

Several export formats available

Core ArcGIS and PLTS tools are both used for our feature and cartographic editing and our

nautical chart production. The PLTS Grid Manager allows us to create grids from INT2 supplied

XML files that are included with the PLTS Nautical Solution. We're also able to efficiently create

surround elements or marginalia such as tide tables, and we can export our hard copy charts once

they're created to several different export formats that are available.



56/74


ENC data

production

Now that we've already seen nautical charting with the Solution, let's talk about S-57 ENC data

production.



57/74


S-57 data management

S-57 import to geodatabase

S-57 data is managed in several ways with the Nautical Solution. The S-57 ENC files, or triple-

zero files, are imported into the geodatabase.



58/74




S-57 primitives and topology management

Update Primitives tool

Topology rules (pre-defined from S-58 validation standard)

Once we have that S-57 imported with S-57 data importer into the geodatabase, we need to

manage our primitives and topology within the geodatabase. The primitives I'm talking about

here are a link between the S-57 data and how it's stored and how I manage data in the

geodatabase. For instance, if I have a light point in the geodatabase, it's represented in S-57 data

as a node, and if it's not connected to anything, it's an isolated node. However, if I add a pier to

extend down into my water that connects to that node, that light, then that isolated node light will

actually change to a connected node when I run the Update Primitives tool. Updating the

primitives and keeping those in sync in the geodatabase is very important in our data management

of S-57 data process. We also have included topology rules. These are included with the Nautical

ENC schema, and are predefined from the existing S-58 ENC validation standard that the IHO

provides.



59/74




S-57 primitives and topology management

Update Primitives tool

Topology rules (pre-defined from S-58 validation standard)

S-57 export from geodatabase

Support new editions and updates (EN/ER)

Once we import our data into the geodatabase, manage it within the geodatabase itself–adding

features, changing them, modifying them–we can produce ENC EN and ER files by exporting

from the geodatabase. The S-57 exporter supports both new editions, EN files, as well as updates,

or ER files.



60/74


Editing tools

S-57 edit extension Operates “behind the scenes”

When we talk about managing our data, it's important to look at some of the editing tools that are

included with the Nautical Solution. One of the most important editing tools is the S-57 edit

extension. This isn't actually a tool that you see on a toolbar and it's not represented by a tool

button. It operates behind the scenes as we're editing our data.



61/74


Editing tools


Maintains relationships

It helps us to maintain specific S-57 relationships within our data.



62/74


Editing tools



Auto populates mandatory fields

And it also auto populates certain mandatory fields, like LNAME, or long name, which is a

unique identifier for each feature. And when I say unique identifier, the IHO specifies that it must

be unique to all features that are captured in ENC in the world. It's very important for us to auto

populate that field correctly.



63/74


Editing tools




Relationsh ip Manager controls complex S-57 object

relationships

Another example of the editing tool within the Nautical Solution for editing ENC or S-57 data is

the Relationship Manager, which allows us to create, manage, and control complex S-57 object

relationships. Here we see an example of the Relationship Manager dialog. It lists in a tree view

all of the collections, master-slave relationships, and multiple representations that we have within

our current data extent. We will see an example of this in the software demonstration later on.



64/74


Editing tools




Relationsh ip Manager controls complex S-57 object

relationships

Sounding tools

Select sounding group

Group soundings

Append soundings

There are also sounding tools included as well. We have the ability to select certain soundings

from an existing sounding group, group selected soundings, as well as append existing soundings

to existing groups. The management of soundings is very important, again, because those are our

most abundant feature on our ENC or chart data. The grouping of those saves on our S-57 file

size later on.



65/74


Automated feature creation

Geoprocessing tools Depth areas

Linear depth areas

In addition to editing tools, we also have automated feature creation tools. For instance, there are

two geoprocessing tools that are included with the Nautical toolbox in the S-57 toolset. They are

Generate Depth Areas tool as well as Generate Linear Depth Areas tool.



66/74



Geoprocessing tools Depth areas

Linear depth areas

Feature Builder for geodesic feature creation

Something else that allows us to automatically create features aside from the GP tools is a new

tool called the Feature Builder. This Feature Builder is extremely important for the Nautical

Solution for geodesic feature creation. In this example here, we see that we're able to create a line

of constant bearing or a great circle within our nautical dataset. It's important also to notice all of

the other types of functions that we can use to create features. The inputs located here as the

coordinates and the azimuth distance, etc., that are needed, dynamically change based on the

functions that are selected here. The Feature Builder can be used for many different types of

creation of complex features, such as geodesics, loxodromes, and lines of constant bearing.



67/74


Software

demonstration

In this final software demonstration, I will be editing ENC data and creating a collection

relationship. You'll notice here that I'm still editing the same Florida ENC data. I'm going to go to

my Relationship Manager bookmark here. I'm editing the same S-57 ENC cell, and notice that it

is also the same data that my nautical chart in the last demonstration was derived from. The

nautical charting ENC, AML, and IENC products, as well as charting, are from the same schema.

In order to create a collection in my ENC data, I need to first be in an edit session, which I am.

The Relationship Manager tool is on the PLTS Nautical toolbar. I'm gonna go to add this toolbar

right now, and I'd like you to notice how many PLTS nautical toolbars you have included with

the Solution. The PLTS Nautical toolbar is the one that I'm interested in right now.

Here we see the Relationship Manager tool. It helps us to maintain two types of relationships

between objects. There are hierarchal relationships and peer-to-peer relationships. The hierarchal

relationships have designated master and slave features, meaning that one is dependent, or

hierarchal, above the other. In peer-to-peer relationships, no feature's existence is dependent on

one another, and the collections are considered to have a type of peer-to-peer relationship that can

be grouped into two different object classes–aggregations or associations. I'm going to create a

collection aggregation relationship right now.



68/74

First let me move this dialog so I can select the features that are going to participate in my

relationship. I should have four features here selected. If I go to my PLTS Selection tab, I can see

that I do have four features, in fact, selected. The four features are two beacons and two

navigation lines. Together, as a collection, these features combine to form a recommended track.

What this means is, as a mariner onboard your ship, they're going to see these beacons in a line

and they'll steer their ship along this path so that as they're moving forward, they see the beacons

in line and that as long as they see them in line, they are following what is referred to as a

recommended path to help them enter a narrow channel. In the Relationship Manager, I'm going

to right-click my Collection and say that I want to create a collection. This is where it asks me if

I'm creating an aggregation of features or association of features. I've already determined from the

S-57 spec that in creating a recommended track, I'm creating an aggregation collection. Now once

I click OK, a new aggregation collection will be created. We can see it in the tree view of the

Relationship Manager. I move this again, clear my selected features, and I can actually add all of

these to my selected set. So now, we see that we have the original four features created as well as

an additional feature object known as a collection object. Because this collection object has been

newly created, combining or having a link between all these new features, I can see a little bit

about how the edit extension is actually working behind the scenes. It said that this is the editor

name that has recently added this feature, the date and time that it was created, the last modified–

so today, May 15th. And the LNAM, or long name, has already been automatically generated as a

random number for this feature in addition to the name, and the dataset name of the

corresponding cell that this is included in has also been automatically generated for us.

So you've now seen the Relationship Manager and how it's used to create a collection

relationship.



69/74


Review

Efficient ENC production S-57 data management

Editing tools


Let's review what we've covered for ENC production so far.

With the Nautical Solution, we have many tools for efficient ENC S-57 data production. We can

manage our S-57 data into and out of and within the geodatabase by use of import/export. In

addition, there are many editing tools working behind the scenes as well as tools we can interact

with, the edit extension and the Relationship Manager being two examples of those, as well as our

automated feature creation abilities with GP tools and the Feature Builder tool.



70/74


PLTS Nautical Solution FAQ

Is the provided INT1 symbology customizable forindividual hydrographic agencies?

Yes. All style files including the INT1.style file can be

customized.

I'd like to take a minute now, at the end of this seminar, to go over some of the frequently asked

questions that I've gotten in relation to the PTLS Nautical Solution. For instance, “Is the provided

INT1 symbology customizable for individual hydrographic agencies?” This is a really good

question, and the answer is yes. All of the style files that are included with the INT1.style can be

customized, meaning that you can take what we've given you as a kind of jumping off point and

create your own customized styles. This is especially useful as many hydrographic agencies have

their own proprietary style that's based in part on the INT1-IHO style. My suggestion to you

before customizing your INT1 style file is to make a backup copy of it first, though.



71/74



Is the provided INT1 symbology customizable forindividual hydrographic agencies?

Yes. All style files including the INT1.style file can be

customized.

What is the NIS?

The Nautical Information System (NIS) is a centralized database

and workflow approach for production of ENC, IENC, AML, and

chart products.

Another question is, "What is the NIS?" The Nautical Information Sytem, or NIS, is a type of

centralized database and workflow approach for the production of ENC, IENC, AML, and chart

products. I mentioned this before, but the schema for the NIS is also the same schema that is used

for ENCs, charts, AML, and IENC. This is all based off of the S-57 schema. So we have here our

enterprise geodatabase, our NIS, where all of our edits and geometry are maintained. We make a

replica of this, or copy, that goes out to produce our product instances, our geodatabases. Here we

have an ENC Florida cell, a California cell of ENC data, as well as a NOAA chart that we're

producing. On this product side, we're not actually making any edits to our geometry or attributes,

but we are making certain finishing touches, for instance, on our charting products. We might

move the representations of the features while leaving the underlying geometry intact. All of our

edits again happen on the NIS side, so any updates that are here can be synchronized to these

geodatabases, and we can publish products from them, so we can export from this ENC Florida

cell product database to produce an EN or ER file, and at that point we can use some external

software for S-58 validation as well as exporting our chart here and producing it for press

operations.



72/74


PLTS Nautical Solution FAQ (ct'd)

Does PLTS Nautical Solution inc lude a way to convertDNC data to ENC?

No. However, we are involved in many IHO working groups

such as the DNC and ENC harmonization work groups.

Another question that we sometimes get is, "Does the PLTS Nautical Solution include a way to

convert DNC data to ENC?" This is a really good question. Currently, no; we don't have a way to

convert DNC to ENC data. However, we are involved in many of IHO working groups, one of

them being the ENC and DNC harmonization workgroup, and our involvement in this workgroup

can eventually lead to a solution that will be able to convert DNC to ENC data and vice-versa.



73/74



Does PLTS Nautical Solution inc lude a way to convertDNC data to ENC?



Is the creation of exchange sets supported with Nautical

Solution?

Yes. The PLTS Nautical Exchange Set tool packages S-57,

related .txt, and image files into exchange sets.

Another question is, "Is the creation of exchange sets supported with the Nautical Solution?" I

didn't mention this earlier, but yes, the PLTS Nautical Exchange Set tool can package S-57 ENC

cells EN, and ER files as well as related text and image files. It groups them together and

packages them into exchange sets, which is what is typically used by mariners and transferred

onboard ships.



74/74



Does the PLTS Nautical Solution include a way to convertDNC data to ENC?



Is the creation of exchange sets supported with Nautical

Solution?

Yes. The PLTS Nautical Exchange Set tool packages S-57,

related .txt, and image files into exchange sets.

Which ArcGIS license do I need to use PLTS Nautical

Solution?

An ArcInfo Desktop license is needed for PLTS Nautical to be

fully functional.

Our last question that I'd like to address is, "Which ArcGIS license do I need to use for the PLTS

Nautical Solution?" An ArcInfo Desktop license is needed for the PLTS Nautical Solution to be

fully functional, meaning if you want to do everything with ENC production and charting

production that you've seen here, you're going to need an ArcGIS desktop license, an ArcInfo

Desktop license.

On behalf of ESRI, I'd like to thank you for your time. We hope you will attend other seminars as

well. Please see the "What's Next?" page for information on other resources related to what's new

in the PLTS Nautical Solution 9.2.

Date post:	07-Jul-2018
Category:	Documents
Upload:	michael-ellis
View:	212 times
Download:	0 times

What s New in Plts for Arcgis Nautical Solution 9 2Slides

Documents