Thanks, that is a good tip to check the type attached to each feature.
Yes, we are using SimpleFeature/SimpleFeatureType. I guess it's on to
the debugger!
Thanks,
Emilio
On 3/6/19 9:26 AM, Andrea Aime wrote:
Hi Emilio,
the honest answer is a "I don't know, use a debugger"...
But let me try some guess.. thinking out loud, make sure that the
namespace shows up
in the FeatureType as well as in the FeatureType attached to every
Feature object.
Beyond that... is the GeoMesa plugin producing SimpleFeature and
SimpleFeatureType right?
The complex features path is significantly more complex, assumes you
have XSD schemas around for all features you generate.
Cheers
Andrea
On Tue, Mar 5, 2019 at 3:44 PM Emilio Lahr-Vivaz <[email protected]
<mailto:[email protected]>> wrote:
Just to follow up, does anyone know what needs to be implemented
in a ContentDataStore to get namespaces working with GML3 in
GeoServer? We are already setting the namespace in
`createTypeNames` based on the configured GeoServer workspace [1][2].
Thanks,
Emilio
1.
https://github.com/locationtech/geomesa/blob/geomesa_2.11-2.2.1/geomesa-fs/geomesa-fs-datastore/src/main/scala/org/locationtech/geomesa/fs/FileSystemDataStoreFactory.scala#L58
<https://github.com/locationtech/geomesa/blob/geomesa_2.11-2.2.1/geomesa-fs/geomesa-fs-datastore/src/main/scala/org/locationtech/geomesa/fs/FileSystemDataStore.scala#L44>
2.
https://github.com/locationtech/geomesa/blob/geomesa_2.11-2.2.1/geomesa-fs/geomesa-fs-datastore/src/main/scala/org/locationtech/geomesa/fs/FileSystemDataStore.scala#L44
On 2/28/19 2:54 PM, Jim Hughes wrote:
Hi Christian,
Sorry for the trouble with this. In GeoMesa, we are using the
ContentDataStore API, and maybe we've missed something in our
implementation. Emilio pointed out the bit of code that is doing
the thing.
We tossed in a GeoMesa ticket here to track this:
https://geomesa.atlassian.net/browse/GEOMESA-2570.
Cheers,
Jim
1.
https://github.com/locationtech/geomesa/blob/geomesa_2.11-2.2.1/geomesa-fs/geomesa-fs-datastore/src/main/scala/org/locationtech/geomesa/fs/FileSystemDataStore.scala#L44
On 2/27/19 10:11 AM, [email protected]
<mailto:[email protected]> wrote:
Hi,
Just ran into an issue with GeoServer's WFS service serving WFS
2.0.0 as GML 3.2 from data stored as parquet files in a GeoMesa
Filesystem (S3) data store. More precisely I'm trying to
visualize those data in QGIS using a WFS layer. With this setup
QGIS is unable to render these data. It complains about an
"unbound prefix in line 1, column 726" in the WFS GetFeature
response. Having a deeper look into the response from GeoServer
reveals that the XML namespace of my feature's (i.e. ModemState)
elements is null where it should have been "vehicle-events":
<?xml version="1.0" encoding="UTF-8"?>
<wfs:FeatureCollection
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:wfs="http://www.opengis.net/wfs/2.0";
xmlns:gml="http://www.opengis.net/gml/3.2";
xmlns:vehicle-events="urn:athena:vcc:crowd:vehicle-events"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
next="https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/vehicle-events/wfs?REQUEST=GetFeature&BBOX=48.67796064700979%2C8.97443411395199%2C48.67995793698221%2C8.980798400236115%2Curn%3Aogc%3Adef%3Acrs%3AEPSG%3A%3A4326&SRSNAME=urn%3Aogc%3Adef%3Acrs%3AEPSG%3A%3A4326&VERSION=2.0.0&TYPENAMES=vehicle-events%3AModemState&SERVICE=WFS&COUNT=10&STARTINDEX=10";
numberMatched="3054" numberReturned="10"
timeStamp="2019-02-27T14:40:11.234Z"
xsi:schemaLocation="http://www.opengis.net/wfs/2.0
https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/wfs/2.0/wfs.xsd
http://www.opengis.net/gml/3.2
https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/gml/3.2.1/gml.xsd
urn:athena:vcc:crowd:vehicle-events
https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/vehicle-events/wfs?service=WFS&version=2.0.0&request=DescribeFeatureType&typeName=vehicle-events%3AModemState
<http://www.opengis.net/wfs/2.0%20https:/develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/wfs/2.0/wfs.xsd%20http:/www.opengis.net/gml/3.2%20https:/develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/gml/3.2.1/gml.xsd%20urn:athena:vcc:crowd:vehicle-events%20https:/develop.vcc.otonomousmobility.com/atvcrwd-geoserver/vehicle-events/wfs?service=WFS&version=2.0.0&request=DescribeFeatureType&typeName=vehicle-events%3AModemState>">
<wfs:member>
<null:ModemState gml:id="006ff4c8-7c65-4d2f-89df-4d7fa9afa2ea">
<timestamp>120708750</timestamp>
<apn>Context 1 </apn>
<basebandModuleFirmwareVersion>20.00.402</basebandModuleFirmwareVersion>
<cellId>160081A</cellId>
...
<dtg>2018-11-12T09:12:48.014Z</dtg>
<geom>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326" srsDimension="2"
gml:id="006ff4c8-7c65-4d2f-89df-4d7fa9afa2ea.geom">
<gml:pos>48.67940694 8.97704929</gml:pos>
</gml:Point>
</geom>
</null:ModemState>
</wfs:member>
...
</wfs:FeatureCollection>
The very same problem has already been reported in the past:
https://dev.locationtech.org/mhonarc/lists/geomesa-users/msg02330.html
I am using the most recent stable versions of GeoMesa (2.2.1),
GeoMesa-FS (2.11-2.2.1) and GeoServer (2.14.2) and the issue
still persists.
Enabling "strict CITE compliance" for WFS in GeoServer and
explicitly requesting WFS 1.0.0 in QGIS (as mentioned in the old
request linked above) leads to GML 2 being served and is a
work-around that fixes the issue for me. However it forces me to
use an old WFS version with limited features compared to WFS 2.0.0.
Do you know what is the for this? Are there any plans to fix
this on your side (not sure whether this is even caused by
GeoMesa or GeoServer)?
Asked the same question in the geomesa-users list.
Thanks and best wishes!
Christian
*Mit freundlichen Grüßen / Kind regards***
*Christian Sickert
*
Crowd Data & Analytics for Automated Driving
Daimler AG - Mercedes-Benz Cars Development - RD/AFC
+49 176 309 71612
[email protected] <mailto:[email protected]>
If you are not the addressee, please inform us immediately that
you have received this e-mail by mistake, and delete it. We
thank you for your support.
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to
this list:
- Earning your support instead of buying it, but Ian
Turton:http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting
guidelines:http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see
this:https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/geoserver-users
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before
posting to this list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Regards, Andrea Aime == GeoServer Professional Services from the
experts! Visit http://goo.gl/it488V for more information. == Ing.
Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di
Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39
0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it
http://twitter.com/geosolutions_it
------------------------------------------------------- /Con
riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene
notizia. This email is intended only for the person or entity to which
it is addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure. We remind that -
as provided by European Regulation 2016/679 “GDPR” - copying,
dissemination or use of this e-mail or the information herein by
anyone other than the intended recipient is prohibited. If you have
received this email by mistake, please notify us immediately by
telephone or e-mail./
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
