[Geoserver-users] Mongodb Extension

The mongodb extension is currently labeled as unsupported. Are there any plans to update the mongodb extension for the latest Mongo geospatial features and support the extension?

Thanks,

Nathan

I have exported a simple sld from qgis – it didn’t work in 2.6.2 so I tried 2.7.0

Are they not supported or have I set something up wrong ?

The error generated is :-

<?xml version="1.0" encoding="UTF-8"?>

java.io.IOException: java.lang.RuntimeException: Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal java.lang.RuntimeException: Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal Unable to find function Literal

And from the log :-

Caused by: java.lang.RuntimeException: Unable to find function Literal

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:205)

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:152)

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:127)

at org.geotools.filter.FilterParsingUtils.lookupExtendedOperator(FilterParsingUtils.java:170)

at org.geotools.filter.FilterParsingUtils.parseExtendedOperators(FilterParsingUtils.java:139)

at org.geotools.filter.v1_1.FilterTypeBinding.parse(FilterTypeBinding.java:111)

at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:155)

… 127 more

SLD :-

<?xml version="1.0" encoding="UTF-8"?>

se:NameAdvisory_Disabled_Bays</se:Name>

se:NameAdvisory_Disabled_Bays</se:Name>

se:FeatureTypeStyle

se:Rule

se:NameSingle symbol</se:Name>

se:PolygonSymbolizer

se:Fill

<se:SvgParameter name=“fill”>#ffffff</se:SvgParameter>

</se:Fill>

se:Stroke

<se:SvgParameter name=“stroke”>#728584</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

<se:SvgParameter name=“stroke-linejoin”>bevel</se:SvgParameter>

</se:Stroke>

</se:PolygonSymbolizer>

se:PolygonSymbolizer

se:Fill

se:GraphicFill

se:Graphic

se:Mark

se:WellKnownNamehorline</se:WellKnownName>

se:Stroke

<se:SvgParameter name=“stroke”>#000000</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

</se:Stroke>

</se:Mark>

se:Size2</se:Size>

se:Rotation

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

ogc:Literal45</ogc:Literal>

</ogc:Filter>

</se:Rotation>

se:Displacement

se:DisplacementX0.850904</se:DisplacementX>

se:DisplacementY0.525322</se:DisplacementY>

</se:Displacement>

</se:Graphic>

</se:GraphicFill>

</se:Fill>

</se:PolygonSymbolizer>

se:PolygonSymbolizer

se:Fill

se:GraphicFill

se:Graphic

se:Mark

se:WellKnownNamehorline</se:WellKnownName>

se:Stroke

<se:SvgParameter name=“stroke”>#000000</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

</se:Stroke>

</se:Mark>

se:Size2</se:Size>

se:Rotation

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

ogc:Literal135</ogc:Literal>

</ogc:Filter>

</se:Rotation>

se:Displacement

se:DisplacementX0</se:DisplacementX>

se:DisplacementY0</se:DisplacementY>

</se:Displacement>

</se:Graphic>

</se:GraphicFill>

</se:Fill>

</se:PolygonSymbolizer>

</se:Rule>

</se:FeatureTypeStyle>

···

Mark Ismail

Hi Nathan,

You might check out Boundless’s MongoDB support: https://github.com/boundlessgeo/geoserver-exts/tree/master/mongodb.

They’d likely be willing and excited to discuss paid support.

Cheers,

Jim

···

On 05/07/2015 11:01 AM, Reese, Nathan wrote:

The mongodb extension is currently labeled as unsupported. Are there any plans to update the mongodb extension for the latest Mongo geospatial features and support the extension?

Thanks,

