Hello,
I'm trying to get an OSM group up and running in Los
Angeles. The former Southern California group, formerly operated by
ESRI, was going to shut down, but I thought I would see if I can get it going.
There are many exciting projects we could do, in addition to
learning
What about just combining the relations for selected states where the AT
crosses back and forth across the state border, like TN/NC and VA/WV?
On Mon, May 2, 2016 at 11:05 AM, Martijn van Exel wrote:
>
> > On May 2, 2016, at 9:49 AM, Mike N wrote:
> >
> > On
> On May 2, 2016, at 9:49 AM, Mike N wrote:
>
> On 5/2/2016 11:41 AM, Elliott Plack wrote:
>> This got me thinking, is there any specific need to have the route
>> broken up by state? Unlike interstate highways, where maintenance
>> changes across state lines, at the border,
On 5/2/2016 11:41 AM, Elliott Plack wrote:
This got me thinking, is there any specific need to have the route
broken up by state? Unlike interstate highways, where maintenance
changes across state lines, at the border, the AT maintenance is handled
by a trifecta of federal agencies and a
I've been doing some mapping along the Maryland portions of the Appalachian
Trail lately and noticed many issues along Maryland's section as well as
nearby Virginia and West Virginia where the route relations were not
continuous or overlapped other states'. Strava's slide has been quite
helpful in
Just to echo Steve’s comment on signs: encouraged but not required. Currently
just under 18% of the USBRS is signed. Budget is the issue, both at the state
and local (non state highway) level.
Kerry
From: OSM Volunteer stevea [mailto:stevea...@softworkers.com]
Sent: Sunday, May 1,
SteveA wrote:
> [Great Divide Mountain Bike Route]
> where MountainAddict keeps setting this to network=ncn
> when clearly it is network=icn (as it crosses the Canadian
> border in Alberta). A partial compromise/consensus
> solution has emerged: keep a duplicate relation synced as
>
7 matches
Mail list logo