Quoting the.promena...@gmail.com:
One more question:
I'm still trying to figure out how the OSM tile-rendering server
loads its data - does it look first in 'relations', then to any
related ways and nodes (top-down), or does it load all data
indiscriminately based on geolocation?
Che
One more question:
I'm still trying to figure out how the OSM tile-rendering server loads its data
- does it look first in 'relations', then to any related ways and nodes
(top-down), or does it load all data indiscriminately based on geolocation?
Cheers,
Josef.
Hi,
> Can someone point me to an explanation/discussion about whether
> overlapping polygons are 'permitted' or not? I get a different answer
> every place I look, and I need to get this question out of the way
> before before I can even consider developing with OSM.
Overlapping polygons are defin
A simple question:
Can someone point me to an explanation/discussion about whether overlapping
polygons are 'permitted' or not? I get a different answer every place I look,
and I need to get this question out of the way before before I can even
consider developing with OSM.
Cheers,
Josef.
___
On Tue, Apr 19, 2011 at 8:48 PM, Ben Supnik wrote:
>
> But I do feel that the area as an OSM primitive is badly needed. Here
>> even _with_ external semantics it is sometimes difficult to determine
>> whether an OSM way represents a polyline or a closed polygon.
>>
>
> Agreed 100%. :-) If we en
Hi Igor,
Ah - now I get it. I would call these features perhaps "implicit
features", and I agree that it's important not to try to make too much
be explicit. The degenerate case would be creating a relation for the
result of every possible spatial DB query. :-)
At the same time, when it co
On Tue, Apr 19, 2011 at 8:04 PM, Ben Supnik wrote:
> Hi Igor,
>
>
> On 4/19/11 1:53 PM, Igor Brejc wrote:
>
> The way I plan to solve this is to leave to the user to tell the
>> renderer what kind of a feature she wants to draw and how to
>> construct the feature from OSM primitives. So for exam
Hi Igor,
On 4/19/11 1:53 PM, Igor Brejc wrote:
The way I plan to solve this is to leave to the user to tell the
renderer what kind of a feature she wants to draw and how to
construct the feature from OSM primitives. So for example:
* "Draw me a road network using OSM ways tagged with highway=m
On Tue, Apr 19, 2011 at 7:27 PM, Ben Supnik wrote:
>
> Of course, it may _still_ be up to the renderer to decide when to connect
> vs. not connect areas...I think under my distinctions here, the renderer
> would have discretion in case 3 to 'merge or not merge' but in cases 1 and
> 2, the correct
Hi Y'all,
On 4/19/11 1:14 PM, Igor Brejc wrote:
> I'm more and
more convinced something better is needed: OSM primitives represent
parts of the higher-level features and should be treated as such. Examples:
* A collection of road ways represent a road graph/network. Graph
vertices are
On Tue, Apr 19, 2011 at 3:15 PM, Jukka Rahkonen <
jukka.rahko...@latuviitta.fi> wrote:
>
> I would say that it is still rendered as an area but the fill is
> transparent and only outline coloured. Which brings to my mind another
> smallish problem with big real world area features which has been s
Hi all,
Earlier this month at FOSSGIS in Heidelberg there was quite some discussion
around working with the full history planet and easier ways to work with
historical OSM data through a 'history API'. Historical analysis becomes
more important for OSM for visualization, analysis and retracing van
Frederik Ramm wrote:
> Ben,
>
> On 04/19/11 13:29, Ben Supnik wrote:
>>> You explain "building=yes" as meaning "is it filled?", when in reality
>>> it is completely up to the renderer whether or not to fill an object
>>> that is tagged to be a building.
>>
>> Wait, I don't think I agree with this.
Hi,
On 04/19/11 13:59, Ben Supnik wrote:
Right...I think the original poster and myself are advocating that a
spatial notion of area be in the data model, but we are definitely NOT
arguing to take visualization decision making away from a renderer.
My main issue with the original poster was th
Hi Frederik,
On 4/19/11 7:53 AM, Frederik Ramm wrote:
It's a two-step thing. Of course you should be able to map the building
and say "this is an area". But the renderer might *still* choose not to
render it as an area (think e.g. of certain kinds of airspace which are
areas but you will usually
Ben,
On 04/19/11 13:29, Ben Supnik wrote:
You explain "building=yes" as meaning "is it filled?", when in reality
it is completely up to the renderer whether or not to fill an object
that is tagged to be a building.
Wait, I don't think I agree with this. That is, to me, the question of
whether
Hi Frederik,
On 4/19/11 4:13 AM, Frederik Ramm wrote:
You explain "building=yes" as meaning "is it filled?", when in reality
it is completely up to the renderer whether or not to fill an object
that is tagged to be a building.
Wait, I don't think I agree with this. That is, to me, the questi
Hi,
On 04/19/11 09:39, the.promena...@gmail.com wrote:
I made yet another suggestion here -
http://www.openstreetmap.org/user/ThePromenader/diary/13610 . Thanks for any
input.
Your suggestion does not suggest anything that has not already been
written in http://wiki.openstreetmap.org/wiki/T
Hello,
I made yet another suggestion here -
http://www.openstreetmap.org/user/ThePromenader/diary/13610 . Thanks for any
input.
Cheers,
Josef.
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
19 matches
Mail list logo