Nathan

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
[http://ad.doubleclick.net/ddm/clk/290420510;117567292;y](http://ad.doubleclick.net/ddm/clk/290420510;117567292;y)
_______________________________________________
Geoserver-users mailing list
[Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)

On Thu, May 7, 2015 at 5:27 PM, Ismail, Mark <mark.ismail@anonymised.com>
wrote:

<se:Rotation>

                    <ogc:Filter xmlns:ogc="http://www.opengis.net/ogc&quot;&gt;

                      <ogc:Literal>135</ogc:Literal>

                    </ogc:Filter>

                  </se:Rotation>

The above is not valid, no wonder it cannot be parsed, QGis SLD generation
is known to emit invalid sld, and/or to use qgis specific extensions.

For a transfer of SLDs from QGis to GeoSever we'd need a two sided effort:
* QGis should generate at least valid SLD (the one above is not)
* GeoServer should learn how to interpret QGis specific extensions to SLD
(e.g. their symbol names and the like)

These issues come up often enough that I'm surprised no one has sponsored
some work in this area yet.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

That isn’t a valid filter. Looks like another QGIS bug.

Ian

On Thu, 7 May 2015 5:48 pm Ismail, Mark <mark.ismail@anonymised.com> wrote:

I have exported a simple sld from qgis – it didn’t work in 2.6.2 so I tried 2.7.0

Are they not supported or have I set something up wrong ?

The error generated is :-

<?xml version="1.0" encoding="UTF-8"?>

java.io.IOException: java.lang.RuntimeException: Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal java.lang.RuntimeException: Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal Unable to find function Literal

And from the log :-

Caused by: java.lang.RuntimeException: Unable to find function Literal

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:205)

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:152)

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:127)

at org.geotools.filter.FilterParsingUtils.lookupExtendedOperator(FilterParsingUtils.java:170)

at org.geotools.filter.FilterParsingUtils.parseExtendedOperators(FilterParsingUtils.java:139)

at org.geotools.filter.v1_1.FilterTypeBinding.parse(FilterTypeBinding.java:111)

at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:155)

… 127 more

SLD :-

<?xml version="1.0" encoding="UTF-8"?>

se:NameAdvisory_Disabled_Bays</se:Name>

se:NameAdvisory_Disabled_Bays</se:Name>

se:FeatureTypeStyle

se:Rule

se:NameSingle symbol</se:Name>

se:PolygonSymbolizer

se:Fill

<se:SvgParameter name=“fill”>#ffffff</se:SvgParameter>

</se:Fill>

se:Stroke

<se:SvgParameter name=“stroke”>#728584</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

<se:SvgParameter name=“stroke-linejoin”>bevel</se:SvgParameter>

</se:Stroke>

</se:PolygonSymbolizer>

se:PolygonSymbolizer

se:Fill

se:GraphicFill

se:Graphic

se:Mark

se:WellKnownNamehorline</se:WellKnownName>

se:Stroke

<se:SvgParameter name=“stroke”>#000000</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

</se:Stroke>

</se:Mark>

se:Size2</se:Size>

se:Rotation

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

ogc:Literal45</ogc:Literal>

</ogc:Filter>

</se:Rotation>

se:Displacement

se:DisplacementX0.850904</se:DisplacementX>

se:DisplacementY0.525322</se:DisplacementY>

</se:Displacement>

</se:Graphic>

</se:GraphicFill>

</se:Fill>

</se:PolygonSymbolizer>

se:PolygonSymbolizer

se:Fill

se:GraphicFill

se:Graphic

se:Mark

se:WellKnownNamehorline</se:WellKnownName>

se:Stroke

<se:SvgParameter name=“stroke”>#000000</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

</se:Stroke>

</se:Mark>

se:Size2</se:Size>

se:Rotation

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

ogc:Literal135</ogc:Literal>

</ogc:Filter>

</se:Rotation>

se:Displacement

se:DisplacementX0</se:DisplacementX>

se:DisplacementY0</se:DisplacementY>

</se:Displacement>

</se:Graphic>

</se:GraphicFill>

</se:Fill>

</se:PolygonSymbolizer>

</se:Rule>

</se:FeatureTypeStyle>

Mark Ismail

This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it.

Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives.

Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this e-mail and any attachments are virus free. You must therefore take full responsibility for virus checking and no responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. Knowsley MBC reserves the right to monitor and/or record all e-mail communications through its network in accordance with relevant legislation.


One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hello Andrea and Ian,

thank you very much for your description concerning the compatibility of QGIS’s SLDs in GeoServer.
Actually, I didn’t get to work nary a SLD of QGIS in GeoServer over the past semesters/years. But QGIS’s style editor is a powerful tool and you can create nice SLD styles by categorization based on attributes. This is important in geo sciences to create a soil map for instance.

Is there an alternative way to create great looking complex SLDs for GeoServer?

Best wishes,

Izabella

···

On 7 May 2015 at 17:58, Ian Turton <ijturton@anonymised.com> wrote:

