Latest Contributions by MarcoBoeringa

Just a generic answer, but I always think linking to the ESRI maintained System Design Strategies wiki pages is useful for threads like these, due to the rich content of those pages. ... View more

This sounds like you me not be embedding fonts in the resulting PDFs, and the PC you are reviewing the PDFs on, may not have the required fonts for the particular annotation you attempt to export. This would be especially possible if you use multiple font faces. Are you sure the "Embed Fonts" option is checked? ... View more

Relevant link to a 3rd of April 2019 post by Cole Andrews that suggests ESRI internally already created an enhancement request for this: https://community.esri.com/ideas/13645-microsoft-access-accdb-support-in-arcgis-pro#comment-72023  ... View more

Relevant link to a 3rd of April 2019 post by Cole Andrews that suggests ESRI internally already created an enhancement request for this: https://community.esri.com/ideas/13645-microsoft-access-accdb-support-in-arcgis-pro#comment-72023  ... View more

In my experience, it can also horribly slow down drawing performance in ArcMap in some cases. I don't know if Pro or AGOL handle that aspect better, but for ArcMap, it can certainly create problems if "Scale symbols" is active for a layer. ... View more

Kory Kramer‌, any updates to this issue regarding a "versioned" Help for ArcGIS Pro? Clearly, based also on other users' responses here in the thread, there is a need for this, and ESRI always supported this for ArcMap. ... View more

Actually, adding the "Note" text mentioned on the Recalculate Feature Class Extent—Help | ArcGIS Desktop  Help page thatJoe Borgione‌ pointed out and that mentions the difference between domains and extents, to the Spatial Reference Help page, would already be a big win. ... View more

    Melita Kennedy schreef:     It's pulling the spatial reference xy domain which is square. The lower left / minimum values are good, but the max values may be blown out to either make the extent square or to make the xy resolution value a reasonable number. Melita Kennedy, Could these specific traits of the "domain" properties of a Spatial Reference be better documented on the Help page of the Spatial Reference? I was running into a similar issue, where calling: spatialRefDomain = spatialRef.domain arcpy.AddMessage("spatialRefDomain: " + spatialRefDomain) to inspect the extent's values, resulted in rather un-expected max values (spatialRefDomain: -20037700 -30241100 900699887774,099 900689684374,099), as I didn't realize these were related to the XY resolution of the dataset. The first impression of the "domains" is that they represent something like the "projection horizon" you mentioned, but your explanation makes clear they are something entirely different. I think the difference must be cleared up in the Help page of the Spatial Reference as well by adding extra documentation. The current page is rather minimal in explanations (although it is comprehensive in mentioning all properties). It probably could use some graphics as well to give some visual impression of these properties. ... View more

I now noticed that the ArcPy Classes Help pages, already provide hyperlinks for complex data types. All the more reason to add them to Geoprocessing tool's Syntax sections as well! ... View more

Huck, I reported this to the Dutch branch of ESRI and got two bugs logged: BUG-000122033 Intermittently, exporting a layout to a pdf if the map is using a coordinate system other than Web Mercator, the Terrain: Tinted Hillshade living atlas layer will export blocky and won't draw the entire layer if it is exported with "Best" image quality with a dpi greater than 96 and a page size greater than 64 x 33. BUG-000122689 Exporting layout to pdf that contain Terrain: Elevation Tinted Hillshade layer and high dpi will not draw the entire layer and some grid visible for all image quality. De workaround is om de optie “Output as Image” te selecteren en de Image Quality op Normal of lager te zetten.   So lets hope a future release solves these issues... ... View more

I am not sure what you are trying to achieve. As you noted yourself, and is also documented here: https://support.office.com/en-us/article/excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3#ID0EBABAAA=Newer_versions Excel can only handle 1M rows maximum. There is no way you will be getting past that limit by changing your import practices, it is after all the limit of the worksheet itself. For this amount of rows and data, you really should be looking at Microsoft Access. Databases can handle a far greater number of records. Access has basic functionality for summarizing and analyzing data too, so doing some calculations you would like to do in Excel, is likely possible in Access as well, although the process to get there will be different (defining SQL queries instead of defining formulas in Excel). ... View more

I think the best bet for something like this to ever see the light, is through the new / upcoming styling options in the OGC GeoPackage standard: https://www.geopackage.org/extensions.html https://github.com/jyutzler/ogc-tb-15-opf/blob/master/spec/5-sse.adoc It will probably take some time though, before we will see any decent support in the different GIS software solutions. Of course, with Pro adopting the common JSON format for its layer file format (*.lyrx), nothing prevents you from writing your own converter to ingest Pro layer files. This was not possible in ArcMap. ... View more

Do note that the OBJECTID field added by e.g. the Add Incrementing ID Field tool (that can be used against tables not registered with a geodatabase to create a unique ID field), will normally also create a database sequence on the same field, to auto-update the objectids whenever data is added to the same table. So simply copying existing data from another OBJECTID field to a newly created field, is not the same if you do not manually also add such a sequence to the new field. ... View more

A couple of basic things to note and take care off: - Field / column names with more than 30 characters will cause issues. Ensure you stay within that limit. - Sanitize column names as well, preferably only use alphanumeric characters and underscore - Don't start column name with number. - Special field types like binary fields or PostgreSQL "hstore" type columns cannot be used in your queries. Exclude them in the SQL, or use database views to do so. - Make sure you don't have GeometryCollection as shape type in any of the records in your geometry column, Polygon and MultiPolygon are OK. - Run the AddIncrementingIDField_management tool. It will add an OBJECTID field including sequence, allowing you to make e.g. selections once the layer is added to the TOC of ArcGIS. Also see my post here: https://community.esri.com/ideas/15921-support-for-postgresql-11#comment-73925  ... View more