Latest Contributions by BrandonPlewe1

FOLLOW-UP: Okay, I buckled and installed a standalone ArcGIS Server 11.0 (no Portal, I don't have a license available and Web Adaptor is not an option with Apache; I'm fine running on Port 6443). AGS works okay generally. When I try to publish the parcel fabric as a feature service (without Portal, I'm saving it as a service definition file to import into AGS). It says I have to include the topology, but when I include it, it says "topology layer is not supported on a non-federated ArcGIS Server." This sounds I not only have to be running Portal, but I have to be running it on multiple servers. Is that the case? Why does this have to be so complicated (and expensive)? ... View more

I just had this happen, and here's my workaround. Basically, an APRX file is a zip-compressed folder, consisting of (among other things) a folder for each element of your project:  map, layout, etc. Inside each are XML files and such defining the setup of each element. Chances are, one of those elements is corrupt. So, use the "Christmas Lights" method! Copy the APRX file Rename the copy to .zip Open the zip file, and delete one of the folders Rename the copy back to .aprx Try to open it in ArcGIS--if it works, that's the offender, if not, repeat steps 1-5 for the next folder. Yes, you can speed this up with a binary search method to narrow it down (delete the first half of the folders, then the second half, ...), but remember that there may be more than one corrupted element (the christmas lights nightmare). Once you narrow it down, you could go into that folder and muck around looking for the problem, or if it isn't too major (my last one was just a selection set, so nothing major), just leave it out and build that element over again. The fact that the master XML file is now referencing a missing element may or may not throw an error or a warning, depending on how vital it is, but in my experience, it seems to make do okay. ... View more

I just had this happen, and here's my workaround. Basically, an APRX file is a zip-compressed folder, consisting of (among other things) a folder for each element of your project:  map, layout, etc. Inside each are XML files and such defining the setup of each element. Chances are, one of those elements is corrupt. So, use the "Christmas Lights" method! Copy the APRX file Rename the copy to .zip Open the zip file, and delete one of the folders Rename the copy back to .aprx Try to open it in ArcGIS--if it works, that's the offender, if not, repeat steps 1-5 for the next folder. Yes, you can speed this up with a binary search method to narrow it down (delete the first half of the folders, then the second half, ...), but remember that there may be more than one corrupted element (the christmas lights nightmare). Once you narrow it down, you could go into that folder and muck around looking for the problem, or if it isn't too major (my last one was just a selection set, so nothing major), just leave it out and build that element over again. The fact that the master XML file is now referencing a missing element may or may not throw an error or a warning, depending on how vital it is, but in my experience, it seems to make do okay. Last time I did this it took about 3 hours (mostly waiting for ArcGIS Pro to crash over and over and over again), but that was a lot better than rebuilding a 30 hour project from scratch! ... View more

Tim, thanks for working so hard on this. Your solution isn't perfect; I'm not really resetting the geometry so it matches the original, just visually transforming (rotate & scale) the geometry so it looks right, but it's probably the best I'm going to get, so I'll mark it as answered. ... View more

Tim, thank you for working through my various scenarios. I hope the several answers to several questions doesn't lose the focus, but I'll try to respond to everything. Adjustment (the white paper etc.): I'm not arguing the validity or rigor of the adjustment process; I'm sure it does what it's supposed to with the data you give it. It does take some practice (and some trial and error) to learn to give it the right data (e.g., the effect of the accuracy attribute, or the best locations for control points), and the inability to "start over" is a problem here. Rejoining: I have tried this. I was originally very hopeful that this would do exactly what I wanted (reset the geometries back to the COGO measurements), because when you unjoin the parcels, and edit them, they appear to be in their original geometry. But alas, when I join or rejoin them (with fewer links, like 1), they retain the adjusted (warped) shapes; in fact, some parcels get far worse during the rejoin process. Maybe I'm doing it wrong POB: yes, that does work when I unjoin and rejoin to it (especially if it is the only link), or if it is part of an existing adjustment set. I won't worry about this one further. Altering measurements: it does appear that if I unjoin the parcels, and edit a parcel, it changes shape and the surrounding parcels are affected by it. If it is still joined, I can change the measurements but the shape doesn't change. I won't worry about this one either for now. Again, thanks for attempting to find a workaround, but it looks like I can't do what I want to do. Seeing the original geometry when I open the parcels when they are unjoined is tantalizingly close; if only there were a button I could push to say "keep that!" ... View more

These are all useful tips that might make the adjustment marginally better (they didn't help my parcels, but then I had already done most of them). However, they don't really answer my original question: how can I eliminate the adjustments altogether and retrieve the geometry purely based on the COGO measurements? I listed several uses for such a capability above, but for this particular situation, I'd like to be able to try a completely different approach to my adjustment: do a global rotation first to account for the coordinate system grid north, then do the least squares adjustment. I must really be misunderstanding the whole parcel fabric idea (this is for a research project, not a municipal GIS where Parcel Fabrics would more commonly be used), because I keep hitting these issues that nobody else seems to have any difficulty with. For example, why is there nothing in the documentation about how to correctly handle the declination between the grid north of the local coordinate system and true north? ... View more

If the problem was as simple as I had goofed up, then versioning would be a satisfactory (if not for me with a file geodatabase) answer. However, it seems like a design flaw. Besides this example, I have in the past two weeks already hit a number of situations where I would like to regenerate the geometry based on the COGO descriptions. For example: - Adjusting a global rotation factor based on the coordinate system grid north - Adjusting the POB based on a better coordinate measurement for a monument - Fixing a mistyped measurement back in an early parcel (i.e., the location of all subsequent parcels is based on it) - Adjusting COGO measurements for a parcel that doesn't close well (yes, in this case I have the freedom to do that). In Survey Analyst (2004), I could make these kinds of changes, and they would propagate throughout the network. Is this capability somehow mutually exclusive with the ability to do the least squares adjustment with control points? ... View more

I'm having the exact same problem on several computers, and we're trying to publish to ArcGIS Online, not our own server, so licensing can't be the problem. Plus, the problem is that Mapping (i.e., dynamic map service) is not showing up. That is the core capability, not an advanced one that would require an extra license. We're using 10.2.2. ... View more