I have developed a Python script using ArcPy with one of the output variable being of Date type. In the actual Python code, the variable is a Python datetime object which has both the date and time sections. A snippet of Python script "ExtractNetCDFToRaster.py" is as below. import sys , os from os . path import basename import arcpy import datetime from dateutil import tz # Convert UTC datetime to local datetime def convertToLocalDT ( string ): from_zone = tz . tzutc () to_zone = tz . tzlocal () # 20/11/2017 1:00:00 PM dtUTC = datetime . datetime . strptime ( string , "%d/%m/%Y %I:%M:%S %p" ) dtLocal = dtUTC . replace ( tzinfo = from_zone ). astimezone ( to_zone ) return dtLocal ... # get dimension values from the time dimension dimension_values = nc_FP . getDimensionValue ( "time" , 0 ) # the dimension_values is of a unicode type of data, e.g. u'20/11/2017 1:00:00 PM' strDimensionValues = dimension_values . encode ( 'utf-8' ) arcpy . AddMessage ( "dimension_values: " + strDimensionValues ) dtDimensionValues = convertToLocalDT ( strDimensionValues ) ... # Set dtDimensionValues as output which has an alias of "outDateTime" in the tool Properties window. arcpy . SetParameter ( 5 , dtDimensionValues ) When I imported this script into a Model as a custom tool and ran the tool, the variable only output the date but not the time section. For example, if the actual datetime is "2017-11-21 00:00:00" the outDateTime only shows "21/11/2017" as below.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Date output does not show "time" in Model Builder

AlexChen

I have developed a Python script using ArcPy with one of the output variable being of Date type. In the actual Python code, the variable is a Python datetime object which has both the date and time sections.

A snippet of Python script "ExtractNetCDFToRaster.py" is as below.

<SPAN class="">import</SPAN><SPAN class=""> sys</SPAN><SPAN class="">,</SPAN><SPAN class=""> os</SPAN><SPAN class="">from</SPAN><SPAN class=""> os</SPAN><SPAN class="">.</SPAN><SPAN class="">path </SPAN><SPAN class="">import</SPAN><SPAN class=""> basename</SPAN><SPAN class="">import</SPAN><SPAN class=""> arcpy</SPAN><SPAN class="">import</SPAN><SPAN class=""> datetime</SPAN><SPAN class="">from</SPAN><SPAN class=""> dateutil </SPAN><SPAN class="">import</SPAN><SPAN class=""> tz </SPAN><SPAN class=""># Convert UTC datetime to local datetime</SPAN><SPAN class=""></SPAN><SPAN class="">def</SPAN><SPAN class=""> convertToLocalDT</SPAN><SPAN class="">(</SPAN><SPAN class="">string</SPAN><SPAN class="">):</SPAN><SPAN class="">&nbsp;&nbsp;&nbsp; from_zone </SPAN><SPAN class="">=</SPAN><SPAN class=""> tz</SPAN><SPAN class="">.</SPAN><SPAN class="">tzutc</SPAN><SPAN class="">()</SPAN><SPAN class="">&nbsp;&nbsp;&nbsp; to_zone </SPAN><SPAN class="">=</SPAN><SPAN class=""> tz</SPAN><SPAN class="">.</SPAN><SPAN class="">tzlocal</SPAN><SPAN class="">()</SPAN><SPAN class="">&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><SPAN class=""># 20/11/2017 1:00:00 PM</SPAN><SPAN class="">&nbsp;&nbsp;&nbsp; dtUTC </SPAN><SPAN class="">=</SPAN><SPAN class=""> datetime</SPAN><SPAN class="">.</SPAN><SPAN class="">datetime</SPAN><SPAN class="">.</SPAN><SPAN class="">strptime</SPAN><SPAN class="">(</SPAN><SPAN class="">string</SPAN><SPAN class="">,</SPAN><SPAN class=""> </SPAN><SPAN class="">"%d/%m/%Y %I:%M:%S %p"</SPAN><SPAN class="">)</SPAN><SPAN class="">&nbsp;&nbsp;&nbsp; dtLocal </SPAN><SPAN class="">=</SPAN><SPAN class=""> dtUTC</SPAN><SPAN class="">.</SPAN><SPAN class="">replace</SPAN><SPAN class="">(</SPAN><SPAN class="">tzinfo</SPAN><SPAN class="">=</SPAN><SPAN class="">from_zone</SPAN><SPAN class="">).</SPAN><SPAN class="">astimezone</SPAN><SPAN class="">(</SPAN><SPAN class="">to_zone</SPAN><SPAN class="">)</SPAN><SPAN class="">&nbsp;&nbsp;&nbsp;&nbsp; </SPAN><SPAN class="">return</SPAN><SPAN class=""> dtLocal </SPAN><SPAN class="">...</SPAN><SPAN class=""></SPAN><SPAN class=""># get dimension values from the time dimension</SPAN><SPAN class="">dimension_values </SPAN><SPAN class="">=</SPAN><SPAN class=""> nc_FP</SPAN><SPAN class="">.</SPAN><SPAN class="">getDimensionValue</SPAN><SPAN class="">(</SPAN><SPAN class="">"time"</SPAN><SPAN class="">,</SPAN><SPAN class=""> </SPAN><SPAN class="">0</SPAN><SPAN class="">)</SPAN><SPAN class=""></SPAN><SPAN class=""># the dimension_values is of a unicode type of data, e.g. u'20/11/2017 1:00:00 PM'</SPAN><SPAN class="">strDimensionValues </SPAN><SPAN class="">=</SPAN><SPAN class=""> dimension_values</SPAN><SPAN class="">.</SPAN><SPAN class="">encode</SPAN><SPAN class="">(</SPAN><SPAN class="">'utf-8'</SPAN><SPAN class="">)</SPAN><SPAN class="">arcpy</SPAN><SPAN class="">.</SPAN><SPAN class="">AddMessage</SPAN><SPAN class="">(</SPAN><SPAN class="">"dimension_values: "</SPAN><SPAN class=""> </SPAN><SPAN class="">+</SPAN><SPAN class=""> strDimensionValues</SPAN><SPAN class="">)</SPAN><SPAN class="">dtDimensionValues </SPAN><SPAN class="">=</SPAN><SPAN class=""> convertToLocalDT</SPAN><SPAN class="">(</SPAN><SPAN class="">strDimensionValues</SPAN><SPAN class="">)</SPAN><SPAN class=""></SPAN><SPAN class="">...</SPAN><SPAN class=""></SPAN><SPAN class=""># Set dtDimensionValues as output which has an alias of "outDateTime" in the tool Properties window.</SPAN><SPAN class="">arcpy</SPAN><SPAN class="">.</SPAN><SPAN class="">SetParameter</SPAN><SPAN class="">(</SPAN><SPAN class="">5</SPAN><SPAN class="">,</SPAN><SPAN class=""> dtDimensionValues</SPAN><SPAN class="">)</SPAN>

