Trimble Business Center

There could be multiple observations to a point so a single time would not be too helpful or easy to determine which time to use.  The Observation is what has a time and these are shown in both optical and occupation spreadsheets.  You could make a feature code for the point to set the time if you want  it on the point.

Regardless, I have added this to the list of enhancements for possible future consideration.

How a point gets defined can be complex.  Perhaps it's more important to know the components used to define the point and when they were observed.  Also note that whenever we import a file we keep up with the import information and make a selection set of the objects created by the import.  Each observation is related to a point and records the file that the observation came from.

We would love to hear about your workflow and the problem you want to solve using times.  Perhaps there are additional ways to provide a better solution to the problem.

There could be multiple observations to a point so a single time would not be too helpful or easy to determine which time to use.  The Observation is what has a time and these are shown in both optical and occupation spreadsheets.  You could make a feature code for the point to set the time if you want  it on the point.

Regardless, I have added this to the list of enhancements for possible future consideration.

How a point gets defined can be complex.  Perhaps it's more important to know the components used to define the point and when they were observed.  Also note that whenever we import a file we keep up with the import information and make a selection set of the objects created by the import.  Each observation is related to a point and records the file that the observation came from.

We would love to hear about your workflow and the problem you want to solve using times.  Perhaps there are additional ways to provide a better solution to the problem.

There could be multiple observations to a point so a single time would not be too helpful or easy to determine which time to use.  The Observation is what has a time and these are shown in both optical and occupation spreadsheets.  You could make a feature code for the point to set the time if you want  it on the point.

Regardless, I have added this to the list of enhancements for possible future consideration.

How a point gets defined can be complex.  Perhaps it's more important to know the components used to define the point and when they were observed.  Also note that whenever we import a file we keep up with the import information and make a selection set of the objects created by the import.  Each observation is related to a point and records the file that the observation came from.

We would love to hear about your workflow and the problem you want to solve using times.  Perhaps there are additional ways to provide a better solution to the problem.

There could be multiple observations to a point so a single time would not be too helpful or easy to determine which time to use.  The Observation is what has a time and these are shown in both optical and occupation spreadsheets.  You could make a feature code for the point to set the time if you want  it on the point.

Regardless, I have added this to the list of enhancements for possible future consideration.

How a point gets defined can be complex.  Perhaps it's more important to know the components used to define the point and when they were observed.  Also note that whenever we import a file we keep up with the import information and make a selection set of the objects created by the import.  Each observation is related to a point and records the file that the observation came from.

We would love to hear about your workflow and the problem you want to solve using times.  Perhaps there are additional ways to provide a better solution to the problem.

We are a construction company, the field use of Trimble equipment is mainly for layout and as-builts, occasionally for topo survey. Our field users don't care much about complexity of defining a point, nor do we need them to be trained in using codes or other advanced features. The field users are either foremen, or equipment operators, not dedicated GNSS operators. When they measure points, they don't always remember about using a proper point ID sequence or keeping observation logs. Knowing the date when the point was created is very useful in reviewing and organizing the field data.

I know that there might be multiple point observations and many components to the point definition, but there is only one point in time when the point was first created, and knowing that time could be very useful. If there is time stamp column in optical spreadsheet, why not make it available in points?