So I've been looking for a good explanation of the difference between how Shape.len or Shape.len and Shape.STLength() is handled in ArcGIS. If anyone can confirm or correct the following for me and explain them better I invite you to do so. Here is what I believe I know: * Both are automatically calculated geometry fields * Both fields are permanent and cannot be removed * Shape.len/Shape.length is calculated by ArcGIS while Shape.STLength() is calculated by Microsoft SQL Server or another DBMS * Shape.STLength() wasn't used by ArcSDE up until a recent upgrade, because it wasn't until our recent upgrade to 10.2 when we started experienceing issues. * Because Shape.STLength() is not calculated by Esri, ArcGIS for Mobile and ArcPad both have difficulties with the field because it also cannot be null.

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

Geometry Fields - Shape.length vs Shape.STLength() in ArcGIS

roemhildtg

So I've been looking for a good explanation of the difference between how Shape.len or Shape.len and Shape.STLength() is handled in ArcGIS. If anyone can confirm or correct the following for me and explain them better I invite you to do so.

Here is what I believe I know:

Both are automatically calculated geometry fields
Both fields are permanent and cannot be removed
Shape.len/Shape.length is calculated by ArcGIS while Shape.STLength() is calculated by Microsoft SQL Server or another DBMS
Shape.STLength() wasn't used by ArcSDE up until a recent upgrade, because it wasn't until our recent upgrade to 10.2 when we started experienceing issues.
Because Shape.STLength() is not calculated by Esri, ArcGIS for Mobile and ArcPad both have difficulties with the field because it also cannot be null.

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

Accepted answers

JakeSkinner

You can do this by exporting the dbtune table, updating the DEFAULTS keyword to use SDEBINARY, and then re-import the dbtune table. Ex:

1. Export the dbtune table using command line:

C:\>sdedbtune -o export -f c:\temp\dbtune.sde -u sde -p sde -i sde:sqlserver:<server name> -D <database name>

2. Open the dbtune.sde file in a text editor

3. Under ##DEFAULTS, change the GEOMETRY_STORAGE parameter from "GEOMETRY" to "SDEBINARY"

4. Save your changes

5. Re-import the dbtune.sde file using command line:

C:\>sdedbtune -o export -f c:\temp\dbtune.sde -u sde -p sde -i sde:sqlserver:<server name> -D <database name>

Note: this will not update existing feature classes. You can use the Migrate Storage tool to do this.

All comments

Tiffany_Chau

Greetings from 2026 - I found your post very useful, even twelve years later!
Our office transitioned from an old system into a SQL-based system, so our old SHAPE.LEN field became SHAPE.STLength. So our attribute rules that referenced SHAPE.LEN needed to be changed to reference SHAPE.STLength.
Your post helped inform us that both are automatically calculated geometry fields, and how SQL comes into play. Thanks!

roemhildtg

Thanks a bunch, Jake. I'll look into changing to SDEBINARY. Hopefully this fixes our issue with Mobile and ArcPad.

JakeSkinner

You can do this by exporting the dbtune table, updating the DEFAULTS keyword to use SDEBINARY, and then re-import the dbtune table. Ex:

1. Export the dbtune table using command line:

C:\>sdedbtune -o export -f c:\temp\dbtune.sde -u sde -p sde -i sde:sqlserver:<server name> -D <database name>

2. Open the dbtune.sde file in a text editor

3. Under ##DEFAULTS, change the GEOMETRY_STORAGE parameter from "GEOMETRY" to "SDEBINARY"

4. Save your changes

5. Re-import the dbtune.sde file using command line:

C:\>sdedbtune -o export -f c:\temp\dbtune.sde -u sde -p sde -i sde:sqlserver:<server name> -D <database name>

Note: this will not update existing feature classes. You can use the Migrate Storage tool to do this.

roemhildtg

That is what I am looking for, I think. Could you point me in the direction of configuring SQL server to use SDEBINARY?

JakeSkinner

Hi Gregg,

If you are using SQL Server, you may want to try using the SDEBINARY geometry type rather than the default GEOMETRY type. Performance is usually faster, and the length will be in a field called 'Shape.len', so you may not experience any issues with ArcGIS for Mobile or ArcPad.

Připojte se k diskusi

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.