Forwarding to list ...
Original Message
Subject:Re: [OSM-dev] Chopped of ways. New flag for OSM XML?
Date: Fri, 15 Aug 2008 06:21:14 +0200
From: Rogier Wolff [EMAIL PROTECTED]
Organisation: BitWizard.nl
To: Brett Henderson [EMAIL PROTECTED]
References:
snip
I'm not sure if I understand things fully, but I thought that e.g. for
offline editing you can request the map data about an area from the
mapserver. Say 45.5N to 45.7N, 4.3E to 4.4E.
Now while exporting from the database, the question is: What do you
do with ways that are only
On Fri, Aug 15, 2008 at 06:28:04AM -0700, Karl Newman wrote:
Those need to be marked in a way that won't interfere with current use
of those ways, as well as inform interested parties/programs that a
more complete way is available on the server.
My personal choice would be to move
On Fri, Aug 15, 2008 at 6:52 AM, Rogier Wolff [EMAIL PROTECTED]wrote:
On Fri, Aug 15, 2008 at 06:28:04AM -0700, Karl Newman wrote:
Those need to be marked in a way that won't interfere with current use
of those ways, as well as inform interested parties/programs that a
more complete way
On Fri, Aug 15, 2008 at 07:04:11AM -0700, Karl Newman wrote:
The suggestion was to mark the version of the entity as negative. The
version attribute does not yet exist but is proposed for the upcoming 0.6
API. Making it negative would prevent it from being uploaded because the
server would
On Fri, Aug 15, 2008 at 7:28 AM, Rogier Wolff [EMAIL PROTECTED]wrote:
On Fri, Aug 15, 2008 at 07:04:11AM -0700, Karl Newman wrote:
The suggestion was to mark the version of the entity as negative. The
version attribute does not yet exist but is proposed for the upcoming 0.6
API. Making it
On Fri, Aug 15, 2008 at 07:59:07AM -0700, Karl Newman wrote:
Making some parameter negative to mean this object is incomplete
sounds like a hack to me. It's something that you might do in an
internal database, or in an in-memory datastructure, but it should not
be in an API. Not ever. It's
7 matches
Mail list logo
