Because of the way IntelliCAD creates a copy of a partial menus content and resource DLL (the icons), then locks that DLL at the operating system level, users of our add-ons that change have to do a special procedure in order to see the new menu items and icons. For example our MapWorks product receives additions on pretty much a weekly basis and while we can update the files in our install folder, that’s not enough as it is on other platforms. Follow this procedure to see the new menu items and icons.
We’ve often said “we don’t mind hard work, it’s unnecessary work that bothers us“. Such is the case in obtaining lidar data for surface generation. From our previous experience the process involved:
- Use a browser to go to a certain government website.
- Zoom and pan around till we found the area of interest.
- Click to select our area and place our order.
- Wait for an email to arrive telling us our data is ready.
- Download to find it’s a massive file.
Most users won’t hit this limit and shouldn’t worry about it until they do. However a handful of our users processing extremely massive surfaces have reported an error message like “System.OutOfMemoryException” and/or “Array dimensions exceeded supported range”.
Most ESRI Shapefiles of contours are defined as flat polylines (at 0.0 elev) in the SHP file, and the user is expected to elevate the polylines using data defined in the accompanying DBF file. Here is a complete procedure using MapWorks to import these files with the polylines properly elevated.
Users of MapWorks/C3DTools 7.0 or higher see revision note below.
We have reached a fork in the road on our Civil/Survey and Mapping add-ons. For years we attempted to provide one package that ran inside plain CAD engines as well as Civil3D while using the best objects available. The problem is that it meant a weaker (than possible) Civil3D connection, prevented us from adding tools only (currently) possible in Civil3D and created confusion on what parts used Civil3D objects.
We are occasionally asked why our products don’t directly import point ascii files.
Keep in mind that TXT/ASC files can contain anything (even the paragraphs of this post content) so we process it differently. We have a Point > File > Convert Text which handles any text file, regardless of the delimiter. It lets you preview the content, specify the delimiter and column order then parse the results into a defined point format.
If your ascii files are P,N,E,Z,D you can simply change the extension to .AUF and the program would read the files directly.
The Coordinate System Select dialog has been improved. The system location panel is now a floating map viewer, when you select a system from the list it will zoom to the extents of the selected system. This allows closer examination of the extents of the system, not just the location on a global map. The rectangular coordinate system area is now filled to make it easier to see.
While the view is displayed, these controls are available.
- Use the mouse wheel to scroll the map in/out.
- Press the left mouse button and drag to pan the map as needed.
Several intersection tools were added to the Points module. New tools include Bearing-Bearing, Bearing-Distance, Distance-Distance and Four Points intersects.
Allows the input of deed calls (bearing/distance) along with curve options. All input is on the number pad for fast entry and the results are drawn as each segment is completed. You can save your input at any time, make changes and replay the script in case of bad input.