Latest Contributions by MarkChilcott

Hi Peoples, One our analysts provided his take on it here.  Some interesting points, so have provided below.  I have seen almost the same issues in the distant past when dealing with Oracle and Oracle Spatial.  As always, it comes back to what the primary business objective is. There are three main issues we found when loading spatial data into PostgreSQL using the PostGIS geometry type (without ArcSDE).   Multiple Geometry Types vs Single Geometry Types PostGIS allows for a mixture of different shape types (point,line,polygon) to be stored against the one feature/row. ArcGIS expects only one shape type per table, so a mixture of geometry types will cause an error or display nothing. Invalid geometry PostGIS allows the storage of invalid geometry. It is up to the application, or developer, to ensure the data is valid before inserting it into the table. Alternatively, all applications reading the data must be able to accommodate invalid geometry. ArcSDE, on the other hand, does not allow for the insertion of invalid geometry. Curve Geometry Representation The storage of curves (curved lines or curved polygons) is varied and complicated in PostGIS. Probably better to explain face-to-face. We had to do a lot of work in FME to create a PostGIS Writer that will create data that is readable by ArcGIS applications. It was complicated, and I wouldn’t be surprised if more issues arise in the future. Note that if only point geometry is being stored, then using the PostGIS geometry should be fine. Consider ArcSDE installed on top of PostgreSQL and using PostGIS as the underlying geometry storage type. At face value this sounds like it should make everyone happy, ArcSDE ensures that only a single geometry type is used, validates the geometry, and converts the curves into a structure that ArcGIS can handle. This approach works for the “single geometry type” and “invalid geometry” issues, but it does something weird to curves – ArcGIS creates an additional binary column in the table and stores the curves in a way that other PostGIS clients can’t read, which actually defeats the whole purpose of using the PostGIS geometry type! We worked out that if we convert curves to straight line segments, and do a bit more data “massaging”, we can load the data in a way that can be read by ArcGIS and PostGIS clients (like QGIS). Assuming we are using PostgreSQL as the underlying database consider : If the applications accessing a spatial database are purely ArcGIS applications, use ArcSDE with ST_Geometry. If ArcGIS is the primary application accessing a database, but other types of clients need access too: Use ArcSDE with PostGIS Geometry Type, but be aware of the curve geometry issues. If non-ArcGIS clients are the predominant software accessing the data, go with straight PostgreSQL/PostGIS, but be real careful with how you handle geometry.   PS:  There is a side note here – you can install the ST_geometry into PostgreSQL and use that. ... View more

Hi Russell, Thanks for looking into this.  I can't seem to reproduce the steps you have used.  Could you break it down for me please. In MyContent New Item URL https://services.thelist.tas.gov.au/arcgis/rest/services/AerialPhotoViewer/AerialPhoto_Time/MapServer Type : ArcGIS Web Server Does not open in map viewers I tried again with reference to the one layer New Item URL https://services.thelist.tas.gov.au/arcgis/rest/services/AerialPhotoViewer/AerialPhoto_Time/MapServer/0 Type : ArcGIS Web Server This opens in Classic Map viewer.  Does not open in new map viewer. The one you created  works - what did you do?   I noted there was not identify in yours?       Cheers, Mark ... View more

Hi Russell, You should be able to see the following public map. https://arcg.is/imG1i Layers are coming from our ArcGIS Server:  https://services.thelist.tas.gov.au/arcgis/rest/services/AerialPhotoViewer/AerialPhoto_Time/MapServer Cheers, Mark   ... View more

Old school.  Love it. ... View more

Hi @KoryKramer - brilliant tool, and necessary for being able to easily document Geodatabase design.  This sort of function is often overlooked in Product Plans for some other interface tools - when in reality it is a more essential part of design which ultimately more often leads to the success of a project, especially larger Enterprise solutions.  Too often in GIS this type of tool is overlooked.  Nothing can substitute for good planning, and communication of the plan. ... View more

Hi Peoples, Answer is here.  This article provides a current status on Esri's certification of Windows 11 for ArcGIS Pro and ArcMap.  FAQ: Is Windows 11 certified with ArcGIS Pro or ArcMap?  "Our goal is to complete this certification testing in early 2022." Cheers, Mark       ... View more

Hi Dan, Our user base are getting notifications from Microsoft their computers are ready for the Windows 11 upgrade, so they are asking if it is OK to proceed. (With Covid and working from home arrangements mainly, not in our core office environment) Considering Esri are not currently certified  -  looking for a more definitive time frame. Cheers, Mark ... View more

I revisited this recently - it has been a few years and things change. From what I can see, if you have data in SQL Server native, then you can use ArcGIS Query layers to read the data.  There are a few caveats around having a unique integer ID, field types being compatible and having only one data type per table (point, line or polygon).  Probably issues with coordinate system definitions as well. To edit the data you need to publish it through ArcGIS Server as web feature layer.   This is one of the better references: Databases and ArcGIS    ... View more

It's an old thread - but for completeness the ArcGIS now supports connecting to Microsoft SQL Server databases on Linux. You can also create geodatabases in SQL Server on Linux. In addition, you can connect from ArcGIS Server on Linux to SQL Server on Windows or Linux.  Introduced in 10.6 What's new in ArcGIS Server 10.6   ... View more