Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About RandyKreuziger
RandyKreuziger
Frequent Contributor
since
07-04-2014
11-11-2020
534
Posts created
928
Kudos given
10
Solutions
280
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(2 Idea Submissions)Latest Contributions by RandyKreuziger
|
POST
|
Mike, I'd like to do that same thing but for 100 different web pages. Each page represents 1 water access site. Will there ever be an option to select the center based on a definition query? Like [site] = '137' Thanks
... View more
02-07-2012
02:32 PM
|
0
|
0
|
1299
|
|
POST
|
Glad to know I'm not entirely crazy. I have tried to register the feature classes and still the metadata disappears. We have some of the metadata in XML for the feature classes that those their's, however, the one's I've tested won't import. It seems that ArcGIS 10 won't import some XML files exported from ArcGIS 9.3. Looks like my new metadata workflow is going to involve lots of cutting and pasting and I'm not happy about that!
... View more
02-06-2012
02:47 PM
|
0
|
0
|
2754
|
|
POST
|
There is a known bug dealing with the XSLTransform_conversion command. It runs from a model but not when exporting to a script. Two ESRI DLLs must be installed on each PC that runs the script. I don't have the bug number handy but can look it up.
... View more
01-31-2012
03:18 PM
|
0
|
0
|
667
|
|
POST
|
Can you double check whether this feature class is registered with geodatabase? You can find this out by right-clicking on the feature, and check whehter "Rgister with Geodatabase" is disabled or not. If it is not registered with geodatabase, register it and try edit the metadata again. See if the metadata stays after registration. Eugene Yes, they are all registered. The metadata was all there before the upgrade for ArcSDE from 9.3.1 to 10.0. I swear that the first time I brought it up the metadata was there and then a second or two later it was got.
... View more
01-27-2012
08:47 AM
|
0
|
0
|
2754
|
|
POST
|
We have the same problem (V10 SP3) and one quick fix that seemed to work for us is after updating and saving, we also validate(press the validate button on the top menu.) The newly added metadata stays ! -Deepti Deepti, I tried are workaround but the FGDC medata is already gone. There is nothing to upgrade / update.
... View more
01-20-2012
07:16 AM
|
0
|
0
|
2754
|
|
POST
|
We need to run the upgrade metadata on over 100 feature classes in a ArcSDE geodatabase. I created a simple model to use as an example that I could export just to get the correct syntax. It runs as a model but not when exported to python. The code and error message are listed below # ---------------------------------------------------------------------------
# Upgrade Example.py
# Created on: 2012-01-13 15:59:14.00000
# (generated by ArcGIS/ModelBuilder)
# Description:
# ---------------------------------------------------------------------------
# Import arcpy module
import arcpy
# Local variables:
targetFC = "Database Connections\\myDB.sde\\myDB.DBO.BLMLands"
# Process: Upgrade Metadata
arcpy.UpgradeMetadata_conversion(targetFC, "FGDC_TO_ARCGIS") ------------------ Traceback (most recent call last):
File "C:\Python26\ArcGIS10.0\Lib\site-packages\pythonwin\pywin\framework\scriptutils.py", line 312, in RunScript
exec codeObject in __main__.__dict__
File "H:\SDE Management\Upgrade Example.py", line 16, in <module>
arcpy.UpgradeMetadata_conversion(targetFC, "FGDC_TO_ARCGIS")
File "C:\Program Files\ArcGIS\Desktop10.0\arcpy\arcpy\conversion.py", line 656, in UpgradeMetadata
raise e
ExecuteError: Failed to execute. Parameters are not valid.
ERROR 000816: The tool is not valid.
Failed to execute (UpgradeMetadata).
... View more
01-13-2012
02:20 PM
|
0
|
1
|
2305
|
|
POST
|
Would something as simple as removing the featureclass from the project and adding it back in be sufficient? No. Last year we developed our first ArcGIS Server javascript web application. We discovered that we had to use the aliases rather than the field names in the javascript app identifies. Aliases are sometimes changed by the data stewards or may be different between two feature classes with the same field. It would be much easier if we could simply delete all the aliases before loading them in the MXD. That way the field name alias within the MXD layer properterites will default to the field name. Does that make sense?
... View more
01-11-2012
11:16 AM
|
0
|
0
|
1758
|
|
POST
|
Is there anyway short of using ArcObjects to delete a fields alias? I'd like to delete all fields aliases for a given feature class. Thanks
... View more
01-11-2012
09:36 AM
|
0
|
5
|
2478
|