Code libraries with additional attributes

I just got the RS3 and would like to use the Emlid Flow 360 software for data collection, but I usually have more than one field for adding comments about the points I take. I can probably make it work for awhile with the single “Description” column, but ideally I would have another field or two to add information to while taking a point. Is there a way to do this that I am not seeing?

Hi @gms,

Welcome to our community!

Emlid Flow currently only allows to determine an object’s code and add a description to it. Could you please elaborate on what you would like to see as an additional field for the objects? Similar text fields like the description field, or more specialized ones such as number or date format fields, or attachment fields?

I would like to see an additional text field. I think when importing codes to a code library if a csv has additional columns those could be used to label new fields. If additional fields are treated as text fields then any input can be added to them while surveying, but if they are all the same data type such as double then that is an easy conversion after the data is exported.

I see. Thank you for the additional details! I’ll note it and pass it on to the team to consider further implementation.

2 Likes

I agree with @gms here on this one… I currently just purchased (2) RS3 Survey Kit and am using it as a proof of concept to shift away from the expensive big box survey hardware and software. We have approx. 8 crews that would be collecting data daily. We also require a hefty robust code list where we capture the following:
Point ID, Northing, Easting, Height, Line ID and Linework, Size, Material, Owner, Electronic Depth, Measure Down, Comment
This addition to the software would go a long way in this proof of concept and could potentially save my company hundreds of thousands of dollars. We can’t be the only ones who are wanting just a little more from this software. I know when I demo’d the gear in Dec. 2023 there was not an Inverse or Traverse feature. Great Add there!

3 Likes

Hi @lambstarfield,

I see. Thank you for sharing your workflow.

We’re collecting such cases for consideration, and I’ve added yours as +1. Thanks!

2 Likes

I would +1 on this as well. the ability to set up attributes per code would be great. A pipe would need size and type. A fence might collect height. Also, if it could be set to required or optional would be great.

Hi @bobby,

Thank you for your request! I’ve noted it and added it as +1.

1 Like

Do we know if there has been any headway with the ability to create more custom fields? We are ready to move forward with more units, but this is currently the limiting factor.

Hi @lambstarfield,

So far, I can’t share new updates. But once there’s any, I’ll make sure to post it here.

1 Like

I am a Trimble R10 user and wanted to purchase Emlid R3 units to test as a comparison. Emlid has multiple features that Trimble has yet to implement, but I use Trimble Feature Codes each time I conduct a survey, and I cannot understand how a modern survey can go without this ability. I look at my survey data as GIS that can be shared with clients, and without point and line attributes, owning an Emlid will not take place until this option is available.

Hi Dave,

Thank you for your feedback!

I’ve noted your request and will add it as +1 for the additional point and line attributes.

Kornel,

I have worked with and developed multiple applications to allow GIS data collection from survey-grade receivers/collectors, and I would be glad to send snapshots and ideas if needed. Trimble has made great strides in allowing point data attributes, but they have fallen short by making most of their equipment very Trimble-oriented and proprietory.

Dave,

Sure, feel free to share further details about your request! We always welcome ideas about how you imagine the different features.