Latest Contributions by MarcoBoeringa

Have you also attempted to first explicitely add both the "target_layer" and "symbology_layer" to a Map in Pro using arcpy "addLayer", and then run the "arcpy.ApplySymbologyFromLayer_management" command, instead of first updating symbology, and then adding the symbolized layer to the Map? In my experience, this seems to solve the issue with the styling not updating. After that, I simply delete the no longer needed "symbology_layer" using arcpy "removeLayer" in the Map document of Pro. ... View more

Can you elaborate what you mean with "tiles" and how you actually know that they are "finished"? This is really unexpected in PostgreSQL. The whole idea of working with a spatial database, is to not have "tiles" or map sheets maintained in the RDBMS, but only generate these upon export to e.g. PDF (or something like modern Vector Tiles). So you should be working "tile-less" on a seamless database. As to technical implementation of some kind of automation in an RDBMS, one feature is the use of "triggers": https://www.postgresql.org/docs/11/plpgsql-trigger.html or define some custom function. But this all requires some DBA skills to implement. Of course, there is also ESRI's commercial products, e.g. "ESRI Production Mapping" (https://www.esri.com/en-us/arcgis/products/esri-production-mapping/overview), that was specifically designed for managing a production mapping workflow and keeping track of progress of tasks and such. ... View more

I think your best bet to make this managable, is to use ArcGIS Pro 2.3+ new "Output as image" option that ESRI's Jeremy Wright‌ refers to in this other thread. At least you will have only a single image to deal with in the resulting PDF, which should make your life a lot easier: https://community.esri.com/thread/179579#comment-819908 If you are still working primarily with ArcMap, you can simply import the map document in Pro, and then output to PDF using the "Share" option from the Layout ribbon. This works really well. ... View more

No doubt, especially if a raster basemap is created. Reducing 400+ vector layers connected to a PostGIS database to a single raster layer, will surely take the memory usage down to next to zero, but at the cost of a huge amount of processing time to create a raster tile cache. And this is no solution for high quality vector output to e.g. PDF, which is my main interest at this point. And there is the added problem, that there seems to be no current option to retain the full complex symbology in a basemap. All options seem to drop at least part of the complex symbology and labeling options (e.g. vector tiles), or don't allow high dpi raster tile output so you sacrifice quality. Neither is particularly appealing to me at this point, especially also since my main interest is outputting PDFs as I already wrote. ... View more

Thomas L schreef: ... Slow ArcGIS Pro project opening and saving time is linked to the number of Layouts and Maps in the project on our systems. Deleting (primarily) Maps, reduce the opening and saving time dramatically. We a still testing what layers in the Maps are responsible for this. @Thomas L, In my experience, slow opening and saving in Pro is directly, and linearly, related to the memory consumption of Pro. Pro in its current state, needs copious amounts of RAM / Virtual Memory compared to ArcMap. I have some very complex topographic map style Map document with hundreds of Query Layers accessing a PostGIS database. ArcMap manages to handle these documents in its 2GB memory limit. Not Pro... The bigger the underlying database in terms of GB storage, the bigger Pro's memory consumption. I have seen Pro consume up to 70GB(!) of memory (my laptop only has 32GB RAM, so rest is consumed as Windows "Virtual Memory" on disk). Such documents take up to 10 minutes to close, simply to release all the used (virtual) memory. I have actually monitored this process, by opening the Resource Monitor from the Performance TAB of the Windows Task Manager. Pro will not close until it has released all this virtual memory, and during this 10 minute waiting time, I slowly see the memory consumption of Pro decline in the Resource Monitor until the app finally closes when almost all memory has been released. I therefor think this is not really a memory leak, but "by design"... probably combined with to conservative releasing of memory during application use, meaning Pro does not release its memory even if it could or should. I do think ESRI should have a closer look at this memory consumption issue of Pro. Having Pro consume anywhere from 5 to 30x more memory for what is essentially the same map document (I literally import ArcMap documents in Pro), is worrying to say the least. ... View more

Kory Kramer‌, Thanks, good to hear! ... View more

Kory Kramer‌, With Pro 2.3 around the corner, and likely quite big and possibly (backwards) compatibility breaking changes coming up due to all the new functionality, is a versioned Pro Help anywhere on the horizon? ESRI never had issues with keeping a versioned Help for ArcGIS for Desktop alive, which was a really big asset to users and programmers, so can we expect this in the near future for Pro as well, is there any work being done to realize this? ... View more

To be fair to ESRI, compared to many other GIS's or CAD applications, ESRI already supports a considerable amount of databases, even for part of their most advanced "geodatabase" type functionality with all it goodies of specialized datasets with advanced properties (Network Datasets, Topology etc.) Anyway, Vertica seems a big data / cloud computation spin off of PostgreSQL if I read this right on the pyodbc pages, so support may be coming one day. ... View more

