On 16/09/09 01:34, andrzej zaborowski wrote:
Let me post the link in this thread too, I think amf getway_history
call does exactly this, except there's nothing similar for relations.
http://svn.openstreetmap.org/sites/rails_port/app/controllers/amf_controller.rb
Curl won't be able to query
Tom Hughes wrote:
BTW do not code anything new that uses amf_controller - anything
which is can currently do that the XML API can't will have to be added
to the XML API for Potlatch 2 anyway as AMF controller will be going
away at that point.
Gah, Nabble ate my first reply to this.
On Wed, Sep 16, 2009 at 10:23 AM, Richard Fairhurst
rich...@systemed.net wrote:
Tom Hughes wrote:
BTW do not code anything new that uses amf_controller - anything
which is can currently do that the XML API can't will have to be added
to the XML API for Potlatch 2 anyway as AMF controller will
Hi,
Matt Amos wrote:
it would be nice to have the API operate in several different formats,
for reading and writing.
Is that not just another form of API bloat? Could people not offer any
format they want by writing either a proxy or, if they don't need write
access, a mirror server?
Bye
On Wed, Sep 16, 2009 at 12:30 PM, Frederik Ramm frede...@remote.org wrote:
Matt Amos wrote:
it would be nice to have the API operate in several different formats,
for reading and writing.
Is that not just another form of API bloat? Could people not offer any
format they want by writing
it would be nice to have the API operate in several different formats,
for reading and writing.
Is that not just another form of API bloat? Could people not offer any
format they want by writing either a proxy or, if they don't need write
access, a mirror server?
I don't know about Ruby on
Matt Amos wrote:
let's please try and avoid API bloat. as tom said, there are already
history calls in the api which give enough information for the client
to reconstruct all geometries of a way (at least as well as the server
can, at any rate).
these APIs are open for everyone to use,
On 16/09/09 12:51, Richard Fairhurst wrote:
I've never understood, though I'm an utter n00b at all of this, why there's
so much XML-specific code in our controllers. Shouldn't the controller send
the data out to the view, and the view render it as XML (or AMF, or JSON, or
the HTML data
On Wed, Sep 16, 2009 at 12:51 PM, Richard Fairhurst
rich...@systemed.net wrote:
Matt Amos wrote:
let's please try and avoid API bloat. as tom said, there are already
history calls in the api which give enough information for the client
to reconstruct all geometries of a way (at least as well
I'm working on a webapp that pulls way/node/relation history data from the
API and does its best to show it in a format that's a little easier to read
than the main openstreetmap.org website.
I've got the node history done for the most part (e.g.
On 15/09/09 18:49, Ian Dees wrote:
Next up are ways. This is pretty difficult, though, as a way's history
only shows the nodes that made up the way at that time, not which
revision of those nodes made up the way at the time. Is there a solution
for this or do I really need to get the full
On Tue, Sep 15, 2009 at 1:01 PM, Tom Hughes t...@compton.nu wrote:
On 15/09/09 18:49, Ian Dees wrote:
Next up are ways. This is pretty difficult, though, as a way's history
only shows the nodes that made up the way at that time, not which
revision of those nodes made up the way at the time.
On 15/09/09 19:05, Ian Dees wrote:
Ok, next question: is there a way to fetch full history for more than
one node at a time? I'd prefer to not have to either (a) download and
parse the full planet or (b) make tons of node/history queries to the
main API server.
Planet won't help as it
On Tue, Sep 15, 2009 at 1:22 PM, Tom Hughes t...@compton.nu wrote:
On 15/09/09 19:05, Ian Dees wrote:
Ok, next question: is there a way to fetch full history for more than
one node at a time? I'd prefer to not have to either (a) download and
parse the full planet or (b) make tons of
in ceratain timerange, but
not primitive versions?
-- Karl
Von: dev-boun...@openstreetmap.org [mailto:dev-boun...@openstreetmap.org] Im
Auftrag von Ian Dees
Gesendet: Dienstag, 15. September 2009 20:30
An: Tom Hughes
Cc: dev
Betreff: Re: [OSM-dev] Deep History App
On Tue, Sep 15, 2009
Hi,
Ian Dees wrote:
That's disappointing. Am I the only one that cares about this? With
permission I'd be happy to try and write something for the
openstreetmap.org http://openstreetmap.org site to make this feasible
and not kill the API frontend servers.
I am very much in favour of
On 15/09/09 19:29, Ian Dees wrote:
Planet won't help as it doesn't have history, and if you do try
scraping the history from the api you will find yourself blocked
as soon as I notice...
When someone changes a way by moving/deleting/adding nodes there's no
way to see what it
On 15/09/09 20:34, Frederik Ramm wrote:
I am very much in favour of supplying, and periodically updating, a full
OSM history dump. I think the main reasons why this is not being done
currently are
(a) nobody wrote a program for it
Very much so. I did try and prod somebody into doing it on
On Tue, Sep 15, 2009 at 2:55 PM, Tom Hughes t...@compton.nu wrote:
(b) any program that does get written would have to be engineered in a
clever way in order not to put too much strain on the data base and
still produce something consistent
I don't know that it needs to be particularly
On Tue, Sep 15, 2009 at 1:49 PM, Ian Dees ian.d...@gmail.com wrote:
I'm working on a webapp that pulls way/node/relation history data from the
API and does its best to show it in a format that's a little easier to read
than the main openstreetmap.org website.
I've got the node history done
On Tue, Sep 15, 2009 at 3:34 PM, Richard Weait rich...@weait.com wrote:
On Tue, Sep 15, 2009 at 1:49 PM, Ian Dees ian.d...@gmail.com wrote:
I'm working on a webapp that pulls way/node/relation history data from
the
API and does its best to show it in a format that's a little easier to
read
Ian Dees wrote:
On Tue, Sep 15, 2009 at 3:34 PM, Richard Weait rich...@weait.com
mailto:rich...@weait.com wrote:
On Tue, Sep 15, 2009 at 1:49 PM, Ian Dees ian.d...@gmail.com
mailto:ian.d...@gmail.com wrote:
I'm working on a webapp that pulls way/node/relation history data
Ian Dees wrote:
On Tue, Sep 15, 2009 at 3:34 PM, Richard Weait rich...@weait.com
mailto:rich...@weait.com wrote:
On Tue, Sep 15, 2009 at 1:49 PM, Ian Dees ian.d...@gmail.com
mailto:ian.d...@gmail.com wrote:
I'm working on a webapp that pulls way/node/relation history data
On Tue, Sep 15, 2009 at 4:44 PM, Andrew Ayre a...@britishideas.com wrote:
Doesn't like this one:
http://osm.mapki.com/history/way.php?id=20
Should be fixed now -- curl wasn't checking for HTTP error codes.
___
dev mailing list
On Tue, Sep 15, 2009 at 5:41 PM, Andrew Ayre a...@britishideas.com wrote:
Nice! However I expected the most recent way/node version to be on the left.
For the way example you have I need to scroll to view it.
Perhaps we can find a magical css trick to collapse everything but the
current and
Frederik Ramm wrote:
Hi,
Ian Dees wrote:
That's disappointing. Am I the only one that cares about this? With
permission I'd be happy to try and write something for the
openstreetmap.org http://openstreetmap.org site to make this feasible
and not kill the API frontend servers.
I don't
2009/9/15 Ian Dees ian.d...@gmail.com:
I'm working on a webapp that pulls way/node/relation history data from the
API and does its best to show it in a format that's a little easier to read
than the main openstreetmap.org website.
I've got the node history done for the most part (e.g.
2009/9/16 andrzej zaborowski balr...@gmail.com:
2009/9/15 Ian Dees ian.d...@gmail.com:
Next up are ways. This is pretty difficult, though, as a way's history only
shows the nodes that made up the way at that time, not which revision of
those nodes made up the way at the time. Is there a
andrzej zaborowski schrieb:
2009/9/16 andrzej zaborowski balr...@gmail.com:
2009/9/15 Ian Dees ian.d...@gmail.com:
Next up are ways. This is pretty difficult, though, as a way's history only
shows the nodes that made up the way at that time, not which revision of
those nodes made up the way
2009/9/16 Peter Körner osm-li...@mazdermind.de:
andrzej zaborowski schrieb:
2009/9/16 andrzej zaborowski balr...@gmail.com:
2009/9/15 Ian Dees ian.d...@gmail.com:
Next up are ways. This is pretty difficult, though, as a way's history
only
shows the nodes that made up the way at that time,
30 matches
Mail list logo
