Latest Contributions by MarcoBoeringa

Nice you got it to work. Haven't had a look at the rotation properties myself, so missed the obvious. ... View more

It may be a bug in the CIM access. The one time I tried it, and used CIM access to change label properties for a Query Layer, I discovered it resulted in the loss of the datasource as soon as I set the CIM definition using lyr.setDefinition. This made CIM access unusable for me. In my particular case, it was possible to workaround the issue by saving the layer to disk first as *.lyrx layer file using lyr.saveACopy, then do a json edit using the ordinary Python json.load and json.dump methods, and finally reload the layer in the project. This requires good knowledge and understanding of the structure of the CIM though, and how it translates to the dictionary structure that json.load creates. It took me a couple of rounds and thought to get it right. Also, ESRI definitely, and probably rightly so, discourages direct json editing of layer files, but it can be done if you are careful. ... View more

Definitely one to report to ESRI, seems like a clear bug as you concluded based on your description. ... View more

The error message itself refers to Unicode and ascii. It suggest you may have some non-ascii text characters in some of your data, that subsequently cause an issue when part of the processing pipeline you are using tries to handle this. E.g. you can't represent a Chinese character in ascii. So, are there any special language specific characters in your data? If so, maybe replacing them by safer ascii text characters only solves the issue. ... View more

Note: I am not working for ESRI Full compatibility may be some time away, but there are some positive developments. There have been recent blog posts from ESRI regarding vector symbols in webservices and efforts for incorporating the full CIM (Cartographic Information Model) in the ArcGIS API for JavaScript, which means that the full potential of cartographic display in ArcGIS Pro, may become available in (vector symbology based) webservices as well. Since ArcGIS Pro can import almost all symbology from ArcMap, I guess this might mean that at some point in the future, you will be able to even have legacy ArcMap TTF fonts symbology fully displayable across the board. Use Published 2D Symbols in ArcGIS Online  What’s New in ArcGIS API for JavaScript (October 2020)  Create points, lines, and polygons using CIMSymbols  ... View more

I also wonder if this issue is actually being worked on? This is a quite hideous issue, causing significant problems for arcpy / Python development. I have reported a similar issue to the Dutch branch of ESRI based on a custom arcpy Python geoprocessing tool of mine that suddenly started failing going from Pro 2.4.3 to Pro 2.5, and the issue was also caused by left over *.lock files in a File Geodatabase folder, that weren't being cleaned up in Pro 2.5, while not an issue and being cleared properly in Pro 2.4.3. It is registered as: BUG-000131154 Fgdb locking behavior is different in ArcGIS Pro 2.5 to ArcGIS Pro 2.4.3 for copying styles ... View more

Cooper Logan‌, I am confused. This issue is about File Geodatabases being kept locked. The workaround you suggested shouldn't work according to this Help page, as arcpy.ClearWorkspaceCache_management() is only supposed to do anything for Enterprise Geodatabases, not File Geodatabases. The Help is quite adamant on that aspect: "This tool only works with enterprise geodatabase workspaces." ... View more

Hi Willem Jenniskens‌, I don't know if this will serve your purpose, but this ESRI blog post talks about the ability to vary WHERE clause or even entire table name depending on view scale when using ArcGIS Query Layers: Scale dependent multiple datasources for a single feature layer  This will likely still require the different spatial tables coming from a single data source though, as the connection settings probably cannot be varied, so unless you could somehow "link" to the other database's table from within the current one, like is potentially possible in PostgreSQL, this wouldn't work for you. And of course, this is only useful if you have strict scale dependency of the different layers. Alternatively, ESRI recently blogged about the ability to reference multiple data sources in one vector tile layer. I haven't been able to find that particular blog article again, but I think this is actually the relevant Pro Help page describing the functionality: Multiple vector tile sources—ArcGIS Pro | Documentation  Of course, this requires to spin up a vector tile service, which may or may not be suitable for you. Note that I have tried neither of these options. ... View more

If you intend to only create read-only feature classes that do not need any ESRI Geodatabase functionality, then I second Mody Buchbinder‌ suggestion of using pyodbc to insert the records into the MSSQL table. This means you need to replace the nested arcpy.InsertCursor with an appropriate pyodbc Cursor object. I have written a Python multi-threaded application doing just that, and successfully used it to insert > 100M(!) records from a File Geodatabase into a PostgreSQL table. Note that pyodbc is available in the ArcGIS Pro Conda environment. Just select it from there and install it to start working with it. By the way, I recommend inserting as WKT (Well Know Text) geometries using the "SHAPE@WKT" token, and not use pyodbc "parameter binding" but just concatenate all fields to transfer into a long INSERT string statement. I have seen some instabilities with WKB and using parameter binding on ultra large datasets, that maybe related to some known unresolved issues with pyodbc and parameter binding (but this is speculation from my side at this point in time... you can try WKB and parameter binding on smaller datasets and see if it works for you). ... View more

