Latest Contributions by MichaelHamsa

Hello, Just to follow up on this, in case someone else runs into a similar problem, I think the issue was that the password I specified for the "Machine Administrator" did not meet Azure's minimum password requirements - it was too short - and the Cloud Builder didn't catch this as I was running through the wizard. I'm pretty sure that it was failing while setting up the Azure VM because of the password problem. Once I set a password that met Azure's minimum requirements for an admin account on a VM, it was successful. One other item I noticed is that I changed the resource prefix from rr (default) to gs and the Virtual Machine that the Cloud Builder created as part of my deployment has the prefix rr (instead of gs). Just a minor issue, and from what I can tell hasn't caused any issues, but I thought I'd bring it up. Mike... ... View more

Hello, Just wanted to clear this up in case anyone else has the same question. I was able to get this working after correctly requesting app permissions. Starting with Android 6.0 you have to request app permissions a little differently and once we got that wired up in the Xamarin Forms app, LocationDisplay started working as expected. If you are having problems starting LocationDisplay I'd suggest using StartSync on the DataSource because it does return more useful error information, I just missed it the first time around. Mike... ... View more

Take a look at the Data Collection Example App. It is a complete application built using MVVM. The Identify operation is performed on GeoviewTapped. Take a look at how it's set up using an Identify Controller to abstract the Identify logic from the view. I'm happy to answer any questions you may have after looking at this app.  ... View more

Mark, I’ll do some more work to try to figure out what’s causing the problem using these suggestions. I was just checking to see if there was some additional detail in a log somewhere that may help narrow things down a little. Thank you very much. Mike Hamsa Chief Technology Officer - GeoSpatial Innovations, Inc. P: 512-982-6735 ... View more

Thank you very much Greg – that’s exactly what I needed. Mike Hamsa Chief Technology Officer - GeoSpatial Innovations, Inc. P: 512-982-6735 ... View more

Katie, Yeah, I’m pretty sure it is – right now It’s just set to * which should allow requests from all domain. I’ve used Fiddler (which shows the request and response data to and from the web service) and I can see the initial response coming back from the WFS to the Online Portal so it looks likes it is returning data correctly. But that’s really all I can see. The Online Portal makes the initial GetCapabilities request to the WFS, and the WFS returns the Capabilities document to the Online Portal. Then you get that message from the Online Portal, So I’m just not sure. I’ve compared the Capabilities document that is returned to the Online Portal from this WFS to other Capabilities documents we have seen and it actually looks identical, except for the layer list and the URLs. It’s weird – I can’t figure out what’s going on. It seems like it should be working. Mike Hamsa Chief Technology Officer - GeoSpatial Innovations, Inc. P: 512-982-6735 ... View more

Morten, Not a problem. I’m using the Visual Studio Android Emulator (I know, probably shouldn’t be). These are actually older Hyper-V virtual machine images. To get it to work correctly while debugging with Visual Studio, I had to make the following changes. Emulator VM changes 1. Go to the Hyper-V manager 2. Right click on the VM for the emulator you are using and press Settings 3. Open the Processor folder 4. Select Compatibility, and then check ON “migrate to a physical computer with a different processor” Visual Studio Build Settings 1. In your solution, right click on the Android Project and press properties 2. Go to Android Options 3. Check OFF, Use Fast Deployment. That pretty much took care of it. Thanks again, Mike Hamsa Chief Technology Officer - GeoSpatial Innovations, Inc. P: 512-982-6735 ... View more

Thanks Nick, appreciate the help and quick responses. ... View more

Marco, To resolve this problem we ended up upgrading from version 4.3 to version 4.5 of the JavaScript API – this seems to have resolved our performance problems. After looking through the release notes, it looked like version 4.4 had some performance improvements in it so going to version 4.5 was the best move. This seems to have resolved our issues. I believe that version 4.6 is out now. What version are you currently running? Mike Hamsa Chief Technology Officer - GeoSpatial Innovations, Inc. P: 512-982-6735 ... View more

Hi， I have the same problem do you solve the problem？ ... View more

Yeah, this could be an error in how the JS API 4.3 interprets renderers.  I'm unsure if null is specified as a valid value for colors.  Apparently it's not if it's the cause of this error, but according to the agol web map viewer, it is a valid value. ... View more

Here's what I'm seeing when I use the Edit Vertices tool on one of the lines in ArcMap. Notice the really short segments at the end of the line. For reference, that dogleg there toward the end is only about 7 feet long - that covers the last 3 vertices. On the device - runtime content - this line would look very bad. ... View more

I've a bit more testing and this does correct the problem - Thanks Morten. I ended up restructuring the geodatabase so it didn't have different types of features in the same table, and that way I didn't need to use the Definition Query. This is definitely a bug: not utilizing the Definition Query on a layer when creating a FeatureTable (for a layer) in runtime content. Most of the other Esri toolbox tools (data export, feature class export, etc) all honor the Definition Query when you export a layer to another geodatabase. Creating runtime content should be no different. Not to mention the runtime geodatabase is MUCH larger then it should be in this situation. Thanks again, mike... ... View more