Re: [GRASS-dev] [GRASS GIS] #2346: r.timestamp: support also YYYY-DOY

[GRASS GIS]

#2346: r.timestamp: support also -DOY
-+-
  Reporter:  neteler |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  normal  |  Milestone:  7.6.0
 Component:  LibGIS  |Version:  svn-releasebranch70
Resolution:  |   Keywords:  r.timestamp, t.register, temporal,
   CPU:  |  doy
  Unspecified|   Platform:  All
-+-
Changes (by martinl):

 * milestone:  7.4.2 => 7.6.0


-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2346: r.timestamp: support also YYYY-DOY

[GRASS GIS]

#2346: r.timestamp: support also -DOY
-+-
  Reporter:  neteler |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  normal  |  Milestone:  7.0.4
 Component:  LibGIS  |Version:  svn-releasebranch70
Resolution:  |   Keywords:  r.timestamp, t.register, temporal,
   CPU:  |  doy
  Unspecified|   Platform:  All
-+-
Changes (by neteler):

 * milestone:  7.0.0 => 7.0.4


Comment:

 See also #964

--
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2346: r.timestamp: support also YYYY-DOY

[GRASS GIS]

#2346: r.timestamp: support also -DOY
+---
 Reporter:  neteler |   Owner:  grass-dev@… 
 
 Type:  enhancement |  Status:  new 
 
 Priority:  normal  |   Milestone:  7.0.0   
 
Component:  LibGIS  | Version:  
svn-releasebranch70  
 Keywords:  r.timestamp, t.register, temporal, doy  |Platform:  All 
 
  Cpu:  Unspecified |  
+---

Comment(by huhabla):

 This must be implemented in the C datetime library and in the temporal
 framework parser in datetime_math.py[1]. I hoped that the dateutils[2]
 already support this to have it out of the box, but unfortunately they
 don't.

 Hence we should orient on the ISO 8601 standard for ordinal dates when
 implementing this (-DDD) but not DDD, since the temporal framework
 and the C datetime library also support relative time and can't decide if
 1900031 is 31. Jan. 1900 or if it is the number of seconds, days, ... .

 [1]
 http://grass.osgeo.org/programming7/datetime__math_8py_source.html#l00704
 [2] https://labix.org/python-dateutil

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2346: r.timestamp: support also YYYY-DOY

[GRASS GIS]

#2346: r.timestamp: support also -DOY
+---
 Reporter:  neteler |   Owner:  grass-dev@… 
 
 Type:  enhancement |  Status:  new 
 
 Priority:  normal  |   Milestone:  7.0.0   
 
Component:  LibGIS  | Version:  
svn-releasebranch70  
 Keywords:  r.timestamp, t.register, temporal, doy  |Platform:  All 
 
  Cpu:  Unspecified |  
+---
Changes (by wenzeslaus):

  * keywords:  r.timestamp, t.register => r.timestamp, t.register,
   temporal, doy


Comment:

 If doing this, try to follow some consistent terminology/naming.

 I've recently encountered different namings in GRASS: DOY, Day of Year,
 day of year, doy, daynum and day.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev