Latest Contributions by deleted-user-VeC5jUIlNXtq

Fair answer, in this case I don't think it's a bad thing. In the bigger picture, because it wasn't intended, I'm not 100% happy with it, but that's ok for now. At least I've been given a good explanation. As for the Do Loop, it's purpose is to prevent the form from closing when the user hits 'OK' without having filled out the required parameters. Without it, they're warned that they didn't fill everything out, but because the OK button hides the form (with the expectation that it will proceed with the rest of the code), they have to re-run the Add-In. It's not required, but I like the idea that if they forget 1 thing, they don't have to go back and re-do everything. Thus the reason as well to handle form closing event. If they hit cancel or 'X' I know they don't want to continue, but the code doesn't unless I tell it. My knowledge is rather limited, so I may be misunderstanding things, but that's the reason I have those in place. ... View more

Thanks for the helpful reply. That makes some sense to me. That behaviour wasn't intentional, but I don't see it as being bad (at least in this particular case)...is that bad practice that the variables are remaining as is? I have an additional question as well. When the form closes (either cancel or 'X') it should be setting bContinue = False. Shouldn't this exiting of the main Subroutine call the garbage collection and dereference any variables? Mainly wondering if I should "fix" the fact that the variables aren't being dereferenced. Thanks again! Here's the code that the Add-In button click runs, if it helps make sense of my problem:         Do             ' Declare and initialize variables.             Dim pUID As IUID             Dim pLayer As ILayer             Dim pEnumLayer As IEnumLayer             Dim pMxDoc As IMxDocument             Dim pMap As IMap             pMxDoc = My.ArcMap.Document             pMap = pMxDoc.FocusMap             ' Set UID to retrieve IFeatureLayer which can be QI'd to ILayer.             pUID = New UID             pUID.Value = "{40A9E885-5533-11d0-98BE-00805F7CED21}"             ' Get list of all feature layers in the map. True means recursive so it will return all feature layers in the table of contents.             ' Set iterator to the front of the list.             pEnumLayer = pMap.Layers(pUID, True)             pEnumLayer.Reset()             ' Get first layer in list, and QI to ILayer (to make use of the .Name property).             pLayer = pEnumLayer.Next             ' Clear the combo boxes in case the user has already attempted to proceed without filling all parameters out.             frmProgress.cbTWPLayer.Items.Clear()             frmProgress.cbLSDLayer.Items.Clear()             ' Iterate through layers to populate combo box list.             Do Until pLayer Is Nothing                 frmProgress.cbLSDLayer.Items.Add(pLayer.Name)                 frmProgress.cbTWPLayer.Items.Add(pLayer.Name)                 pLayer = pEnumLayer.Next()             Loop             ' Display the form.             frmProgress.ShowDialog()             ' OK and Cancel buttons determine whether or not to proceed.             If Not Procedures.bContinue Then                 Exit Sub             Else                 ' Store information from combo boxes.                 sLSD = frmProgress.cbLSDLayer.Text                 sTWP = frmProgress.cbTWPLayer.Text                 If sGPXPathPublic = "" Or sGDBPathPublic = "" Or sLSD = "" Or sTWP = "" Then                     MsgBox("You must fill out all parameters.")                     Continue Do                 Else                     Call Procedures.Main(frmProgress)                     Exit Sub                 End If             End If         Loop ... View more

Once they hit OK on the form (assuming all parameters have been filled out), the program does a whole bunch of stuff (irrelevant for now). If they hit cancel or the 'X' button, the intention is to quit out of the Add-In (don't proceed with aforementioned stuff). ArcMap would remain open in this case. The issue is that, if they click the Add-In again, I want it to be a clean slate. Since it's not, that means my code is somehow doing something it shouldn't be...e.g. remembering variables. ... View more

Hey Neil, I originally had the integer values, but switched to the longer definition just for some quick testing purposes. That definitely wasn't the problem, the integer values for both the NAD83 and WGS84 projection definitions still fail. This is being developed as an Add-In for ArcMap. ArcMap is running, user clicks the button, choose GPX file, and the code does all the rest. Very strange. I'm sure I had it at least partially working Friday too, can't figure out what happened. I started thinking it might be my logic in the IF statement check. Might just tell it to use Zone 11 (since that's the test data location), and ignore the check for meridian. Anyways, I'll keep this thread updated as I test different things, maybe a miracle will happen haha. ... View more

Thanks for the advice. Yes, my debugging style is message boxes and it was the pPCS = pSRFactory.CreateProjectedCoordinateSystem() line that seemed to be the problem. We typically work with just NAD83 which is why I've defaulted to that. My alternative thought to that would be to project the original geographic data into NAD83 and then set up NAD83 UTM Zones since the datums will then match. Quick check shows failing on UTM Zones for WGS84 as well 😞 Might attempt my alternative in the meantime. Let me know if you come up with any other ideas. I appreciate the help in eliminating some options. Thanks! ... View more

Spoke too soon. The "pFreshPoint" is given a spatial reference above all this code. So it specifically knows it has WGS84 as the spatial reference. I'm sure I'm overlooking something minor, but at this point I'm at least happy you've picked out some things to check. Anything else you can think of? We have some similar code in a different program that does essentially the same thing (just for different file input). I'm going to check against that again, maybe I've missed something. Thanks for your help! ... View more

Interesting point Neil. The feature class that the point are being "run" from, is the result of some previous code which calls the Geoprocessing tool "GPX to Feature" which converts a standard .gpx file into a feature class (in this case, inside a file geodatabase). When I examine the result in ArcCatalog (or look at the tools help), it indicates a default spatial reference of WGS84. However, perhaps telling the code to specify is the answer. Sure it exists...but does the code know that? Perhaps not. Will try that. Thanks! ... View more

Thanks for the quick reply Neil, you've been my saviour more times than I can count and your help is always extremely appreciated! Unfortunately, I'm pretty amateur with debugging...and I'm using VS2010 express, so I don't know if there are some limitations. However, now that you mention it, I think perhaps I should have included a transformation. Even though in my neck of the woods, the WGS84 and NAD83 datum are almost identical, if I do it through the toolbox, ESRI automatically adds a transformation (obviously because datums are switching). So it's quite possible my code is failing because I'm not telling the code to transform the data? I thought of that earlier, but wasn't sure if it was necessary because no other code snippet included that. I'm going to try that. I know for a fact that my data is all points and they are part of a WGS84 feature class. ... View more

No problem, glad I could help! Was hoping some veterans might be able to confirm, but I think if they see something incorrect they will notify us. Cheers, ... View more