[ First Message Last
| Table of Contents
| <- Digest ->
| Search
Archive Index
| <-
Browser ->
]
------------------------------
[ Message 1 -> end
| Table of Contents
| <- Digest 970316 ->
| Search
Archive Index
| <-
Browser ->
]
Date: Sat, 15 Mar 1997 03:34:47 -0500
From: Chris Marsden <Byway@compuserve.com>
Subject: Database info
Alan, Don and all,
GREEN LANE DATABASE
Description of fields used in an Excel database. I have found this to be
optimum for my use. Comments welcome and a sample can be provided if reqd.
This is for one 100km sq only, SO sq. (There would be about 22 to cover
the whole of England & Wales, if based on the 100km sq.)
Chris
Ref No. (2col) 4 digit NGR ref of Western end. (As described separately)
S/N 5th digit x0.1, (only reqd if two + routes start in same
1km sq.)
Duplicate ref? A field I use to see if identical to previous entry
(n) Northings of Western end.
To (e) Eastings of Eastern end.
(n) Northings of Eastern end.
SLD (m) Straight Line distance, calculated from above fields
Home DX km How far from a given grid reference. (Calculated)
NAME Council's or own name for a route.
Cnty No. County Rd No. or Byway reference.
pf Map No. First two digits of map ref i.e. 971 (SO26/36) is 26.
Cnty H.A./County Council (2 digit code)
Type UCR, BOAT, RUPP, No Status, etc.
Code Code Letter to indicate obstruction, TRO, impassable
Skill Ease of driving, or special requirements
Heritage Historic or scenic value
Seasonal Seasonal restrictions to passage.
Future Further action required. (Clearance, research etc.)
Driven Dates driven, for user evidence.
Condition & Descrp. Free text for brief notes.
Code
XM out of Mtce (i.e. Washed out, undergrowth)
XO Obstructed (i.e Fenced, locked gate, bollards)
XG overGrown (i.e. side growth-landowners resp.)
XR Rubbish (Local authorities resp.)
(X means undrivable, other Codes could indicate VR, TRO, Partly obstructed,
etc.)
Skill
1 Surfaced Road, a normal car should be able to use
2 A more robust and larger ground clearance vehicle can use with
negligible risk of damage to vehicle.
3 A Single 4WD should be able to complete with minimal risk
4 Scratches may occur, a new Discovery may baulk at this route.
5 Should not be attempted with a single vehicle.
6 High Lift Jack, and other recovery equipment may be required.
7 Passable at times, body damage could occur, advanced skills
required.
8 Impossible to Drive with any twin track Vehicle
9 Impossible to Drive with any Vehicle
Heritage
1 Of minimal scenic or Heritage value.
9 Of utmost importance to preserve.
Seasonal
A All Seasons, firm surface.
B May be slippery in Wet.
C Convoy of 2 or more vehicles recommended
D Damage may occur to route, so AVOID IN WET.
------------------------------
[ <- Message 2 -> end
| Table of Contents
| <- Digest 970316 ->
| Search
Archive Index
| <-
Browser ->
]
From: TimLARA@aol.com
Date: Sat, 15 Mar 1997 12:00:16 -0500 (EST)
Subject: An idea for coding RoW details: Comments please
An idea for coding green road conditions
A Archeological interest (historic route or surroundings)
B Boggy (ie peat), BB passable only by light motorcycle, BBB seriously boggy
C Concrete surface in part
D Dirt surface, grassed over, DD bare earth in places
E Easy, useable with ordinary vehicles, ideal for use by beginners
F Ford generally passable (10cm), FF difficult ford, FFF deep or swift ford
G Gates (one G per gate), width in metres if less than 2m
H Holes, use with special care, HH dangerous holes
I Irate landowner, black spot, etc
J Junction with another unsurfaced vehicular route
K Keep (of alternatives, use <^>v symbols)
L Lost, hard to find the way or easy to go astray
M Muddy (ie clay), MM passable in wet weather only by light vehicles MMM
avoid in wet weather
N Narrow, (under 2m) give width in metres
O Obstructed or blocked (not by vegetation), give usable width in metres
P Popular with other users (avoid on bank holidays) PP always popular
Q Quiet when passing habitation, church, etc
R Rocks (skull size or bigger) and irregular ground-rock
S Steep (causes traction problems, 1 in 5 or steeper) SS if surface is loose
or slippery
T Tarmac surface in part
U Under- and over-growth
V Symbol for south, use with < ^ >
W Wildlife interest (eg badgers, kites, orchids), stick carefully to route,
WW=SSSIetc
X TRO, Voluntary Restraint, or similar restriction
Y Young children, so special care
Z Limited headroom (metres)
Start the description from the end with the lower grid reference number,
use symbols <^>v to indicate compass direction.
Example: Arncliffe Cote, YDNP:
G,J,D,G,F,L,D,G(1),DD,G(1.2),N(1),R,H,G,A^,F,D,G,T,Q
Tim Stevens, LARA Information Officer 1997
------------------------------
[ <- Message 3 -> end
| Table of Contents
| <- Digest 970316 ->
| Search
Archive Index
| <-
Browser ->
]
Date: Sat, 15 Mar 97 21:41 GMT0
From: srawlings@cix.compulink.co.uk (Stephen Rawlings)
Subject: Re: An idea for coding RoW details: Comments please
Nice, I like it. Possibly needs reducing somewhat:-)
Steve Rawlings
------------------------------
[ <- Message 4 -> end
| Table of Contents
| <- Digest 970316 ->
| Search
Archive Index
| <-
Browser ->
]
Date: Sat, 15 Mar 1997 21:16:54 +0000
From: Peter Bradley <hm50@dial.pipex.com>
Subject: Re: An idea for coding RoW details: Comments please
Tim
(resending)
> An idea for coding green road conditions
> A Archeological interest (historic route or surroundings)
> B Boggy (ie peat), BB passable only by light motorcycle, BBB seriously boggy
> C Concrete surface in part <snip>
> Example: Arncliffe Cote, YDNP:
> G,J,D,G,F,L,D,G(1),DD,G(1.2),N(1),R,H,G,A^,F,D,G,T,Q
> B Boggy (ie peat), BB passable only by light motorcycle, BBB seriously boggy
That looks very comprehensive to me. It's giving a lot
of information in just one shortish line. 2 or 3 minutes
to decode it is not a problem. With regular use we'd all
soon get used to the codes.
I like it.
Peter Bradley
------------------------------
[ <- Message 5 -> end
| Table of Contents
| <- Digest 970316 ->
| Search
Archive Index
| <-
Browser ->
]
Date: Sat, 15 Mar 1997 17:12:46 -0500
From: Chris Marsden <Byway@compuserve.com>
Subject: An idea for coding RoW details: Comments please
A D I J L N 3G 0.9m P S W Y Z 1.9m
And thats just to the Bedroom!
------------------------------
[ <- Message 6 -> end
| Table of Contents
| <- Digest 970316 ->
| Search
Archive Index
| <-
Browser ->
]
END OF * LIST DIGEST
Input: messages 5 lines 211 [forwarded 11 whitespace 40]
Output: lines 223 [content 115 forwarded 11 (cut 0) whitespace 38]
[ First Message
| Table of Contents
| <- Digest 970316 ->
| Search
Archive Index
| <-
Browser ->
]