Jump to content

jbrhwy

Member
  • Posts

    231
  • Joined

  • Last visited

Everything posted by jbrhwy

  1. Michael What happens when you increase the radius that is geometrically correct, but the tangent length is greater than 1/2 the distance between the vertexes. Never has worked correctly & probably will not until VW adds an additional vertex mode that doesn't depend on a mid-point (false vertex).
  2. Response from Tech Support: "Here is the result from offsetting the HPGCTerasen polyline. Handles show extra vertices on the outer offset polys; uppermost handle is the arc vertex from the original road centerline. So, to answer your original question, it looks like offsetting operations have improved. The vertex behavior that you have observed is still present." Arc vertex polylines where the tangent length of the curve is greater than 1/2 the distance between the vertexes can not be edited correctly. In addition there is no warning that the program will change the RADIUS.
  3. Chad Problem right from the start, even through the existing site model was clipped with a valid closed polygon (Boundary Object) the "Projected Area (Existing)" is shown the same before & after the boundary object added.
  4. Request suggestions on how to get VW to calculate volume of excavated base material (a pay quantity). Paved airport taxiway with variable slope: Pavement removed (variable depth), unsuitable base material excavated (variable depth & area). COGO survey undertaken to pickup bottom of pavement & top & bottom of base excavation areas, survey points imported as stake objects.
  5. VWL12 & VWL2008: Menu - Modify - Convert - Create object form polyline - Property line. I don't need a table of bearings & distance, but I am sure that someone on this board suggested using a worksheet.
  6. Azimuth update I spoke to Richard in late September & he the provided the following: I've been updating Azimuth recently to make it fully compatible with both PowerPC and Intel Macs. I've also been making Azimuth run more cleanly. There were too many bugs in the last version. There is still no support for datums. That would require Azimuth to create the upper plot layer to do some independent things that I've never gotten into. Richard Furno Azimuth
  7. Hello Alex Just send you a private email as I your email address bounced. Bruce
  8. Miguel Would appreciate your comments on my dilemma "agencies are requiring that as-built drawings be georeferenced." I have old optical total station data, old road designs & over 1 thousand cadestral plans that need to be georeferenced to GPS control. I am looking for a method of being able to switch views between ground & georeferenced grid so I can adjust the source data & check it against georeferenced aerial photography.
  9. I have been investigating other software because of the lack of georeferencing (will check to see if Safe Software's FME translation engine could be incorporated into Vectorworks).
  10. I use "Stake Obj List Plug-in" (I can't remember who supplied it). It exports a text file of point number, northing, easting, elevation, description for all stake objects in the file, all I need to transfer to my Ranger 500x running TDS Survey Pro Max.
  11. It would be very much appreciated if someone at Nemetschek would comment on this issue. It is causing a dilemma for me as road design projects often exceed 1 kilometre, survey data is collected from optical total stations & GPS, source cadestral data are in ground distances & agencies are requiring that as-built drawings be georeferenced.
  12. Fervently? - "having or displaying a passionate intensity" & all I have asked for for 15 years is a arc polyline that works correctly.
  13. Ian I think your thoughts above may be down playing the potential that landXML has for civil engineers, surveyors or land developers. Numerous schemas have been developed for these fields. Every major CAD software developer except Nemetschek is a member, which probably accounts for the low number of engineers & surveyors using Vectorworks, in fact most don't even know it exists. I would suggest that any one involved in these fields visit http://www.landxml.org/.
  14. Assume you are referring to ".xml" format which is the LandXML schema. I hope that VW will include import & export of LandXML data like AutoDesk & the developers of software for data collectors. Also VW should look at how polylines are handled by LandXML. "The LandXML schema facilitates the exchange of data create during the Land Planning, Civil Engineering and Land Survey process. Land development professionals can use LandXML to make the data they create more readily accessible and available to anyone involved with a project. With LandXML, project data is independent of the authoring software, thus overcoming the interoperability problems that have plagued the land development industry. Not only does LandXML provide interoperability between different application software, but also between varying versions of software. As a result, data can be archived and accessed more readily on future projects. Additionally, other web-based tools can be used to view, edit, and report LandXML data. Extensible Stylesheet Language (XSL) style sheets can be easily created and applied to LandXML data and then run from a project web page. Examples include XSL style sheets that format raw point data into point tables, or format data to match an organization's internal standards, such as legal descriptions for parcel reports. . ."
  15. One thing to keep in mind when using published "Minimum Vehicle Turning Radii Guidelines" - the minimum values assume that the vehicle is turning at a minimum speed (usually a minimum of 15 km/h). My low speed residential road designs are attempting to provide "Liveable Roads for All Travellers". Minimum radii that encourages motor vehicle drivers to enter residential intersections at speed ≥ 15 km/h increases the risk to pedestrians & cyclists. The minimum turning radii that I use were developed from actual measurements of motor vehicles turning from a stopped position, which in the residential situation is encouraged.
  16. Andi Would you post a Vectorworks file that demonstrates the problem you have with precision between layers.
  17. Raymond's Reshaper is an essential editing tool for me. For lines it has the option to display angles as an azimuth, wish Nemetschek would add this as an option in the OIP window. Raymond does it working with VW2009? I can't check as I am not upgrading until the issue of arc polylines is resolved (15 year wait).
  18. M.CH In VW2009 when you attempt to increase the arc radius of the polyline where the tangent distance of 1 arc is greater than 1/2 the total distance between the points of intersection - due you not get the error message "The arc radius is set to the maximum radius allowed" even though the selected radius would be mathematically correct?
  19. Jeffrey Thanks for looking at the file. What happens in VW2009 when you try & increase the radius of one of the arc vertexes using the object info pallet? In all previous versions it is not allowed even though it is mathematically correct, the "quietly placed extra vertices" prevents increasing the radius & the only work around is to delete the extra vertex & then add recussive vertexs until the new radii is accepted.
  20. Hello Ian Discussions regarding this problem are ongoing with Frank Brault of Vectorworks, but it appears Vectorworks 2009 doesn't address this problem & possibly never will be able to. In the mean time I am attaching a design drawing HPGCTerasen.mcd that shows how dependant I am on the polyline objects & will demonstrate the magnitude of the problem if I have to increase the radius of only 1 curve due to a design change. All polylines would have to be redrawn. Thanks to everyone for bearing with me on this issue, but I have spent thousands of hours trying to work around this limitation.
  21. Has anyone had the opportunity to check the result of offsetting the polyline created at step 4 in version 2009, is the resulting offset polyline no longer parallel to the original? Note: the polyline at step 5 can not be offset correctly with the Offset tool, but is correctly offset when using Manuel Garcia de Paredes Offset Path tool! Benson The problem is not unique to designing roads, any polyline with more than 2 arcs where the tangent distance of 1 arc is greater than 1/2 the distance between the intersection points can not be offset correctly & there is no warning that the new radii is not what was set in the preferences.
  22. Benson Thanks for taking the time to look at the problem, yes there is a short section of tangent between end of the first curve & start of the second curve. When I check the coordinates of PI's against the coordinates of the arc vertexes they are the same & the bearings to each PI, therefore, tangent. Did you look at what happens when you try to offset the polyline?
  23. Ariel I think the steps below sent to Frank Brault will show why 5 steps are needed to use the reshape tool. Yes the fillet tool will work, but you would have to use it twice & reset the radius preference & then end up with 8 vertexes instead of 5. If you need to revise the first radius to 90 metres you can not do it because Vectorworks inserted corner vertexes & if you delete them to change the radius, the PI (intersection point) moves. This defeats the original requirement to have total control of placing a radius between intersecting lines. Now try use to Offset tool to set the edge of curb at 4 metres, the first radius becomes 83.615 not 84 & the second radius becomes 23.875 not 24. "Frank 1. Connect road intersection points using polyline tool, all roads are designed from points of intersection & bearing to the next PI. 2. Change vertex corner points to arcs, the first will not accept the required 80 m radius, defaults to 61.08, the second one is changed to a radius of 20 metres. 3. Add a default corner vertex between PI1 & PI2. 4 Add a default corner vertex between the corner vertex created in step 3 & PI3. 5. Delete the corner vertex created at step 3 & now the radius of the first curve changes to 80 metres. The problem with this is that, if the design radius has to be changed then you have to start all over again because of the corner vertex placed at step 4 will not change with a new radius. What is required is mode that allows placing an arc between intersecting tangent lines. The Road tool has the same problem you can not create a road where the tangent distance of the curve is greater than 1/2 of the distance between the PI's.
  24. The attached file "Polyline problem.mcd" shows that it takes 5 steps to be able to have an arc radius of 80 metres for the first intersection point. If the first radius needs to be changed then the polyline has to be redraw if the required radius is greater than 61.801.
  25. Frank I did looked at the movie the day that VW2009 was released & it appeared that the offset polyline had added additional vertexes! After using this product since 1990 I find your remark very condescending, all you had to do was draw a polyline with the above condition to determine if 2009 had resolved the problem.
×
×
  • Create New...