MicroSurvey STAR*NET

Welcome to the MicroSurvey STAR*NET feedback and ideas forum. This forum is for you to use to offer us feedback about features you would like added or improved.

You have 25 votes that can be used, a minimum of one vote is needed per feature request. You can also use your votes towards existing features that other users have requested.

After a feature has been implemented, you will get your votes back to apply to new or other existing features.

How can we improve MicroSurvey STAR*NET?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Treat HI's and HT's as observables

    Reality is, HI's are among the least precise measurments we make in the field. They're hand measured with pocket tapes (unless you're using constant height pods), and debugging a bad HI can be a nightmare, if you've ever chased one, you know. Was never able to convince Ron this was worth while. Lets see if anyone else thinks this would be useful.
    Thanks,
    Alan

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Ability to fully analyse Double Level Runs that do not close on the same starting point. Not possible at the moment.

    When converting a double level run each of the two measurements (BFFB) to the same stations are averaged out but with no check on how accurate the two height differences match each other. Any height error in here will just be averaged into the DAT file. The only way to check this is to manually calculate the height differences in the Log file which takes time. If StarDNA can keep all the measurements in the DAT file then full analysis can take place.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add Covariance Data to Listing File

    Users of TGO and TBC know exactly what I'm looking for here. One section of Trimble's Network Adjustment Report is a listing of covariance data. This data is a representation of relative positional accuracy between each pair of connected stations and is shown as a ratio. Anyone looking for an simple indication of whether or not your control net meets standards, that is 1:10,000 or whatever the desired minimum requirements, will appreciate having this data available. I've messed around with Starnet's Dump File, but the resultant covariance data is not in a format I can digest. I can calculate my…

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Include plotted histograms of residuals by type of observation in Listing output

    An enhanced sense of the distribution of residuals would be to be able to see them plotted on a histogram.

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Improve listing output to allow sorting by columns especially "Adjusted Obs & Residuals" section

    I would like to see more of a tabbed style interface with grids and sortable columns

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Incoporate a rinex baseline processor

    Why not complete your software package by including a rinex baseline processor. The User Friendly CORS site provides all base station data in rinex format and there are ConvertToRinex tools available. This would make your software truly independent.

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. GSI to STAR*NET dat-file

    GSI 8/16 is one of the most commonly used file formats in the sureying industry for storage and exchange of total station and levelling data. Some older, but far from outdated, Leica total stations even use GSI as native format. While there is a converter for Leica system 1200 files available for import into STAR*NET, there is no such tool for GSI data.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Option to remove unconnected fixed control from list report

    An additional project option - to remove any fixed control that is not connected to the traverse from the listing report. Also an option if you require the unconnected fixed control to appear in the final pts file.

    For example if you have 100's/1000's of fixed GPS detail observations (not part of the traverse) then they appear in many of the listing report sections with no values to analyse. The report is huge and takes time to find the traverse data. However you may still require the unconnected fixed coords to appear in the final pts.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Side Shot points to be sorted alphabetically/numerically in the pts file

    Currently sideshot points are only sorted by time rather than by alphabetically/numerically in the final pts file output. Traverse points are sorted alphabetically/numerically. It would be beneficial to have sideshot points sorted the samne as traverse points.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Improve / Expand Reading of Native Data Files

    Star*Net is almost universal. It would be nice if it read the native data files from Leica, Trimble, and Topcon. This would include GPS, Total Stations, & Levels.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
    started  ·  Darcy Detlor responded

    We are going to add everything that is published. Some manufactures keep this proprietary and change their formats constantly.

  11. Additional section in the listing report highlighting overall traverse accuracy ratio ie 1:20,000

    Most client specifications state a required accuracy level ratio for any control networks ie 1:20,000. Many other processing software output this. Would be very useful for Starnet to introduce this to the listing report. Is a pain to calculate by hand, or find another software to clarify.

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. After conversion with Leica DBX (GPS Coordinates), add GPS 3D Quality Values + Standard Deviations as a note next to each point observed

    When converting GPS data as a coordinate output, to add the 3DCQ and SD values (and length of time observed) as a note next to each GPS point in the converted dat file. This will allow the user to analyse the accuracy of each observation. Easy to output from the Leica DBX data (and others).

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Include Total Station Check Point Observations in the Listing Report

    It can take a long time to scan through data files to make sure all of the surveyor's check point observations are accurate from the noted text. Having these included as observations in the listing report would be hugely beneficial. Any large deviations could be instantly viewed.

    This would be the ideal scenario. Or failing that, a log file is created from the convertor highlighting all check point deviations in one easily readable text file. This could show missing check points at the end of setups. And highlight check shots over a certain tolerance.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Option to turn off Sideshots appearing in the pts file

    Currently you can only turn off sideshots from the listing file but not from the pts file.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Star*NET Increase Maximum Number of Stations Beyond 10,000

    I need to have the ability to adjust a network with more than 10,000 stations. I am responsible for monitoring the integrity and correctness of the State of Minnesota's geodetic network. The network consists of 81765 GPS vectors and 79094 elevation difference records . The GPS vectors connect 42285 unique stations. The elevation difference records connect 35907 unique stations. There are 40469 unique stations having BOTH GPS and elevation difference measurements. It is clear that I need to break the network into several pieces in order to analyze it. Eventually, I will need to run a statewide adjustment of all…

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Better Printing of Network Plot

    A pan/zoom function or 'Print Window' option for the network plot would be nice to see, to allow complete control of what is printed. As it sits, the preview doesn't necessarily coincide with what is printed, so you have to print it, then check it, then print again. Expanding the network plot view doesn't help either, it cuts off the edges at some invisible boundary.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Character limit

    There appears to be a character limit on either the input files or output. Using v8.1 point files are truncated at 81 to 83 characters, cutting off the description of a point if it is too long. A longer limit or no limit would be appreciated.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow both grid and ground data to be shown during an inverse query.

    Have the inverse in map produce both grid and ground distances. This is helpful when doing boundary lines in state plane and reporting ground distances between the monuments.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add an option to display all ties to a point with residuals and std residuals to "find" command.

    It would be very helpful to have all horizontal angles, distances and vertical angles to a point visible in the same place along with the residuals and std residuals. This would make it much easier to find "problem" measurements. It would be very nice if the user could enter a point number and have all this data pop up in a box.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Star*Net - automatically detect and compute closures for traverses

    automatically detect and compute closures for traverses formed by observations not explicitly labeled “T”, or alternatively, be able to enter a list of stations forming a traverse and have it compute closures based on observations connecting the stations in the list.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6
  • Don't see your idea?

MicroSurvey STAR*NET

Feedback and Knowledge Base