Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I'm currently creating an ArcSDE DB on an SQL Server. It is designed to complete species survey, with information from the field.

In order to help themselves, they asked me to implement a particular yet logical behavior: in a first field Order, they want a list of related taxa. In a second field, a list of Genera (Genus) related to their Order choice. In a third field Species the list related to their Genus choice.

Basically, it is the subtype/domain behavior, but here, the field Genus should be a subtype and a domain at the same time and it's not possible.

So, I thought about implementing this behavior in SQL Server but is it possible? Moreover, will this behavior work directly in ArcMap when working in a editing session on the DB?

Other ideas? Thanks, Merlin

share|improve this question
    
I think your "gender" field may be genus or genera. I would refer to this as hierarchical fields. –  PolyGeo May 16 '13 at 21:45
1  
There is an ArcGIS Idea which relates I think to part of your requirement. Another part of the requirement can be met with Tool Validation but the last part (as I see it) which I don't yet have an idea for is how to enforce the hierarchy during Attribute editing. –  PolyGeo May 18 '13 at 5:32

2 Answers 2

I would tackle your problem using four SQL Server tables:

table 1: Order Lookup (orderid int, OrderName varchar (100))

table 2: Genus Lookup (genusid int, orderid int, GenusName varchar (100))

table 3: Species Lookup (speciesid int, genusid int, SpeciesName varchar (100))

table 4: SurveySpecies (surveyid int, orderid int, genusid int, speciesid int)

Set the Genus Lookup to have the constraint that the orderid foreign key value exists in the Order Lookup Table and is NotNull. Set the Species Lookup to have the constraint that the genusid foreign key value exists in the Genus Lookup Table and is NotNull.

Populate the lookup tables with everything you will ever run across. Then you can back populate order and genus in the SurveySpecies table using their related tables (and I would use a python script calling a stored procedure to do that).

share|improve this answer

I don't think there is a really good answer to this but ...

  1. This is an existing ArcGIS Idea that I would encourage you to vote for because it sounds like your question.
  2. Hierarchical field behaviour can be programmed into Geoprocessing tool dialogs using Tool Validation.
  3. There is another ArcGIS Idea (mine) related to this for Validation of Hierarchical Fields.
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.