Latest Contributions by WalterSimonazzi1

The workflow to create an enterprise geodatabase in PostgreSQL/RDS is bit different compared it with going through the same workflow in a PostgreSQL deployed on premises. We basically need to manually do some of the steps the tool Create Enterprise Geodatabase does and then complete the process using the tool Enable Enterprise Geodatabase. The steps are: Create a connection to the PostgreSQL/RDS instance using PgAdmin 4.  In PgAdmin4, create or select the database you want to use for your GIS data. Create the sde user, Add the user to the rds_superuser role and create an sde schema. If in addition to the st_geometry storage type you want to have the option to store geometries in PostGIS storage type, check out this link , it describes the process to install PostGIS in Amazon RDS. Open ArcMap and search for the tool Enable Enterprise Geodatabase. Add the link to the connection file you previously created in ArcMap and browse for the license. The Enable Enterprise Geodatabase tool will create the sde repository using the sde user you created in the previous steps. Once the process completes, create a connection using the sde user. You will use this connection to perform admin tasks in the enterprise geodatabase. Note: make sure you have installed the PostgreSQL database drivers in ArcGIS Desktop (the 32 bits version) and/or Pro/ArcGIS Server (64 bits version). To avoid complications, download the drivers from My Esri. The good practice in terms of loading data into an enterprise geodatabase is to use a user specifically created for that end. This user is normally a headless database user, in other words, a connection that can be shared with all the users of your team that will load data into the geodatabase. Create a new user (called data_owner, for example), create a connection to the database with this new user and use this connection to load data in the geodatabase. The result will be that all your data will be owned by this user which ease a lot the administration of the geodatabase.   Link: Create a geodatabase on Amazon Relational Database Service for PostgreSQL—ArcGIS Enterprise on AWS | ArcGIS Enterprise  ... View more

Microscope Image Processing (written by AvQiang Wu,Fatima Merchant,Kenneth Castleman). Excerpt: Thinness is typically used to define the regularity of an object. Having computed the area (A) and perimeter (P) of an object, we can define the thinness ratio as T = 4pi(A/P 2 ) This measure takes a maximum value of 1 for a circle. Objects of regular shape have a higher thinness ratio than similar irregular ones. So, you can calculate your new field in Field Calculator to be: 4 * 3.14 * [Shape_Area] / ([Shape_Length] * [Shape_Length]) Most sliver polygons would have the ratio really close to 0, but from what I've seen whatever that is lower than 0.3 might be a good candidate, too. However, consider the features areas first before running into any hasty conclusions. Large and/or multipart features with irregular shape might have a really low thinness ratio yet they are not even close to be sliver polygons. You would probably want to set a definition query on your feature class excluding most of the polygons with large area….” Source: Fighting sliver polygons in ArcGIS: thinness ratio | Tereshenkov's Blog​ ... View more