Daniele Romagnoli created an issue |
Move GeoServer’s TimeParser code/parsing capabilities down to GeoTools |
Issue Type: |
Task |
---|---|
Assignee: |
Unassigned |
Created: |
23/Oct/19 4:16 PM |
Priority: |
Medium |
Reporter: |
GeoTools’s ImageMosaic has a TimeParser mainly used to extract part of the filename and parsed as an ISO8601 String. For example, a standard date-time format: has some supported alternatives:
Moreover, ImageMosaic’s timeParser can return current time when “current” or “now” Strings are provided as time to be parsed. GeoServer has its own TimeParser class having very similar code but with a few differences:
It would be great to merge these different classes into a single DateTimeParser class available at GeoTools level in order to avoid duplication of code and combine all the available capabilities into a single piece, that can be customized/enabled via flags. The idea is to have GeoServer class extending the new one being moved into GeoTools so that it can still throw the OWS ServiceException when exceeding a max number of results and keep supporting strict ISO8601 formats. Whilst ImageMosaic will support lenient variations to ISO8601 formats too and gain the Fuzzy parsing on reduced accuracy date times. |
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114-sha1:baaa228) |