I'm working in a company, producing cadastral maps in ArcGIS where some clients prefer the maps being delivered in a .dwg-format. We're using a tool which preserves the feature class styles when importing them into AutoCAD.

The problem is how to handle som texts in the cartographic visualization. As we're not really allowed to move around objects in the enterprise database but still want some adjacent annotation classes, eg. administrative property information, to be visualized in the layout and the product, I can't really find a solution.

  • Converting the text to graphic would label the layer 'Graphic' in the DWG.
  • Exporting the layer to a file geodatabase and make the edits solves the problem. But might be time consuming.
  • Entering edit mode, move the annotations, make the export and stop editing without saving seems to be the fastest practice but at the same time a bit risky if the user by accident saves the edits.

So what I basically want is a method of making changes in the text, that doesn't store them in the enterprise database but still preserves the attributes of an annotation class.

Does anyone have a solution for the issue?

  • 1
    Can you really not change the enterprise database? There is Cartographic Representations resources.arcgis.com/en/help/main/10.2/index.html#//… but that would need to add some columns to the table... the geometric feature does not change but the visual feature can be moved, rotated etc.. – Michael Stimson Oct 4 '17 at 22:14
  • Well, I can but there's an external map service tied to the sde_database, so the changes will be visualized in that service immediately so it's not a recommended workflow making changes. Perhaps there´s a workaround for the map service but it is administrated by a third party. – user21070 Oct 5 '17 at 17:21
  • 1
    Ah, this is what cartographic representations are all about, your service will not even be aware, if it was designed properly, of your representations... the features (annotation is still just a feature) stay exactly as they are but your maps' perception of them can be different. They are also reusable, so all that work pushing around text isn't lost. Have a go at it in a checkout or copy of your enterprise feature classes, it should only take a few hours to get your head around the concepts and tools - only a little investment lost if you decide not to go that way. – Michael Stimson Oct 5 '17 at 21:22
  • Another option that I'll add for the sake of completeness is to make your edits in a version and then export. That way even if the editor accidentally saves the map service will not be aware of the edits. Then delete the version when done. – Dowlers Nov 3 '17 at 4:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.