|
POST
|
Thanks, that makes it a bit clearer, but the still confusing part is where the line on one side is marked 500' , but on the other side the two parcels add up to 499.01'. Maybe not a big difference, but it seems inconsistent. I can see how it could happen from two different surveys, but it looks odd.
... View more
08-03-2012
01:55 PM
|
0
|
0
|
3382
|
|
POST
|
Thanks Amir, that's very helpful, although #4 confuses me. Two lines connected to the same points with different measurements? I think running a topology to clean up the data before implementing a fabric seems like it will be the most work. I went to several of the LGM sessions at the UC that Scott Oppman ran, got me interested in the idea. Starting with Land, my area, maybe then see if other depts. like Public Works, Fire, etc, would be interested.
... View more
08-03-2012
11:35 AM
|
0
|
0
|
3382
|
|
POST
|
I'll look for the white paper. Thanks for the offer, may take you up on it ata a later date. Couple other kettles boiling right now, but this is a project I'd like to get on sometime soon.
... View more
07-31-2012
11:18 AM
|
0
|
0
|
3382
|
|
POST
|
Thanks Ryan. So basically, use a topology to clean up the data, then relatively simple to import it into the fabric? I had that idea, but some of the help online and at the UC made it seem more confusing - using XRay, editing xml files, etc. Maybe that's more intended for data in the Local Government model. That said, cleaning up errors will take a while. I've got a feeling curves and vertices will be needing lots of work. A lot of previous data was entered into Arc by folks more used to CAD. I'll probably try a subset, see how it goes.
... View more
07-31-2012
09:08 AM
|
0
|
0
|
3382
|
|
POST
|
What is the advantage of using a Parcel Fabric vs. using a topology? The two advantages I know of are that the Parcel Fabric will allow use of the Maps & Apps (phrase drilled into my head at the UC last week), and that a fabric can have associated features in order to maintain spatial relationships. A topology would need to be periodically validated and corrected. But the work involved in migrating all our polygon parcel data into a fabric seems pretty substantial, so maybe a topology, which we (I) would have to create anyway, would be sufficient for our needs. I'm also unclear whether using a fabric involves editing each individual parcel. This seems like a lot of work compared to a typical workflow of using a cogo traverse around a block and splitting parcels out. Are there other advantages of a fabric I'm missing? Thanks.
... View more
07-30-2012
12:18 PM
|
1
|
9
|
8096
|
|
POST
|
I don't have any advice, but unless it's a geosynchronous satellite, line of sight will always be changing, and not always be there anyway. Would the Observer Points or Viewshed tools in Spatial Analyst help?
... View more
07-20-2012
12:43 PM
|
0
|
0
|
1055
|
|
POST
|
When you are making selections you need to make your feature classes layers. Thanks, appreciate it. Which feature classes? I create a temporary layer to hold the preliminary Case feature before adding it to the feature class. Also, both features - Case and Parcel - are feature classes in the TestCases_Geodatabase, where it runs fine, so I don't know why it wouldn't run in production, except that Parcel is in a sde database there. That's the only difference I can think of. It would be inconvenient to make the sde Parcel feature class a lyr file. It contains tens of thousands of records that are updated fairly frequently. I'd have to recreate it every time the script is run. The purpose of this script is to automate a task for another department where the users don't have a lot of Arc experience.
... View more
07-19-2012
11:26 AM
|
0
|
0
|
491
|
|
POST
|
The script below runs fine when all the feature classes are in the same geodatabase (TestCases_Geodatabase.gdb). But for production, one of the features, Parcel, is in a SDE geodatabase. This fails, however. Not sure if problem is in the workspace setting, feature class name, if I need a connection string to the SDE, or what. The actual feature class name is in a feature dataset in the db and is named CitySDE.GIS.Parcel. If I use the name CitySDE.GIS.Parcel in the line parcel =, I get error 1; if I change the line to parcel = "Parcel" (the name in the TOC), I get error 2. Any help greatly appreciated. Thanks. Error 1 - parcel = "CitySDE.GIS.Parcel"
Executing: CreateCaseFeature del1
Start Time: Wed Jul 18 10:52:30 2012
Running script CreateCaseFeature...
Case number: del1
Checking for previous layer
<class 'arcgisscripting.ExecuteError'>: Failed to execute. Parameters are not valid.
ERROR 000732: Input Rows: Dataset TempleSDE.GIS.Parcel does not exist or is not supported
Failed to execute (GetCount).
...
Error 2 - parcel = "Parcel"
Dissolve complete...Appending to Cases
Error adding parcels to Cases in SelectCases().
Failed to execute. Parameters are not valid.
The value cannot be a feature class
ERROR 000840: The value is not a Raster Catalog Layer.
ERROR 000840: The value is not a Mosaic Layer.
Failed to execute (SelectLayerByLocation).
Adding Case number...
Case number del1 added.
Setting definition query to: "Case_" = 'del1'
<type 'exceptions.UnboundLocalError'>: local variable 'layer' referenced before assignment
Failed to execute (CreateCaseFeature).
Failed at Wed Jul 18 11:03:02 2012 (Elapsed Time: 43.00 seconds)
import arcpy, sys
from arcpy import env
env.workspace = r"\\ServerA\Planning\Cases_Geodatabase.gdb"
#env.workspace = r"\\ServerA\Planning\TestCases_Geodatabase.gdb"
env.overwriteOutput = True
case_number = arcpy.GetParameterAsText(0)
arcpy.AddMessage("Case number: " + case_number)
lyr = r"\\ServerA\Planning\Cases_Geodatabase.gdb\temp_parcel_lyr"
#lyr = r"\\ServerA\Planning\TestCases_Geodatabase.gdb\temp_parcel_lyr"
parcel = "CitySDE.GIS.Parcel"
mxd = arcpy.mapping.MapDocument("CURRENT")
#-------------------------------------------------------------------------------
def MakeCaseFeature():
''' Dissolve selected parcel features into one temporary lyr file.
Append it to the Cases feature class.
Delete the temporary lyr file.
Clear the parcel selection. '''
clear = "CLEAR_SELECTION"
target = "Cases"
schemaType = "NO_TEST"
fld = "CENTRACT" # no data is stored in this field
selectType = "HAVE_THEIR_CENTER_IN"
try:
arcpy.AddMessage("Starting Dissolve...")
# make temporary parcel lyr file from selected parcels, dissolving them
# into one feature
arcpy.Dissolve_management(parcel, lyr, fld)
arcpy.AddMessage("Dissolve complete...Appending to Cases")
# add case feature in temporary layer to Cases
arcpy.Append_management(lyr, target, schemaType, "", "")
# select new case feature
arcpy.SelectLayerByLocation_management(target, selectType, lyr)
# delete temporary layer
arcpy.Delete_management(lyr)
arcpy.AddMessage("Append complete...")
# clear selection on parcels
arcpy.SelectLayerByAttribute_management(parcel, clear)
except Exception as e:
arcpy.AddError("Error adding parcels to Cases in SelectCases(). \n" + e.message)
#-------------------------------------------------------------------------------
# Add case number to case_ field in Cases
#
def AddCaseNumber():
fc = "Cases"
fld = "Case_"
arcpy.AddMessage("Adding Case number...")
try:
arcpy.CalculateField_management(fc, fld, '"%s"' % case_number)
arcpy.AddMessage("Case number " + case_number + " added.")
except Exception as e:
arcpy.AddError("Error setting Case_ field value to case number: " + case_number + "\n" + e.message)
#-------------------------------------------------------------------------------
# Set the definition query to display only the new case
#
def SetDefinitionQuery():
clear = "CLEAR_SELECTION"
fc = "Cases"
fld = "Case_"
query = "\"Case_\" = '%s'" % case_number
# alternate formatting methods for query
# query = "\"%s\" = '%s'" % (fld, case_number)
# query = '"%s"' % fld + " = " + "'%s'" % case_number
mxd = arcpy.mapping.MapDocument("CURRENT")
arcpy.AddMessage("Setting definition query to: " + query)
try:
arcpy.RefreshActiveView()
for layer in arcpy.mapping.ListLayers(mxd, fc):
layer.definitionQuery = query
# clear selection on parcels
arcpy.SelectLayerByAttribute_management(fc, clear)
except Exception as e:
arcpy.AddError("Error setting definition query. \n" + layer.definitionQuery + "/n" + e.message)
arcpy.RefreshActiveView()
arcpy.RefreshTOC()
mxd.save()
del mxd
#-------------------------------------------------------------------------------
# Start 'er up!
#
def main():
arcpy.AddMessage("Checking for previous layer")
if arcpy.Exists(lyr):
arcpy.Delete_management(lyr)
# Check how many parcels are selected. Count returns all parcels if none are
# selected, or only selected ones if there are any. Check returns a list of
# selected parcels, or 0 if none are selected.
count = int(arcpy.GetCount_management(parcel).getOutput(0))
desc = arcpy.Describe(parcel)
check = desc.FIDSet
# make sure parcels are selected before running rest of script, otherwise exit
if len(check) != 0:
arcpy.AddMessage("There are " + str(count) + " parcels selected \n" )
for layer in arcpy.mapping.ListLayers(mxd, "Cases"):
layer.definitionQuery = ""
MakeCaseFeature() # create the case feature
AddCaseNumber() # add case number to the case field
SetDefinitionQuery() # only display current case
arcpy.RefreshActiveView()
arcpy.RefreshTOC()
else:
arcpy.AddError("No features selected! \n Please select at least one parcel feature. \n")
arcpy.AddError("Quitting the Create Case tool \n")
if __name__ == '__main__':
main()
... View more
07-18-2012
08:49 AM
|
0
|
3
|
689
|
|
POST
|
I must be doing something wrong. All I get by right clicking is a What's This? popup. I'm right clicking the CreateCase script tool (image attached). What am I missing? Probably something simple.
... View more
07-16-2012
01:26 PM
|
0
|
0
|
2222
|
|
POST
|
Is there a way to add a thumbnail to a python script? I've added the script to the [Geoprocessing tools] Commands and from there added it to a toolbar for easy one click access. But I have several tools I'd likr to do this for, and they all show the default proclamation looking scroll image. I'd like to be able to set individual images for each script icon. I did set a .png image as an illustration in the metadata area in ArcCatalog, but that doesn't display for the icon. Thanks for any and all help.
... View more
07-16-2012
12:14 PM
|
0
|
5
|
2363
|
|
POST
|
Thanks much, that appears to have fixed it. If I edit a cogo value in the attribute table, that doesn't actually change the feature , does it? It didn't when I tried it, but maybe missed something.
... View more
05-14-2012
06:22 AM
|
0
|
0
|
2266
|
|
POST
|
Thanks for the reply. I added them via the tool in ArcCatalog. I'm pretty sure the Direction field was 12 characters; I tried changing the length but can't do that on an existing field afaik. I did enter the direction in the format N 45.2367 E rather than N 45-23-67 E, but either way they should fit in field length 12. I can enter the segments, and they display properly, until I click Finish. I didn't used to have this problem; maybe it's related to one of Arc 10's SPs?
... View more
05-11-2012
04:55 AM
|
0
|
0
|
2266
|
|
POST
|
I re-posted this question in the land records forum, but don't see where I can delete this one. Please ignore this post. Thanks.
... View more
05-10-2012
05:30 AM
|
0
|
0
|
398
|
|
POST
|
I added COGO fields to a line feature class table in a file geodatabase in ArcCatalog, and then used the Traverse tool on the COGO toolbar to create a parcel. But whenever I do this, I get the error below when I click Finish on the COGO box. This happens with every parcel. If I delete the COGO fields, it works fine. Any ideas on how to fix this? I didn't find anything searching support. Thanks. edit: I originally posted this under editing, but this seems a better forum. I can't delete the old post, though, so apologies if it seems like double posting. Not my intention. [ATTACH=CONFIG]14233[/ATTACH]
... View more
05-10-2012
05:25 AM
|
0
|
5
|
2376
|
| Title | Kudos | Posted |
|---|---|---|
| 6 | 08-22-2019 07:41 AM | |
| 1 | 05-05-2014 04:30 AM | |
| 1 | 08-15-2018 06:23 AM | |
| 3 | 08-06-2018 07:31 AM | |
| 1 | 03-30-2012 08:38 AM |
| Online Status |
Offline
|
| Date Last Visited |
12-12-2021
01:00 PM
|