Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About SteveSalas
SteveSalas
Frequent Contributor
since
07-04-2014
01-22-2023
47
Posts created
17
Kudos given
0
Solutions
27
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(1 Idea Submissions)Latest Contributions by SteveSalas
|
POST
|
The link to the bug report does not work - can you check and re-post? Thanks!
... View more
11-10-2014
07:11 AM
|
0
|
3
|
2400
|
|
POST
|
Thanks for jumping in the thread, Vince... "There have been bugs in the past..." - how far in the past? We're at 10.1 on both the desktop and ArcSDE and that was my first thought (adding projected data to the GCS SDE feature class), but I haven't been able to reproduce it... I've asked the GIS editors to explain their workflow but unless you see them do it, most are hard pressed to recall what they did (typically they are natural resource specialists, etc. and GIS is not a primary function of their jobs). Also, do you know if ArcCatalog 10.3 will support updating the envelope in T_n_DIRTYAREAS? I've had to fix this with SDELAYER a few times and I understand 10.3 will not include SDE command line tools. Thanks!
... View more
07-11-2014
08:26 AM
|
0
|
3
|
2920
|
|
IDEA
|
-->
arcpy.Describe returns the dataset property isVersioned as boolean - the described dataset could be either fully versioned or move-to-base and there is no way to determine which, other than to open the property sheet of each table or feature class using ArcCatalog. Might need to create a property with a different name to avoid breaking scripts that currently use isVersioned and expect a True/False return.
... View more
07-09-2014
01:59 PM
|
5
|
0
|
4232
|
|
IDEA
|
-->
arcpy.Describe returns the dataset property isVersioned as boolean - the described dataset could be either fully versioned or move-to-base and there is no way to determine which, other than to open the property sheet of each table or feature class using ArcCatalog. Might need to create a property with a different name to avoid breaking scripts that currently use isVersioned and expect a True/False return.
... View more
07-09-2014
01:59 PM
|
4
|
1
|
509
|
|
POST
|
I don't have a solution but I can say we have a similar issue... we use GCS NAD 1983 and sometimes the max extents of the feature class get changed to very large values that make no sense in terms of degrees of latitude/longitude. If there is no data outside of our normal extent, we use the Feature Extent property tab in ArcCatalog to fix it, or sdelayer -o alter -E. Other times we have data entered during editing that ends up a complete revolution around the world from where it should be. To fix that I have to select those features in ArcMap and use "Move..." in the Editor toolbar pulldown to subtract 360 degrees from their location and the features are then in the correct location. Then I can change the extents as above. I've also had to fix dirty areas in topologies that go far outside the extent of the data - they cannot be validated as-is and you need to use sdelayer -o alter -E on the dirtyareas feature class as there is no topology extent property in ArcCatalog (10.2.0). I've talked to several editors and tried to use their recollections of their editing workflows to duplicate it in my test SDE geodatabase, but so far I have not been able to make it happen. http://forums.arcgis.com/threads/101700-SDE-Feature-Class-envelope-(max-x-y)-too-large
... View more
07-02-2014
11:45 AM
|
0
|
0
|
2920
|
|
POST
|
By empty I think you mean an empty string that is not NULL? If that is the case, I think you need to ensure that all of those empty strings are converted to NULL prior to running this check. One or more space characters is probably being treated as just another text string that doesn't match a value in the coded value domain list. At least by converting them to NULLs, you have the toggle for "Search for Null Values" which you could use to ignore NULL values. If your field does not allow NULL values, well, you're probably stuck adding a new value (to represent "unknown" or "not applicable") to both your data and the coded value domain.
... View more
06-06-2014
07:29 AM
|
0
|
0
|
786
|
|
POST
|
ArcGIS Desktop 10.1 (sp2) ArcSDE 10.1 (sp2) on Oracle 11.2.0.3 SUSE LINUX ST_Geometry storage type Editors working in protected versions that they own, SDE.Default is protected. Data is all stored in GCS NAD 1983 Occasionally our editors report that they are no longer able to display certain feature classes in ArcMap. Typically it is because the spatial envelope of the feature class has been expanded to unrealistic values in the max-x and max-y for geographic... Typical extents in our data: Layer Envelope .......: minx: -125.00000, miny: 41.00000 maxx: -116.00000, maxy: 50.00000 But sometimes we get max-x and max-y values of 500,000 or even over 1,000,000... certainly not likely values for degrees of latitude/longitude. Resetting these values we know how do... I'd be curious if anyone knows what causes these envelopes to change to such values? The editors are using standard ArcMap tools for entering geometry. Sometimes they edit in the projection of the SDE data, sometime they switch the data frame to UTM. Data loaded from other sources is typically via the copy/paste tools. I've run several tests with source data in the 3 most common projections our user's would obtain data in, and matched those with common data frame projections they might edit in, but haven't been able to reproduce the change to the envelope values. If anyone has seen this issue and found a possible cause we'd like to know... I think we reset an envelope every couple of weeks on at least on of our 40+ editable feature classes.
... View more
01-29-2014
08:54 AM
|
0
|
2
|
4121
|
|
POST
|
I do not recall all of the details, but I know I had to update some Python scripts by leaving the join name parameter blank (which removes all joins) for them to function properly. Sorry, I can't remember more of the specifics just now...
... View more
08-14-2013
09:45 AM
|
0
|
0
|
1938
|