POST
|
I have large table in a MS database. The table alone has 57GB... holding 18 million features. The table has a primary clustered key and a spatial index based on its 'Shape' attribute. The spatial index was generated with the following statement USE Contours_MSSpatial
CREATE SPATIAL INDEX SIndex_Contours_Shape
ON Contours(Shape)
USING GEOMETRY_GRID
WITH (
BOUNDING_BOX = (xmin = 440000, ymin = 6050000, xmax = 920000, ymax =6403000),
GRIDS = (LOW, LOW, MEDIUM, HIGH),
CELLS_PER_OBJECT = 32,
PAD_INDEX = ON
);
GO The data are in EPSG:25832 and I can get the layer into the map, but there is only a fraction of the data loaded before it stops loading. It takes a while, but in QGIS at least the data are loading. This way I was able to confirm that the data to be shown are actually correct. The spatial index might be the culprit but why does ArcGIS Pro stop reading the data in?
... View more
a month ago
|
0
|
0
|
156
|
POST
|
I am using sqlalchemy in a Python script that I created in VSC using a clone of the arcgispro-py3 environment. When I run the code in VSC there is no problem. Now I need to have the code running in the Data Interop Workbench in a PythonCaller, and that's where I am facing Python Exception <ModuleNotFoundError>: No module named 'psycopg2' I went to check the Package Manager in ArcGIS Pro to check if the clone is set as the active environment and if I in fact have psycopg2 installed. Here a screenshot of the installed module and here the sqlalchemy Can I get some help why I am facing this issue, if the module is installed?
... View more
04-08-2025
02:47 AM
|
0
|
1
|
405
|
POST
|
I am sharing a grayscale TIF from ArcGIS Pro 3.3 as an Image Layer to our ArcGIS Enterprise. The screenshot shows the settings for the image service. The issue I am facing is that the Image Layer in our Enterprise Portal shows in the Mapviewer by default with an RGB symbology, the value range goes from 0 to 255, and the pop-up will always show three values, but never the correct one of the pixel value. Pixel values should be floats, but the pixel values for the Image Layer are always integers in the range from 0 - 255. This behavior also doesn't change if I switch the symbology from RGB to Stretch. If I create a new item within ArcGIS Enterprise, then I can create an Image Layer where the value range is correctly identified as 2 - 100 and the symbology is by default set to Stretch. Finally, the pop-ups show the float pixel value. But, of course this is a dynamic Image Layer, and nothing is cached. Neither is my tiling scheme anywhere taken into account As written above, I am sharing from ArcGIS Pro 3.3. Our Enterprise is in version 11.3. Does any of you made similar experiences and might have a solution for these issues?
... View more
11-29-2024
01:40 AM
|
0
|
0
|
513
|
POST
|
When I connect to my PostgreSQL (PostGIS) database then everything seems fine until I basically add data to the map in ArcGIS Pro 3.3. While at a first glance it seems all good, the diagnostic monitor shows the following: Database: ip-address -> SQL: SELECT * FROM db_name.schema.table -> Number of rows returned: 0 That is strange since when I visualize the features in the Query Feature Class then it shows all the features (103.609). But when I open the attribute table then I am getting a warning: Table -> Failed to open table., yet in the background the attribute table loads and is populated. In the same context I have also seen an error message: Cancelling statement due to user request::SQL STATE=57014 The moment I add a definition query to the class it is getting pretty interesting when I try to see attribute data... I am getting again the warning Table -> Failed to load the data. More info on the warning reveals: Failed to retrieve a page of rows. The event class for this subscription is in an invalid partition When I click OK on the warning, the attribute table is closed the map shows the correct features according to the definition query Interesting is, that when I create the definition query then I can select from the correct values in the value field of the WHERE statement, and the diagnostics monitor returns the correct count of rows from the DISTINCT statement against that column. But when I apply the definition query then the statement issued against the database is the following: SQL: SELECT ESRI_OID FROM db_name.schema.table WHERE column_name = selected_value ORDER BY ESRI_OID LIMIT 1 The number of rows returned is 1 There should be thousands... Then I confirm the properties dialog of the Query Feature Class, and the diagnostics monitor shows a new SQL statement issued: SQL: SELECT * FROM db_name.schema.table -> Number of rows returned: 0 Looking at help pages I get the advice the check the accessibility of the data, especially if the data is on a shared drive or database server. Regarding the rights of the user connecting successfully to the database, I am testing currently with admin rights, and I am the owner of the data. Regarding the error 57014, several hints are pointing at npgsql, but that's where I am out, because I have no idea if ESRI is using npgsql or not. Anybody here who had the same problem, found a solution and solved it? @George_Thompson or @AyanPalit maybe?
... View more
11-09-2024
07:03 AM
|
0
|
2
|
903
|
POST
|
Is it possible to adjust the 'reference' layer that comes with some basemaps, e.g. Dark Gray Canvas? The layer would be 'Dark Gray Reference' in this case and I would like to remove some of the references in it but not all.
... View more
11-04-2024
07:04 AM
|
0
|
1
|
441
|
POST
|
The solution for the error of This geodatabase does not support this client or operation. seems to be the database version I was trying to write to. Since 10.9 versions does not know about datatypes like date_only, and I added an attribute of date_only to the schema the writing part failed. The suffix of _[geometry type] to the feature class name in the database seems to be a bug. I am reading the input data from a zipped geopackage, and FME shows the geopackage_type as geopackage_polygon. In my case, the fme_feature_type would be lakes, and the resulting name of the feature class is lakes_polygon. I tried to circumvent the suffix, fishing with a regular expression for possible parts, separated by an underscore - to no avail. Since the feature information in the Workbench do show fme_feature_type with a value of lakes, right until the Geodatabase_SDE writer, and even setting the regex in the settings of the writer shows no effect, I assume it is a bug within the writer. The suffix is also shown when using the Geodatabase_File writer... After the attempt to write the data into a file geodatabase, and getting the same result as with the enterprise database, I renamed the feature class in the file geodatabase by deleting the suffix. Then I read the file geodatabase in the same workspace, and used the same dynamic writer to the enterprise database as I used before... this time the name of the resulting feature class in the enterprise database did not receive any suffix and is simply called lakes, as expected. In the end I used the SchemaScanner, and for good measure I left the regex in the writer settings for the feature class name. I am using the Data Interoperability Workbench in version 2023.1.1.1, build 23636
... View more
04-24-2024
04:23 AM
|
2
|
1
|
1705
|
POST
|
I am trying to write to on of my Enterprise databases without success. The error message is. The error number from ArcObjects is: '-2147216035'. The error message from ArcObjects is: This geodatabase does not support this client or operation. The Geodatabase_SDE writer is set to dynamic schema definition, feature class name is set to fme_feature_type, and geometry type is set to 'from schema definition'... the usual settings one would do to write data with different schemas. I can see that the name for the feature class to be written is in fact of the following structure: [fme_feature_type]_[geometry type]. That puzzles me quite a bit since the setting for the writer clearly is to use only fme_feature_type. The other thing that bothers me is, the message that the geodatabse does not support this client or operation. I am using ArcGIS Pro 3.2.1 and the database is in version 10.9.0.2.7 on an MSSQL server.
... View more
04-24-2024
12:05 AM
|
0
|
2
|
1769
|
POST
|
Hi @Robert_LeClair, looking for a solution to the problem described by the author I found this thread. I am working in version 3.2.1 of ArcGIS Pro, but following the bug trail I can see that this, originally ArcMap issue, is also in ArcGIS Pro, and according to BUG-000133433 the status is: Will not be addressed. Is the conclusion that I won't be able to color balance a mosaic dataset with ESRI?
... View more
03-20-2024
05:34 AM
|
0
|
1
|
1308
|
POST
|
I am trying to add a directory full of raster files to a mosaic dataset. All my data (raster files and GDB with the mosaic dataset) are on a drive attached as close as possible to our Image Server. To connect to the file share I am using the UNC path e.g. \\img-storage.adddmz.com\raster\project\orthophotos. I had no problem creating the geodatabase in the project directory, but already creating the mosaic dataset in that geodatabase (let's call it mosaic.gdb) took ages. Now I am trying to add the raster files from the orthophotos directory to the mosaic dataset. The raster data are JPGs, where each JPG comes along with a *.JGW and a *.JPG.AUX.XML file. When I tried to use the geoprocessing tool in ArcGIS Pro version 3.2.1 I experienced that the program became unresponsive right after pointing the tool to the mosaic dataset. The next time it took for ever was when I defined the source for the raster data. Here I defined the path to the directory where the raster files recide in. This might be related to the numbers of JPGs in the directory (490), but I would not see the point why the tool has to index the files in the directory at this point. When I run the tool then it looks fine at the beginning, but there are no messages about what raster file is processed or anything in the details of the tool. Looking in the rasterproxies directory where the cache should be build, there is not even a directory created for the job! So I was moving over to Python, hoping to get at least some info. Everything seems pretty slow, but runs until I run the AddRasterToMosaicDataset. import os
import arcpy takes 13.5 seconds arcpy.env.workspace = r'\\img-storage.adddmz.com\raster\project\orthophotos'
sr = arcpy.SpatialReference(29902) takes 57.7 seconds! in_mosaic_dataset=os.path.join(arcpy.env.workspace,'mosaic.gdb','m_dataset')
arcpy.AddRastersToMosaicDataset_management(
in_mosaic_dataset=in_mosaic_dataset,
raster_type="Raster Dataset",
input_path=arcpy.env.workspace,
update_cellsize_ranges="UPDATE_CELL_SIZES",
update_boundary="UPDATE_BOUNDARY",
update_overviews="UPDATE_OVERVIEWS",
maximum_pyramid_levels=None,
maximum_cell_size=0,
minimum_dimension=1500,
spatial_reference=sr,
filter="*.jpg",
sub_folder="NO_SUBFOLDERS",
duplicate_items_action="OVERWRITE_DUPLICATES",
build_pyramids="BUILD_PYRAMIDS",
calculate_statistics="CALCULATE_STATISTICS",
build_thumbnails="BUILD_THUMBNAILS",
operation_description="",
force_spatial_reference="NO_FORCE_SPATIAL_REFERENCE",
estimate_statistics="ESTIMATE_STATISTICS",
aux_inputs=None,
enable_pixel_cache="NO_PIXEL_CACHE",
cache_location=r"C:\Users\me\AppData\Local\ESRI\rasterproxies\m_dataset"
) throws the following error: ExecuteError Traceback (most recent call last) ~\AppData\Local\Temp\ipykernel_27880\1483089116.py in <cell line: 2>() 1 in_mosaic_dataset=os.path.join(arcpy.env.workspace,'mosaic.gdb','m_dataset') ----> 2 arcpy.AddRastersToMosaicDataset_management( 3 in_mosaic_dataset=in_mosaic_dataset, 4 raster_type="Raster Dataset", 5 input_path=arcpy.env.workspace, C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py in AddRastersToMosaicDataset(in_mosaic_dataset, raster_type, input_path, update_cellsize_ranges, update_boundary, update_overviews, maximum_pyramid_levels, maximum_cell_size, minimum_dimension, spatial_reference, filter, sub_folder, duplicate_items_action, build_pyramids, calculate_statistics, build_thumbnails, operation_description, force_spatial_reference, estimate_statistics, aux_inputs, enable_pixel_cache, cache_location) 14066 return retval 14067 except Exception as e: > 14068 raise e 14069 14070 @gptooldoc('AlterMosaicDatasetSchema_management', None) C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py in AddRastersToMosaicDataset(in_mosaic_dataset, raster_type, input_path, update_cellsize_ranges, update_boundary, update_overviews, maximum_pyramid_levels, maximum_cell_size, minimum_dimension, spatial_reference, filter, sub_folder, duplicate_items_action, build_pyramids, calculate_statistics, build_thumbnails, operation_description, force_spatial_reference, estimate_statistics, aux_inputs, enable_pixel_cache, cache_location) 14063 from arcpy.arcobjects.arcobjectconversion import convertArcObjectToPythonObject 14064 try: > 14065 retval = convertArcObjectToPythonObject(gp.AddRastersToMosaicDataset_management(*gp_fixargs((in_mosaic_dataset, raster_type, input_path, update_cellsize_ranges, update_boundary, update_overviews, maximum_pyramid_levels, maximum_cell_size, minimum_dimension, spatial_reference, filter, sub_folder, duplicate_items_action, build_pyramids, calculate_statistics, build_thumbnails, operation_description, force_spatial_reference, estimate_statistics, aux_inputs, enable_pixel_cache, cache_location), True))) 14066 return retval 14067 except Exception as e: C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py in <lambda>(*args) 518 val = getattr(self._gp, attr) ... ExecuteError: Failed to execute. Parameters are not valid. ERROR 000732: Mosaic Dataset: Dataset \\img-storage.adddmz.com\raster\project\orthophotos\mosaic.gdb\m_dataset does not exist or is not supported ERROR 000732: Input Data: Dataset \\img-storage.adddmz.com\raster\project\orthophotos does not exist or is not supported Failed to execute (AddRastersToMosaicDataset). Can somebody, based on the provided information tell me why I cannot add the raster data to the mosaic dataset? The mosaic dataset does exists, and it is loading just fine into a map in ArcGIS Pro.
... View more
03-02-2024
04:25 AM
|
0
|
0
|
1471
|
POST
|
I have an Enterprise database and want to write data into it. In case the table I am addressing does not exists I would need to create the table. Creating the table seems to give me some challenge with respect to the required data type for the geometry column. When I look into other Enterprise database tables the geometry column is initiated by SHAPE geometry NULL and using the geometry type let's me at least create the table. However, looking for the right procedure I came across this workflow, where there are several versions of how to create a spatial table in an Enterprise database, but SQL Server is not in there. But I was wondering if the geometry type is the right one. Once the table is created, I went to register the table with the geodatabase in ArcGIS Pro. Back in SQL my next statement is INSERT INTO Buildings (SHAPE)
VALUES
(geometry::STGeomFromText('POLYGON Z ((695023.53 6181945.6 25.55,695014.58 6181947.59
25.7,695014.32 6181946.41 25.7,695010.94 6181947.17 25.4,695009.57 6181941.03 25.4,
695013.02 6181940.26 25.55,695010.59 6181929.37 25.55,695019.48 6181927.39 25.55,
695023.53 6181945.6 25.55))', 25832); But this one gives me the following error Query failed, possibly due to a malformed statement. Query Text `INSERT INTO Buildings (SHAPE) VALUES (geometry::STGeomFromText('POLYGON Z ((695023.53 6181945.6 25.55,695014.58 6181947.59 25.7,695014.32 6181946.41 25.7,695010.94 6181947.17 25.4,695009.57 6181941.03 25.4,695013.02 6181940.26 25.55,695010.59 6181929.37 25.55,695019.48 6181927.39 25.55,695023.53 6181945.6 25.55))', 25832)'. Provider error `(-2147217900) Incorrect syntax near ')'.' Does somebody can point me at the mistake I am making?
... View more
02-22-2024
02:31 AM
|
0
|
1
|
1517
|
POST
|
Yes, I am aware of this possibility, and as the help already states "...for query layers and text files,...". This does not help in any way to overcome the issue that ArcGIS Pro 3.2 seems to force our hand updating our Enterprise Portal to a version we have no intention to. I agree with @RyanUthoff that this seems to be a poor design choice. The way this implementation effects the wider ArcGIS environment causes a lot of issues, and that there is no way to circumvent these data type changes is really bad. "In ArcGIS Pro 3.2 and later, new field types to support date, time, and big integer values are available...." -> available suggest that I do not have to bite the bullet and can refrain from using them! For the majority of cases that's not possible. Forcing the use of database versions incompatible with the latest long-term support version of ArcGIS Enterprise is equally bad!
... View more
12-13-2023
12:46 AM
|
0
|
0
|
4083
|
POST
|
Since we updated to ArcGIS Pro 3.2 we have issues with our Enterprise databases. One of the issues is, that we cannot write to them... New data types such as 'date only', object ids are now 64 bit instead of 32 bit, etc. With a test database I luckily had laying around I attempted an upgrade from 11.0.0.3.9 to 11.2.0.49743. Not that I could have selected any lower database version! The upgrade went well and now I am able to write data again to this database! However, the next that is throwing stones in my way is sharing the data as a web layer to our Enterprise portal. When analysing the layer I am getting the following error: We actually never had the intention to upgrade our portal (10.9.1) to 11.2, since 11.2 is a short-term support release, while 11.1 is a long-term support release. Could it be that we are forced to upgrade to a short-term support release, simply because ArcGIS Pro 3.2 does not support the long-term support release? It kind of makes the whole thing ridiculous.
... View more
12-12-2023
07:49 AM
|
3
|
7
|
4242
|
POST
|
I am trying to add a TMS layer to ArcGIS Pro as well as to a web map in our Enterprise Portal, without success. The service comes with a negative value for the row parameter. When I try to add this layer to a map in ArcGIS Pro then I get the following error message. If I remove the minus in front of the row parameter, then the service is loaded, but is unusable as the following screenshot is trying to illustrate. Adding the layer to QGIS works without a problem... just the wrong platform 😅 The url for the service is: https://map02.eniro.no/geowebcache/service/tms1.0.0/nautical/{z}/{x}/{-y}.png and it would be really nice if some of you have a solution. Especially for getting the data into web maps.
... View more
11-14-2023
12:24 AM
|
0
|
0
|
977
|
POST
|
Thanks Aubri for your reply. You are of course right, and the Bygninger item are set to show only what is visible in the map at the time. I would say that's reasonable in terms of cartography. Turning that feature off goes against proper cartography and looking at the map with points of only a few classes instead of all sorts of them (as suggested by the legend) will raise some questions by the client... Not using the feature, as a solution means to me the feature does not work properly. It still escapes me, that I cannot set the legend to a specific width and height, lock it and it stays that way. I should be able to tell the program how the legend has to look, and not the other way around that the program is basically telling me that's the way "I think" it should look like. Then there is of course the auto adjustment of the legends title, visibly altering the font size, thereby introducing a line break, but the settings still set to 14pt (in my case). Do you, or anyone else have a solution to that problem? Bests Tom
... View more
08-30-2023
12:58 AM
|
0
|
0
|
2160
|
POST
|
I need to get constant design of my legends in a template, but I am almost every time surprised how ArcGIS Pro has its own interpretation of things. It starts with that the legend in the template is locked (after I was satisfied with the look), but when I activate the template and choose another area of my data, the legend gets alive! Here when everything is as it should be; legend is locked, and aspect ratio of the legend is linked Now I am changing only the area of interest. I do not touch anything in the layout. The width of the legend is the same, but the title is obviously wrapped, and the font size increased. Yet, when I have a look at the font size to adjust it, the setting is still at 14pt.
... View more
08-29-2023
03:53 AM
|
1
|
3
|
2255
|
Title | Kudos | Posted |
---|---|---|
1 | 10-24-2022 01:23 AM | |
1 | 09-15-2021 01:21 AM | |
1 | 08-30-2022 04:31 AM | |
2 | 04-24-2024 04:23 AM | |
3 | 12-12-2023 07:49 AM |
Online Status |
Offline
|
Date Last Visited |
a month ago
|