|
|
David Forrest created an issue |
|
Issue Type: |
|
|---|---|
|
Assignee: |
Unassigned |
|
Components: |
Documentation |
|
Created: |
06/Jul/15 4:49 PM |
|
Priority: |
|
|
Reporter: |
|
As I following the tutorial at http://docs.geoserver.org/latest/en/user/tutorials/imagemosaic_timeseries/imagemosaic_time-elevationseries.html and examining the resultant shapefile with ‘ogrinfo -al’ , it might be nice to document or point to the documentation on the datetime format. From GeoTools getFieldStringDateTime() in https://github.com/geotools/geotools/blob/aa0d0346e4bb4a5a2055559c22d2b12ded7cbd20/modules/plugin/shapefile/src/main/java/org/geotools/data/shapefile/dbf/DbaseFileWriter.java#L443 it appears to be 8 bytes, with 4 containing the number of days since year 4173, and the other four containing the number of milliseconds within the day. One thing that confused me with the -Dorg.geotools.shapefile.datetime=true option is that the generated shapefile instead of a ‘Date’ field, has a ‘String’ field with what appears to be constant garbage in it, as printed by ogrinfo. I guess the embedded null bytes truncate ogrinfo’s string parsing. Things that might be nice to note in the documentation are the long list of ISO-8601 time formats that are automatically parsed by GeoTools’ TimeParse https://github.com/geotools/geotools/blob/aa0d0346e4bb4a5a2055559c22d2b12ded7cbd20/modules/plugin/imagemosaic/src/main/java/org/geotools/gce/imagemosaic/properties/time/TimeParser.java#L38 – Basically any date-time with a T in it, with dashes and colons accepted or optional. Such a list would provide guidance on generating the filenames. I’m also curious if a timeregexp.properties ‘format=’ string could be used for times or filenames not following one of the default formats. |
|
|
|
This message was sent by Atlassian JIRA (v6.5-OD-08-001#65007-sha1:1fc9846) |
|
|