The properties window for the custom tool

When I imported this script into a Model as a custom tool and ran the tool, the variable only output the date but not the time section. For example, if the actual datetime is "2017-11-21 00:00:00" the outDateTime only shows "21/11/2017" as below.

Trouver plus de publications taguées avec

Accepted answers

DanPatterson_Retired

Yes... your alternative would be as I suggested which would complicate your workflow, since you would have to do the date conversion to string, then add the result to a text field and not a date field. I would suggest the FC in the gdb

All comments

AlexChen

Thanks Dan. You are right. The help documentation states:

Fundamentals of date fields—Help | ArcGIS for Desktop
Displaying dates
A coverage or shapefile stores dates in a date field with this format: yyyy-mm-dd. A geodatabase formats the date as datetime yyyy-mm-dd hh:mm:ss AM or PM. Settings on your Windows system determine how the dates are displayed in ArcMap—M/d/yy, MM/dd/yy, yy/MM/dd, and so on. ArcMap uses the system short date format (numerical) for displaying dates.

So I should use feature class in a file geodatabase instead of shapefile.

DanPatterson_Retired

If it is adding it to shapefile..,. time is not supported wish I had known that initially....

date fields only support date. They do not support time.

Caution:

The nonsupport of time in date fields can be a serious limitation for any tool that performs temporal analysis, such as those found in the Space Time Pattern Mining toolbox. Avoid using shapefiles for any kind of temporal analysis or date time calculation.

AlexChen

@Dan. Thanks! I can do String output from the script. But the script will be used as a custom tool to be imported into a main Model called "MainModel". The MainModel will add the output date and time to a field of Date type (called "_Time") in a Shapefile. Does the "_Time" field automatically pick up a String as Date type?

DanPatterson_Retired

Would an output string be what you are looking for from the python side?

n <SPAN class="operator token">=</SPAN> datetime<SPAN class="punctuation token">.</SPAN>datetime<SPAN class="punctuation token">.</SPAN>now<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
n
datetime<SPAN class="punctuation token">.</SPAN>datetime<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2017</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">11</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">20</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">1</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">14</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">19</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">245760</SPAN><SPAN class="punctuation token">)</SPAN>

n<SPAN class="punctuation token">.</SPAN>__str__<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="string token">'2017-11-20 01:14:19.245760'</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.