We have a dataset with a personal GDB (mdb) with several feature classes and an mxd tied to those features to create layers based on definition queries…
Currently to QAQC our data we use MsAccess queries to cross check data both within a feature class table and across feature classes that have common ID’s…
This is building space data, so things we check are a field that marks the space vacant [sp_vacant ] and another field within the same feature class that marks the space classification (hallway, stair, office, etc [sp_type])… Since we do not want to mark public areas as vacant the query checks any vacant values against the space type to get a list of possible errors…
Another type of MSAccess query we run would be to check personnel recorded for that building [sp_person] in one feature class against a matching field [sp_type] from the other feature class where both features contain matching room ID’s [sp_ID]…
Rather than exporting the query results to excel from MSAccessand hand checking/editing the entries in ArcMap then re running the queries to check for completion, I would like to do any of the fallowing in order of preference with the last being the most preferred but the most complicated:
1.Have the queries set up in MsAccess viewable in ArcMap.
2.Create, run and view the same queries in ArcMap rather than using MsAccess.
3.Same as number two however instead of an unlinked table I would get a layer with attributes that I can edit directly and those changes will propagate to the original feature class data.
4.Same as three but once features are edited they will be removed from the query once the query parameters are no longer valid for that row.
Currently to QAQC our data we use MsAccess queries to cross check data both within a feature class table and across feature classes that have common ID’s…
This is building space data, so things we check are a field that marks the space vacant [sp_vacant ] and another field within the same feature class that marks the space classification (hallway, stair, office, etc [sp_type])… Since we do not want to mark public areas as vacant the query checks any vacant values against the space type to get a list of possible errors…
Another type of MSAccess query we run would be to check personnel recorded for that building [sp_person] in one feature class against a matching field [sp_type] from the other feature class where both features contain matching room ID’s [sp_ID]…
Rather than exporting the query results to excel from MSAccessand hand checking/editing the entries in ArcMap then re running the queries to check for completion, I would like to do any of the fallowing in order of preference with the last being the most preferred but the most complicated:
1.Have the queries set up in MsAccess viewable in ArcMap.
2.Create, run and view the same queries in ArcMap rather than using MsAccess.
3.Same as number two however instead of an unlinked table I would get a layer with attributes that I can edit directly and those changes will propagate to the original feature class data.
4.Same as three but once features are edited they will be removed from the query once the query parameters are no longer valid for that row.