Hi guys,
I haven't looked at the monuments api [1] that closely for a while so I was pleasantly surprised when I took a good look at it yesterday and noticed a lot of things were already implemented :-) I want to do some follow ups after the May meeting [2]. I'm sending this directly because I'm not sure all of you are keeping a close eye on the Wiki Loves Monuments mailing list. What features still need to be added and how do we make it easy for everyone to make use of this api? I have some things: * DynamicKML seems to work. Bit rough, but seems to be working in Google Maps [3] and Earth - Tim, can you try to get dynamickml [4] working in OpenStreetMap? - Platonides, would it be possible to implement a sort by random? That prevents clusters * Raul implemented Layar [5]. Is this part of the api or on it's own Raul? Can you maybe tell a bit more about this? * I believe JSON(P) still needs to be implemented. That makes reuse easier. Anyone? * Joan has been working on HTML lists [6]. This might turn into an easy tool to make lists of monuments you want to take a photo of. Keep us posted Joan! * api.wikilovesmonuments.eu seems to be a good domain to host this api from. I'll see if I can get this setup at the toolserver * gpx and poi also need to be implemented. Anyone? (please add more points)
The goal of the api should be to provide a easy but powerful tool that all countries can use. We're going in the right direction now.
Keep up the good work!
Maarten
[1] http://toolserver.org/~erfgoed/api/api.php [2] https://secure.wikimedia.org/wikipedia/commons/wiki/Commons:Wiki_Loves_Monum... [3] http://maps.google.nl/maps?q=http:%2F%2Ftoolserver.org%2F~erfgoed%2Fapi%2Fap... [4] http://toolserver.org/~erfgoed/api/api.php?action=search&format=dynamick... [5] http://owlz.org/?url=http://toolserver.org/~erfgoed/layar/location.html [6] http://toolserver.org/~erfgoed/api/api.php?action=search&format=html
Hi,
I already began some work in a feature I believe it would be interesting, a kind of a trip planner. For those not in the chat, it's a web tool in which "points" can be added. i.e., if you are travelling to Barcelona, add all monuments near the hotel where you are staying. But say that then you're going to Tarragona, so add the monuments in that city. And so on.
The tool then generates HTML/PDF output ready to print. It could be brought during the trips and make it easier to photograph the maximum number of monuments. A kind of high level interface to the API.
By the way, if the API is hosted on wikilovesmonuments.eu, will you just change the nameservers and make it point to the Toolserver API or will the whole database be moved there?
Joan.
2011/7/27 Maarten Dammers maarten@mdammers.nl
Hi guys,
I haven't looked at the monuments api [1] that closely for a while so I was pleasantly surprised when I took a good look at it yesterday and noticed a lot of things were already implemented :-) I want to do some follow ups after the May meeting [2]. I'm sending this directly because I'm not sure all of you are keeping a close eye on the Wiki Loves Monuments mailing list. What features still need to be added and how do we make it easy for everyone to make use of this api? I have some things:
- DynamicKML seems to work. Bit rough, but seems to be working in Google
Maps [3] and Earth
- Tim, can you try to get dynamickml [4] working in OpenStreetMap?
- Platonides, would it be possible to implement a sort by random? That
prevents clusters
- Raul implemented Layar [5]. Is this part of the api or on it's own Raul?
Can you maybe tell a bit more about this?
- I believe JSON(P) still needs to be implemented. That makes reuse easier.
Anyone?
- Joan has been working on HTML lists [6]. This might turn into an easy
tool to make lists of monuments you want to take a photo of. Keep us posted Joan!
- api.wikilovesmonuments.eu seems to be a good domain to host this api
from. I'll see if I can get this setup at the toolserver
- gpx and poi also need to be implemented. Anyone?
(please add more points)
The goal of the api should be to provide a easy but powerful tool that all countries can use. We're going in the right direction now.
Keep up the good work!
Maarten
[1] http://toolserver.org/~**erfgoed/api/api.phphttp://toolserver.org/~erfgoed/api/api.php [2] https://secure.wikimedia.org/**wikipedia/commons/wiki/** Commons:Wiki_Loves_Monuments_**2011/May_Meeting/Notes/Techhttps://secure.wikimedia.org/wikipedia/commons/wiki/Commons:Wiki_Loves_Monuments_2011/May_Meeting/Notes/Tech [3] http://maps.google.nl/maps?q=**http:%2F%2Ftoolserver.org%2F~** erfgoed%2Fapi%2Fapi.php%**3Faction%3Dsearch%26format%**3Ddynamickmlhttp://maps.google.nl/maps?q=http:%2F%2Ftoolserver.org%2F~erfgoed%2Fapi%2Fapi.php%3Faction%3Dsearch%26format%3Ddynamickml [4] http://toolserver.org/~**erfgoed/api/api.php?action=** search&format=dynamickmlhttp://toolserver.org/~erfgoed/api/api.php?action=search&format=dynamickml [5] http://owlz.org/?url=http://**toolserver.org/~erfgoed/layar/** location.htmlhttp://owlz.org/?url=http://toolserver.org/~erfgoed/layar/location.html [6] http://toolserver.org/~**erfgoed/api/api.php?action=** search&format=htmlhttp://toolserver.org/~erfgoed/api/api.php?action=search&format=html
Hello Maarten, dynamickml has some disadvantages/missing things to my version [1] (mostly created by multichill): *declustering by random (also not perfect, because not stable) *different icons for different object types-- *detectable if an image exist or not
As long this is so I see no reason to change to dynamickml.
Greetings Tim
P.S.: I have not the time to follow the mailing list but I will help where I can if somebody ask me.
[1] http://toolserver.org/~kolossos/wlm/getMonument-source.php
Am 27.07.2011 22:45, schrieb Maarten Dammers:
- Tim, can you try to get dynamickml [4] working in OpenStreetMap?
[4] http://toolserver.org/~erfgoed/api/api.php?action=search&format=dynamick...
Hi Tim,
Op 28-7-2011 22:06, Tim Alder schreef:
Hello Maarten, dynamickml has some disadvantages/missing things to my version [1] (mostly created by multichill): *declustering by random (also not perfect, because not stable)
I asked Platonides to have a look at this.
*different icons for different object types--
I changed it to blue and yellow icons.
*detectable if an image exist or not
On Commons? We just assume it does at Commons.
As long this is so I see no reason to change to dynamickml.
Maybe you can produce a OSM snippet people can use. At http://www.wikilovesmonuments.nl/monumenten/ we now use Google Maps.
Maarten
Greetings Tim
P.S.: I have not the time to follow the mailing list but I will help where I can if somebody ask me.
[1] http://toolserver.org/~kolossos/wlm/getMonument-source.php
Am 27.07.2011 22:45, schrieb Maarten Dammers:
- Tim, can you try to get dynamickml [4] working in OpenStreetMap?
[4] http://toolserver.org/~erfgoed/api/api.php?action=search&format=dynamick...
Hello together, there is now a OSM-map that use ~erfgoed/api/api.php: http://toolserver.org/~kolossos/wlm/wlm-on-osm_api.php?zoom=13&lat=52.38...
Parameters format=kml, srcountry=nl and srlang=nl are hardcoded in the moment.
Greetings Kolossos
Am 28.08.2011 23:30, schrieb Maarten Dammers:
Hi Tim,
Op 28-7-2011 22:06, Tim Alder schreef:
Hello Maarten, dynamickml has some disadvantages/missing things to my version [1] (mostly created by multichill): *declustering by random (also not perfect, because not stable)
I asked Platonides to have a look at this.
*different icons for different object types--
I changed it to blue and yellow icons.
*detectable if an image exist or not
On Commons? We just assume it does at Commons.
As long this is so I see no reason to change to dynamickml.
Maybe you can produce a OSM snippet people can use. At http://www.wikilovesmonuments.nl/monumenten/ we now use Google Maps.
Maarten
Greetings Tim
P.S.: I have not the time to follow the mailing list but I will help where I can if somebody ask me.
[1] http://toolserver.org/~kolossos/wlm/getMonument-source.php
Am 27.07.2011 22:45, schrieb Maarten Dammers:
- Tim, can you try to get dynamickml [4] working in OpenStreetMap?
[4] http://toolserver.org/~erfgoed/api/api.php?action=search&format=dynamick...
Hi Tim,
Op 31-8-2011 20:04, Tim Alder schreef:
Hello together, there is now a OSM-map that use ~erfgoed/api/api.php: http://toolserver.org/~kolossos/wlm/wlm-on-osm_api.php?zoom=13&lat=52.38...
Good job!
Parameters format=kml, srcountry=nl and srlang=nl are hardcoded in the moment.
Could you just remove the hard coded language and country? Or even better: Make it possible to pass along these variables. Could you add a default view/point (when you give no parameters) somewhere in Europe? It now ends up somewhere under Africa (lat=0 & lon=0). Can you put your code at /home/project/e/r/f/erfgoed/public_html/osm/index.php ? That makes it possible to reach it at http://toolserver.org/~erfgoed/osm/
Maarten
Greetings Kolossos
Am 28.08.2011 23:30, schrieb Maarten Dammers:
Hi Tim,
Op 28-7-2011 22:06, Tim Alder schreef:
Hello Maarten, dynamickml has some disadvantages/missing things to my version [1] (mostly created by multichill): *declustering by random (also not perfect, because not stable)
I asked Platonides to have a look at this.
*different icons for different object types--
I changed it to blue and yellow icons.
*detectable if an image exist or not
On Commons? We just assume it does at Commons.
As long this is so I see no reason to change to dynamickml.
Maybe you can produce a OSM snippet people can use. At http://www.wikilovesmonuments.nl/monumenten/ we now use Google Maps.
Maarten
Greetings Tim
P.S.: I have not the time to follow the mailing list but I will help where I can if somebody ask me.
[1] http://toolserver.org/~kolossos/wlm/getMonument-source.php
Am 27.07.2011 22:45, schrieb Maarten Dammers:
- Tim, can you try to get dynamickml [4] working in OpenStreetMap?
[4] http://toolserver.org/~erfgoed/api/api.php?action=search&format=dynamick...
Am 31.08.2011 20:20, schrieb Maarten Dammers:
Could you just remove the hard coded language and country? Or even better: Make it possible to pass along these variables.
Done. Example objects in Austria: http://toolserver.org/~kolossos/wlm/wlm-on-osm_api.php?zoom=7&lat=47.949... Same with srlang, but doesn't work. Is there a i18n planned.
Could you add a default view/point (when you give no parameters)
Done. Amsterdam (somewhere in Europe ;-)).
Can you put your code at /home/project/e/r/f/erfgoed/public_html/osm/index.php ? That makes it possible to reach it at http://toolserver.org/~erfgoed/osm/
No. I have no write-access to this folder but each project member can copy my folder. Keep this script in my directory shouldn't be also no problem.
Greetings Tim
Maarten
2011/8/31 Tim Alder tim.alder@s2002.tu-chemnitz.de:
Am 31.08.2011 20:20, schrieb Maarten Dammers:
Could you just remove the hard coded language and country? Or even better: Make it possible to pass along these variables.
Done. Example objects in Austria: http://toolserver.org/~kolossos/wlm/wlm-on-osm_api.php?zoom=7&lat=47.949...
10x 1e+100 :)
Done. Example objects in Austria:
http://toolserver.org/~kolossos/wlm/wlm-on-osm_api.php?zoom=7&lat=47.949...
Same with srlang, but doesn't work. Is there a i18n planned.
That is awesome. Thanks Tim.
Is there a way to embed it in a iframe for the websites ?
Tim Alder wrote:
Am 31.08.2011 20:20, schrieb Maarten Dammers:
Could you just remove the hard coded language and country? Or even better: Make it possible to pass along these variables.
Done. Example objects in Austria: http://toolserver.org/~kolossos/wlm/wlm-on-osm_api.php?zoom=7&lat=47.949...
Same with srlang, but doesn't work. Is there a i18n planned.
Could you add a default view/point (when you give no parameters)
Done. Amsterdam (somewhere in Europe ;-)).
Can you put your code at /home/project/e/r/f/erfgoed/public_html/osm/index.php ? That makes it possible to reach it at http://toolserver.org/~erfgoed/osm/
No. I have no write-access to this folder but each project member can copy my folder. Keep this script in my directory shouldn't be also no problem.
? You are a member of the erfgoed group. You can as well as any of us.
I made it a symlink to your folder
http://toolserver.org/~erfgoed/wlm/wlm-on-osm.php?zoom=7&lat=47.94971&am...
Still, I think it would be good that you moved it into svn and have a real copy there.
Greetings
Hallo,
layar script is on it's own, it uses modified classes from lightrod.org * https://svn.toolserver.org/svnroot/p_erfgoed/layar/ * https://svn.toolserver.org/svnroot/p_erfgoed/prox_search/ * https://svn.toolserver.org/svnroot/p_erfgoed/api/includes/clsBasicGeosearch.... * https://svn.toolserver.org/svnroot/p_erfgoed/api/includes/clsARLayarServer.p...
-- Raul
2011/7/27 Maarten Dammers maarten@mdammers.nl:
- Raul implemented Layar [5]. Is this part of the api or on it's own Raul?
Can you maybe tell a bit more about this?
wikilovesmonuments@lists.wikimedia.org