Latest Contributions by DavidGeorge

‎03-06-2020

The table contains in total 122,794,859 rows. The table took 15:55 hrs to register. 15:13 of which were down to the following queries being executed: CREATE UNIQUE INDEX r25_sde_rowid_uk on area (objectid) WITH (FILLFACTOR = 75) 05:10 SELECT ST_xmin(b1.bnd), ST_ymin(b1.bnd), ST_xmax(b1.bnd), ST_ymax(b1.bnd), ST_zmin(b1.bnd), ST_zmax(b1.bnd), 0, 0 FROM (SELECT ST_3Dextent(sde.area.shape)::Box3d FROM sde.area ) AS b1 (bnd) 03:32 SELECT COUNT(*) FROM sde.area WHERE shape IS NOT NULL 03:29 SELECT MIN(ST_xmin(shape)), MIN(ST_ymin(shape)), MAX(ST_xmax(shape)), MAX(ST_ymax(shape)), MIN(ST_zmin(shape)), 0, MAX(ST_zmax(shape)), 0 FROM sde.area WHERE shape is NOT NULL 03:02 What I don't understand is why ArcGIS decided to delete a perfectly good existing b-tree index on the objectid column (int, notnull)! This made the process run 5 hours longer than it needed too. Why did ArcGIS need to execute 3 queries to calculate the full extents of the table, surely only one would have sufficed? Again this made the process run 6 hours longer than it really needed to. Whilst the Register with GeoDatabase documentation state if the dataset being registered contains existing features, the extent of the existing features will be used. This obviously a time-consuming task with such a large dataset, if you already know the full extents of the data, you should be able to manually specify the extents if they are known, but this only seems to apply if the table is empty. It also appears that ArcGIS renamed the existing spatial index from area_shape_1582215224548 to r27_sde_rowid_uk - not sure why the was necessary? The PostGIS database is hosted in Azure and the Geoprocessing tasking is being executed from a Windows 10 virtual machine hosted in Azure

‎03-03-2020

Can anyone advise exactly what processes ArcGIS Pro 2.4.2 does when running the Register with Geodatabase tool? I'm registering a spatial table within the enterprise geodatabase and it is taking a long, long time. The table does have several million features (polygon) which are all spatially referenced. The database is Postgres 10.11 with PostGIS 2.4, the geometry column and objectid column are both indexed (GIST and B-Tree) and all of the geometries are spatially referenced to the correct coordinate system, What is ArcGIS Pro doing that is making it slow. Is there a way to make it go faster? To get a fuller understanding is there an explicit list of functions/procedures that the Register with Geodatabase tool executes as the documentation here is rather muted?

‎05-16-2019

I have a polyline feature class which contains Street Names, which I wish to use as a locator. For some reason, it does not seem possible to create a Locator using the Create Locator tool using the Street Address role with a polyline feature class that contains only Street Names and no House Numbers From/To. Reading the documentation for the Street Address role, it implies that it should be possible to create a Locator using this role with Street Names but without house numbers from/to. However fields for house numbers from/to are set as mandatory: Is there any way around this? As the Street Address role seems to be the only role which supports Polyline Feature Classes. I wish to use to a Polyline Feature Class for this locator so that it reverse geocodes correctly along the whole of each street.

‎05-16-2019

With the new Create Locator tool in ArcGIS Pro, is it possible to customise the results output in any way? I am looking to have the ability to customise the output that is returned in the [Match_addr] field which is used in applications like Collector for ArcGIS to display results when searching for. With the legacy Create Address Locator it was possible to customise the results output in the [Match_addr] field by customising the XML stylesheet, but this does not seem to be possible with the new Create Locator tool. This does appear to be somewhat limiting compared to the legacy versions. In addition to this, why does the 3 digit country code get returned in the results? This is not necessary if you are building a locator for a single country, can this be turned off?

‎10-02-2017

Hi, Would anyone know whether support for NTv2 grid transformations and geoid models is in the Collector for ArcGIS development road map plan? Thanks

‎06-22-2017

Ok thanks. I would have thought connecting to the database as the database administrator through ArcCatalog would give me the power to register whatever layer I wanted to with Geodatabase regardless what schema the table/layer is in? This does seem a bit illogical to say the least! This means now I have to create users for all of the schemas I have in the database which seems allot of work in order to complete a simple task!

‎06-22-2017

Hi Jake, I am the db_owner and have full control of the SQL Database

‎06-22-2017

I have a SQL Server Database that I have enabled as an Enterprise Geodatabase 10.5 This enabled fine however it appears that I can only register tables/layers which are held in the dbo schema of the database. I have numerous other spatial tables which are held in other schemas which had been set-up prior to our upgrade to an Enterprise Geodatabase which it appears I cannot register with the Geodatabase as the option is greyed out when I right click on the layer in ArcCatalog 10.5. I really don't want to transfer these tables to the dbo schema if I can avoid it. Can anyone advise how I can register these spatial tables with the Enterprise Geodatabase? Thanks

Online Status	Offline
Date Last Visited	‎09-07-2023 03:16 AM

My Ideas

Latest Contributions by DavidGeorge

Re: Register a Feature Class with Geodatabase slow

Register a Feature Class with Geodatabase slow

Create Locator for Street Name

New Create Locator tool: Customise result output?

NTv2 Transformations & Geoid Models

Re: Registering Feature Classes not in the dbo schema

Re: Registering Feature Classes not in the dbo schema

Registering Feature Classes not in the dbo schema