This Saturday, April 11, from 9am – 1pm EDT we will be performing maintenance on the Vectorworks Community Board. During this time, the site will be unavailable.
Search the Community
Showing results for tags 'shapefile'.
Found 2 results
Hi Team. In previous versions of Vectorworks Landmark the User Origin is recognised by the shapefile importer & exporter as the 0,0 point for GIS data. This allows shapefiles to be generated directly from drawings which have an offset User Origin through a previous CAD file import (eg. from a civil engineer or surveyor). You simply georeference the layer to the coordinate system of the received CAD file, and export. It also allows a shapefile imported into an existing drawing based on a previously imported CAD file to appear in the correct position, provided that the shapefile and the CAD file share the same coordinate system. In Vectorworks Landmark 2020 I've found so far that both the shapefile import and export functions ignore any User Origin settings, and handle GIS data relative to the Internal Origin only. This prevents a shapefile from being correctly exported from a drawing with an offset User Origin (through previous import of a surveyors CAD file), and results in shapefile data imported into drawings with an offset User Origin appearing at the wrong numerical coordinates within Vectorworks. Perhaps for technical reasons the introduction of the new Geolocate and Geoimage tools required this separation of GIS and CAD workflows, but it certainly seems like a step backwards in terms of CAD/GIS integration. I'd be interested to hear other's thoughts.
We are trying to propose on a project that requires a fairly regulated interchange with certain GIS shapefile standards. I was wondering if anyone has had any experience exporting shapefiles (.shp) and if so, have you ever had to meet any standards? The requirements of our interchange are as follows: DIGITAL SUBMISSION STANDARDS: §The required format for digital submissions of the graphic data is an ESRI v10.4.1 shapefile or Geodatabase (personal or file) §Must be projected in NAD 83 CA State Plane V §Must contain FDGC and City compliant metadata (See section 08 for Metadata template) §Documentation on any MXDs or Domains created§Should be topologically correct against City data §Provide validation documentation (topologies, data quality checks)