2009/10/11 Anthony :
> That's my point though. I'm not sure we should allow "proposed" or
> "historical" data unless and until OSM supports the features of
> traditional layers. Perhaps there is a way to be smarter about it
> (allow links between layers but warn when they are broken), but I'm
> n
On Sat, Oct 10, 2009 at 7:31 PM, Frederik Ramm wrote:
> Hi,
>
> Anthony wrote:
Even then, I have mixed feelings about it, until there's support in
the major editors for downloading and editing subsets of data.
>
>>> First of all, this would have to be supported by the API as well. A
Hi,
Anthony wrote:
>>> Even then, I have mixed feelings about it, until there's support in
>>> the major editors for downloading and editing subsets of data.
>> First of all, this would have to be supported by the API as well. And it is
>> always very difficult because "everything's connected".
On Sat, Oct 10, 2009 at 5:50 PM, Frederik Ramm wrote:
> Hi,
>
> Anthony wrote:
>>
>> Even then, I have mixed feelings about it, until there's support in
>> the major editors for downloading and editing subsets of data.
>
> First of all, this would have to be supported by the API as well. And it is
Hi,
Anthony wrote:
> Even then, I have mixed feelings about it, until there's support in
> the major editors for downloading and editing subsets of data.
First of all, this would have to be supported by the API as well. And it
is always very difficult because "everything's connected". Imagine yo
On Sat, Oct 10, 2009 at 4:41 PM, Randy Thomson wrote:
> Then you are proposing
>
> highway=planned
> planned=* (highway class)
>
> Is that correct? Sounds OK to me.
Make sure you get permission from the designer of the plans - in the
form of a release under CC-BY, CC-BY-SA, or into the public dom
6 matches
Mail list logo
