ArcGIS Professional 2.2 Labelling I am having an issue labelling polygons in a query layer from SQL Server 2008 R2. No labels seem to be drawing. I have checked the data and all columns are populated. * Labelling works for point and polyline query layers. * Labelling works for point, polyline and polygon feature types in a FGDB * Labelling works for point, polyline and polygon feature types in a SHP file Could someone please point me in the right direction. I have tried the polygon labelling in SQL Server 2008 R2 and 2016 without luck.

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; } } }

Labelling a polygon query layer from SQL Server in ArcGIS Pro 2.2

deleted-user-QWCWfF11Rtxw

ArcGIS Professional 2.2 Labelling

I am having an issue labelling polygons in a query layer from SQL Server 2008 R2.

No labels seem to be drawing.

I have checked the data and all columns are populated.

Labelling works for point and polyline query layers.
Labelling works for point, polyline and polygon feature types in a FGDB
Labelling works for point, polyline and polygon feature types in a SHP file

Could someone please point me in the right direction. I have tried the polygon labelling in SQL Server 2008 R2 and 2016 without luck.

Encuentra más publicaciones etiquetadas con

Accepted answers

deleted-user-QWCWfF11Rtxw

Just wanted to thank the Esri team. A patch ArcGIS Professional 2.2.3 came out the other week. This has included a fix for this issue. Thanks again.

All comments

ChristopherJohnson1

Just an update here...after months and months of troubleshooting, we were able to determine that there was a bug -- BUG-000121886. Hopefully, we will have a resolution soon.

Thanks...Chris

ChristopherJohnson1

No worries, Wendy. I figured it was worth a try. 🙂

Yes, I have provided the Support team with the data that they need. Yet, they are unable to replicate. It is being escalated, so, hopefully, we will have a resolution soon.

I will send an update once we figure it out.

Thanks...Chris

WendyHarrison

Hi Chris,

I'm sorry that I don't have any ideas off the top of my head as to what may be causing the issue. You are in the best hands having the support call open. Once they are able to reproduce it they will log it to my team and we will take it from there.

So let's get them all the information they need so that they can reproduce the issue in house. A lot of the times things are best reproduced with the data you are working with. They don't need the whole dataset. The best thing you can send them is a map package with two datasets with a feature in each with the join between them and labels turned on (basically the smallest possible amount of data that will reproduce the issue). As long as they can load it into SQL Server and repro.

Keep us posted

Thanks

Wendy

ChristopherJohnson1

Hi, Wendy. I have a similar issue to the one that you were discussing with Shane recently. I do have a ticket open with Support, but I wanted to see if you had any ideas.

We have data (spatial and non-spatial) stored in the same database on a SQL Server 2012 instance. The spatial data and non-spatial data are joined in ArcMap 10.6.1 (I tried with 10.5, as well) and labeling is turned on. I see the labels in ArcMap, but when we publish to ArcGIS Server (10.61), the labels do not appear when viewing the map in ArcGIS JavaScript preview. The same set-up/workflow is successful on ArcGIS Server 10.41. The issue seems to be related to the join between the spatial data and non-spatial data. If I publish the map document without the join, the labels appear.

I tried the suggestion you had about exporting the spatial data, running the repair tool and re-importing to SQL Server. That did not work.

Any other ideas?

Thanks...Chris

P.S. Support is not able to duplicate the issue. Are there any server settings at which I may look to try and resolve this issue?

deleted-user-QWCWfF11Rtxw

Just wanted to thank the Esri team. A patch ArcGIS Professional 2.2.3 came out the other week. This has included a fix for this issue. Thanks again.

ChetDobbins

Hi Shane,

I think i know this particular issue, and believe it may be something we have recently fixed in the software which was related to ring order. You mentioned that you are using ArcGIS Pro 2.2, and ArcMap as well... can you confirm the version of ArcMap? I suspect it is 10.6.1 because that is when the issue I am thinking about would have been introduced.

The reason you wouldn't see the issue with data created by ArcGIS is because we will always follow our ring order requirements when inserting the data into a feature class. I suspect the method used to insert directly into the spatial table where you see this issue is not following our required ring order direction. SQL Server really does not care about this when the data is stored in the geometry spatial type so STIsValid would return the shape as valid no matter which way you inserted.

In 10.6.1 we made some changes to our validation method which improved performance, but also resulted in problems when reading shapes that have this reversed ring ordering.

What is the possibility that you could log a case with technical support so that we can get you hooked up with a defect?

deleted-user-QWCWfF11Rtxw

We used to use the extension but reverted back to uploading a OGC well known binary. I have also tried using the GDAL libraries to upload to a SQL geometry data type directly and still have the same labelling issue.

bharold

Shane does your edition of FME not include the SQL Server Spatial writer?

deleted-user-QWCWfF11Rtxw

wendy, appreciate the help.

Data Format

Data is stored using the SQL Server geometry data type and SRID 2193 (NZ Transverse Mercator)

Process

The data is downloaded from an external vendor LINZ Data Service as a SHP file
Uploaded into SQL Server using FME and converting the spatial object to an OGC Well Known Binary object
Once in the database, the spatial object is created using standard SQL Server OGC functions OGC Static Geometry Methods | Microsoft Docs
All objects are then verified using the same set of spatial functions STIsValid (geometry Data Type) | Microsoft Docs
Spatial Index is then created
Layer is opened up into ArcMap - labelling works
Layer is opened up into ArcGIS Pro 2.2 - labelling does not work

Notes

Layers created in a SQL Server database (using ArcMap) with geodatabase enabled seem to label correctly. In ArcGIS Pro and the catalog view the layers that work (labelling that is) have a symbol that seems to indicate a polygon layer (green tick) whereas the ones that do not work just have a hollow polygon (red cross)

Hope this helps

WendyHarrison

Hi Shane - it is probably something to do with the ring ordering. Still trying to get to the bottom of it. A few more questions...

What storage type (geometry or geography) are you using in SQL Server?

Where did the data come from? was it created in ArcGIS?

thanks

Wendy

deleted-user-QWCWfF11Rtxw

Forgot to add, I am doing this in SQL Server 2016. I check the geometries with the following function STIsValid(). URL link below:

STIsValid (geometry Data Type) | Microsoft Docs

deleted-user-QWCWfF11Rtxw

Wendy, when I exported the records out to the a FGDB and labelled them, they only the polygons with the holes were labelled. When I ran the repair as instructed, the labelling worked!!!

The geometies in the database are OGC compliant so what would the issue be?

deleted-user-QWCWfF11Rtxw

Inside SQL Server I have run a check to ensure that all geometries are valid. This particular layer is refreshed each night in SQL Server via a spatial query from four separate tables. One spatial and 3 not spatial. Once completed, a STIsValid() function is run on the resultant table. Any objects not valid are reported to the data team. Why would it be working in ArcMap?

WendyHarrison

ohhh - I saw something like this last week...

try exporting the data out to a file gdb and run the repair geometry gp tool on it with the OGC validation method. then put it back into sql server.

let me know how that goes.

thanks

Wendy

deleted-user-QWCWfF11Rtxw

Wendy, I have recreated the database in SQL Server 2016 as well and have the same issue. The only polygons that label in both database version are polygons with a hole in them. The label appears in the hole. Very unusual. It does seem to work when I open the same layer in an SQL Server database that has had geodatabase enabled. I have emailed support in NZ.

WendyHarrison

Hi Shane,

SQL Server 2008/2008R2 are not supported with Pro 2.2. SQL Server 2016 is though. Are you seeing the issue on both?

The best way to deal with this will be to log a support call so that we can take a look at the data and get a repro case.

thanks

Wendy

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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