Latest Contributions by VincentLaunstorfer

Thanks! It does improve readability, for sure. On the other hand, it cannot allow to view cell content with multiple lines (which is not often the case I must admit). ... View more

Hi, This thread is enormous! I do encounter performance issues which are unacceptable. In the meantime, I found an interesting (short) thread which greatly improved speed: https://community.esri.com/ideas/5157  I tested it this morning and it is much much better. To me, slowness issues are most of the time linked to GUIs. My issue this morning was about Calculate Field performance. However, I had similar problems editing annotation with Attributes pane open, which considerably slowed things. And I suspect updating symbology is a similar problem but I don't know how to update symobology with no GUI opened... Hope this help some of you. ... View more

Apparently, the Update Annotation Reference Scale is in the Cartography Toolbox: And the Code Sample from the tool section shows an example: import arcpy arcpy.cartography.UpdateAnnotationReferenceScale Is it not working? ... View more

Hi, The screenshot I shared above is with Annotation created in Pro (not imported from ArcMap). Also, the tool documentation states in the Usage section : "Before an annotation feature class can have its reference scale updated, it must be upgraded to the current release using the Upgrade Dataset tool. " Update Annotation Reference Scale—ArcGIS Pro | ArcGIS Desktop  And I believe the Reference scale would be updated in the Annotation Properties ... View more

Hi Jeff, Thanks for sharing details with us. To me, it seems essential to find out how certain software, such as Autocad, mentioned above can export smart and small .pdf. Because rasterizing exports won't necessarily produce smaller file compared to the "smart" .pdf export linked in this discussion. Technically, a simple 24x36 inches map will produce 10,800x7,200= 77,760,000 pixels image, for true colors at 3 bytes/pixel or 24 bit/pixel, will make 233,280,000 bytes, thus 222 MB (if I am not wrong). Fortunately, .png (or .jpg), do use good algorithms to reduce this size... For example, my 24x36 map mentioned earlier exports as 1,765KB in .png vs 2,614KB after performing some simplication before exporting to .pdf. There must be a trade-off, but not necessarily better in raster. And Jeff, what is the EAP for the next release? ... View more

Hi, I agree with Marco. A few months ago, I tried to upload a simple rasterized, tiled, on ArcGIS Online as a truly static "Web Map" for my organization and dotted lines were to rendered properly... On the other hand, all these dotted do export properly in regular .png directly from Pro. Something is not consistent in the raster exports. ... View more

Malcolm, To give you some number, I just performed an example on which I am currently working. It is a 24 x 36 inches map. I turned off all layers except the largest polyline feature class. There is no other map elements such as legend, title, text... - the polyline feature class has 2,606,964 vertices in total and it exports as a 18,310 KB .pdf file - same polyline feature class largely simplified and smoothed to suit the 1/4'000'000 map scale, has a new total of 311,224 vertices and it exports as 2,614 KB It clearly shows any projects with unnecessary vertices tend to slow projects, displays, analysis...and export file sizes! However, I still wonder if certain .pdf export "engine" are smarter depending on compression algorithms used. ... View more

"And there is no comparison to any .pdf exported from ArcGIS...", yes, I meant in filesize. As for the possibility to simplify/generalize vectors (in future Pro releases) to reduce the number of vertices, I would imagine this setting would be adjustable and users should be aware of the consequences. Finally, for "decreasing the vector quality", I made some tests by simplifying vectors to reduce vertices, and it did make a substantial smaller filesize. However, I mentioned "smart" export because I wonder if there are any smarter algorithms to compress vectors in exported .pdf files in order to reduce the final .pdf final without compromising the quality... Perhaps? Is the Autocad "engine" to export .pdf files smarter than the ESRI's one? ... View more

Hi, I totally agree with Malcolm. This .pdf exported from Autocad is unusually small, only 650k. And there is no comparison to any .pdf exported from ArcGIS... Inspecting the file in Adobe Illustrator in more details, it shows vertices are minimalist and Bezier curve were exported to further minimize vertices. All of this makes a surprisingly small file. We all know that total number of vertices and raster elements greatly impact exported .pdf file size, but it looks like it is also feasible to export smarter .pdf file. Good if ESRI works on "generalizing" vectors on export, but there is perhaps other settings/algorithm to explore to produce smarter .pdf... ... View more

Hi Keith, What do you mean by "Distances are off by varying factors ranging from 50 to 5000"? In your example above, I would believe nearest distance with the Near tool would be US feet... If you were using the Measure tool set to US feet and mode Geodesic and/or Planar in this case because shapefile is projected, you should get similar measurements. Is it the case ? If you get 5000 US foot difference, it looks like a lot! ... View more

Thanks for the letting us know about the right-click and "Add Leader" option... because for the time being, there was no solution to add a leader line easily. I mean you had to go to Edit tab -> Tools group -> Annotation tool and select Symbol properties in the Attributes dialog pane. ... View more

Thanks Jeremy for your reply. Turning off all other layer do not improve performance at all. For redrawing, yes. But not for editing annotations... In addition, in a typical ArcGIS Pro mapping project, there is always quite a few annotation feature classes open at the same time in order to make a complete map. On the other hand, what I discovered and which can be of great help to anybody editing annotation: if you edit annotation thought the Attributes Pane (Edit tab-> Selection group-> Attributes), it takes much longer than editing interactively directly on the map. So CLOSE the Attributes Pane. On the other end, you cannot edit angles (with precision), alignments and other properties interactively...  In terms of performance, updating an annotation in the Attributes pane mentioned above (Editing tab -> Tools group -> Attributes), such as a text, can take up to 45ec. Unbelievable! Just like changing Angle. In addition, I also noticed that any annotation with an angle other than 0 tend to take much longer to Apply changes. So far, I rebuild regularly the Spatial indexes in case they become not optimized and use Compact FGDB. Also, I am trying to fine tune Cache to improve performance... All of this until I find the best settings to work in better conditions... And something else bothers me. Even editing symbols from in point feature class (stored locally on FGDB) is really slow and perhaps slower than editing annotations. As Jeremy explained earlier, I understood that regular feature classes do not redraw like the annotation feature classes. Regular feature classes should make good use of Cache settings. This is another mystery to investigate. (previously in ArcMap, I used to convert point symbols in annotation feature class - not graphic layer stored only in .mxd project - and this was the best and faster workaround I found). But in ArcGIS Pro, it is not possible to convert point symbols in annotation feature class. Finally, there is a similar discussion in parallel on these issues here: https://community.esri.com/thread/222302-arcgis-pro-22-best-configuration  ... View more