XAPI is intended to provide capabilities that are not available with the
standard API. It is not intended to duplicate the API capabilities. So the
quick answer is use the API if you want to get a way by id.
The longer answer is that it could be implemented in XAPI fairly trivially,
and was
hi!
but XAPI is also intended to take load off the API, right? so it might
be a good idea to implement these simple query functions.
my 2cts
cheers
gerhard
gary68
On Tue, 2009-08-25 at 07:31 +0100, 80n wrote:
XAPI is intended to provide capabilities that are not available with
the
Gary68 schrieb:
hi!
but XAPI is also intended to take load off the API, right? so it might
be a good idea to implement these simple query functions.
actually, no. The XAPI was really written to answer types of queries
where the API would not cope, or the API was not made for (give me every
On Tue, Aug 25, 2009 at 9:05 AM, Gary68 g...@gary68.de wrote:
hi!
but XAPI is also intended to take load off the API, right? so it might
be a good idea to implement these simple query functions.
Yes, it does now help to take the load off the main API so there is some
sense in implementing
hi,
on API i can GET
http://www.openstreetmap.org/api/0.6/way/Id
using the same string on XAPI like
http://osmxapi.hypercube.telascience.org/api/0.6/way/38427403
results in firefox can't find the file...
initially I typed
http://www.informationfreeway.org/api/0.6/way/23328268 (other id,
5 matches
Mail list logo