Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

[Ondřej Pešek]

Hi Maris, Luca,

On 12 June 2017 at 08:11, Maris Nartiss  wrote:
> >
> > I have no idea how much of XML parsing is needed, but implementing an
> > own XML parser never sounds a good idea unless it is a quick hack.
> > Working with XML in a correct way is PITA, unless your parser is
> > really good.
> > Just my 0.02, as I haven't seen teh codez.
> >
>
>
As it's specific xml for SOS and not OSM xml, the converter is needed to
convert the SOS output into something readable for GRASS GIS (to import
data as a layer). And as Luca says, the conversion between this xml () and
GeoJSON was just about 50 lines of code.


2017-06-12 9:51 GMT+02:00 Luca Delucchi :

> they are not much lines of code, however I think this code should be
> added to OWSLib, Ondrej do you think is it possible?
>
>
Good idea. I will ask Tom Kradilis and guys from OWSLib about that.

Ondrej
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

[Luca Delucchi]

Hi,

On 12 June 2017 at 08:11, Maris Nartiss  wrote:
> 2017-06-11 20:20 GMT+03:00 Ondřej Pešek :
>> Hi everyone!
>> * I had a problem with xml parser in OWSLib for SOS observations, because it
>> works completely different way than we expected. After few conversations I
>> have decided to work with raw output and write parser by myself.
>
> I have no idea how much of XML parsing is needed, but implementing an
> own XML parser never sounds a good idea unless it is a quick hack.
> Working with XML in a correct way is PITA, unless your parser is
> really good.
> Just my 0.02, as I haven't seen teh codez.
>

they are not much lines of code, however I think this code should be
added to OWSLib, Ondrej do you think is it possible?

>> Regards,
>> Ondrej
>
> Māris.
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

[Maris Nartiss]

2017-06-11 20:20 GMT+03:00 Ondřej Pešek :
> Hi everyone!
> * I had a problem with xml parser in OWSLib for SOS observations, because it
> works completely different way than we expected. After few conversations I
> have decided to work with raw output and write parser by myself.

I have no idea how much of XML parsing is needed, but implementing an
own XML parser never sounds a good idea unless it is a quick hack.
Working with XML in a correct way is PITA, unless your parser is
really good.
Just my 0.02, as I haven't seen teh codez.

> Regards,
> Ondrej

Māris.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

[Ondřej Pešek]

Hi everyone!

Here is the first report of my GSoC project - SOS tools in GRASS GIS. You
can see my project at wiki at [1]

What did you get done this week?

* I had a problem with xml parser in OWSLib for SOS observations, because
it works completely different way than we expected. After few conversations
I have decided to work with raw output and write parser by myself.

* Created pull request solving [2] for OWSLib.

* Created converter between text/xml;subtype="om/1.0.0" output from OWSLib
and geoJSON for points

* Imported converted output from istSOS into GRASS GIS

* Created a shuck of v.in.sos module
What do you plan on doing next week?

* Continue in improving converters (I would like to support other than
point-geometries, but I don't have any other data on server yet)

* Continue in writing v.in.sos module

* Find some raster-data SOS server

Are you blocked on anything?

* I hope not anymore


Regards,
Ondrej

[1] https://trac.osgeo.org/grass/wiki/GSoC/2017/SOSInGRASS
[2] https://github.com/geopython/OWSLib/issues/248
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev