Latest Contributions by MichaelHanna

‎11-15-2013

Robert - Alright. I guess I will have to try something similar and see if I can reproduce your successful results. If that works, I guess I will start adding in the rest of the feature classes until it breaks. Although, if it doesn't work with only that feature class, then I'm not sure what to do. Thanks for investigating this! Michael

‎11-12-2013

Robert - I have prepared a file gdb with just that layer in it, but I cannot attach to this thread in a public setting (utility security issues). I would need to send it you in a private message, but you currently do not accept them. Can you private message me with an alternative way to get the file to you? Thanks, Michael

‎11-11-2013

Robert - This the information from the REST Services for the layer titled "Pressurized Main" ArcGIS Services Directory Home > MSEX_Enterprise_TUI_TESI (MapServer) > Pressurized Mains Help | API Reference Layer: Pressurized Mains (ID: 16) Parent Layer: Water Mains Display Field: MSEX_ID Type: Feature Layer Geometry Type: esriGeometryPolyline Description: Definition Expression: Copyright Text: Min. Scale: 150000 Max. Scale: 0 Default Visibility: True Extent: XMin: 555140.000183105 YMin: 164442.531005859 XMax: 759743.955810547 YMax: 560517.237792969 Spatial Reference: 2235 Has Attachments: False HTML Popup Type: esriServerHTMLPopupTypeNone Drawing Info: Renderer: Unique Value Renderer: Field 1: LifecycleStatus Field 2: Field 3: Field Delimiter: , Default Symbol: Unsupported Symbol Default Label: Unique Value Infos: Value: In-Service Label: In-Service Description: Symbol: Simple Line Symbol: Style: esriSLSSolid, Color: [0, 112, 255, 255], Width: 1.5 Value: Out-of-Service Label: Out-of-Service Description: Symbol: Simple Line Symbol: Style: esriSLSSolid, Color: [255, 211, 127, 255], Width: 1.5 Value: Abandoned Label: Abandoned Description: Symbol: Simple Line Symbol: Style: esriSLSDash, Color: [104, 104, 104, 255], Width: 0.4 Transparency: 0 Labeling Info: N/A Fields: OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID) ENABLED (Type: esriFieldTypeSmallInteger, Alias: Enabled, Domain: Coded Values: [0: False], [1: True] ) MSEX_ID (Type: esriFieldTypeString, Alias: MSEX_ID, Length: 50 ) DIAMETER (Type: esriFieldTypeDouble, Alias: Diameter, Domain: Coded Values: [0.5: 1/2"], [0.75: 3/4"], [1: 1"], ...23 more... ) INSTALLDATE (Type: esriFieldTypeDate, Alias: InstallDate, Length: 36 ) LIFECYCLESTATUS (Type: esriFieldTypeString, Alias: LifeCycleStatus, Length: 20, Domain: Coded Values: [Planned: Planned], [In-Service: In-Service], [Out-of-Service: Out-of-Service], ...4 more... ) LOCATION (Type: esriFieldTypeString, Alias: Location, Length: 40 ) LOCATIONDESCRIPTION (Type: esriFieldTypeString, Alias: LocationDescription, Length: 200 ) COMMENTS (Type: esriFieldTypeString, Alias: Comments, Length: 255 ) MATERIAL (Type: esriFieldTypeString, Alias: Material, Length: 10, Domain: Coded Values: [DI: Ductile Iron], [CI: Cast Iron], [PE: Polyethylene], ...10 more... ) HYPERLINK (Type: esriFieldTypeString, Alias: Hyperlink, Length: 200 ) EDIT_BY (Type: esriFieldTypeString, Alias: Edit_By, Length: 30 ) EDIT_DATE (Type: esriFieldTypeDate, Alias: Edit_Date, Length: 36 ) DATASOURCE (Type: esriFieldTypeString, Alias: DataSource, Length: 50, Domain: Coded Values: [As_Built: As_Built], [DeveloperDrawing: DeveloperDrawing], [GPS: GPS], ...3 more... ) DATASOURCE_COMMENTS (Type: esriFieldTypeString, Alias: DataSource_Comments, Length: 255 ) CRITICALITY (Type: esriFieldTypeString, Alias: Criticality, Length: 5, Domain: Coded Values: [1: 1], [2: 2], [3: 3], ...6 more... ) WAMPARENT_ID (Type: esriFieldTypeString, Alias: WAMParent_ID, Length: 15 ) ACTIVATIONDATE (Type: esriFieldTypeDate, Alias: ActivationDate, Length: 36 ) WAM_DEPARTMENT (Type: esriFieldTypeString, Alias: WAM_Department, Length: 50 ) WAM_AREA (Type: esriFieldTypeString, Alias: WAM_Area, Length: 50 ) WAM_ID (Type: esriFieldTypeString, Alias: WAM_ID, Length: 15 ) COMPANY (Type: esriFieldTypeString, Alias: Company, Length: 50, Domain: Coded Values: [MWC: Middlesex Water Company], [PWC: Pinelands Water], [SA: South Amboy], ...6 more... ) WAM_DESCRIPTION (Type: esriFieldTypeString, Alias: WAM_Description, Length: 255 ) FAILURELIKELIHOOD (Type: esriFieldTypeString, Alias: FAILURELIKELIHOOD, Length: 5, Domain: Coded Values: [1: 1], [2: 2], [3: 3], ...6 more... ) FAILURECONSEQINT (Type: esriFieldTypeString, Alias: FAILURECONSEQINT, Length: 5, Domain: Coded Values: [1: 1], [2: 2], [3: 3], ...6 more... ) FAILURECONSEQEXT (Type: esriFieldTypeString, Alias: FAILURECONSEQEXT, Length: 5, Domain: Coded Values: [1: 1], [2: 2], [3: 3], ...6 more... ) SUB_TYPE (Type: esriFieldTypeString, Alias: Sub_Type, Length: 255, Domain: Coded Values: [Blowoff: Blowoff], [Bypass: Bypass], [AirRelease: AirRelease], ...10 more... ) REPORTEDLENGTH (Type: esriFieldTypeDouble, Alias: REPORTEDLENGTH) MATERIALSPEC (Type: esriFieldTypeString, Alias: MaterialSpec, Length: 20, Domain: Coded Values: [TY: Tyton], [SB: SuperBell], [C900: C900], ...6 more... ) PIPECLASS (Type: esriFieldTypeString, Alias: PipeClass, Length: 20, Domain: Coded Values: [50: ThicknessClass_50], [51: ThicknessClass_51], [52: ThicknessClass_52], ...27 more... ) ROUGHNESS (Type: esriFieldTypeDouble, Alias: ROUGHNESS) MANUFACTURER (Type: esriFieldTypeString, Alias: Manufacturer, Length: 50 ) DEPTH (Type: esriFieldTypeDouble, Alias: DEPTH) CORROSIONPROTECTION (Type: esriFieldTypeString, Alias: CorrosionProtection, Length: 25, Domain: Coded Values: [Poly Wrap: PolyWrap], [CathodicProtection: CathodicProtection], [None: None], ...2 more... ) LD_REMARKS (Type: esriFieldTypeString, Alias: LD_Remarks, Length: 255 ) LD_LINED_1 (Type: esriFieldTypeString, Alias: LD_Lined_1, Length: 20 ) LININGTYPE (Type: esriFieldTypeString, Alias: LiningType, Length: 10, Domain: Coded Values: [FCL: Factory Cement Lined], [C&L: Cleaned & Lined], [Epoxy: Epoxy], ...3 more... ) LINEDATE (Type: esriFieldTypeDate, Alias: LineDate, Length: 36 ) LD_INCLUDE (Type: esriFieldTypeString, Alias: LD_Include, Length: 10, Domain: Coded Values: [Yes: Yes], [No: No], [Unknown: Unknown] ) LD_BOOKPAGE (Type: esriFieldTypeString, Alias: LD_BookPage, Length: 20 ) LD_BOOKLINE (Type: esriFieldTypeString, Alias: LD_BookLine, Length: 20 ) LD_ROW (Type: esriFieldTypeString, Alias: LD_ROW, Length: 10, Domain: Coded Values: [Yes: Yes], [No: No], [Unknown: Unknown] ) DISTRICT (Type: esriFieldTypeString, Alias: District, Length: 50 ) MUNICIPALITY (Type: esriFieldTypeString, Alias: Municipality, Length: 50 ) WATERTYPE (Type: esriFieldTypeString, Alias: WaterType, Length: 20, Domain: Coded Values: [Raw: Raw Water], [Potable: Potable Water], [Non-Potable: Non-Potable], ...2 more... ) PRESSUREZONE (Type: esriFieldTypeString, Alias: PressureZone, Length: 30 ) LD_TCODE (Type: esriFieldTypeString, Alias: LD_TCODE, Length: 20, Domain: Coded Values: [CA: Carteret], [CL: Clark], [EB: East Brunswick], ...34 more... ) LD_FIREDISTRICT (Type: esriFieldTypeString, Alias: LD_FireDistrict, Length: 20, Domain: Coded Values: [CA: CA], [CL: CL], [EB: EB], ...56 more... ) ABANDONMENTTYPE (Type: esriFieldTypeString, Alias: AbandonmentType, Length: 20, Domain: Coded Values: [InPlace: InPlace], [Removed: Removed] ) ABANDONMENTMETHOD (Type: esriFieldTypeString, Alias: AbandonmentMethod, Length: 20, Domain: Coded Values: [Capped/Plugged: Capped/Plugged], [Grouted: Grouted] ) ABANDONMENTDATE (Type: esriFieldTypeDate, Alias: AbandonmentDate, Length: 36 ) SHAPE (Type: esriFieldTypeGeometry, Alias: Shape) SHAPE.LEN (Type: esriFieldTypeDouble, Alias: SHAPE.LEN) Type ID Field: N/A Supported Interfaces: REST Supported Operations: Query If you need anything else to help figure this out, please let me know. Thanks, Michael

‎11-08-2013

Robert - I recently upgraded the Identify widget from 2.5.8 to 3.5.1 (as well as to flew viewer 3.5). I had identified an issue with the Identify 2.5.8 in which is what not returning any domain associated values. I was ecstatic when upgrading to 3.5.1 cleared up the issue. However, it was pointed out to me that I seem to have traded one issue for another. Now, the Identify widget is not returning non-domain associated values! I have tried a number of things, but have had no success with addressing this issue (the Search tool 3.5.3 is returning both domain and non-domain associated values). Unfortunately, my webservices are internal only, but I am including the Identify.XML for your perusal. For reference, I am including a screen cap showing the results for Identify and Search for the same feature. In particular, LOCATION, LOCATIONDESCRIPTION, INSTALLATIONDATE are blank for Identify but not for Search. Any help you can provide is greatly appreciated! Thanks, Michael <?xml version="1.0" ?>  <configuration> <identifylayeroption>visible</identifylayeroption> <identifytolerance>5</identifytolerance> <defaultzoomscale>5000</defaultzoomscale> <keepidentifyactive>true</keepidentifyactive> <returngeometryforzoom>true</returngeometryforzoom> <enablelineselect>true</enablelineselect> <enableextentselect>true</enableextentselect> <enablepolyselect>true</enablepolyselect> <enablecircleselect>true</enablecircleselect> <enableellipseselect>true</enableellipseselect> <enablemouseovergraphicsinfo>false</enablemouseovergraphicsinfo> <enablemouseoverrecordinfo>true</enablemouseoverrecordinfo> <enablegraphicclickinfo>true</enablegraphicclickinfo> <usemaptime>false</usemaptime> <infoautoclosemilliseconds>2000</infoautoclosemilliseconds> <autoactivatedtool>mappoint</autoactivatedtool> <excludebasemaps>true</excludebasemaps> <disablepopuplinks>false</disablepopuplinks> <disablelayerdropdown>false</disablelayerdropdown> <disablealllayerschoice>false</disablealllayerschoice> <replacenullswithemptystring>true</replacenullswithemptystring> <labels> <zoom2message>Click to Zoom to Point</zoom2message> <identifylabel>Identify</identifylabel> <resultslabel>Results</resultslabel> <descriptionlabel>Use the identify tool to identify features on the map:</descriptionlabel> <pointlabel>Identify by Point</pointlabel> <linelabel>Identify by Polyline</linelabel> <rectlabel>Identify by Rectangle</rectlabel> <polylabel>Identify by Polygon</polylabel> <circlelabel>Identify by Circle</circlelabel> <ellipselabel>Identify by Ellipse</ellipselabel> <clearlabel>Clear</clearlabel> <loadinglabel>Loading...</loadinglabel> <removeresultmessage>Remove Result</removeresultmessage> <idfrom>Identify From</idfrom> <noresultsfoundlabel>No Results Found</noresultsfoundlabel> <resultsfoundlabel>Results Found</resultsfoundlabel> <alllayers>All Layers</alllayers> <layersremaining>layers remaining:</layersremaining> </labels> <useproxy>  </useproxy> <layers onlythese="true"> <layer> <name>Pressurized Mains</name> <id>16</id> <url>http://gisweb/ArcGIS/rest/services/MSEX_Enterprise_TUI_TESI/MapServer</url> <fields> <field name = "MSEX_ID" alias="MSEX_ID" /> <field name = "SUB_TYPE" alias="Type of Main" /> <field name = "DIAMETER" alias="Diameter" /> <field name = "MATERIAL" alias="Material" /> <field name = "LIFECYCLESTATUS" alias="Life Cycle Status" /> <field name = "INSTALLDATE" alias="Installation Date" dateformat="MM/DD/YYYY" /> <field name = "ACTIVATIONDATE" alias="Activation Date" dateformat="MM/DD/YYYY" /> <field name = "LOCATION" alias="Location" /> <field name = "LOCATIONDESCRIPTION" alias="Location Description" /> <field name = "REPORTEDLENGTH" alias="Reported Length (ft)" /> <field name = "SHAPE.LEN" alias="GIS Length (ft)" numberformat="2|,|."/> <field name = "WAM_ID" alias="WAM ID" /> <field name = "CRITICALITY" alias="Criticality" /> <field name = "MATERIALSPEC" alias="Material Specification" /> <field name = "PIPECLASS" alias="Pipe Class" /> <field name = "COMMENTS" alias="Comments" /> </fields> <linkfield></linkfield> <linkprefix></linkprefix> <linksuffix></linksuffix> <iconfield></iconfield> <iconprefix></iconprefix> <iconsuffix></iconsuffix> <zoomscale>5000</zoomscale> <forcescale>true</forcescale> </layer> </layers> <symbols> <simplefillsymbol color="0x448ccb" alpha="0.4" style="solid"> <outline color="0x448ccb" alpha="0.8" width="2" /> </simplefillsymbol> <simplemarkersymbol style="circle" size="12" color="0x448ccb" alpha="0.8" xoffset="0" yoffset="0" angle="0"> <outline style="solid" color="0xffffff" alpha="0.8" width="1" /> </simplemarkersymbol> <picturemarkersymbol url="assets/images/i_info.png" height="30" width="30" xoffset="0" yoffset="0" /> <simplelinesymbol color="0x448ccb" alpha="0.8" width="2" /> </symbols> </configuration>

‎11-05-2012

Having some issues with being able to zoom further than the default LODs defined for the ESRI Streets and Aerials basemaps. I understand that I can add in additional LOD levels and have also found information on being able to define for "secondary" basemaps the display levels. My issue seems to be that despite setting these based on the information I uncovered, the webservice is locking up when I zoom in beyond the initial set of LODs for the ESRI mapping. I also want to add that I am not able to do any custom programming - any solution (if there are any) must be handled within the config.xml. Here is the information from my config.xml I am using: <map initialextent="-9385000 4681000 -7719000 5170000" top="0"> <lods> <lod scale="591657527.591555" resolution="156543.03392800014"/> <lod scale="295828763.79577702" resolution="78271.516963999937"/> <lod scale="147914381.89788899" resolution="39135.758482000092"/> <lod scale="73957190.948944002" resolution="19567.879240999919"/> <lod scale="36978595.474472001" resolution="9783.9396204999593"/> <lod scale="18489297.737236001" resolution="4891.9698102499797"/> <lod scale="9244648.8686180003" resolution="2445.9849051249898"/> <lod scale="4622324.4343090001" resolution="1222.9924525624949"/> <lod scale="2311162.2171550002" resolution="611.49622628137968"/> <lod scale="1155581.108577" resolution="305.74811314055756"/> <lod scale="577790.55428899999" resolution="152.87405657041106"/> <lod scale="288895.27714399999" resolution="76.437028285073239"/> <lod scale="144447.638572" resolution="38.21851414253662"/> <lod scale="72223.819285999998" resolution="19.10925707126831"/> <lod scale="36111.909642999999" resolution="9.5546285356341549"/> <lod scale="18055.954822" resolution="4.7773142679493699"/> <lod scale="9027.9774109999998" resolution="2.3886571339746849"/> <lod scale="4513.9887049999998" resolution="1.1943285668550503"/> <lod scale="2256.994353" resolution="0.59716428355981721"/> <lod scale="1128.4971760000001" resolution="0.29858214164761665"/>  <lod scale="564.248588" resolution="0.149291070823808"/> <lod scale="282.124294" resolution="0.074645535411904"/> <lod scale="141.062147" resolution="0.0.037322767705952"/> <lod scale="70.5310735" resolution="0.018661383852976"/> <lod scale="35.26553675" resolution="0.009330691926488"/> <lod scale="17.632768375" resolution="0.004665345963244"/> <lod scale="8.8163841875" resolution="0.002332672981622"/> --> </lods> <basemaps> <layer label="StreetsBase" type="dynamic" visible="false" url="http://gisweb/ArcGIS/rest/services/StreetBaseMap/MapServer" displaylevels="20,21,22,23,24,25,26"/> <layer label="Streets" type="tiled" visible="true" url="http://server.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer" displaylevels="0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19"/> <layer label="Aerial" type="tiled" visible="false" url="http://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer"/> --> Any help on straighening this issue out would be appreciated. I will have no problems if someone tells me I am simply doing something wrong! 🙂 Thanks, Michael Hanna, GISP GIS Manager, Middlesex Water Company Just to add in an additional item - the "locking" is occurring when I attempt to go past the LOD "282.124294". Beyond that the screen blanks of all data (both dynamic and basemap) and I am no longer able to change the navigation (zoom in/zoom out). When I attempt to drag the zoom slider past the 282 LOD, it simply reset to 282.

‎06-18-2012

Robert - I have been configuring the Enhanced Search widget for use in my company's webservices and have a question. I like the ability to define a hyperlink field as part of the data grid, but there doesn't seem to be a way to define a hyperlink for the info pop-up. The grid is great for wide text searches or for spatial searches, but if my field guys know the data record they specifically want to reference then it would be easier for them to open the hyperlink from the info window. Am I being dense - I have been through the documentation several times and I know the hyperlink functionality is there in the stock "Search" widget with Flex Viewer. Thanks, Michael Hanna Middlesex Water Company

‎11-18-2011

Robert - Right in one! All of the feature classes that were giving me issues had those fields toggled to "off". Something so little and yet SO much trouble. Thank you so much for a timely and correct answer!!! Michael

‎11-18-2011

I have a number of search choices set up using the stndard Search widget available with Flex Viewer 2.4. While the Search widget is returning results for all search choices, for some of the feature classes it is not displaying the little icon that usually accompanies the search and clicking on the returned result does not zoom the map to that feature. It seems to be limited to only a couple of my feature classes but I cannot determine any differences in the data or configuration that would cause this to happen. Has anyone else experienced a similar issue or know what is going on so I may fix it? Thanks in advance! Michael J. Hanna Tidewater Utilities, Inc./Middlesex Water Company

‎09-29-2011

Robert - According to my IT guy, yes, we are running SP2. Do you have any specific debugging thoughts I could try? Thanks for all you help! Michael

‎09-28-2011

Robert - Don't know, but I will check in the morning. Thanks, Michael

‎09-28-2011

Robert - The problem seems to be more systemic than I originally thought. While trying to tweak other widgets (as well as yours), I noticed that none of the attributes that have a domain associated with them return a value in the Results screen. I don't believe the HYPERLINK issue I am having is directly associated with that, but there must be something I have not configured correctly. I apologize for the questions, but I have only been working with Flex Viewer for a little over two weeks and my ignorance is probably showing. Thanks, Michael PS As for the public availibility of the service, the only option would be to conduct a Webex for you to be able to even see the service, etc. but that would be imposing on your time.

‎09-26-2011

Robert - No, only internally at the company and through VPN for field crews. Thanks, Michael

‎09-26-2011

Robert - Okay, that makes some sense and I figured I might have to change the pathing to adjust to the upgrade to Flex that we just underwent. But that doesn't explain why I am getting NULL values or not seeing the field at all. Any additional suggestions? Thanks, Michael

‎09-26-2011

Robert - First off, this is an awesome widget. However, I am having an issue with the widegt with regards to hyperlinks. I see from the documentation that I can define via <linkfield></linkfield> a feature class attirbute that contains a URL and should be able to access that URL by clicking. My issue is two fold. 1. The attribute I am defining is titled, fittingly enough, HYPERLINK and contains a UNC path to a pdf document containing additional information on the particular feature. The HYPERLINK attribute is often returned as NULL in the Identify Results window even though there should be a URL there. 2. When I do use <linkfield></linkfield>, then the HYPERLINK attribute is not even listed in the Results window. For Issue #1 above, I did not define the <linkfield></linkfield>. I am running a Flex Viewer 2.4 webservice off an ArcGIS 10 SDE database. Can you think of what I might be doing incorrectly or have I identified a previously unidentified bug (and if so, do I get a prize? )? You help would be greatly appreciated. Michael Hanna Middlesex Water Company

Online Status	Offline
Date Last Visited	‎10-06-2022 07:18 PM

My Ideas

Latest Contributions by MichaelHanna

Re: Identify Widget 3.5.1 issue

Re: Identify Widget 3.5.1 issue

Re: Identify Widget 3.5.1 issue

Identify Widget 3.5.1 issue

Using mixed tiled and dynamic basemaps and controlling zoom LODs

Re: Enhanced-Search-Widget-for-FlexViewer Part II

Re: Standard Search Function NOT zooming to returned result

Standard Search Function NOT zooming to returned result

Re: Identify Widget version 2.4.0.1 for FlexViewer 2.4 - Issue with Hyperlink

Re: Identify Widget version 2.4.0.1 for FlexViewer 2.4 - Issue with Hyperlink

Re: Identify Widget version 2.4.0.1 for FlexViewer 2.4 - Issue with Hyperlink

Re: Identify Widget version 2.4.0.1 for FlexViewer 2.4 - Issue with Hyperlink

Re: Identify Widget version 2.4.0.1 for FlexViewer 2.4 - Issue with Hyperlink

Identify Widget version 2.4.0.1 for FlexViewer 2.4 - Issue with Hyperlink