command line useage

51
FOR557 FOR557

Upload: milton

Post on 13-Jan-2016

54 views

Category:

Documents


0 download

DESCRIPTION

FOR557. Command Line Useage. Command Line. No choices (menus, clicking). YOU have to remember what to type! Strange stuff like Arc: &workspace e:\yourname\ugis\data. Command Line. Arc: &workspace e:\yourname\ugis\data. Arc prompt (you are supposed to type something). Command Line. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Command Line Useage

FOR557FOR557

Page 2: Command Line Useage

Command Line

• No choices (menus, clicking). YOU have to remember what to type!

• Strange stuff like– Arc: &workspace e:\yourname\ugis\data

Page 3: Command Line Useage

Command Line

Arc: &workspace e:\yourname\ugis\data

Arc prompt(you are supposed to type

something)

Page 4: Command Line Useage

Command Line

Arc: &workspace e:\yourname\ugis\data

& tells ARC that the following command is an

AML

Page 5: Command Line Useage

Command Line

Arc: &workspace e:\yourname\ugis\data

The command:Name of a program to

execute

Page 6: Command Line Useage

Command Line

Arc: &workspace e:\yourname\ugis\data

The argument to this AML is the path to a workspacee: is the drive letterThe rest is a hierarchy of folders

Page 7: Command Line Useage

Path

Local disk (E:)

yourname

ugis

data

e:\yourname\ugis\data

Page 8: Command Line Useage

In chapter 4 these cmds are used

• &workspace• &station• Create• Drawenvironment• Draw• Coordinate digitizer• Mapextent• Editfeature

• Usage• Kill• Quit• Listcoverages• Describe• Select• Arc• Arcedit

Page 9: Command Line Useage

A Incantation of Cmds

ARC: &workspace e:\lpherrrin\land

ARC: listcoverages

ARC: station 9999

ARC: arcedit

ARCEDIT: editco stuff

ARCEDIT: drawenvironment tics arcs nodes

ARCEDIT: draw

Page 10: Command Line Useage

A Mantra of Cmds

ARC: &workspace e:\lpherrrin\land

ARC: listcoverages

ARC: station 9999

ARC: arcedit

ARCEDIT: edit stuff

ARCEDIT: drawenvironment tics arcs nodes

ARCEDIT: draw

&WORKSAPCEAllows you to change the directory at which ARC is

pointing (or using).And it can only point to

1(one) directoryBUT you can run multiple

Arc sessions.

Page 11: Command Line Useage

A Mantra of Cmds

ARC: &workspace e:\lpherrrin\land

ARC: listcoverages

ARC: station 9999

ARC: arcedit

ARCEDIT: edit stuff

ARCEDIT: drawenvironment tics arcs nodes

ARCEDIT: draw

LISTCOVERAGELists all the coverages in the current workspace.

If there are no coverages then the current workspace

is NOT a workspace!OR use

&SYS DIRToo see all contents

Page 12: Command Line Useage

A Mantra of Cmds

ARC: &workspace e:\lpherrrin\land

ARC: listcoverages

ARC: station 9999

ARC: arcedit

ARCEDIT: edit stuff

ARCEDIT: drawenvironment tics arcs nodes

ARCEDIT: draw

ARCEDITLaunches the arc editor,

one of the most used programs in ARC

The following 3 are arcedit commands – they do not

work in ARC!Or may do something you

don’t expect!

Page 13: Command Line Useage

Abbreviated Cmds

ARC: &workspace e:\lpherrrin\land &works

ARC: listcoverages lc

ARC: station 9999

ARC: arcedit

ARCEDIT: edit stuff

ARCEDIT: drawenvironment tics arcs nodes

ARCEDIT: draw drawe works for above

Page 14: Command Line Useage

Cmd help structure

• BUILD <cover> {POLY | LINE | POINT}• < > enclose required argument• lower case arguments replaced by a name • { } enclose options in upper case• | means OR• # is a place holder• BUILD mymap POLY

Page 15: Command Line Useage

Navigation

• A/I has this neat little trick:

These will allow scrolling through last n commands

The horizontal arrow keys will

allow you to scroll through

the current command and

edit it by backspacing

over characters and typing new

ones.

Try it – it is a great time saver when you screw up a command!

Page 16: Command Line Useage

Creating digital data

orHow to be a dig-grunt

Page 17: Command Line Useage

OUTLINE

• Digitizing

• Why we are doing it?

• What are we going to do?

• How are we going to do it?

Page 18: Command Line Useage

Data structures• There are only three data types

– point• user id in a poly cov

• point data ( i. e... wells)

– line– poly

Warning: You can’t mix poly and point data!Because A/I can’t tell the difference between labels and

points

Page 19: Command Line Useage

Coverages

• The data structure you will be making is called a coverage

• A coverage contains geographic and attribute data

• Part of the coverage is a folder called INFO.

• A workspace contains both coverages and an INFO folder

Page 20: Command Line Useage

