On Fri, Jan 04, 2008 at 03:02:15PM +, Artem Pavlenko wrote:
What I could see working is something like this :
we define a standard interpolation method that turns a set of point
into
a sucession of bezier curves. (for an example see
On Sun, Feb 10, 2008 at 01:10:14PM +0100, Martijn van Oosterhout wrote:
This is beginning to get rather messy. TBH as a community not
rendering the area in question is the only bargaining chip we have. Or
slightly less extreme solution, drop the rendering of names. At the
end of the day
On Thu, Feb 28, 2008 at 02:44:06PM +0100, Frederik Ramm wrote:
The only thing I'd ask of editors is to support create_changeset
and then use the ID returned on subsequent edits. This, I believe, is
a small price to pay for the grouping advantages we would get.
Automatically creating one
On Fri, Mar 14, 2008 at 02:06:04AM +0100, Frederik Ramm wrote:
Merkaartor fully supports them (both in editing and rendering)
Good to know. So for a lake with an island, Merkaartor only requires
tags on the relation, and neither on the lake circumference way nor on
the island circumference
On Fri, Mar 14, 2008 at 03:32:45PM +, 80n wrote:
Sometimes this is unavoidable. Consider a commercial area
(landuse=commercial) surrounded by a residential area
(landuse=residential). It's not possible to create a single way that can be
used as the boundary for both these features as
Just to add some information : I got this 401 on deleting a node, but when I
redownloaded
the area, the node was gone. So it seems that the operation did go through
correctly...
cu bart
On Sun, Mar 23, 2008 at 09:29:49AM +0100, bvh wrote:
I am sometimes seeing 401 errors returned by the API
Chris Browet has been working on getting Yahoo map support in
Merkaartor. His first implementation downloaded tiles directly
from Yahoo. On advice from the OSM community we disabled this
since it was felt this would go against the Terms of Usage of Yahoo :
we had to use the flash of javascript API
On Fri, May 02, 2008 at 03:37:57PM +0100, Richard Fairhurst wrote:
The other one is that it would be good if the getway call, in
Just curious : what does this call actually do in fact?
cu bart
___
dev mailing list
dev@openstreetmap.org
OK, it seems yesterday a page went live on the wiki with a proposal
for the 0.6 api. It is advertised as going live half may and
seems to propose significant changesi with the disregard for the
needs for non-JOSM api users (potlatch is mentioned, for a change).
This time around the process
On Mon, May 05, 2008 at 11:04:32AM +0100, Tom Hughes wrote:
I agree that going forward is the right thing to do, but I also agree
with bvh that the announcement was made a bit clumsy in that it would
have been nice to mail a list of proposed changes to dev, rather than
put up a wiki page
On Mon, May 05, 2008 at 10:48:51AM -0400, Christopher Schmidt wrote:
Based on my reading, there is only one aspect of the changes in the API
that forces backwards incompabitibility: the requirement for the client
to generate a changeset before uploading and provide that changeset
identifier.
On Mon, May 05, 2008 at 07:05:01PM +0200, Martijn van Oosterhout wrote:
In other words, I think it's easier to get clients to support both
versions, than it is to get the server to support both.
That would be doable. Is there a 0.6 server instance running
against we can test and develop this?
On Tue, May 06, 2008 at 09:25:24AM +0100, SteveC wrote:
Without reference to the ongoing debate or the changeset stuff,
is there anything else that should be put in 0.6? Probably a good idea
to talk about it now.
Well, since 0.6 is all about giving us some tools to deal with
vandalism, has
On Wed, May 07, 2008 at 08:47:29AM +0200, Stefan Baebler wrote:
I propose to introduce the ability to limit the age of trackpoints
downloaded into the client by introducing an extra parameter age,
eg:
GET
/api/0.6/trackpoints?bbox=left,bottom,right,topage=ageInDayspage=pageNumber
+1!
On Sat, May 10, 2008 at 10:05:28PM +0200, Frederik Ramm wrote:
Look at how fossilized big projects like Debian have become, where
every slightest move requires ages just because they want to be
stable, professional, respect the established user base and so on.
That is a strawman. No one has
On Sun, May 11, 2008 at 07:35:57PM -0400, Christopher Schmidt wrote:
I've now got an api06 server running on dev:
http://api06.dev.openstreetmap.org/
This should let any client developers test against a server that should
be up/accessible from anywhere (and isn't hosted on my home
On Sun, May 11, 2008 at 09:55:22PM -0400, Christopher Schmidt wrote:
It looks like the main API and Potlatch have different ideas of what
should be done when a node is deleted which is a member of a way or
relation. Potlatch deletes the node from any way or relation that it is
a member of: the
On Wed, May 14, 2008 at 02:43:19PM +0100, Andrew Chadwick (email lists) wrote:
You _don't know_ where the edge of the rendered road will be but that
it'll lie within a certain zone. Thus you infect the edge of the abutted
area with that uncertainty, and for most buildings, fields, residential
On Wed, May 14, 2008 at 04:41:34PM +0200, Marcus Wolschon wrote:
GPS-devices are very, very good at providing correct coordinates
relative to the rest of the track. They are getting good at giving
the same coordinates twice, when walking the same road again a few
days later.
Thus small
On Wed, May 14, 2008 at 08:21:45PM -0400, Christopher Schmidt wrote:
There is one other new-style piece of information which is only
applicable to changeset-uploading: the 'old id', the placeholder ID with
which 'create' objects were uploaded. I think that 'old_id' is
appropriate for this.
On Wed, May 14, 2008 at 09:20:57PM -0400, Christopher Schmidt wrote:
One of the bigger changes in the 0.6 API from an implementation
perspective for clients may well be the use of a content body on DELETE
requests. kleptog found that to be the most difficult part of
implementing the
On Thu, May 15, 2008 at 08:30:08AM +0200, Martijn van Oosterhout wrote:
So, we specced out what you would need for a changeset download,
invented old_version and new_version and then used old_version
everywhere we needed it. If we do it your way then we would get
old_version and version for
On Thu, May 15, 2008 at 09:10:42AM +0200, Martijn van Oosterhout wrote:
I'm not talking abot diff upload responses, I'm talking about
changeset downloads. Say I note that object 123 was modified in
changeset 456 six weeks ago. And I go to the API and say: show me
everything done in changeset
On Thu, May 15, 2008 at 09:02:04AM +0100, Tom Hughes wrote:
But isn't old_version+1 always equal to version?
Under the current plan, yes. We didn't think it was reasonable to
push that assumption down to the clients thought.
Why would that be unreasonable? In what (futuristic) scenario would
On Thu, May 15, 2008 at 11:31:13AM +0200, Frederik Ramm wrote:
Under the current plan, yes. We didn't think it was reasonable to
push that assumption down to the clients thought.
Why would that be unreasonable? In what (futuristic) scenario would
version numbers not increment monotonically
On Thu, May 15, 2008 at 12:02:39PM +0100, Dave Stubbs wrote:
On Thu, May 15, 2008 at 11:31:13AM +0200, Frederik Ramm wrote:
It is also possible to change the same object multiple times within the
same changeset, so one single changeset might catapult the object
version from 1 to 15.
Is
On Thu, May 15, 2008 at 07:18:30AM -0400, Christopher Schmidt wrote:
But one of them will be accepted first and the other will later
be judged as sufficiently different, right? So the actually history
in the database will have two transitions, one from v1 to v2 and
the other from v2 to v3.
On Thu, May 15, 2008 at 01:26:56PM +0200, Frederik Ramm wrote:
The most usable type of response for the user would certainly be:
As a result of this changeset, Object X was changed from state A to
state B.
As a user, I am not interested in the 318 intermediate editing steps;
I want to
On Thu, May 15, 2008 at 02:20:42PM +0200, Frederik Ramm wrote:
If you wanted raw access, then you can have it - just download the
history of every object. You can do that even now.
Changesets are introduced to lessen the complexity. We want one big
edit, ideally associated with a comment
On Thu, May 15, 2008 at 05:45:22PM +0200, Frederik Ramm wrote:
I was not aware this is also a server
load issue. And frankly if this is about server load then there
are better ways to mitigate that like rewriting the map call as
a C/C++ apache module...
The map call is not involved.
No,
On Thu, May 15, 2008 at 06:45:01PM +0200, Frederik Ramm wrote:
Out of interest, why's that a bad thing? We have several editors, for
example: each of them works differently and presents information
differently. Why do we have to have One True Rollback?
We have enough trouble as it is
Hi,
deleting a node on the api06 instance that crschmidt is running
on dev results in a 500 internal server error. The log file
(~crschmidt/api06/log/development.log) complains about
ActionController::MissingTemplate (Missing template node/delete.html.erb
in view path
Hi,
The current 'documentation' for merkaartor is just some bunch of static
html files that I host on my personal website. As a result it is
badly lacking. Sven Lanke approached me with the idea to keep the
documentation inside subversion, which then gets checked out on the
web server so that it
On Sat, Jul 12, 2008 at 07:20:15PM +0200, Jochen Topf wrote:
The current 'documentation' for merkaartor is just some bunch of static
html files that I host on my personal website. As a result it is
badly lacking. Sven Lanke approached me with the idea to keep the
documentation inside
On Thu, Aug 21, 2008 at 01:26:22AM +0200, Sascha Silbe wrote:
As you might have guessed both solutions do not work. Or at least not
good enough for my taste. I would like a simple (or at least fast)
solution.
As part of a new namefinder (not completed yet), I've written a custom
On Mon, Sep 22, 2008 at 12:10:40PM +0100, David Earl wrote:
This is the first discussion I can remember on these lists about this
issue. There's no flashing lights on the website that says the info from
Garmin receivers is lacking. You've only mentioned vaguely algorithms
exist to make use
On Thu, Oct 09, 2008 at 04:34:37PM +1000, Hugh Barnes wrote:
Spurred on by this, I tried it in Merkaartor. The UI accepted my input and I
assumed all was good. I just remembered to follow this up and it appears the
data didn't make it. Possibly the last occurrence of the tag in the app was
37 matches
Mail list logo
