Latest Contributions by ClaudioRuschel

‎02-15-2023

The problem is that to connect to SQL Server there are many "handshaking" operations that are not necessary for a local FGDB connection. The operation to insert 30 rows is quite simple, but to carry it out, many messages are exchanged between the client and the server that slow down the process.

‎08-07-2022

Enterprise Geodatabase on-line documention currently is spread over desktop.arcgis.com and pro.arcgis.com domains. As ArcGIS Enterprise evolves, such documentation should be re-organizing. Indeed, Enterprise Geodatabase is so important that it would deserve its own domain, like: geodatabase.arcgis.com, or just include it on the current enterprise.arcgis.com. So, in this new domain the documentation could be reorganized splitting the administrative geoprocessing tools and Python scripts documentation to the pro.arcgis.com domain, but gathering all conceptual contents. Also, specific sections content should not be copied and paste anymore, like the current structure. When dealing with specific RDMS the common content would be presented just once, pointing to the specific issues in specializes sections.

‎08-04-2022

If you have access to a maintenance account you could explore the archiving workflows shown in this web course: https://www.esri.com/training/catalog/57630435851d31e02a43efb0/archiving-data-in-a-multiuser-geodatabase/

‎05-24-2022

If you are trying to give some intelligence to your daily tasks, it seems you might consider to deploy a Utility Network model in order to take some benefits, like relate customer points to service lines. It is needed only an ArcGIS Pro and a File Geodatabase. Take a look: https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/what-is-a-utility-network-.htm

‎04-30-2022

If your spatial queries are performed by ArcGIS tools it would be no problem, because the tool would perform the needed conversions. But If you use SQL with ST_Geometry it seems a real issue to deal. The set of native functions of spatial databases such Oracle Spatial/Graph and PostGIS are much more complete than the ST_Geometry ones. So, if one intends to use SQL, it seems to choose the native spatial database geometry format at the beginning of the project is the best choice.

‎04-24-2022

You didn't mention why the geodatabase needs to keep the ST_GEOMETRY format for that specific FC. The same Enterprise Geodatabase can have both feature classes with the geometry encoded in ESRI format (ST_Geometry) or in the database's proprietary format (in the case of Oracle, SDO_Geometry). The entry in the sde_dbtune table only defines the default format when a new FC is created. OK, such a change means changing the table structure and recreating the spatial index. If this change does not impact other applications or any published geoservices, it seems to be the simplest solution.

‎01-14-2022

You only need two layers with points features to this analysis (observer and target). In the tool parameters that requires a "Feature Set", you can use standard point feature classes (from a FGDB, for instance) or you can load it on a Map in ArcGIS Pro, select some features and use the layer name. It seems to be a documentation formalism, but the solution is simple.

‎01-14-2022

If you don't know how to program, maybe the demand you received was to create a "Feature Dataset"; which is a geodatabase structure. In a Geodatabase File (or Enterprise) a Feature Dataset is like a folder, where you can group feature classes for special needs, for example to build topology or network structures. A "Feature Set" is very different as it is just a programming resource (Python arcpy lib). I don't think you'll find this concept in the ArcGIS Pro User Interface. It's a way to define a data structure and store data (such as a JSON file) to use in memory or to persist in a Feature Class.

‎01-07-2022

George, it is a general question. The geodatabases that I´m mentioning usually support applications like spatial data infrastructures with hundred of geoservices acccessing feature layers, almost allways on a read-only way. I once read a long time ago that internally ArcGIS would convert the PostGIS format to ST_Geometry for any operation. In other words, theoretically there would be a performance difference considering the same server environment and changing only the storage format. I have not found this issue documented in current versions of Enterprise Geodatabase. Therefore, I am questioning whether, in practice, there might be any noticeable difference in the performance of a geoservice considering only the variation of the geometry's storage format type.

‎01-06-2022

I have been using by default the "PG_GEOMETRY" type to store features in Enterprise Geodatabase hosted in PostgreSQL. This strategy is very interesting when building and loading the database. But, in a production environment where most feature classes are accessed by geoservices in read-only mode, can the difference in the performance of accessing features kept in "PG_GEOMETRY" compared to "ST_GEOMETRY" be significant?

‎06-04-2021

I understand that these licenses are needed to manage the geodatabase content. But, considering that one wants to edit a Feature Service, I think it is required only an "Editor" user from ArcGIS Portal if it is available through a Web GIS application. If you want to use ArcGIS Pro to edit this service, beyond the Portal´s "Editor" role, is it also needed an Standard or Advancee license?

‎06-02-2021

Are you able to edit features from this feature service using ArcGIS Pro Basic, or it is needed at least a Standard License?

‎01-15-2021

The link is broken. There is no "idea" about this topic. But, it is a very useful tool that must be upgraded to ArcGIS Pro.

‎01-15-2021

It is more than an idea, it is an obvious requisite, like a regular CRUD operation. If you register a table "by accident"; you must have the resource to undo the operation.

‎04-27-2018

Hi, I created a custom spatial reference at spatialreference.org ( http://spatialreference.org/ref/sr-org/8391/ ) and defined it in PostGIS using the INSERT statement generated by this site. I created my tables with geometry type using this custom SRID ( st_setsrid(geom,98391) ). These tables works fine when accessed through QGIS, but when I try to load at ArcMap with a Database Connection, I receive the message "Could not add the specified object to the map. The coordinate system identifier is invalid". Ok, I invented this identifier. But, how can I tell this to ArcGIS? I tried this connection using different ArcGIS versions (10.2, 10.4) and database instances. The message is the same. So, it´s an old issue. P.S.: I don´t have a geodatabase configured, and don´t want it.

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by ClaudioRuschel

Re: Append (Data Management GP tool) - Why the extreme speed difference between SQL Server and Local File geodatabase

Enterprise Geodatabase help documentation

Re: How to store historic or archived data.

Re: How to automatically fill attribute table field after snapping?

Re: ST_GEOMETRY FC: Options for using Oracle Spatial functions

Re: ST_GEOMETRY FC: Options for using Oracle Spatial functions

Re: Create Feature Set

Re: Create Feature Set

Re: PostgreSQL Enterprise Geodatabase performance using PG_GEOMETRY

PostgreSQL Enterprise Geodatabase performance using PG_GEOMETRY

Re: Share branch versioning to AGS

Re: Share branch versioning to AGS

Re: XRay for Pro

Re: Why Can't a Layer be De-Registered with the SDE

Accessing a PostGIS table with a custom SRID

Re: How to automatically fill attribute table fiel...

Re: ST_GEOMETRY FC: Options for using Oracle Spati...

Re: XRay for Pro

Re: Why Can't a Layer be De-Registered with the SD...