Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WFS - dateTime objects are not recognized #26518

Closed
qgib opened this issue Apr 4, 2018 · 3 comments
Closed

WFS - dateTime objects are not recognized #26518

qgib opened this issue Apr 4, 2018 · 3 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Regression Something which used to work, but doesn't anymore

Comments

@qgib
Copy link
Contributor

qgib commented Apr 4, 2018

Author Name: Eric Eagle (Eric Eagle)
Original Redmine Issue: 18630
Affected QGIS version: 3.0.0
Redmine category:web_services_clients/wfs


On QGIS 3.0.1, dateTime objects that are served via WFS are not recognized, yielding a null field value. I tested this by connecting 3.0.1 to a WFS feature service with dateTime objects (stored in Oracle, registered as a data store in GeoServer). Looking at the attribute table for the layer, all columns holding date&time objects show null.

However upon a direct db connection, date&time objects are loaded in the attribute table correctly (ISO 8601).

@qgib
Copy link
Contributor Author

qgib commented Apr 4, 2018

Author Name: Eric Eagle (Eric Eagle)


Eric Eagle wrote:

On QGIS 3.0.1, dateTime objects that are served via WFS are not recognized, yielding a null field value. I tested this by connecting 3.0.1 to a WFS feature service with dateTime objects (stored in Oracle, registered as a data store in GeoServer). Looking at the attribute table for the layer, all columns holding date&time objects show null.

However upon a direct db connection, date&time objects are loaded in the attribute table correctly (ISO 8601).

I marked this as regression because older versions of QGIS show this data as a string. That would probably be the fastest way to "fix" it, though it would create extra encumbrance if one desired to do temporal math.

@qgib
Copy link
Contributor Author

qgib commented May 31, 2018

Author Name: Even Rouault (@rouault)


Can you point to a WFS server and layer that exhibits the issue ?

Or at the very least provide the output of the DescribeFeatureType and GetFeature WFS requests as files


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Aug 15, 2018

Author Name: Giovanni Manghi (@gioman)


Closing for lack of feedback.


  • resolution was changed from to not reproducable
  • status_id was changed from Feedback to Closed

@qgib qgib closed this as completed Aug 15, 2018
@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Regression Something which used to work, but doesn't anymore labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Regression Something which used to work, but doesn't anymore
Projects
None yet
Development

No branches or pull requests

1 participant