Iterations: Best Practices

when you work in optioneer, these are some things to keep in mind to optimise your experience 🚫 deleting r esults , points, lines, configurations, and polygons is permanent deleting objects and project features deletes them for you and everyone in the project area here are some recommended ways to minimise the risk of mistaken deletion export all points, lines and polygons for a local backup from the data tab export all options for a local backup from the results library make copies of points, lines or polygons if you wish to edit them via the ⋮ icon 🗣 use descriptions and comments when you add a point, line, or polygon or run an analysis in optioneer, you have the option to provide a description we recommend you use the description section to detail why it was actioned, who approved the action and reference any relevant document or correspondence use https //shared archbee space/doc/gkezv3rgh6bdgt wvojm6/ssj9zklkmy8 ma biamtf to make this simple 🏷 naming conventions naming conventions help keep your work organised we've outlined some suggested conventions for naming optioneer's different project elements below configurations we suggest a naming structure that connects the name to its intended purpose use the configuration description to add more detail where possible the description can be accessed in the basic information of any configuration date type name or, version type name where, type = the config, which can either be baseline exactly what is determined in the data register without any tweaks iteration an iteration of the baseline evaluation includes the penalties specified plus design rules which allow you to obtain metrics from optioneer name = another distinctive characteristic it may minimise length through a national park, follows roads etc cases and options cases and options are ordered by the date and have the time stamp next to them in the results library so, dates aren’t required in case and option naming we suggest the following structure to keep your cases searchable startpoint endpoint config type startpoint endpoint configtype version e g pointa pointb baseline alternatively, if evaluating a line then you could use this general format whatever you choose, just keep it consistent throughout the project linename configname linename configname version project features naming project features sensibly will help you search, filter and track them effectively use the project feature description for keywords that will help you filter certain results project feature names should be unique unambiguous to the team for example, naming a point edinburgh castle (start point) describes its location and relevance to the project 📑 assign categories to project features and comments assigning categories can help visualise different scenarios or types of comments within the optioneer environment type in the select category field to create a new category changing the colour or deleting a category will do the same for all lines within that category if you've developed other good best practices, let our team know! we'd love to see how you use optioneer