Latest Contributions by DaveOrlando

Ya it was bad timing for a lesson. We were having field crews use collector to gather data and office staff ordering supplies based on the lengths. Just when you think you get a win for GIS.......   ... View more

to answer my own question after some more experimenting..... Yes, ArcOnline is treating their services different than our own ArcServer services. a few things that got me to this conclusion are that when you open the attribute table in the ArcOnline map, you see all the 'proper' UTM lengths when they are outside the map extent. try this by: zoom to where there are no features (roads for me) open attribute table and screen shot some of the IDs and Length close the table, zoom to one of those features and re-open the table the length will now change to their coordinate system. also, you will notice all the generalization happening when you zoom from way-out to way-in which also supports the fact that they treat their services different than our own. something to be very aware of when you make applications for the non-GISrs and critical decisions are being made specifically regarding the length of features...... ... View more

finally had some time to do some reading and more experimenting and I have a follow-up question for anybody willing...... I've published the same service on my server and ArcOnline, both as UTMZ11 (wkid: 26911) I have verified that both services state 26911 in their service definitions both services show UTM length in ArcMap my service shows UTM length in ArcOnline/Map popup ArcOnline/service shows WebSphere coordinate system length in the ArcOnline/Map popup My question is: how is it treating the ArcOnline Service different than my own if they are both published as 26911. Is ArcOnline actually detecting that this is 'their' service and taking the liberty of converting the length on the fly? I understand what they are saying about reprojecting on the fly (esri response above) by why for their services and not ours, not that I want that but how are they being treated different? Thanks ... View more

I find this disturbing and I'm not sure I believe a projection change would case such a drastic difference, but I could be wrong. I ran into this with Collector and WebMaps / AppBuilder. Strange tho that in collector it displayed the correct length in the popup header, (circled in pic) but wrong in the attributes, almost x2 (removed from this pic) haven't had time to investigate much,  just had to remove from popup, ... View more

Hi Daniel, Thanks very much for the response, I really appreciate the time you put into it. I can also appreciate the complexity you must face with all the different formats and the larger datasets. I may have to create a geoprocessing script to create a shapefile and kml on the fly from a Hosted Feature service. I've created a few in the past so it shouldn't be too much a stretch for me. We're dealing with Emergency Response and Evacuation Zones. It's great that most agencies will use our REST endpoints directly, but some are non-ESRI users and need a shapefile or KML download Thanks again, ... View more

I should note that the issue disappeared after changing my data and dataframe's projection from WKID 4326 to 3857 UTM Z11N (WKID 26911) also worked fine. ... View more

Was a bug ever reported? Maybe this should go into a Server forum because I feel this is a server issue. I've published the exact same service (a service with a simple table join, feature class and table in same file geodatabase) on 10.22, 10.41, 10.51 & 10.6 and the Query widget fails on all except for 10.22 Surely if a bug was reported after 10.22 it would have been fixed by now,.... right? haha ... View more

note - September 1st, 2016 - Chrome updated to 53 and the problem still exists. ... View more

I have ran into similar problems when publishing Geoprocessing scripts. Just because it published fine, does not mean that it will run fine. When you publish the script, it (ESRI) will manipulate your python script and add its own interpretation of your variables / data locations / connection files. You have to look at the error messages to hunt down the actual script that it is running so you can either change stuff back or overwrite it with your original script. For example, I had a connection file to a SQL database so it could GeoCode a View that I created. Even though during the publishing it made me add the connection file to the Server's Data Store, the new script doesn't even use the Data Store, and it copied the file and repointed my script to the ....\v101 directory. On top of that, it changed the connection file from a 'SQL Server' to an 'Application Server' and it doesn't even open in ArcCatalog. Basically, just be aware that once you publish, it is not your original script anymore and you must start another round of trouble shooting. Enjoy!, Dave ... View more

