Latest Contributions by RyanKelso

Mike, did you ever get any resolution to this issue?  I'm seeing almost exactly the same thing using 10.1. ... View more

Thanks Tim!  That add-in is exactly what I was looking for, without knowing what to look for.  Worked perfectly to remove the point. I really poorly worded my second question, and ended up figuring out the answer.  With the LGIM disabled, by default there are relates on the lines layer between it and the points layer based on the ToPointID and FromPointID fields.  With the LGIM enabled, these relates aren't established.  It's handy if you want to identify a curve center point and, through the relate, see which curve/parcel it belongs to. ... View more

Isn't it Historical <> 1? Historical can be 0 or null so that doesn't work.  I guess it would be best to calc Historical null values to 0 but I'm still migrating so I haven't done that yet, and probably not everybody will think to do that.  But in that case, Historical = 0 from ESRI's script would work.  Like I said in my last post, historical parcels have already be queried out of the Tax Parcels layer, so I just removed that part of the query from ESRI's script all together. Another thing I noticed about this script is that it will append all the parcels from the fabric's Tax Parcels layer to the ParcelPublishing\TaxParcels feature class every time you run it, even if the parcels already exist in that feature class.  So you will end up with parcels stacked on parcels stacked on parcels...  I haven't messed around with the script any further, but I'll probably add a line that runs Delete Features on ParcelPublishing\TaxParcels somewhere before the append runs in order to clear it out for a fresh set of parcels. ... View more

It looks like this thread never really got an answer and it popped up on a search for me, so I'll repost my solution to this problem from another thread... If you have enabled the Local Government Information Model on your parcel fabric, which you would have if you want to use the Tax Parcel Editing Template, then there is no "Parcels" sub-layer in the fabric.  This is why the following line fails: parcels = r"%s_Layer\Parcels"%(name) With the LGIM enabled on the parcel fabric, there is a sub-layer called "Tax Parcels", which is what you want to use.  So change the line I mentioned before to: parcels = r"%s_Layer\Tax Parcels"%(name) Also, the Tax Parcels sub-layer has already queried out historical parcels, so the query in the following line will return 0 parcels so none will be appended to the parcels publishing feature class: arcpy.management.SelectLayerByAttribute(parcels, "NEW_SELECTION", """Type = 7 AND Historical = 0""") So remove AND Historical = 0 from the query to get the proper results.  I suppose you could even completely remove the Select Layer By Attributes line because the Tax Parcels sub-layer has already been queried to only include Type 7.  These are the things I had to do to get the script working, I hope this helps anybody with this problem. ... View more

I've found the 'Tax Parcel Publishing' script in the ParcelPublishingTools toolbox from the TaxParcelEditingfor10.1 that I believe is supposed to migrate our data from the Parcel Editing dataset to the Parcel Publishing dataset.  I have not been successful in running this tool.  Looking at the updatetaxparcels.py in the same Parcel Publishing folder I cannot figure out where to change the python code to make this script work.  Is there an updated version of this script or any reason for it to not be working? I want to provide an answer to this question since I had the same problem as b.blackman and this thread came up for me in a search. If you have enabled the Local Government Information Model on your parcel fabric, which you would have if you want to use the Tax Parcel Editing Template, then there is no "Parcels" sub-layer in the fabric.  This is why the following line fails: parcels = r"%s_Layer\Parcels"%(name) With the LGIM enabled on the parcel fabric, there is a sub-layer called "Tax Parcels", which is what you want to use.  So change the line I mentioned before to: parcels = r"%s_Layer\Tax Parcels"%(name) Also, the Tax Parcels sub-layer has already queried out historical parcels, so the query in the following line will return 0 parcels so none will be appended to the parcels publishing feature class: arcpy.management.SelectLayerByAttribute(parcels, "NEW_SELECTION", """Type = 7 AND Historical = 0""") So remove AND Historical = 0 from the query to get the proper results.  I suppose you could even completely remove the Select Layer By Attributes line because the Tax Parcels sub-layer has already been queried to only include Type 7.  These are the things I had to do to get the script working, I hope this helps anybody with this problem. edit: sorry for reviving such an old thread, but it came up on a google search and I only noticed the last two posts were from a month ago! ... View more

Thanks Steve.  It's not the answer I was hoping for but at least I understand what's happening now. ... View more

So it sounds like you're saying Spatial Analyst doesn't provide the user any way to control how it resamples data?  I may also be seeing this same issue in areas of the mosaic that are being projected on the fly. That's a real bummer, because I thought one of the big advantages to using the mosaic dataset is that you could combine original source data even in different coordinate systems and resolutions, on the fly.  The assumption being, you could run geoprocessing tools on the dataset and get acceptable results. Anyways, I do appreciate your responses, Steve. ... View more

Steve, thanks for the reply.  I think I get what you're saying, but I'm not sure because I don't understand how that matters in the scenario I'm describing. In my case, I have 6-foot and 3-foot pixels.  If what you're saying applies, then the 3-foot pixels are getting resampled to 6-foot so they are the ones that should look jagged, or they all should look that way if all cells are being resampled.  But if you look at my picture, the contours on the north half look fine, that is the area represented by 3-foot pixels.  It's the ones generated from the original 6-foot pixels that look bad.  And when I generate these contours from the source mosaic with all 6-foot pixels (the purple lines in my example) they look fine, so it's not like this resolution is "too low" to look good at this scale. Besides, I can take the 3-foot source mosaic, resample it to 6-foot using either Nearest or Bilinear, create contours from it and they look perfectly fine.  So unless Spatial Analyst uses some other resampling method that isn't as good, why should this even matter? ... View more

Hmm, I wasn't sure whether to post this here, on the Spatial Analyst forum, or the desktop general forum.  Maybe this was the wrong place...  I can't be the only person who has encountered this before. ... View more

Paul, I agree that it should be more obvious what units are being used for EPE and the user should be able to decide which units are used.  It would also be nice if you could set EPE as the main display property on the GPS Position Window instead of elevation. If you are a Trimble GPSCorrect user and you turn on the status bar in your ArcPad map, it will display your positional accuracy as you have set it up in GPSCorrect.  In my case, it displays the estimated accuracy after postprocessing, in inches.  This spot on the status bar toggles between your map scale and the accuracy estimate. ... View more

I've solved my problem.  I incorrectly assumed that this was some kind of usual ArcMap behavior, and I simply needed to find a way to deal with it.  Thank you for your replies, Jason, while I didn't go through the debugging process you suggested, you did get me thinking along the correct lines. Since I have a number of other ArcMap add-ins installed on my machine, I decided to uninstall all of them then test for this behavior.  After doing this, it worked fine, the locks were going away even after saving edits.  I reinstalled my current project and it still worked fine.  Using the process of elimination, I narrowed the problem down to an add-in called Attribute Assistant, from ESRI's water utilities team.  Maybe there is a memory leak, as Jason suggested, but I didn't look into it further since I don't need the Attribute Assistant anymore.  They have also updated it a number of times since I installed it, so maybe it's fixed. ... View more