Select to view content in your preferred language

Dynamic filtering in ArcPad

2631
2
09-06-2013 01:13 AM
BruceKerridge
Deactivated User
Hi,

I am trying to create an ArcPad data collection form for ecological assessments, and would like to be able to create a dynamic filter to limit the items in a list box based on a previous selection in the form.

The reason for this is there are 10 "Habitat Types" which each have approximately 10 "Habitat Classes" associated with them.  If the field collector selects a habitat type from a list box, I would like them to see just the habitat class associated with this in the next list box.  I've attached a spreadsheet to show these.

I could simply allow a manual selection from the longer list of the habitat classes, but wanted to see if there was a better and more efficient way.

Any suggestions greatly appreciated.

Kind Regards

Bruce Kerridge
Tags (3)
0 Kudos
2 Replies
HannahFerrier
Deactivated User
This is a perfect scenario for setting up your geodatabase to use subtypes!!

Using subtypes will allow you to apply coded or ranged domains to features, enabling you to constrain input information to a valid set of values. For example, in a water distribution network, the subtype 'water mains' could have a coded domain for building materials restricting them to be made of cast iron, ductile iron, or copper.

Subtype/domain relationships in the geodatabase are exported to ArcPad during checkout using the Data Manager Toolbar.

- Hannah
0 Kudos
KyleCollins
Deactivated User
Hannah is right given that your table is so simple, either or as Parent / Subs.  It will make your life much easier.

However, if you have as we do, 5 levels of subtypes; that subs of subs of subs of subs, ESRI couldn't give us a way to make it work.
Our "IF Then" section of VBS file has, over the past 10 years, grown and shrank, and been modified again and again.

What I'd like to know is for the next generation of this project would it be better to switch to ArcMobile and use a tablet?  Will the VBScript be translatable.  Or has there been any developments in the Geodatabase that would allow multiple layers of subtypes?

I'll attach a copy of our lookup table for the forms.
0 Kudos