Latest Contributions by mpboyle

Does anyone know if it's possible to create a SQL trigger which would auto-calculate coordinate values for a feature class? Example: For a point feature class, when a point is added or updated, the fields 'XCoordinate' and 'YCoordinate' would be auto-updated. If this is possible, would it also be possible to calculate the coordinate values based on another coordinate system from what is used for the feature class, like WGS84 for longitude and latitude? Example Environment: DBMS: SQL Server 2008 R2 Geometry: SQL Geometry Thanks in advance! ... View more

Does anyone know how to register a SQL spatial view using a feature class that has Esri binary as its shape? I have tried sdetable -o register and sdetable -o create_view but have been unsuccessful.  This could be because of my own lack of knowledge with the command line. ArcSDE = 10.1 DBMS = SQL Server 2008 R2 Feature class name = lcbase.dbo.Parcels Joined table name = gis.dbo.vw_parcels Trying to create the view in a geodatabase called 'gisstaging'. Below is the create_view command line prompt I've tried with an error (Error -162, Invalid Database Name) sdetable -o create_view -T VWTest -t lcbase.dbo.PARCELS,gis.dbo.vw_parcelsweb -c lcbase.dbo.PARCELS.SHAPE,lcbase.dbo.PARCELS.GPNNUM,gis.dbo.vw_parcelsweb.GPN -w"lcbase.dbo.PARCELS.GPNNUM = gis.dbo.vw_parcelsweb.GPN" -i sde:sqlserver:lcgissql -D gisstaging -u **** -p **** Below is the register command line prompt I've tried after creating the view in SSMS with an error (Error -144, Wrong Column Type, SE_table_get_shape_type failed) --- I'm assuming this is due to the Esri binary shape. sdelayer -o register -l gisstaging.dbo.ParcelsSearch,Shape -e a -t geometry -i sde:sqlserver:lcgissql -s lcgissql -D gisstaging -u **** -p **** Any ideas on how I can create a spatial view using an Esri binary feature class...? Thanks in advance! ... View more

I believe there should be a way of auto-calculating geometry attributes for a feature class.  Kind of like editor tracking fields in that they are system maintained and defined by the user. For example, if I have fields meant to store Longitude and Latitude, a tab would be available to select which field I wanted to store the longitude value and which field I wanted to store the latitude value.  These fields would then be system maintained and I wouldn't have to worry about calculating geometry. A similar option could be available for polygon features...different types of areas: acres, square feet, square meters, hectares, etc, etc... ... View more

I think there should be a way to import a domain from another geodatabase rather than having to export the domain to a table and then import that table to a domain.  One step, instead of two should be required for this. ... View more

When I add a feature that has a date field(s) with Collector and those fields are not visible as an editable field, they have a default date of 1/1/1970.  This is rather annoying to go back and fix either manually or creating a script to <null> those records out. ... View more

I'd like the ability to have 'smart' form entry with Collector.  For example, if field A equals 'True' then field B, C and D do or do not show up for entry. ... View more