Additional Optioneer Design Rules

beyond optioneer's docid\ qvg268wfcjftpo4d mwzm , docid\ tfvxo7liwgk0waxc0apkv and getting familiar with docid 27bqf8ykvxa8xyjh6awkm , there are a few other design rules in the platform that offer valuable insights for your development process these are generally tied to specific use cases or reporting requirements, which we are happy to explore in greater depth with your team docid\ hplwzecx8c kq83s3z7p a key design rule when docid\ u m3xc 1mi7ywqjjuukwq docid\ mxpeprqicszt5o2qxytal calculates the number of proximal features docid\ fwnijrg4q l4in3m0gstk calculates the degree of proximity to features docid\ wohrcm3ffewmemojripwn habitat impact quantification docid\ oghomcb9l5orhlkqn7yuc hourly breakdown of constraint impacts to development docid 0dmyphc1lzlizun3o4hwz legacy superseded by visualize parameters docid\ ggqzao7hqh vscyqetem legacy encourages following your instance of optioneer might not have some of these additional design rules for a few reasons 1 geographical continent / region 2 asset class onshore vs offshore 3 subscription screening vs development vs enterprise get in touch with us if you expect to see something that isn't there! pro tip if a design rule doesn't exist for the calculation you want carried out on your development options, you can build one out yourself once you have gone through docid\ lfrskxndb1bp2mta6augq by setting up your own docid\ boo ouqh7dl7c723vixeo !