Latest Contributions by RandyBurton

suspect that AGOL cannot symbolize the hydrants using Categories without a defined domain.  My tests were providing results similar to yours. I noticed that you are trying to use green for any valid pressure reading (including a NULL value) and red for zero.  When I tried to publish a feature where the values zero and null were symbolized as red hydrants and any other value as green hydrant, the feature failed to publish with an unknown error. My suggestion would be to create a domain of valid pressures  (such as: 0, under 10, 11, 12,...., 49, 50, over 50).   For the pressure field, prohibit null values and set the default value to 0.  In the symbology categories, add the zero category as a red hydrant. All other values in the domain will be green hydrants.  The table to domain tool might make it easier to enter a long list of numbers.  There is also a sort domain tool that is helpful in making sure the list is in a logical order, either by the code or the label. ... View more

Hmmm....  I'll do some experimenting and see if I can duplicate the issue. ... View more

I would suggest taking a look at the json file using  REST API.  For AGOL, select your hydrants feature layer in MyContent.  Then, on the next screen,  click on the link under layers to go to the “Service URL".  There will be a link at the top of the next page for the json file which contains information about your feature. In the “fields” section, you should see something like this:   "fields" : [     ... other fields ...     {       "name" : "staticPressure",       "type" : "esriFieldTypeInteger",       "alias" : "Static Pressure",       "sqlType" : "sqlTypeOther",       "nullable" : true,       "editable" : true,       "domain" : null,       "defaultValue" : null     },     ... other fields ... ], For domain, does it show "null"? ... View more

So, related tables are not being used.  The dropdown for Static Pressure would suggest to me that the field is using a domain for look-up values and that 0 is the only value defined in the domain.  The "no value"  would suggest that nulls are allowed for the field. If you wish to collect either integer or double type values for the field, you probably shouldn't be using a domain.  Then collector will not offer a drop-down.  For this, an integer type might be best. If you wanted to group values into a domain for a drop-down menu, you should set up the domain to use an integer type field with something like 0 = "0", 1 = "0 to 20", 2 = "21 - 30", .... n = "51 or over". ... View more

The hydrants inspection uses related tables.  It is my understanding that you cannot have symbology in the related table.  You need to create a field in the feature that you can change either when collecting data or by a script.  See this thread for additional information. ... View more

It seems ArcGIS Online cannot properly measure Mars coordinates (using the Mars 2000 projection).  If you view your map using the Explorer for ArcGIS app, it will give better measurements. Online measured Olympus Mons at about 650 miles across; Explorer gave a measurement of about 335 miles across. ... View more

This sounds like an interesting project.  I don't know how you can change the settings in ArcGIS Online.  Since AGOL is using the size of the earth, you might need to use a scale factor of about 53% to calculate the actual distance on Mars. ... View more

When publishing a service from ArcMap, go to "Capabilities" and enable "Feature Access" and then select the following under "Operations allowed": Create, Delete, Query, Sync, Update.  Your feature should be published with the correct settings. If the layer has been published, go to "My Content:" and select the layer (view item details). At the top of the screen will be a series of options that include open, share, edit, etc. Select "edit".  Near the bottom is a section for Properties.  Check the selections to enable editing and to enable sync and save your changes. It is also possible to edit the json file and update the section "capabilities" to "Create,Delete,Query,Update,Editing,Sync".  I suggest this only if you cannot republish the layer with the sync setting enabled, only after backing up your data and if you are comfortable using the REST API.  To edit the json, you will need to insert "admin" in the url: .../arcgis/rest/services/... becomes .../arcgis/rest/admin/services/...  (assuming you are using ArcGIS Online).  You will need sufficient privileges to do this action. A link "Update Definition" will be available at the bottom of the page. ... View more

The ArcServer is using UTC, which is 6 hours from Central time.  This thread may help: Did the date format change for Query, REST, Post, JSON responses at ags 10? See also: Convert Time Zone—Help | ArcGIS for Desktop ... View more

Comment out the TableToExcel portion so that the MakeQueryTable section can be checked.  Add the following code after MakeQueryTable to see if it is selecting the proper number of rows and the correct fields. # Print the total rows print arcpy.GetCount_management("CompletedProjectView") # Print the fields Fields = arcpy.ListFields("CompletedProjectView") for field in Fields:     print field.name ... View more

I did some further experiments with your original code. My version of Python didn't like the slashes.  I also think that if you are using the OBJECTID field, it should be included in your field list. It hung on me without it. In my experiment, it did pull the alias from the feature class table. Either: arcpy.MakeQueryTable_management(defeatureclasspath,                                 "CompletedProjectView",                                 "USE_KEY_FIELDS",                                 "OBJECTID",                                 "OBJECTID; CUSTOMERLASTNAME; PROJECTIDENTIFIER") Or: arcpy.MakeQueryTable_management(defeatureclasspath,                                 "CompletedProjectView",                                 "NO_KEY_FIELD",                                 "",                                 "CUSTOMERLASTNAME;PROJECTIDENTIFIER") arcpy.TableToExcel_conversion("CompletedProjectView", r"path\to\excel.xls", "ALIAS") ... View more

Brandon, Your line for TableToExcel looks correct  using "ALIAS". I believe the MakeQueryTable_management needs the aliases to be defined in the in_field parameter, such as: [[Field, {Alias}],...,...] or in your case, such as: [["CUSTOMERLASTNAME", 'Last Name of Customer'],["ACCOUNTNUMBER", 'Customer Account'], .... ,["ACTUALONLINEDATE", 'Online Date']] ... View more

Since I have the same question, I was hoping you would get an answer. I think the symbology could only be part of the feature and not in the related table because of a one to many relationship.  So when a user completes the form part in the related table, they would need to reset the symbology flag in the feature. As an alternative, it may be possible to access the REST API via a Python script to query the related table to see if a form had been completed within a specified time period. If a form meets the criteria, then the script would make an update to the feature’s symbol indicating “not due”. Likewise, if a related form is found to be out of date, then the feature’s symbol could be changed to “due”. ... View more