2011/8/29 Michael Kugelmann :
> On 29.08.2011 12:46, Erik Johansson wrote:
>>
>> I wonder if someone has
>> some information material catered for this kind of audience?
>
> What about licence issues? According to my understanding, this is/was one of
> the reasons for the licence change from OSM to
On Tue, Aug 30, 2011 at 12:15 AM, Steve Bennett wrote:
> On Tue, Aug 30, 2011 at 12:07 PM, Anthony wrote:
>> +1. While I'd rather see these objects go away altogether, I think a
>> tag of "name=Melbourne;Geelong;South-Central NSW Area;Central Victoria
>> Area" on a closed way implies that this c
On Tue, Aug 30, 2011 at 12:07 PM, Anthony wrote:
> +1. While I'd rather see these objects go away altogether, I think a
> tag of "name=Melbourne;Geelong;South-Central NSW Area;Central Victoria
> Area" on a closed way implies that this closed way represents an area
> called "Melbourne;Geelong;Sout
On Mon, Aug 29, 2011 at 9:22 PM, Ian Sergeant wrote:
>
> Steve Bennett wrote on 30/08/2011 11:14:32 AM:
>
>> The same mechanism is used for Yahoo, Bing etc coverage. Yes, it's
>> debatable whether meta-objects should be stored in the OSM database,
>> but that debate would also extend to meta-tags
Steve Bennett wrote on 30/08/2011 11:14:32 AM:
> The same mechanism is used for Yahoo, Bing etc coverage. Yes, it's
> debatable whether meta-objects should be stored in the OSM database,
> but that debate would also extend to meta-tags (note=*, fixme=*)
When I encounter these "meta" ways/nodes w
On Tue, Aug 30, 2011 at 10:29 AM, Stephen Hope wrote:
> Particularly in this specific case, as nearmap coverage can't be used
> to derive OSM objects any more.
The same mechanism is used for Yahoo, Bing etc coverage. Yes, it's
debatable whether meta-objects should be stored in the OSM database,
b
On 30 August 2011 01:01, Tom Hughes wrote:
> Yes I should have added that, in this case, my preference would be to remove
> the object altogether as aerial imagery coverage areas are not real on the
> ground objects that should be in our database.
Particularly in this specific case, as nearmap co
On 29.08.2011 12:46, Erik Johansson wrote:
I wonder if someone has
some information material catered for this kind of audience?
What about licence issues? According to my understanding, this is/was
one of the reasons for the licence change from OSM to OBDL.
Best regards,
Michael.
On 29.08.2011 17:47, Andrei wrote:
Are we trying to do the impossible by importing the whole planet with
just 12Gb of RAM? Is there some trickery we can use to do the import
on this machine, or maybe another method we can use for the import?
A while ago I did import the planet on my windows ma
Martijn van Oosterhout gmail.com> writes:
>
> On 8 June 2011 17:11, Martijn van Oosterhout gmail.com> wrote:
> > Actually, it looks like it's breaking on the pending_ways query. It's
> > possible there's a lot of those, perhaps it's just running out of
> > memory there. The code was designed th
On 29/08/11 16:00, Martin Koppenhoefer wrote:
2011/8/29 Steve Bennett:
On Mon, Aug 29, 2011 at 7:03 PM, Tom Hughes wrote:
Thanks for the explanation. So I guess we should avoid using name=* on
anything which should not be rendered.
+1, IMHO it is also generally disputable to keep coverage-po
2011/8/29 Steve Bennett :
> On Mon, Aug 29, 2011 at 7:03 PM, Tom Hughes wrote:
> Thanks for the explanation. So I guess we should avoid using name=* on
> anything which should not be rendered.
+1, IMHO it is also generally disputable to keep coverage-polygons of
other data providers in the OSM m
On 29/08/11 15:45, Steve Bennett wrote:
On Mon, Aug 29, 2011 at 7:03 PM, Tom Hughes wrote:
It's always been the case that names sometimes get rendered for objects that
haven't been rendered, because the names are produced by separate rendering
rules and trying to attach to those rules a set of
On Mon, Aug 29, 2011 at 7:03 PM, Tom Hughes wrote:
> It's always been the case that names sometimes get rendered for objects that
> haven't been rendered, because the names are produced by separate rendering
> rules and trying to attach to those rules a set of filters which match the
> set of obje
> Have you tried folowing?
>
> h = 1/2*g*t^2
>
I think you may get into trouble for trying that technique on a tall
building!
I had heard about the android application, and am a bit sceptical about how
accurate it can be, but I suppose if you want to know if something is 50m or
100m tall it will b
Am 29.08.2011 14:32, schrieb maning sambale:
> Has anyone tried this?
> http://androidboy1.blogspot.com/2010/10/smart-measure-ver-10-manual.html
>
> Cool tool for 3d mapping. :)
Have you tried folowing?
h = 1/2*g*t^2
SCNR
;-)
--
Mit freundlichen Gruessen
Doru Julian Bugariu
signature.asc
Has anyone tried this?
http://androidboy1.blogspot.com/2010/10/smart-measure-ver-10-manual.html
Cool tool for 3d mapping. :)
--
cheers,
maning
--
"Freedom is still the most radical idea of all" -N.Branden
wiki: http://esambale.wikispaces.com/
bl
Maybe it is something for osm2pgsql to deal with ?
Yves
"SomeoneElse" a écrit :
>On 29/08/2011 09:44, Steve Bennett wrote:
>> I'm not sure if this is a recent change (or I've just noticed it), but
>> it seems that tags that don't contain anything recognisable to mapnik
>> other than a name are
I'm going to attend a book fair in Gothenburg were I'll walk around
telling people publishers about Openstreetmap, I wonder if someone has
some information material catered for this kind of audience?
Or examples of OSM used in books.
--
/emj
___
talk
On 29/08/2011 09:44, Steve Bennett wrote:
I'm not sure if this is a recent change (or I've just noticed it), but
it seems that tags that don't contain anything recognisable to mapnik
other than a name are getting rendered: http://osm.org/go/uG42g@6EB--
It's not a new thing, I don't think - in e
On 29/08/11 09:44, Steve Bennett wrote:
I'm not sure if this is a recent change (or I've just noticed it), but
it seems that tags that don't contain anything recognisable to mapnik
other than a name are getting rendered: http://osm.org/go/uG42g@6EB--
It's always been the case that names someti
I'm not sure if this is a recent change (or I've just noticed it), but
it seems that tags that don't contain anything recognisable to mapnik
other than a name are getting rendered: http://osm.org/go/uG42g@6EB--
That "Melbourne;Geelong..." label is on a way that defines the edge of
the Nearmap imag
22 matches
Mail list logo