INFO files

• The INFO folder is the key to a workspace.

• If a folder contains an INFO folder it is a Workspace

• Workspaces can be moved using DOS or Windows explorer operations

• Coverages CANNOT be moved except by the use of COPY in ARC

Page 21: Command Line Useage

File StructureF:

F:/HarryF:/JaneF:/Jones

F:/Jones/H20

F:/Jones/Info

F:/Jones/shore

F:/Jones/dock

F:/Jane/build

F:/Jane/street

F:/Harry/Srp

F:/Harry/tfd

F:/Harry/ejst

F:/Harry/stuff

root

F:/Jane/street/A2

F:/Jane/street/A2

F:/Jane/street/info

Page 22: Command Line Useage

File StructureF:

F:/HarryF:/JaneF:/Jones

F:/Jones/H20

F:/Jones/Info

F:/Jones/shore

F:/Jones/dock

F:/Jane/build

F:/Jane/street

F:/Harry/Srp

F:/Harry/tfd

F:/Harry/ejst

F:/Harry/stuff

root

F:/Jane/street/A2

F:/Jane/street/A2

F:/Jane/street/info

Page 23: Command Line Useage

The book “problem”

• Find site for laboratory

• Criteria– suitable soil– suitable landuse– >20m from streams– <= 300m of sewer– area >=2,000m2

Page 24: Command Line Useage

Data layers for the “book problem”

• Find site for laboratory

• Criteria– suitable soil soil cover poly– suitable landuse landuse cover poly– >20m from streams hydro cover arc– <= 300m of sewer sewer cover arc– area >=2,000m2 final product poly

Page 25: Command Line Useage

Sources of this data

– soil cover poly NRCS?– landuse cover poly Planning? NRCS?– hydro cover arc USGS– sewer cover arc City engineering

Page 26: Command Line Useage

Simplified Book Processlanduse

soil

Intersec t

soil & use OK

hydro

Page 27: Command Line Useage

Simplified Book Process

Select>= 2000

Erase-cov

Bufferstream

Intersec t

soil & use OK

landuse

soil

hydro

Page 28: Command Line Useage

Getting ready

• Format ZIP disk if necessary

• Follow the directions to move the “book” data from

CD to your zip drive –move the data directory from

the CD to the root of your zip

• Start Lesson 4

– Prepare paper map

– Tape map down on digitizer near the center

Page 29: Command Line Useage

Prepare the manuscript

• Tics numbered

• Start/stop points on all island polys

• Nodes marked on long arcs

• Boundary extended by 1/16”

Why: Because what you digitize will be clipped to fit within a surrounding coverage!

Existing data

YourMap

Your boundary will be clipped off

Page 30: Command Line Useage

Map on the digitizer• Some digitizers in the lab have a plastic sheet over the active

surface. Tape your map on top of the plastic sheet or you will

not be able to mark the “done” arcs are you go.

• Not marking as you go is a MAJOR BOO BOO!!!

• NOTE: You DO NOT have to put the map back in the same

place every time - A/I will adjust for map placement. That is

what registering TIC’s is all about.

Page 31: Command Line Useage

Putting the map on the digitizer

• Orientation does not matter

• Make it flat and tight

• BUT you must be within active zone of tablet

• Experiment to see where active zone is by watching the light on the digitizer as you move the cursor around.

Page 32: Command Line Useage

Starting Arc/Info

• Always start any of the arc programs (arcedit, arcplot, etc.) from ARC

• ARC is started from the icon on the left side of the screen or from Start Menu

• Can only be seen after you login– userid: FOR557– password: lagis

Page 33: Command Line Useage

First Incantation

• Launch Arc

• Go to folder: &WORKSPACE path

• Create a new workspace in that folderCREATEWORKSPACE name

• Move into the new workspace &WORKSPACE name

Page 34: Command Line Useage

Fire up ARCEDIT• When you start ArcInfo you will have a prompt like

– Arc:• Type arcedit• Specify which digitizer is hooked to your computer

– Digitizer 3400 Com1 -- for Calcomp digitizers– Digitizer ALTEK32 -- for LUCY– Digitizer 9100 Com1 -- for RERUN

• Follow book in creating a TICCOV• Use CREATE to make a new cover from the TICCOV into

which you are going to digitize data• NEVER, EVER digitize data into your TICCOV!!!

Page 35: Command Line Useage

Input from digitizer

• Start arcedit to edit the new coverage – Arcedit: edit [cover]– Arcedit: drawe all– Arcedit: draw

• You have to tell A/I where data is coming from– Type COORDINATE DIGITIZER

(or COO DIG) to tell arcedit data is coming from digitizer

– Use COO MOUSE | CURSOR for mouse input– Use COO KEYBOARD for keyboard input

Page 36: Command Line Useage

What is a TICCOV?

• A TICCOV is a special coverage which contains only TICs

• TICs are the spatial locators for the coverage• TICs have x,y coordinates

