Maptitude - http://research.umbc.edu/~roswell/maptitude.html
--------------------------- ListBot Sponsor --------------------------
Dial 800-555-TELL for FREE long-distance calls.
Tell your friends -- forward this message!
http://on.linkexchange.com/?ATID=27&AID=2144
----------------------------------------------------------------------
Peter has granted me permission to share this solution. I haven't tried it
yet (will do shortly), but it looks good. Later today I'll also be sharing
Armando's very helpful solution for copying street segments to a target
layer.
_________________________________________________________
Marjorie Roswell, Spatial Analyst
UMBC Center for Health Program Development and Management
1000 Hilltop Circle Fx: (410)455-6850
Baltimore, MD 21250 E: [EMAIL PROTECTED]
Ph: (410)455-6802 http://umbc.edu/~roswell/mipage.html
_________________________________________________________
---------- Forwarded message ----------
Date: Fri, 02 Feb 2001 10:38:19 -0500
From: Peter H. Van Demark <[EMAIL PROTECTED]>
To: Marjorie Roswell <[EMAIL PROTECTED]>
Margie:
Is the goal to tag street segments that are bike routes? If so, why do
they need to be in another layer? You can have a joined table, with a join
field (the ID of the street segment) and any other descriptive fields
(flag that the street segment is a bike route, or has a hazard, e.g.). It
is like a permanent selection set. to do this:
1. Select all the segments in the area containing the bike routes.
2. Use File-New to create a new table; check the Add Records box and add
matching records for the Streets dataview, using the selection set and the
ID field as the join field.
3. Set up your screen so you can see the map and the joined dataview; for
the former, create a theme that emphasizes the flagged segments; for the
latter, make sure the bike route flag field is handy and that the dataview
is only showing selected records.
4. Select street segments that are bike routes on the map.
5. Right-click the bike route flag column heading, choose Fill, and fill
the selected records with the flag of your choice. If there are other
fields to fill (e.g., all of these are on Route 1, so you want to fill a
route number field), do so now.
6. Repeat steps 4 and 5 until you are done. Then, in a dataview of just the
joined table, you can select all of the records which do not have a flag
and delete them, so the table just has records for bike route segments.
If you want to do another region, you can create a second table, and when
you are done with step 6 you can append it to the first table. While
Maptitude does not have an Append command, if the tables are fixed-format
ASCII you can use DOS or a text editor to merge them.
When you want to, you can export all of the flagged street segments to
their own geographic file.
One note: the ID in the Streets file is sequence number and not the
permanent TIGER record ID, so the IDs change from version to version of the
Streets file, and you can use this table only with the version of the
Streets file that you created it with. But, by then, you probably will have
Version 4.5, and be using the Merge Geography command to manage bike routes
in their own geographic file.
Peter
----------------------------------------------------------------
Peter Van Demark
Director of GIS Products and Training Phone: 617-527-4700
Caliper Corporation Fax: 617-527-5113
1172 Beacon Street E-mail: [EMAIL PROTECTED]
Newton MA 02461-9926 Web site: http://www.caliper.com
______________________________________________________________________
To unsubscribe, write to [EMAIL PROTECTED]