Per esri support, there is no way to connect to Vertica in ArcGIS Pro This is not entirely true. While it is true ESRI does not list Vertica under its "Supported database management systems" (Supported database management systems—Help | ArcGIS Desktop ), and you will thus not be able to create an "ordinary" ArcGIS Database Connection (*.sde) and access Vertica tables directly from the catalog window, nothing prevents you from connecting to Vertica using ODBC and Python / ArcPy. I have successfully used the "pyodbc" Python package (Home · mkleehammer/pyodbc Wiki · GitHub) to connect to PostgreSQL 11.1 and send DDL statements to the database from both ArcMap and ArcGIS Pro through ODBC. The same thing would work with Vertica, as Vertica is listed for pyodbc as well. Although I personally have only used pyodbc to send DDL statements like CREATE (MATERIALIZED) VIEW to the database, you should be able to access record sets as well in Python / ArcPy using SELECT statements and pyodbc. You could then use ArcPy to write out the resulting data received through ODBC to a supported database platform, or just simply an ESRI File Geodatabase. Of course, this is not as convenient as an ArcGIS Database Connection, yet it will allow you to do a lot with the Vertica stored data with a bit of programming. By the way, installing pyodbc in Pro is dead simple using the included Python Package Manager. It is listed as one of the installable packages. For ArcMap, it is a little bit more complicated, as you need to use the Windows Command Line and "pip" to install it. ... View more

Hi Umut, Interesting issue. One thing I did notice though, when watching that video, is that your output location is set to your user profile, and that the failure is about not being able to create the output table. Have you also attempted to write to another drive? I am wondering, since the background processing runs in another process, if that process potentially has different rights, and simply has no access to your user profile, and hence fails to write the required new feature class to the file geodatabase. ... View more

@Timothy Casey, Do note that this is of course all "at your own risk"... And it will be vital to have basic knowledge of configuring access to a PostgreSQL database, the type of knowledge a good DBA should have. There is some configuration to be done to get access to a PostgreSQL database from another computer than where the PostgreSQL server runs, and there are PostgreSQL configurations files you may need to modify, e.g. to specify allowed IP addresses of computers that should be able to access the database, and possibly things like port numbers the database should listen at. I've managed to figure out a lot of this stuff myself based on reading documentation, help and PostgreSQL discussion threads on the internet, but I strongly recommend some "starter" DBA type course for PostgreSQL if you don't have a solid IT background and some form of DBA experience (not necessarily PostgreSQL). ... View more

Hi, I am slightly wondering what issue you have connecting to the Relational Data Store being a PostgreSQL database? I must admit I have no experience with Data Store itself, but looking through some of the Help pages of Data Store, I am pretty sure you should be able to connect to the underlying database using at least your ArcGIS Server administrator's credentials and using something like a plain Window's PostgreSQL ODBC connection DSN. Do note though, that ESRI actually intends the Data Store to be a kind of "encapsulated" and internally managed by e.g. ArcGIS (Server) tools, not so much directly managed and accessed (which may represent a risk in trashing the Data Store just like you can when accessing an ESRI Enterprise Geodatabase through tools not designed by ESRI), see the link to the other GeoNet thread entirely below and what Derek Law wrote there. However, as to this topic, I have successfully used ArcPy and the "pyodbc" Python package (you can install it from the ArcGIS Pro package manager as it is listed there. For reference of pyodbc, see this: https://github.com/mkleehammer/pyodbc) to connect to a plain spatial PostgreSQL database, so not an ESR Enterprise Geodatabase enabled database. I have used this connection to create e.g. spatial database views using standard SQL DDL statements like "CREATE (MATERIALIZED) VIEW" written in ordinary Python / ArcPy sripting etc. without issues. I can subsequently browse such spatial database views from Pro by creating a standard ArcGIS "Database Connection" in the Catalog window and add the layers as ArcGIS Query Layers (http://pro.arcgis.com/en/pro-app/help/data/query-layers/what-is-a-query-layer-.htm). You just need to be careful defining the views: some PostgreSQL field / column types are not supported in ArcGIS, a notable example being the key/value storage PostgreSQL field type "hstore". If your database tables contain such field, you must exclude it in the SQL DDL statement for creating the view, so don't blindly specify something like "CREATE VIEW X AS SELECT * FROM YOUR_TABLE", because it may not be accesible due to invalid field types. Specify the exact field names to use in the DDL statement. To do this kind of thing though, you will need DBA type knowledge of managing PostgreSQL. If you don't have that, get some course to educate yourself in this respect. This post by Derek Law also explains something about ArcGIS Data Store that might be of use: https://community.esri.com/thread/191678-arcgis-data-store-and-rdbms ... View more

Jeff, Will this rasterization option retain the full symbology of existing maps? Is it going to be truly WYSIWYG, except for being rasterized at hopefully high ppi (300+ ppi minimum)? I ask this, because e.g. the high performance engine driving creation of (raster) tiles for web maps, isn't capable of fully retaining symbology, there are some debilitating limitations. This is actually a bit of a headache, as it seems, even if you explicitly choose to build tiles locally instead of in the cloud, you still loose the ability to fully retain detailed topographic styling. Maybe I have missed it while looking over the options, but it seems ESRI actually currently offers no option at all, not even as a simple flattened single layer rasterized image, to retain full high quality cartographic maps in some form of a web mapping service. It would be a pain to see similar limitations in a future PDF rasterization output option, with loss of vital symbology. I really hope for a true WYSIWYG solution. ... View more

Kory, while you're on it, could you please keep in mind, and possibly take this up with the same dev team members, the performance issue and suspision I raised concerning "Tasks" and toolvalidation in Pro: https://community.esri.com/ideas/15362  This may be related, and I have never heard a definitive answer of you whether this was actually being looked and worked on seriously by the dev team, while I think it should. ... View more