– table inches

– real world coordinates• Note: the name TICCOV is not Holy but is sort of standard. You

can use any name you want for a TICCOV - note the two uses of the word: a coverage name and a type of coverage!

Page 37: Command Line Useage

Creating a new coverage• Now you have to create a new coverage of TICs

only• After creating a workspace and doing

– arc: &Station 9999– arc: arcedit – arcedit: coo dig– arcedit: CREATE TICCOV1

– digitize a minimum of 4 tics

– Signal the end of tic input with TIC-ID = 0

1: CREATE will create a TICCOV out of whole cloth OR it will create a new coverage from an existing coverage (TICCOV)

Page 38: Command Line Useage

Inputting tics• Always hold puck same way and approach

the tics from same direction• You are going to

– enter the TIC-ID from the PUCK!!!– WAIT FOR THE ID TO APPEAR ON THE

SCREEN!!!!– if ID is wrong enter a B or a # to redo– IF OK enter an A or an *– NOW Pput the PUCK X-HAIRS over the tic

– Then press ANY KEY on the PUCK

Page 39: Command Line Useage

Done with tics?• Enter tic id 0 (zero) then press A or *

• Now you will be asked to enter corners of the data boundary or EXTENT– Click on upper right and lower left corners of

box (imaginary) enclosing data– This is called the BND or EXTENT of the

cover

• SAVE the coverage

Page 40: Command Line Useage

Paper

BND? EXTENT?

Extent of total book

data

TIC

Extent of your book

data

Your data goes in here

Page 41: Command Line Useage

Setting the drawing environment

• DRAWENVIRONMENT TIC IDS (DRAWE TIC IDS)

• DRAW

• Yup! two commands– DRAWE sets the draw environment (tics, arcs,

label points, etc. {or all})– DRAW draws that environment

Page 42: Command Line Useage

Create a real coverage• Type CREATE LANDDG01 TICCOV

– CREATE make new coverage from another

– DON’T digitize data into your TICCOV!• Re-enter tics (why?)• Accuracy! What if initial tics had error???• ARCEDIT will give RMS error - a comparison of the two

tic sets• If =< 0.005 you are OK

– if not OK do it again– if still not OK then error is in original, redo ORIG!!

Page 43: Command Line Useage

Editing environment• NODESNAP --- sets distance over which

nodes will be snapped and how they will be snapped– NODESNAP CLOSEST .05

• set features to be edited– EDITFEATURE ARC (EF ARC)

• set drawing environment– DRAWE ARC NODE LABELS IDS

Page 44: Command Line Useage

Now add the arcs

• What to do to with the arcs?????– ADD

– On each NODE press 2– On each vertex press 1– Pattern is 2 1 1 1 1 2, 2 1 1 1 2, 22,212– NOT 21111211122212– Press 9 on the puck when you are done.

1) vertex 2) node 3)4) del vertex 5)del arc 6)7) 8) 9) QUIT

Page 45: Command Line Useage

TRICKS

• BE CAREFUL!!!!!!!!!!!!!!!!!!!!!!!!!!!!

• MARK ARCS AS YOU DO THEM– duplicate arcs are a real PAIN to remove

• Use only enough vertices to define curves

• DO NOT use stream digitizing!!!

Page 46: Command Line Useage

More tricks• How to digitize - 2 methods

– Overshoot method• overshoot each arc intersection a wee bit

• use CLEAN to clean up the coveage– make intersections, delete dangles

– but this moves stuff around on you - ‘puter decides

– Node method• put a node at every arc intersection

• count on the snap distance to snap the nodes together

Page 47: Command Line Useage

Using Clean

• If you have data that looks like this then the best technique is to digitize the straight lines and let CLEAN put in the nodes

• Why? Because you cannot digitize a straight line if putting in nodes!

If you do it carefully then clean

will remove

the overshoots

also!

Page 48: Command Line Useage

Another technique

• Digitize the long straight lines and then split the arcs at the intersection points to put in nodes

• Now digitize the other lines and let the snap distance work to snap the nodes

Page 49: Command Line Useage

More tricks• Don’t wait to delete arc if you see it is

wrong!• Use the 5 option on the puck if just added• If is an old arc then quit ADD (9)• You are still in edit feature arc (STATUS)

– : SELECT– put x-hair on offending arc to select it (yellow)– : DELETE

• Do a few arcs and check, DELETE ALL if you are not happy and restart

Page 50: Command Line Useage

More tricks yet• Use the STATUS cmd to find out where you are

(try it, you’ll like it!)• To see if you have dangles

– drawe node dangle ; DRAW

• To move a node– EF NODE– MOVE– May have to set EDITDIST AND SNAPDIST

Page 51: Command Line Useage

WarningWarning• If you are careful you can do this in 3

hours

• If you are – sloppy and don’t pay attention to directions– didn’t read lesson before coming to lab

• It will take more than 3 hours

• In any case: get it done before next lab!!!