On Tue, Aug 30, 2011 at 12:15 AM, Steve Bennett stevag...@gmail.com wrote:
On Tue, Aug 30, 2011 at 12:07 PM, Anthony o...@inbox.org 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
Anthony wrote:
Sounds good. I don't think storing these in OSM, with the
non-overlapping tags, is harmful. While I'd love to see them in a
separate database or at least a separate layer, the fact of the matter
is that separate database and/or separate layer hasn't yet really been
implemented.
On Tue, Aug 30, 2011 at 3:36 AM, Lester Caine les...@lsces.co.uk wrote:
Anthony wrote:
Sounds good. I don't think storing these in OSM, with the
non-overlapping tags, is harmful. While I'd love to see them in a
separate database or at least a separate layer, the fact of the matter
is that
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
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
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
Maybe it is something for osm2pgsql to deal with ?
Yves
SomeoneElse li...@mail.atownsend.org.uk 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
On Mon, Aug 29, 2011 at 7:03 PM, Tom Hughes t...@compton.nu 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
2011/8/29 Steve Bennett stevag...@gmail.com:
On Mon, Aug 29, 2011 at 7:03 PM, Tom Hughes t...@compton.nu 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
On 29/08/11 16:00, Martin Koppenhoefer wrote:
2011/8/29 Steve Bennettstevag...@gmail.com:
On Mon, Aug 29, 2011 at 7:03 PM, Tom Hughest...@compton.nu 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
On Tue, Aug 30, 2011 at 10:29 AM, Stephen Hope slh...@gmail.com 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
Steve Bennett stevag...@gmail.com 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
On Mon, Aug 29, 2011 at 9:22 PM, Ian Sergeant iserg...@hih.com.au wrote:
Steve Bennett stevag...@gmail.com 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
On Tue, Aug 30, 2011 at 12:07 PM, Anthony o...@inbox.org 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
14 matches
Mail list logo
