Is this question about GeoJSON? or 52 north web app?
Looking at their website
<https://wiki.52north.org/bin/view/Geostatistics/WPS4R> I cannot see
anything specific for R. They do have project details
<https://wiki.52north.org/bin/view/Geoprocessing/StructuresAndProcedures> page
(with an email list
<http://list.52north.org/mailman/listinfo/geoprocessingservices-dev> you
could ask your question on).
I am not really sure how the 52 web app is structured and intended for
extension.
--
Jody Garnett
On Fri, Oct 10, 2014 at 12:11 PM, Girija Kalyani <smileismys...@gmail.com>
wrote:
> Dear Group,
>
> I dont know if this is the right place to post my question. But still, Im
> giving a try, since i'm helpless now. I have an issue dealing with 52north
> wps with an R extension. In order to configure R module, I need to set up
> source code with geotools and build the project with geotools. I have done
> that through and the war file is generated which i deployed into my web
> app. But the problem is, when i start the 52n wps web app, i cant see the
> configuration file with geotools getting loaded instead the default config
> file is getting loaded. What could be the issue? Can anyone help me out
> please?
> I would be greatly obliged with your help.
> Thank You in advance
> please excuse me if its irrelevant to the group.
>
> On Wed, Aug 20, 2014 at 2:25 AM, Jody Garnett <jody.garn...@gmail.com>
> wrote:
>
>> There is a validator (http://geojsonlint.com), if your Json works there,
>> and does not work in our parser please report it as a bug.
>>
>> Jody Garnett
>>
>>
>> On Tue, Aug 19, 2014 at 11:08 AM, James Chamberlain <
>> james.chamberl...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> I am using geotools 11.1 and am trying to convert from GeoJSON to a JTS
>>> Geometry. All of the GeoJSON files that I have are of type
>>> "GeometryCollection". I have noticed that the conversion does not work if
>>> the "type" key is not in the expected order.
>>>
>>> Here is a working example:
>>> {
>>> "type": "GeometryCollection",
>>> "geometries": [
>>> {
>>> "type": "Polygon",
>>> "coordinates": [
>>> [[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0],
>>> [100.0, 0.0]]
>>> ]
>>> },
>>> {
>>> "type": "Point",
>>> "coordinates": [100.0, 0.0]
>>> }
>>> ]
>>> }
>>>
>>> and here is a NOT working example:
>>> {
>>> "geometries": [
>>> {
>>> "type": "Polygon",
>>> "coordinates": [
>>> [[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0],
>>> [100.0, 0.0]]
>>> ]
>>> },
>>> {
>>> "type": "Point",
>>> "coordinates": [100.0, 0.0]
>>> }
>>> ],
>>> "type": "GeometryCollection"
>>> }
>>>
>>>
>>> Should it require a specific order for the keys? In looking at the
>>> GeoJSON spec, I didn't see any mention of a required order.
>>>
>>> Any thoughts on whether this is a bug?
>>>
>>> Thanks,
>>>
>>> James
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> GeoTools-GT2-Users mailing list
>>> GeoTools-GT2-Users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> GeoTools-GT2-Users mailing list
>> GeoTools-GT2-Users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> GeoTools-GT2-Users mailing list
> GeoTools-GT2-Users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