....and in Canada we were just quoted $5000 CAD annually. too bad, it was fun getting to know it. ... View more

    # Process: Delete Features (6)     arcpy.DeleteFeatures_management(QA_WaterLines)     # create FieldMap objects     #     # !! bug found: if the target field exists in the source table (ie Asset_ID), but you want to map away from it (ie SomeNewID),     # !! it must be deleted from the source, if not it will override these mappings     #     # field map Jur_Flag     fldName = arcpy.Field()     fldName.name = 'Jur_Flag'     fldName.aliasName = 'Jur_Flag'     fldName.type = 'Text'     fldName.length = 3     fmJur = arcpy.FieldMap()     fmJur.outputField = fldName     fmJur.addInputField(ENG_WaterLine_tmp, 'Jur_Flag')     fmJur.addInputField(DWK_WaterLine_tmp, 'Jur_Flag')     fmJur.addInputField(DLC_WATR_PIPES_tmp, 'Jur_Flag')     fmJur.addInputField(PCH_WaterLines_tmp, 'Jur_Flag')     fmJur.addInputField(WFN_WaterLines_tmp, 'Jur_Flag')     #     # field map WaterLineType     fldName = arcpy.Field()     fldName.name = 'WaterLineType'     fldName.aliasName = 'WaterLineType'     fldName.type = 'Text'     fldName.length = 20     fmType = arcpy.FieldMap()     fmType.outputField = fldName     fmType.addInputField(ENG_WaterLine_tmp, 'WaterLineType')     fmType.addInputField(DWK_WaterLine_tmp, 'WaterLineType')     fmType.addInputField(DLC_WATR_PIPES_tmp, 'WaterLineType')     fmType.addInputField(PCH_WaterLines_tmp, 'WaterLineType')     fmType.addInputField(WFN_WaterLines_tmp, 'Type')     #     # field map Path     fldName = arcpy.Field()     fldName.name = 'Path'     fldName.aliasName = 'Path'     fldName.type = 'Text'     fldName.length = 255     fmPath = arcpy.FieldMap()     fmPath.outputField = fldName     fmPath.addInputField(DWK_WaterLine_tmp, 'Path')     #     # field map Asset_ID     fldName = arcpy.Field()     fldName.name = 'Asset_ID'     fldName.aliasName = 'Asset_ID'     fldName.type = 'Text'     fldName.length = 20     fmAsset_ID = arcpy.FieldMap()     fmAsset_ID.outputField = fldName     fmAsset_ID.addInputField(ENG_WaterLine_tmp, 'Asset_ID')     fmAsset_ID.addInputField(DLC_WATR_PIPES_tmp, 'Asset_ID')     fmAsset_ID.addInputField(PCH_WaterLines_tmp, 'Asset_ID')     fmAsset_ID.addInputField(WFN_WaterLines_tmp, 'AssetID')     #     # field map RDCO_LinkID     fldName = arcpy.Field()     fldName.name = 'RDCO_LinkID'     fldName.aliasName = 'RDCO_LinkID'     fldName.type = 'Text'     fldName.length = 50     fmRDCO_LinkID = arcpy.FieldMap()     fmRDCO_LinkID.outputField = fldName     fmRDCO_LinkID.addInputField(ENG_WaterLine_tmp, 'RDCO_LinkID')     fmRDCO_LinkID.addInputField(DLC_WATR_PIPES_tmp, 'RDCO_LinkID')     fmRDCO_LinkID.addInputField(PCH_WaterLines_tmp, 'RDCO_LinkID')     fmRDCO_LinkID.addInputField(WFN_WaterLines_tmp, 'RDCO_LinkID')     # add field map to field mappings     fms = arcpy.FieldMappings()     fms.addFieldMap(fmJur)     fms.addFieldMap(fmType)     fms.addFieldMap(fmAsset_ID)     fms.addFieldMap(fmRDCO_LinkID)     fms.addFieldMap(fmPath)     # Process: Append (6)     arcpy.Append_management(Append_inputs, QA_WaterLines, "NO_TEST", fms) so, for example, in the second field map, the last input I wanted to go away from 'WaterLineType' but had to delete that field to force it go to 'Type' Thanks ... View more