Ben Beaumont

Hi @Aaron B Design, as per our discussions and correspondence with our local Aus Technical Support, we are following this up with the engineers and will endeavour to update you when we can. Thank you for bringing this to our attention.

@Carol Reznor I can offer the following: Plan rotation doesn't do anything other than pick your monitor up and rotate it so you don't need to crank your head. At least for Australia*, this is how we do it: 1. Establish your geolocation at a logical and known (pivot) point in the vicinity of your project. [Record the Lat/Long or Easting/Northing values separately.] 1 (a). Align your User Origin with the Internal Origin (the same pivot point above). [Cleverly Vectorworks holds the geo-location of the project in the background. It is only revealed with some tools like the Geo Stake]. 2. Set your angle precision very high, establish a useful 'project north' rotation and then use that angle as your Angle to True North (will rotate about the pivot point above). [Record this value separately.] 2 (a). Work on your project. 3. Prior to exporting back to .dwg, momentarily (ie; save prior, then revert to save afterwards) scrub the Angle to True North value and set the User Origin to match the georef. coordinate system. Vectorworks will write the User Orgin as the Internal Origin of the resulting exported .dwg file plus the rotation will be true to the source file/s. I hope that helps. I'm happy to assist further as required. *In Australia, the wider industry uses the very distant map grid datums of our map zones (which occur in Antarctica). ie; the Internal Origin of an incoming .dwg file (eg; a survey file) actually uses the datum of the grid zone. It's a simple method that serves our industry well - except for the floating point errors that can get introduced with such vast distances.

@LivingEarthDesignRegarding the blue fescue, try searching for festuca. Regarding the armeria maritima, try searching for armeria. A decent amount of housekeeping has happened, including tightening up the naming of plants.

@LivingEarthDesignI'll answer this via our local Support channel. Regards, Ben.

Hi Hugo, As discussed, I got a result by selecting a single emitter and using menu: Modify > Create Symbol [eg: Symbol-Z] I then selected the Plants and used menu: Modify > Convert > Replace with Symbol and used the Symbol-Z above. I then selected all the Symbol-Zs and used menu: Modify > Convert > Convert to Plug-in objects and elected to not convert sub-objects to groups. You'll be left with an emitters in the location of each of Plant.

@Narellecheck under menu: Tools > Partner Products > EvergreenConnect > EvergreenConnect Plant Availability.

@ontouralldayYou'll find ~700 complete Plant Styles with high quality Image Props in the _Plant (styles).

This is VE-99036 "Class visibility check box required" that @Hugues is looking into.

@DSmith2300you can view and download our 'paper' catalogue here. There are placeholders in our libraries with this same link in the data pane of the RM. We are actively looking to improve the catalog feature in the software. Please contact me via support@vectorworks.net.au, I genuinely would like to work with you on this.

@DSmith2300Thank you for your contribution. You must know that the libraries are provided as a convenience to our users. We are not a nursery and we can't provide detailed and authoritative botanical information. We are a CAD software company. Having said that, I encourage you to use the Vectorworks Plant Database and/or the 'Plant Catalog' feature to sort and find existing records based on various search criteria, including - in some instances - the provenance of a plant. The growers, nurseries and suppliers are definitely the more likely source of the kind of information you're after. There are also excellent resources online if you spend the time. You are welcome to contact the Australian office directly and speak with me, I would be more than happy to point you in the right direction and I am truely open to discussing your thoughts on how we might improve. I work a lot with our Australian users and have spent a lot of time building and extending the content. Our primary challenge is getting high quality images of good specimens that can be used to create Image Props, that can then be distributed by us. Our libraries are a combination of plant images we have inherited from the Northern Hemisphere and other more regional sources. Our users are routinely re-purposing the plants in our libraries as other species (based on form, size and appearance). [Are you aware we have a .pdf catalogue with images of all the plants in the libraries? Users find this incredibly useful.] Our users do their own research, manage and control their own catalogues and build their own libraries of Plant Styles they routinely use. I appreciate your engagement and sentiment but it's entirely up to you to make sure you're specifying the correct plant/s.

All Design Layers should be georeferenced to match the Document's CRS. Use the Geolocate Tool to position the Internal Origin in the vicinity of the site. There is a general 7km soft radius and 10km hard radius that you should work to. Generally the Internal Origin should be very close to the project geometry. [tip: (unless you have a specific project position/known setout point) set the User Origin to match the Georeferencing Coordinate System, then make a 1 km x 1km or 1 Mile x 1 Mile grid visible and snap to a grid intersection. That makes for nice whole figured Eastings and Northings for your Internal Origin position.] The Geolocate Tool will preserve the cartesian location of your geometry by placing a User Origin in the original (distant) location of the Internal Origin. The User Origin is discretionary. Unless an Angle to True North is introduced, it conveniently aligns to the 'hidden' CRS cartesian grid and can assist to display Eastings and Northings by way of the rulers. We don't need a User Origin for georeferencing to work.* When importing a 'geo aware' dwg file, the check box simply aligns the source .dwg origin with the CRS cartesian grid origin (it ignores the User origin entirely). In the case of the original post, the Internal Origin would have still been coincident with the (distant) origin of the 'hidden' CRS grid. Hence the imported geometry appearing a long way from that point. *To export your geometry as a .dwg, you'll need to set the User Origin to match the Georeferencing Coordinate System. This is because the .dwg export will write the location of the geometry relative to the User Origin not the Internal Origin. So the resulting geometry - when opened in a different piece of software - will be distant to the origin, just as the geometry you received in the first place was.

@gloruis please be in touch with me at bbeaumont@vectorworks.net.au. Regards, Ben.

Thank you @Peter Neufeld.. It took some tweaking, but I got it working (mostly) by considering neighbouring spigots as a single post. We just end up with an orphaned spigot at the end of a run, that's all. But that's easily fixed by ungrouping and deleting. The handgate works nicely - with the safety latches and self closing hinges included. @brody98 you'll find the Swimming Pool (glass) Fence Style options in the tool selector under ANZ Swimming Pool AS1926.1 ...

@John MoeThere is an issue with some of the (strappy leaf/ succulent type) 2d plant graphics not displaying correctly as a group when 'Apply fill across plant group' is checked. It is fixed for 2024. You can fix it yourself by rebuilding and/or inserting the filled polyline/polygon that appears at the back of the stack on Class 'Plants-Component-Color Fill'. That's the object that is unified to create the silhouette graphic. Tip: To quickly create the silhouette poly, use the polygon in 'outer boundary mode' and mouse around the folliage graphic. [CD-3937]

@Benson ShawI'll need to come back to you on how the Property Line behaves. If one draws a Property Line at the meridian of a CRS (so it's true and square) and change the longitude of the Internal Origin, we might expect the Property to become distorted on transformation - but it doesn't behave that way. The insertion of the object is shifted, but the regular shape and rotation is preserved. The Property Line tool may not be Geo aware - it may not show convergence. It's a question for the engineers. The Rotate Plan feature is a bit like picking up your monitor and turning it like a steering wheel so you don't need to crank your head. It's of transient help only. I think a better way to 'hard wire' your project to a "project north" would be to use the key-in Angle to True North and/or the Geolocate compass tool (yes, your option B). That way you could 'set and forget' the dominant geometry of your project to the regular internal Vectorworks cartesian grid AND preserve the geolocation.