Well, the rumors are true: changes are coming to the AAVSO website and server infrastructure. This may/will have an impact on any software that you have written that queries aavso.org directly for information and charts. This is the topic of the Developer Announcement that is coming out today: we want developers to be aware that change is coming and to work with us here in this forum to sort out the issues.
Tell us here, or in an email direct to firstname.lastname@example.org, what mechanisms your software uses. For example, I know that the TransformApplier calls "http://www.aavso.org/apps/vsp/api/chart/"+ sd->CHART+ "/?format=xml" to fetch the photometry of a chart. Knowing this HQ can make sure this mechanism continues to work in the future. And if it has to change, give you the details of how it will change.
The AAVSO is meant to be a resource to the professional/amateur community, to help them do good science. Help us here help you.
And if you have a new idea of information that will help you do science, bring that too!
Thanks for the head's up. It's greatly appreciated.
Using MPO Canopus, this is a sample call to get photometry data for a U GEM field that is 20x20 arcminutes with a limiting mag of 16. Note the resulting XML includes the parth to a chart as well.
The field (Name or RA/Dec), FOV, Limiting mag, and orientation are the allowed user inputs.
Thanks for trying to avoid breaking code, but it happens sometimes.
Brian D. Warner
Just to add to the VSP service call that I use format=JSON.
Using the python astroquery package I query APASS data from Vizier as catalog "II/336".
I love it that you guys are doing such a great job of keeping your data consumers appraised of potential API changes. Thank you!
Pylcg 1.00 (code at https://github.com/edose/pylcg) has 3 API calls, example URLs given here:
Photrix, my daily planning and processing system (code at https://github.com/edose/photrix) has 2 API calls, example URLs given here:
Please prepend "https//www." to each of the above URLs (omitted to prevent forum sw from corrupting them).
Hope this helps. E-mail me if I can clarify anything, and thanks for the opportunity to comment.
1) I use the VSP API ( https://www.aavso.org/apps/vsp/api/chart ), to get photometry data or chart, for two web applications (Extinction-o-Meter and Variable Stars Atlas)
2) I use the web service that powers the old observations planner ( service URL http://www.aavso.org/cgi-bin/obs_planner_web.pl , planner URL https://www.aavso.org/observation-planning) to power my own version of the planner ( Variable Stars Observations Planner ; this alternative planner can provide a customized view of the atlas mentioned above).
Hi and thanks for this initiative. I use custom scripts that 1) download observations for plotting light curves and 2) get charts for visual use. The API calls are:
(in bold are variables)
This scheme is also used in LCplot, a freely available Perl program that can be run locally to plot light curves of variable stars.
(again, my variables in bold)
The script then parses the JSON file to get the image URI and download it.
In my experience so far the API works fine, is fast and very reliable for my purposes.
Thanks again and will be nice to hear how this work evolves!
I use several API calls for my personal data analysis workflow, so it's not a big deal if the APIs change - I just need the ability to get the same data:
Retrieve comparison stars
Generate light curves:
Retrieve data from VSX:
Yup I use a call to get charts and comp star data:
I assume you will let us know if and how these things will change?
Similarly to others, I use the following code, embedded in an iframe within a script, to retrieve and display a chart whose parameters are posted in an HTML form, to include the name and others as shown:
src='.....//www.aavso.org/cgi-bin/vsp.pl?name=" + varName +
"&charttitle=" + varTitle + "&fov=" + varFOV +
"&maglimit=" + varLimit + "&ccdtable=on'
Thanks for asking.