Hi,
On Tue, Jun 07, 2011 at 09:00:20PM +0200, Stefan Keller wrote:
2011/6/6 Sarah Hoffmann lonvia@denofr.de wrote:
Using JXAPI now. That should work reliably. Restricting the request
Thanks for bringing this Taginfo Switzerland service to us!
We really need a Swiss XAPI.
To me XAPI has such a limited query syntax (assuming you mostly use something like this http://jxapi.openstreetmap.org/xapi/api/0.6/*%5Bkey=value]). What is the use case for the XAPI button? What are you doing with the raw OSM XML reponse?
In case of Taginfo if is really meant for correcting errors. You can load the raw XML into JOSM although the remote control ist much more confortable. You can also just have a look at it to further look at the tag combinations used.
Would it be also acceptable if there would be a webservice which would respond with a webmap of switzerland (instead of an OSM XML file)?
That can actually easily be done with some OpenLayers magick because OpenLayers allows to directly display the XML files. Interesting idea but nothing I would want to bother the global XAPI with.
Apart from this, I think there are a ton of uses for a Swiss XAPI even if it has limited capabilities. Benni could get the data for his public transport map easier, for example. And maybe there are other people who would want to experiment with very special data without having to process the entire Swiss extract. Even the pbf has now 80MB, nothing you want to download and process every day.
And, of course, it would be just fun to try. ;) The challenge is to maintain an up-to-date Swiss extract in the osmosis Postgresql DB.
Sarah