[OSM-dev] proposal to kill areas
ben at somethingmodern.com
Thu Jul 20 18:08:45 BST 2006
RENAME TABLE ways TO areas_and_ways;
ALTER TABLE areas_and_ways ADD is_area BOOLEAN;
CREATE VIEW ways AS SELECT [all but is_area]
FROM areas_and_ways WHERE is_area = FALSE;
CREATE VIEW areas AS SELECT [all but is_area]
FROM areas_and_ways WHERE is_area = TRUE;
On Thu, 20 Jul 06 @05:48pm, Nigel Magnay wrote:
> IMO - Sounds to me like an area is a subclass of way, with the
> constraint that the start and end node must be the same. The API
> should enforce this, but it doesn't neccesarily require separate
> On 20/07/06, Immanuel Scholz <immanuel.scholz at gmx.de> wrote:
> >> There are only 4 areas in OSM and osmarender treats certain tagged ways
> >> as an area. I figure it'd make the server simpler and make client area
> >> support simpler if 'area=true' on a way made it in to an area.
> >> Functionally, if they were working, an area is identical to a way
> >> already.
> >> Thoughts?
> >I am not very happy with an area defined as it is currently.
> >The problem I see is, that there are too many possibilities to specify an
> >ill-formed area.
> >I have no problem with deleting the 4 areas (probably test areas anyway?),
> >skip out the area feature from the server for now and maybe reopen the
> >brain storming for a different data structure solution.
> >Even if the current data structure is kept, I dislike the idea of
> >specifying an "area" as a parametrized kind of way.
> >Ciao, Imi
> >dev mailing list
> >dev at openstreetmap.org
> dev mailing list
> dev at openstreetmap.org
More information about the dev