Phil! and Kevin, I like everything said!
"Huge are tough to edit," yes. "Tie them all together with a super-relation to
show that they are together with certain tags," yes, or maybe. I'm kicking it
around, we are.
The C Trail does make for an interesting case. We might agree that
I like this idea, I would be happy to talk about StreetComplete and Vespucci.
12 Jul 2019, 23:10 by m...@rtijn.org:
> Hi all,
>
> Thanks for participating in the Virtual Mappy Hour this week! We had a record
> number of 16 participants (from as far away as Poland and Japan) and lively
>
Hi all,
Thanks for participating in the Virtual Mappy Hour this week! We had a record
number of 16 participants (from as far away as Poland and Japan) and lively
discussion on a variety of mappy topics. I enjoyed it very much and I hope you
did as well.
I will announce the next Mappy Hour
On Fri, Jul 12, 2019 at 9:36 AM Phil! Gold wrote:
> The "state at a time" pattern, as I have always understood it, exists to
> keep vastly distant objects from being linked with each other. It makes
> it much less likely for someone, say, updating I-95 in Florida to get an
> editing conflict
* stevea [2019-07-11 17:38 -0700]:
> I know it seems "like it just makes sense" to combine Maryland and DC
> relations, but there are rather deliberate reasons to keep these
> separate. One is state-level, the other is federal-level (is one), but
> the "state at a time for route relations" is a
Minh Nguyen wrote:
> As with the network tag on bus routes, what's important for both
> network and cycle_network is that the route is intended to form
> part of a coherent *network* (almost like a brand, but not quite).
It's also useful for those of us writing routers, as it means we can avoid
6 matches
Mail list logo
