[Zoo-discuss] WPS

[Anunay Sinha]

I am trying to install ZooWPS on *Windows*. I am having some trouble with
the prerequisites. They are not very specific with the version numbers of
the corresponding softwares.
1. Anyhow I went ahead and downloaded the latest stable releases(Binaries
wherever I can and compiled the rest).
2. Next I compiled Libgic
3. I Downloaded the OSGGeo4W (It asked about Desktop and WEBGIS and I
selected Desktop)
4. Next It asked me to download "This Package" which was tool-win32.zip (I
am not sure where to add this. For now I have kept it in my path)
5. Next it talked about full runtime dependencies to be places in
C:OSGeo4WBin (I am assuming it is c:\OSGeo4w\bin
6. Next was to download zoo_loader.cgi and the Main.cfg file (*I cannot
find the Main.cfg* file and still looking around for the content of the
file)
7. Next was to get OGR Service Providers which were provided in
Zoo-services-win32.zip. I have placed them in C:\OSGeo4W\bin (It talked
about two libraries but i simple copied everything into the bin. Was not
sure which two are we talking about here )

I have no previous experience with CGI and C coded servers so am missing a
lot of things here. For instance I dont know where the server is and how to
start it? I am looking into these things, but since this whole effort was
sort of a POC i will really appreciate if some one can help me run the zoo
kernel with OGR and once with my exiting code. So that we can see how it
works and decide on what WPS framework to choose.
In the mean time I am trying to bridge this gap and get more info on CGI.

Thanks for your efforts.

Anunay



On Tue, Nov 19, 2013 at 1:36 AM, nicolas bozon <nicolas.bozon at gmail.com>wrote:

> Anunay,
>
> If your code base is in C++, i would definitively recommend you give ZOO a
> try.
> You could probably use your existing C++ and take advantage of the
> available GDAL and GRASS support we maintain.
> Also, the MapServer support (i.e the resulting data source(s) of your WPS
> request is automatically written to a mapfile and it thus makes it very
> easy to publish as WMS/WFS/WCS) provided by ZOO 1.3 may be of interest for
> your needs.
> FYI, such capabilities are also used into our MapMint platform, which
> provides an admin interface to both ZOO, GDAL, MapServer and OpenLayers and
> that will soon be released open source too.
> Do not hesitate to ask more practical/technical questions publicly or
> privately if needed.
> Hope it helps
>
> Best,
>
> Nick
>
>
>
>
>
>
>
>
>
> 2013/11/18 Anunay Sinha <anunay.sinha88 at gmail.com>
>
>> Thanks.
>> Will post it up there.
>> I was for a second interested in Zoo for the same reason (My GIS Engine
>> was initially in C++ so wrapping it with C will be easy compared with the
>> overhead it requires for other languages ). I just wanted to know how is
>> Zoo compared with the rest?
>> In terms of acceptance in the market. And what are the points I need to
>> take into consideration when choosing one over the other (you gave me one
>> point, if there are more?)
>>
>> I will put up this post in the mailing list you mentioned but just to
>> continue the discussion am keeping this thread running.
>>
>>
>>
>>
>> On Mon, Nov 18, 2013 at 11:09 PM, nicolas bozon <nicolas.bozon at gmail.com>wrote:
>>
>>> Hello Anunay and welcome to this list.
>>>
>>> I think you did a great choice for your 'web based GIS system', because
>>> WPS can handle pretty much things for it.
>>>
>>> As far as i know, there are 5 open source WPS platforms out there, but
>>> GeoTools isn't one (although it is used by GeoServer). Your list would then
>>> become, by alphabetical order:
>>> 1. Degree
>>> 2. GeoServer
>>> 3. PyWPS
>>> 4. ZooWPS
>>> 5. 52North
>>>
>>> They are all implementing the WPS specification from OGC and they are
>>> all open source.
>>>
>>> I guess they are all able to run GIS algorithms available from other
>>> open source libraries such as GDAL, GRASS, Sextante, GeoTools,
>>> Sextante...,using different methods.
>>>
>>> Most of them are written in Java or Python, but ZOO-Kernel (ZOO-Project
>>> engine) is written in C language.
>>> This somehow allows him to execute WPS Services coded in different
>>> languages (C, Python, Java, JavaScript...), so you won't be limited to only
>>> Java or Python. It can open doors to 'any' source code you want to turn
>>> into a compliant Web Service.
>>>
>>> This is my simple ZOOer answer, but i would recommend you post such a
>>> generic question to wps-dev at lists.opengeospatial.org, so you would
>>> probably get more answers from the different projects developers and users.
>>>
>>> Good luck and feel free to ask more questions on this list too.
>>>
>>> Best regards,
>>>
>>> Nick
>>>
>>>
>>>
>>>
>>> 2013/11/18 Anunay Sinha <anunay.sinha88 at gmail.com>
>>>
>>>>  We have a requirement where in we need to expose our analysis to a
>>>> web based GIS system. We decided to do it using WPS.
>>>>
>>>> However I have general question about WPS (This may not be the best
>>>> platform but still.)
>>>> What is a difference between different WPS Frameworks out there
>>>> 1. GeoServer
>>>> 2. GeoTools
>>>> 3. Deegree
>>>> 4 52North
>>>> 5 ZooWPS
>>>>
>>>> I am not sure which one to choose and what are things I need to
>>>> consider when making this choice.
>>>> Also if you can let me know where ZooWPS stands when compared with the
>>>> rest (My thinking here is since they all provide OGC WPS Implementation
>>>> they all should be doing pretty much the same thing, but that is a wild
>>>> thought)
>>>>
>>>> Looking for your help
>>>>
>>>> Anunay
>>>>
>>>> _______________________________________________
>>>> Zoo-discuss mailing list
>>>> Zoo-discuss at lists.osgeo.org
>>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/zoo-discuss/attachments/20131121/950e73ac/attachment.html>