That isn’t a valid filter. Looks like another QGIS bug.

Ian

On Thu, 7 May 2015 5:48 pm Ismail, Mark <mark.ismail@anonymised.com> wrote:

I have exported a simple sld from qgis – it didn’t work in 2.6.2 so I tried 2.7.0

Are they not supported or have I set something up wrong ?

The error generated is :-

<?xml version="1.0" encoding="UTF-8"?>

java.io.IOException: java.lang.RuntimeException: Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal java.lang.RuntimeException: Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal Parsing failed for Filter: java.lang.RuntimeException: Unable to find function Literal Unable to find function Literal

And from the log :-

Caused by: java.lang.RuntimeException: Unable to find function Literal

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:205)

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:152)

at org.geotools.filter.FunctionFinder.findFunction(FunctionFinder.java:127)

at org.geotools.filter.FilterParsingUtils.lookupExtendedOperator(FilterParsingUtils.java:170)

at org.geotools.filter.FilterParsingUtils.parseExtendedOperators(FilterParsingUtils.java:139)

at org.geotools.filter.v1_1.FilterTypeBinding.parse(FilterTypeBinding.java:111)

at org.geotools.xml.impl.ParseExecutor.visit(ParseExecutor.java:155)

… 127 more

SLD :-

<?xml version="1.0" encoding="UTF-8"?>

se:NameAdvisory_Disabled_Bays</se:Name>

se:NameAdvisory_Disabled_Bays</se:Name>

se:FeatureTypeStyle

se:Rule

se:NameSingle symbol</se:Name>

se:PolygonSymbolizer

se:Fill

<se:SvgParameter name=“fill”>#ffffff</se:SvgParameter>

</se:Fill>

se:Stroke

<se:SvgParameter name=“stroke”>#728584</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

<se:SvgParameter name=“stroke-linejoin”>bevel</se:SvgParameter>

</se:Stroke>

</se:PolygonSymbolizer>

se:PolygonSymbolizer

se:Fill

se:GraphicFill

se:Graphic

se:Mark

se:WellKnownNamehorline</se:WellKnownName>

se:Stroke

<se:SvgParameter name=“stroke”>#000000</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

</se:Stroke>

</se:Mark>

se:Size2</se:Size>

se:Rotation

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

ogc:Literal45</ogc:Literal>

</ogc:Filter>

</se:Rotation>

se:Displacement

se:DisplacementX0.850904</se:DisplacementX>

se:DisplacementY0.525322</se:DisplacementY>

</se:Displacement>

</se:Graphic>

</se:GraphicFill>

</se:Fill>

</se:PolygonSymbolizer>

se:PolygonSymbolizer

se:Fill

se:GraphicFill

se:Graphic

se:Mark

se:WellKnownNamehorline</se:WellKnownName>

se:Stroke

<se:SvgParameter name=“stroke”>#000000</se:SvgParameter>

<se:SvgParameter name=“stroke-width”>0.26</se:SvgParameter>

</se:Stroke>

</se:Mark>

se:Size2</se:Size>

se:Rotation

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

ogc:Literal135</ogc:Literal>

</ogc:Filter>

</se:Rotation>

se:Displacement

se:DisplacementX0</se:DisplacementX>

se:DisplacementY0</se:DisplacementY>

</se:Displacement>

</se:Graphic>

</se:GraphicFill>

</se:Fill>

</se:PolygonSymbolizer>

</se:Rule>

</se:FeatureTypeStyle>

Mark Ismail

This e-mail and any attachments are confidential. It may contain privileged information and is intended for the named recipient(s) only. It must not be distributed without consent. If you are not one of the intended recipients, please notify the sender immediately and do not disclose, distribute, or retain this email or any part of it and do not take any action based on it.

Unless expressly stated, opinions in this email are those of the individual sender, and not of Knowsley MBC. Legally binding obligations can only be created for, or be entered into on behalf of, Knowsley MBC by duly authorised officers or representatives.

Knowsley MBC excludes any liability whatsoever for any offence caused, any direct or consequential loss arising from the use, or reliance on, this e-mail or its contents. We believe but do not warrant that this e-mail and any attachments are virus free. You must therefore take full responsibility for virus checking and no responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. Knowsley MBC reserves the right to monitor and/or record all e-mail communications through its network in accordance with relevant legislation.


One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users