Good you got some of these issues logged with ESRI. I do think however, that some limitations to "Clause Mode" versus "SQL Mode" are logical. It is probably really hard to represent some of the more complex SQL in a sensible way in the "Clause Mode". If you are that much into SQL anyway, why not directly edit in SQL? I personally almost never use "Clause Mode", I much prefer seeing and editing the actual SQL statement. Only rarely do I switch to "Clause Mode". I actually filed an ArcGIS Idea for allowing a preset in the ArcGIS Pro project settings for choosing between Clause or SQL mode. Vote it up if you agree: Application wide setting / option to switch between "Clause" and "SQL" mode for expressions  ... View more

Hi H.Alex, I don't work for ESRI, I am a user like you. However, posting performance issues based on mediocre hardware, won't help clarifying the real problems. There is a lot more software out there, that won't properly run without at least a dedicated graphics card. I am totally with you that an ESRI SWAT team hunting down and fixing bugs is direly needed... In fact, I think one of the main issues is that ESRI's backlog of fixing true bugs or other issues is so huge, that they don't manage to catch up with it. As a result, users keep reporting the same issues time and again, which in turn leads to valuable resources in terms of man power dedicated to support and resolving issues being wasted (support analysts / software developers) . Each time a user needs to report an issue that is already known by ESRI, a support analyst - and the user / client - wastes his precious time, that could have been used to track down and report other issues. This is a vicious circle, that can only be broken by drastic measures (e.g. automated testing, better quality control before shipping releases etc.). In addition, I have always felt that beside a "SWAT" team, ESRI maybe should halt *all* new development on all their software for a period of e.g. 3-6 months, and put all of their developer resources behind an all out effort into fixing as many known issues / bugs as possible. This is super drastic measure, but I think almost inevitable given the current situation if ESRI really wants to ever be able to catch up with the problems. This could help in shifting the severe imbalance between the amount of time and manpower going into dealing with recurring known issues, and real knew ones, and significantly lower the allover "technical debt" in terms of issues needing fixing, and shift the overall balance between time spend on known issues to a more sane level, freeing up valuable resources to invest in e.g. overall quality control before shipping and thereby significantly and durably reduce the overall quality deficit and amount of issues in released software. This issue of imbalance is almost like an ecological problem, where disturbing the natural balance, can shift an entire ecosystem to a new stable, but severely degraded, equilibrium with much less species diversity and ecological health. We need to get to a sane new "natural balance", away from the current sickly equilibrium I.M.O. Unfortunately, this has been an seemingly almost perpetual issue with ESRI to some extent. It is sad, because I do think there is a lot of dedicated support analysts out there doing great work, but could spend their time way more efficiently and satisfactory if issues were fixed in timely, A.S.A.P., manner instead of left to linger for release after release in some cases. ... View more

I do not want to challenge your real world problems, but your specs and screenshot clearly show this is not a high end laptop, nor even close to it, and unfortunately you also don't seem to have a dedicated GPU contrary to what you thought. Most Intel processors have an integrated GPU, and the "Intel UHD Graphics 620" you show, is just such a one. This has far less performance than e.g. a dedicated NVidia GPU. The 8GB "Shared GPU memory" is just ordinary RAM, not dedicated GPU DDR5 OR 6, which means the GPU "eats" away at your RAM, leaving less memory for the OS and ArcGIS Pro to work with. Also, the latest Intel mobile Core i5 processors are already above 4GHz at top speed, rather than the slow 1.9GHz (although that may be base frequency, not peak). At least having a dedicated GPU should definitely help with Pro, although it is also definitely not a panacea for all performance issues with Pro, far from it unfortunately... ... View more

I am slightly at loss why you don't feed the SQL clause used in the "Table Select" tool directly into the arpy.da.SearchCursor. If I am right, this should just work and give the same results, and maybe then the ORDER BY will work as well, as there is an actual SQL clause to combine it with. ... View more

Melissa Brooks‌, I would definitely recommend reporting this to ESRI as a supposed bug a.s.a.p. I unfortunately have had to report multiple major bugs in the Maplex label engine for multiple consecutive versions of ArcGIS in the past three years. In fact, the Maplex label engine has had blocking issues for me personally in versions 10.3.x to 10.5.x of ArcMap, and Pro 2.0? to 2.3?. Only with ArcMap 10.6 and I think it was Pro 2.4.3 were these issues finally resolved and could I finally get results comparable to ArcMap 10.2.x (which appeared to be largely bug fee to me). ... View more