<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ngày 3/11/09 8:48 PM, Paul Johnson viết:
<blockquote cite="mid:gp9t5t$k1k$1@ger.gmane.org" type="cite">
<pre wrap="">Spencer Riddile wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Chris,
What would the advantage/disadvantage be of using a different network
name ("usbrs" vs. "ncn") for U.S. bike routes. The author of open cycle
map would have to adjust their symbolization if we started using
"usbrs". Is it good to try to keep some international standard even
though trail and route systems may be different in various ways.
</pre>
</blockquote>
<pre wrap=""><!---->
Plus there are areas in the US that are already using the ncn/rcn/lcn
convention so cyclemap renders things properly. This breaks down pretty
nicely for cycleways that front US and Interstates as well as the 2
designated NCNs in the US (as ncn), state owned routes as rcn and city
and county maintained routes as LCN (such as the 40 Mile Loop and
Portland/Salem/Eugene's bicycle boulevards and city greenways).
</pre>
</blockquote>
Pennsylvania seems to be tagging trails as NCNs pretty extensively on
what probably aren't existing or proposed U.S. Bike Routes. [1] I'm
guessing that's to get the trails to appear more prominently at lower
zoom levels.<br>
<br>
[1] For example, BikePA Route S:
<a class="moz-txt-link-freetext" href="http://www.opencyclemap.org/?zoom=11&lat=40.18381&lon=-80.23126&layers=B000">http://www.opencyclemap.org/?zoom=11&lat=40.18381&lon=-80.23126&layers=B000</a><br>
<pre class="moz-signature" cols="72">--
Minh Nguyen <a class="moz-txt-link-rfc2396E" href="mailto:mxn@zoomtown.com"><mxn@zoomtown.com></a>
AIM: trycom2000; Jabber: <a class="moz-txt-link-abbreviated" href="mailto:mxn@1ec5.org">mxn@1ec5.org</a>; Blog: <a class="moz-txt-link-freetext" href="http://notes.1ec5.org/">http://notes.1ec5.org/</a></pre>
</body>
</html>