<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi Jorge,<br>
<br>
The main idea it's create a final API available for any client, the
proposal includes a final testing part on other clients like
OpenLayers, after the Android library project for gvSIG Mini has
been developed.<br>
<br>
Use GeoServer and Geotools sounds really interesting. Also, the
implementation of part of OGC standards on gvSIG Mini.<br>
<br>
Thanks for your feedback, it's really appreciated,<br>
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: arial,sans-serif; font-style:
normal; font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; font-size: small;"><span
class="Apple-style-span" style="line-height: 15px;"></span></span><br>
Ruben Blanco<br>
<br>
<br>
<br>
El 12/04/2011 12:34, Jorge Gaspar Sanz Salinas escribió:
<blockquote cite="mid:4DA42AAA.5000909@gvsig.com" type="cite">
<pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
El 12/04/2011 12:09, Rubén Blanco escribió:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Jukka,
The GSoC proposal have two important parts:
The first one it's create a documented service that includes all
geo-located social network data APIs and returns a single GeoJSON with
an unique structure easily interpretable, solving the problem of the
different implementations (Youtube, Twitter, Panoramio, Last.Fm,
Flickr..) on a cloud computing host like App Engine.
The second part it's create a library that interprets the GeoJSON and
has the ability to draw and list the information in gvSIG Mini Maps.
I think it's a good idea try to implement the standard WFS services in
this second development GSoC part, as part of the implementation and
testing.
</pre>
</blockquote>
<pre wrap="">
mmm I'm not sure of this.
- - I would implement the first part as an abstract provider
- - Then wrap it as a provider for GeoServer as a GeoTools datastore
(maybe I'm wrong on the specific vocabulary, sorry)
- - And then consume it at gvSIG mini using the GeoGJSON output format and
the most basic WFS requests
This way you are allowing other clients (OpenLayers, i.e.) to use your
development and also implementing an OGC standard on gvSIG Mini (or at
least a part of it).
And as a extra points, someone afterwards can wrap your abstract
provider as a gvSIG 2.0 DAL one to be used on gvSIG Mobile and gvSIG
Desktop... triple win!!! XD
Hope it helps
- --
Jorge Gaspar Sanz Salinas
gvSIG Team at Prodevelop
Technical Collaborations Manager
<a class="moz-txt-link-freetext" href="http://www.gvsig.org">http://www.gvsig.org</a>
<a class="moz-txt-link-freetext" href="http://www.gvsig.com">http://www.gvsig.com</a>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a>
iQEcBAEBAgAGBQJNpCqqAAoJEAOYD75lvHdB7Y8H/10dr8JwLThjWpmBYJ1WQMnL
Ww1VFNShV7LEkoVSD/AntYV4xNA7nygLRm5rOdYG26hMcBSOVQzU1mH2vB52rSnl
HarkHSgmuTRSda4zNuOR2PUydFGw6QfBYh5KdzaEBdMSxz53cy5YDDrNM3PycTnG
zAff7/oTOY73SHf6fLY8F2q3GyrqbewKwRGMYjaYSnhmsqstQEPUZHmHtabq3iAT
kKZXnwS+ls3dXZG543DaHubPAiR/ptsCSMDn+MZlQYqQYSIVYynbHWLVY4LR4LNU
sNy+rPgo7qGKc3fiD/wG8RWBoOs00d0XPBLIhSZs/YnO9wkHA6wPNH0c3rQmllM=
=Q+9x
-----END PGP SIGNATURE-----
_______________________________________________
Gvsig_internacional mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a>
<a class="moz-txt-link-freetext" href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a>
</pre>
</blockquote>
<br>
</body>
</html>