I have a layer, water_pipe. I am creating a feature layer in the arcgis javascript api, and when the feature layer loads, it give the error "cannot execute query" in the network logs. The query string parameters look like this: * f:json * returnGeometry:true * spatialRel:esriSpatialRelIntersects * maxAllowableOffset:1 * geometry:{"xmin":-10384451.501584552,"ymin":5510511.210446009,"xmax":-10383876.812244719,"ymax":5511085.899785845,"spatialReference":{"wkid":102100,"latestWkid":3857}} * geometryType:esriGeometryEnvelope * inSR:102100 * outFields:* * outSR:102100 * token: On the server logs, the above error message is given. Geodatabase error: Only one spatial column is supported in this operation [gis.DBO.water_pipe][STATE_ID = 1447]. There is only one Shape column, here is a screenshot from the sql server manager: Any suggestions on what I can do to fix this?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Server: Geodatabase error: Only one spatial column is supported in this operation

GreggRoemhildt1

I have a layer, water_pipe. I am creating a feature layer in the arcgis javascript api, and when the feature layer loads, it give the error "cannot execute query" in the network logs.

The query string parameters look like this:

f:
json
returnGeometry:
true
spatialRel:
esriSpatialRelIntersects
maxAllowableOffset:
1
geometry:
{"xmin":-10384451.501584552,"ymin":5510511.210446009,"xmax":-10383876.812244719,"ymax":5511085.899785845,"spatialReference":{"wkid":102100,"latestWkid":3857}}
geometryType:
esriGeometryEnvelope
inSR:
102100
outFields:
*
outSR:
102100
token:
<token>

On the server logs, the above error message is given.

Geodatabase error: Only one spatial column is supported in this operation [gis.DBO.water_pipe][STATE_ID = 1447].

There is only one Shape column, here is a screenshot from the sql server manager:

Any suggestions on what I can do to fix this?

Najděte více příspěvků označených jako

Accepted answers

GreggRoemhildt1

After talking to support, we found out there's a bug BUG-000099970 that causes this to happen. It is based on the arrangement of fields in the ArcMap Document.

The synopsis is, if you rearrange fields or add new ones, make sure the SHAPE field comes AFTER the new fields, as a safe measure, move the Shape field to the very last one.

This happens on server version 10.4.1 as far as I know.

All comments

George_Thompson

Do you have multiple shape types in that column? For example records 1 - 10 are points and 20-15 are polygons?

Do any records in the table have an empty shape?

https://community.esri.com/groups/geodatabase?sr=search&searchId=45a6bb71-8b8d-4f83-8c00-78a28fe1e7ae&searchIndex=0‌ https://community.esri.com/community/gis/enterprise-gis?sr=search&searchId=aeb971e4-0302-4116-9468-63e82375be9f&searchIndex=1‌

GreggRoemhildt1

I'm not sure, that is a good question. I'm fairly certain they are all polylines, but is there a simple way to check for this and for empty shapes? It looks like the check/repair geometry tools only work on file geodatabases.

EDIT: All of the features appear to have a valid Shape.STLength() value (there are no nulls when I sorted the column).

EDIT2:

It looks like the issue is fairly obvious actually the rest page has two Shape fields..but how did the second one get there? The sql table has only one, and the arcmap document used to publish has only one. Perhaps the issue is with Shape.STLength(). It looks like ArcGIS Server is interpreting that field as "Shape"?

George_Thompson

Try this: STGeometryType (geometry Data Type)

ArcGIS can only read/display one spatial type in the table. You may need refine the query to only include one spatial type, i.e. Point Database data and ArcGIS—Help | ArcGIS Desktop

GreggRoemhildt1

George Thompson‌ it looks like the issue is with the Shape.STLength() field (see my edit above).

GreggRoemhildt1

After talking to support, we found out there's a bug BUG-000099970 that causes this to happen. It is based on the arrangement of fields in the ArcMap Document.

The synopsis is, if you rearrange fields or add new ones, make sure the SHAPE field comes AFTER the new fields, as a safe measure, move the Shape field to the very last one.

This happens on server version 10.4.1 as far as I know.

MikeVolz

So Gregg your water_pipe and san_pipe layer both had the Shape field before the newly added field when they were not working, unlike the storm_pipe layer that had the Shape field last so it always worked properly. Once you moved the Shape field to the last field in both the water_pipe and san_pipe layers, the problem was resolved in AGS 10.4.1. Would you say that is the correct summary of this problem?

Would you know if this same problem is occurring in AGS v10.5 that has now been released?

GreggRoemhildt1

Yes, that is exactly what was the issue. I haven't been able to test this on version 10.5 yet though.

MattCharton

I can confirm that this occurs in 10.5 though not dependably. I had two MapService layers that were doing this. For one, I was able to just move the Shape field to the end of the field list in the MXD and republish and it worked. For the second, this was not enough. I noticed that the only significant difference between the layer that was working correctly after the fix and the one that was not was that I had an alias on the OBJECTID field as ESRI ID. When I removed the alias and republished, it worked.

I also had another MapService layer that was not showing any of the fields after the Shape field (but was at least only showing the Shape field once). Once I moved the Shape field to the end of the field list in the MXD, all the fields showed up in the REST endpoint.

I have been a bit frustrated with the number of silly bugs like this in 10.5.

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.