web API and WFS
I've been writing clients to interact with the WiGLE database, and I wrote some information about that
http://wigle.net/wiki/index.cgi?API
but UhTu insists that that API is going to change, and will break all the clients written to that API. Is anyone planning a stable REST-ful web API? If no, why not? I'd like to integrate the data from WiGLE into some mapping applications other than JiGLE, so a stable cgi interface to the database would be really helpful for data output in XML/RDF or even CSV.
Another thing that would be amazing is a WFS/WMS implementation on the database, then the access points could rendered with clients like NASA's WorldWind, so you'd see a space flyby with the results of our warbiking efforts.
http://wigle.net/wiki/index.cgi?API
but UhTu insists that that API is going to change, and will break all the clients written to that API. Is anyone planning a stable REST-ful web API? If no, why not? I'd like to integrate the data from WiGLE into some mapping applications other than JiGLE, so a stable cgi interface to the database would be really helpful for data output in XML/RDF or even CSV.
Another thing that would be amazing is a WFS/WMS implementation on the database, then the access points could rendered with clients like NASA's WorldWind, so you'd see a space flyby with the results of our warbiking efforts.
RESTful APIs are not something we have an interest in doing right now.
establishing an API with an external contract puts a lot of demand
on what we can change. as is, we change what we need as needed,
which suits us quite well. we make every effort to make changes
gradual and effective (we are fairly lazy) but there dosen't seem
to be a compelling reason to do so for non-nefarious purposes.
that and we're lazy.
WFS/WMS would a be a fun thing.
We're always interested in folks who are willing to
donate their code and time to development of new
and interesting ways to use WiGLE data.
i'd also like to express my sincere hope that your clients are
non-commercial in nature, and in keeping with the spirit of the eula.
establishing an API with an external contract puts a lot of demand
on what we can change. as is, we change what we need as needed,
which suits us quite well. we make every effort to make changes
gradual and effective (we are fairly lazy) but there dosen't seem
to be a compelling reason to do so for non-nefarious purposes.
that and we're lazy.
WFS/WMS would a be a fun thing.
We're always interested in folks who are willing to
donate their code and time to development of new
and interesting ways to use WiGLE data.
i'd also like to express my sincere hope that your clients are
non-commercial in nature, and in keeping with the spirit of the eula.
Well obviously nothing is stable or guaranteed to last, or guaranteed at all, but hang out in the chat room, #wigle @ irc.wigle.net. uhtu and bobzilla are pretty good about mentioning when the world will end in there.
Brad Isbell
brad@musatcha.com
http://www.musatcha.com
[img]http://www.musatcha.com/images/logo.jpg[/img]
brad@musatcha.com
http://www.musatcha.com
[img]http://www.musatcha.com/images/logo.jpg[/img]
Didn't the world end newyears eve 1999 ?Well obviously nothing is stable or guaranteed to last, or guaranteed at all, but hang out in the chat room, #wigle @ irc.wigle.net. uhtu and bobzilla are pretty good about mentioning when the world will end in there.
Dutch
[url=http://www.wigle.net/gps/gps/StatGroup/listusers?groupid=20041206-00006][img]http://home19.inet.tele.dk/dutch/netstumblerwigle.gif[/img][/url]
Return to “WiGLE Project Suggestions”
Who is online
Users browsing this forum: No registered users and 5 guests