<span class="Apple-style-span" style="border-collapse: collapse; "><div>Dear List,</div><div><br></div><div> I am Christian Martin Reinhold and I am working on a client-server communication for extending a Web Symbol Service (WSS) on gvSIG. This week, I have been busy on the server side, defining its technology, which is finally django and pinax, and start implementing on it for the first days. Then, I started thinking about how to make this communication possible via Web Service, and also reading the OGC specification for SLD files. </div>
</span><div><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;">All the related documentation is and will be available at the following site:</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;"><a href="https://confluence.prodevelop.es/display/WSS/Home">https://confluence.prodevelop.es/display/WSS/Home</a></span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;">Now you can just read about my first week [1] and about the project in general [2], as well as the points stated at the weekly meetings for determining goals for the next weeks.</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;">The code of the project will be uploaded via SVN at one of the prodevelop-gvsig files next weeks.</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;">[1] <span class="Apple-style-span" style="border-collapse: separate; "><a href="https://confluence.prodevelop.es/display/WSS/Week+1+-+First+steps+on+developing+the+server+side">https://confluence.prodevelop.es/display/WSS/Week+1+-+First+steps+on+developing+the+server+side</a></span></span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; ">[2] <span class="Apple-style-span" style="border-collapse: separate; "><a href="https://confluence.prodevelop.es/display/WSS/2009/05/27/First+post+-+About+the+WSS+project">https://confluence.prodevelop.es/display/WSS/2009/05/27/First+post+-+About+the+WSS+project</a></span></span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; "><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;">Regards,</span></div><div><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></div><div><span class="Apple-style-span" style="border-collapse: collapse;">Christian.</span></div><div><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></div><div><span class="Apple-style-span" style="border-collapse: collapse;"></span><span class="Apple-style-span" style="border-collapse: collapse; "></span><div class="gmail_quote"><br></div><div class="gmail_quote">
On Fri, May 29, 2009 at 10:01 PM, <span dir="ltr"><<a href="mailto:soc-request@lists.osgeo.org">soc-request@lists.osgeo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Send SoC mailing list submissions to<br>
<a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.osgeo.org/mailman/listinfo/soc" target="_blank">http://lists.osgeo.org/mailman/listinfo/soc</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:soc-request@lists.osgeo.org">soc-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:soc-owner@lists.osgeo.org">soc-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of SoC digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. H2/OpenJUMP integration week 1 (Christopher)<br>
2. QGIS label placement, week 1 (Martin Dobias)<br>
3. Developing extension to thematic mapping capabilites of<br>
Spatialytics (Adhyan Arizki)<br>
4. - Ossimplanet integration with Grass and Qgis - status report<br>
#1 (massimo di stefano)<br>
5. GRASS - Network Analysis, 3rd week report (Daniel Bundala)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 29 May 2009 10:10:37 -0700 (PDT)<br>
From: Christopher <<a href="mailto:infinityedge@yahoo.com">infinityedge@yahoo.com</a>><br>
Subject: [SoC] H2/OpenJUMP integration week 1<br>
To: <a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a>, OpenJump develop and use<br>
<<a href="mailto:jump-pilot-devel@lists.sourceforge.net">jump-pilot-devel@lists.sourceforge.net</a>><br>
Message-ID: <<a href="mailto:311716.8359.qm@web38802.mail.mud.yahoo.com">311716.8359.qm@web38802.mail.mud.yahoo.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
<br>
<br>
This week, I finalized the direction of the project and began coding the first stage: a simple read only plugin for the H2 database modeled along the lines of the current postgis plugin. Next week, I will finish that plugin then begin work on adding read/write capability to OpenJUMP's DataStore framework. The biggest problem I had this week was keeping JUMP's DataStore, JUMP's DataSource, and Java's DataSource frameworks all separate in my head. A second problem was that I was strapped for manhours this week due to my big wedding happening tomorrow (my wife and I were legally married in a small ceramony last November before my dad died of Multiple Sclerosis this spring, now we're having the big party with all the relatives and associated stress ;)<br>
<br>
My wiki page (hosted in the OpenJUMP wiki) is very rudimentary right now, but will be expanded as new problems, choices, and solutions appear.<br>
<br>
--Christopher DeMars<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 29 May 2009 19:23:13 +0200<br>
From: Martin Dobias <<a href="http://wonder.sk" target="_blank">wonder.sk</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>><br>
Subject: [SoC] QGIS label placement, week 1<br>
To: <a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a>, Gary Sherman <<a href="mailto:sherman@mrcc.com">sherman@mrcc.com</a>><br>
Message-ID:<br>
<<a href="mailto:e8e7199c0905291023h314b9ba5q99d36b680c987bfc@mail.gmail.com">e8e7199c0905291023h314b9ba5q99d36b680c987bfc@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Hi,<br>
<br>
I'm working on improved label placement for Quantum GIS.<br>
<br>
You can see my first week's report on the dedicated wiki page:<br>
<a href="http://www.qgis.org/wiki/Label_Placement_GSoC_2009" target="_blank">http://www.qgis.org/wiki/Label_Placement_GSoC_2009</a><br>
<br>
Bye<br>
Martin<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sat, 30 May 2009 02:02:37 +0800<br>
From: Adhyan Arizki <<a href="mailto:a.arizki@gmail.com">a.arizki@gmail.com</a>><br>
Subject: [SoC] Developing extension to thematic mapping capabilites of<br>
Spatialytics<br>
To: <a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a><br>
Message-ID:<br>
<<a href="mailto:c673ddde0905291102h29f82241o6ed8ee4174334391@mail.gmail.com">c673ddde0905291102h29f82241o6ed8ee4174334391@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Hi,<br>
<br>
Arizki here. Working for ULaval on extending Spatialytics thematic<br>
capabilities. follow me up at:<br>
<br>
<a href="http://geosoa.scg.ulaval.ca/wiki/doku.php?do=show&id=gsoc2009_weekly_reports_adhyan_arizki" target="_blank">http://geosoa.scg.ulaval.ca/wiki/doku.php?do=show&id=gsoc2009_weekly_reports_adhyan_arizki</a><br>
<br>
<br>
--<br>
<br>
Best regards,<br>
Adhyan Arizki<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 29 May 2009 21:01:25 +0200<br>
From: massimo di stefano <<a href="mailto:massimodisasha@yahoo.it">massimodisasha@yahoo.it</a>><br>
Subject: [SoC] - Ossimplanet integration with Grass and Qgis - status<br>
report #1<br>
To: OSGeo SoC <<a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a>><br>
Cc: <a href="mailto:ossim-developer@lists.sourceforge.net">ossim-developer@lists.sourceforge.net</a><br>
Message-ID: <<a href="mailto:44C9643F-FB63-4B4E-98BA-F458170AFB4C@yahoo.it">44C9643F-FB63-4B4E-98BA-F458170AFB4C@yahoo.it</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
<br>
<br>
Hi All,<br>
<br>
i'm Massimo Di Stefano, working on the Ossimplanet integration with<br>
Grass and Qgis.<br>
<br>
here for my first report, a description about the project, its<br>
timeline etc .. is on<br>
<br>
my wiky page for the project is hosted here:<br>
<br>
<a href="http://trac.osgeo.org/ossim/wiki/GoogleSummerOfCode" target="_blank">http://trac.osgeo.org/ossim/wiki/GoogleSummerOfCode</a><br>
<br>
The code is under svn you can browse it here :<br>
<br>
<a href="http://svn.osgeo.org/ossim/trunk/gsoc/" target="_blank">http://svn.osgeo.org/ossim/trunk/gsoc/</a><br>
<br>
I'll store the summary reports for each week here :<br>
<br>
<a href="http://trac.osgeo.org/ossim/wiki/WeekReport?action=edit" target="_blank">http://trac.osgeo.org/ossim/wiki/WeekReport?action=edit</a><br>
<br>
<br>
-- Report --<br>
<br>
i start to wrote code .... my first time using svn (cool!)<br>
<br>
i'll try to describe it here ...<br>
<br>
<br>
<br>
what is done :<br>
<br>
- code to use ossim TCP capabilities to set a position and a point of<br>
view based on (lon, lat, altitude, roll, pitch, gain) (finished)<br>
- code for reading the gps data from dgps and display the nmeadata in<br>
the gui (include a map view using qtwebkit), it will use a fixed<br>
position (gps) and a modificable view setting (roll,pitch,gain)<br>
(finished)<br>
- code to change the position using a joystic (needs some<br>
implementation yet, but is ready for test)<br>
<br>
so the position message can be sended using gui, gps, joystick<br>
<br>
- code to read the grass environment and retrieve a list for vector,<br>
raster and regions in the running mapset<br>
so it is possible to syncronize the posiotion in ossimplanet on the<br>
center of the active grass region or change the region to a speciphic<br>
layer or saved region<br>
<br>
- code to export grass elevation data to ossimplanet (g.ossim) the<br>
code is usable from the pyqt gui or directly from grass (finished)<br>
- code to read vector layer in grass and export it to kml (it is to<br>
have a custom kml settings, like color, label etc...) (needs testing,<br>
not finished)<br>
<br>
<br>
next steps :<br>
<br>
- finish the code i described first<br>
- initial work on a table widjet (it will contain the avayable layer<br>
in the mapset and a checkbox for each layer i'll try to realize a<br>
"query system" connected to the gui )<br>
- reorganize the code in a clean way, ranaming function give them a<br>
better position in the code and create comment<br>
- starts a depth immersion in the ossim-gdal code<br>
<br>
<br>
known problems that can block me :<br>
<br>
using the gdal-ossim plug-in we can read grass raster layer but there<br>
are problems to reneder images with more than 255 entries in the<br>
colortable.<br>
<br>
i had a chat with FrankW where we discuss a bit the problem, i stored<br>
the irc log here :<br>
<br>
<a href="http://trac.osgeo.org/ossim/attachment/wiki/GdalOssimPlugin/frankw_irclog.txt" target="_blank">http://trac.osgeo.org/ossim/attachment/wiki/GdalOssimPlugin/frankw_irclog.txt</a><br>
<br>
tring to summarize it :<br>
<br>
the code needs to be modified to handle three cases - 8bit, 16bit and<br>
32bit integers and to error out gracefully if it isn't one of those<br>
cases...<br>
... and "the s[sample] value it fetched from the input buffer this<br>
would need to be altered to fetch it based on the type of the buffer."<br>
in function loadIndexTo3BandTile<br>
<br>
what i learn .. :<br>
<br>
theSingleBandTile ---> point to a byte array (that isn't every true)<br>
theGdalBuffer.resize(theSingleBandTile->getSizePerBandInBytes()*2);<br>
---> the band is readed correctly but is is "casted" to 8bit<br>
<br>
i think gdal-grass should read correctly the grass data, so maybe the<br>
problem is in the colortable rendering in the GDAL OSSIM driver.<br>
<br>
i'm tring to documenting myself reading :<br>
<br>
<a href="http://www.gdal.org/gdal_datamodel.html" target="_blank">http://www.gdal.org/gdal_datamodel.html</a><br>
<br>
and :<br>
<br>
ossimGdalTileSource::loadIndexTo3BandTile()<br>
<br>
... seems it accepts only raster files with 3band or with indexcolor ,<br>
need i a function to port in rgb mode a grass color table ?<br>
<br>
i'm reading the grass colortable structure to learn more<br>
<br>
any suggestion, lines of code, examples ... that can help me to know<br>
how to work on the gdal-ossim code .. can make me happy<br>
... i know it is not a simple task.<br>
<br>
<br>
thanks to Osgeo, All the Dev-Team and Google for this cool experience!<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Massimo Di Stefano<br>
<a href="mailto:massimodisasha@yahoo.it">massimodisasha@yahoo.it</a><br>
<br>
epifanio on <a href="http://irc.freenode.net" target="_blank">irc.freenode.net</a> /join gfoss<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.osgeo.org/pipermail/soc/attachments/20090529/9bccb389/attachment-0001.html" target="_blank">http://lists.osgeo.org/pipermail/soc/attachments/20090529/9bccb389/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Fri, 29 May 2009 21:01:42 +0100<br>
From: Daniel Bundala <<a href="mailto:bundala@gmail.com">bundala@gmail.com</a>><br>
Subject: [SoC] GRASS - Network Analysis, 3rd week report<br>
To: <a href="mailto:soc@lists.osgeo.org">soc@lists.osgeo.org</a><br>
Message-ID:<br>
<<a href="mailto:9211715e0905291301u71fc082fw14b03518c9e6c869@mail.gmail.com">9211715e0905291301u71fc082fw14b03518c9e6c869@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Hi List,<br>
<br>
This week, I implemented a module that computes the shortest path<br>
between all pairs of nodes in the graph. You can also specify which<br>
pairs you are interested in, so that the module does not have to<br>
produce the entire NxN matrix. Also, I started on network flow<br>
modules. So far, I have implemented a flow algorithm and a simple<br>
module that finds the maximum flow between two given vertices(Well,<br>
for debugging purposes, it can handle only the flow between nodes 215<br>
and 219, so far....) Anyway, here is couple of pictures:<br>
<a href="http://people.ksp.sk/~dano/grass/mfu.png" target="_blank">http://people.ksp.sk/~dano/grass/mfu.png</a>,<br>
<a href="http://people.ksp.sk/~dano/grass/mfu2.png" target="_blank">http://people.ksp.sk/~dano/grass/mfu2.png</a>. One cross is source, the<br>
other one is sink. Blue edges correspond to low flow, green to medium<br>
and red to high flow. I used speed limit as edge capacities. Although<br>
it is not the case in the two pictures I posted, the forward and<br>
backward capacities of an edge can be different.<br>
<br>
For the next weeks, I plan to revise for my exams. As you may be<br>
aware, I have started two weeks earlier and so I will take a short<br>
break now.... Currently, I have no blocking issues.<br>
<br>
See you in July!<br>
Daniel<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
SoC mailing list<br>
<a href="mailto:SoC@lists.osgeo.org">SoC@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/soc" target="_blank">http://lists.osgeo.org/mailman/listinfo/soc</a><br>
<br>
<br>
End of SoC Digest, Vol 22, Issue 14<br>
***********************************<br>
</blockquote></div><br></div>