{% extends "upload/layer_upload_base.html" %} {% load i18n %} {% load staticfiles %} {% load layer_tags %} {% block body_class %}data data-list upload{% endblock %} {% block title %} {% trans "Upload Layer Step: Time" %} - {{ block.super }} {% endblock %} {% block head %} {{ block.super }} {% endblock %} {% block body %}

{% trans "Inspect data for " %} "{{ layer_name }}"

{% csrf_token %}

{% trans "Configure as Time-Series" %}

{% blocktrans %}Toggling this selector allows you to configure (or not) this data as a time series; in this case you will also have to select an attribute to drive the time dimension.

If GeoNode is not able to parse any of the values for the selected attribute red markers will appear to highlight the problems.

More information is provided at the bottom of the page in the "Additional Help" sections. {% endblocktrans %}

{% if time_form.time_attribute or time_form.text_attribute or time_form.year_attribute %}
{% for att in layer_attributes %} {% if att in time_form.time_names %} {% elif att in time_form.text_names %} {% elif att in time_form.year_names %} {% else %} {% endif %} {% endfor %}
{{ att|camelize }}
{% endif %} {% trans "Cancel" %}  
{% trans "Advanced Options" %}
{% if time_form.text_attribute %}
{{ time_form.text_attribute_format }}
{% endif %}
{% if time_form.time_attribute %}
{{ time_form.end_time_attribute }}
{% endif %} {% if time_form.text_attribute %}
{{ time_form.end_text_attribute }}
{{ time_form.end_text_attribute_format }}
{% endif %} {% if time_form.year_attribute %}
{{ time_form.end_year_attribute }}
{% endif %}

{% trans "Enabling Time" %}

{% blocktrans %}A layer can support one or two time attributes. If a single attribute is used, the layer is considered to contain data that is valid at single points in time. If two attributes are used, the second attribute represents the end of a valid period hence the layer is considered to contain data that is valid at certain periods in time.{% endblocktrans %}

{% trans "Selecting an Attribute" %}

{% trans "A time attribute can be" %}:

  • {% trans "An existing date" %}
  • {% trans "Text that can be converted to a timestamp" %}
  • {% trans "A number representing a year" %}

{% blocktrans %} For text attributes, one can specify a custom format (as part of the "Advanced Options") or use the 'best guess' approach which will try to automatically translate well-known recognized patterns into valid times. {% endblocktrans %}

{% trans "The 'best guess' will handle date and optional time variants of" %} ISO-8601. {% trans "In terms of the formatting flags noted above, these are" %}:
    yyyy-MM-dd'T'HH:mm:ss.SSS'Z' --> 2017-12-05T12:00:30.001Z
    yyyy-MM-dd'T'HH:mm:sss'Z' --> 2017-12-05T12:00:030Z
    yyyy-MM-dd'T'HH:mm:ss'Z' --> 2017-12-05T12:00:30Z
    yyyy-MM-dd'T'HH:mm'Z' --> 2017-12-05T12:00Z
    yyyy-MM-dd'T'HH'Z' --> 2017-12-05T12Z
    yyyy-MM-dd --> 2017-12-05
    yyyy-MM --> 2017-12
    yyyy --> 2017
                        
{% endblock %} {% block extra_script %} {{ block.super }} {% endblock %}