AGS 3.1 RTA 1.1 Import

Jesse Greenwald — Mon, 07 Aug 2023 21:35:11 GMT

Current Revision posted to OpenGround Wiki by Jesse Greenwald on 8/7/2023 9:35:11 PM

The latest version of the standard Australia configuration pack includes an import mapping file that can be used to import AGS 3.1 RTA 1.1 data into OpenGround. It is named “Default (AGS 3.1 RTA)” and can be selected within the import wizard under Data>Import Data.

Users with previous versions of the standard Australia configuration pack will have to import the mapping file into their existing configuration pack as an AGS 3.1 mapping following these directions. Please file a Service Request if you would like a copy of the AGS 3.1 RTA 1.1 import mapping file.

Please also see our Australia Example gINT Import Mapping File.

Known issues and additional information:

AGS 3.1 RTA 1.1 is an older data transfer format. Certain data structures and conventions have been updated within more recent formats (such as AGS 4.1 AU), so some data may not be fully supported for import into OpenGround, or may be manipulated in some fashion to enable import. Known issues are listed below. Please also see the Professional Common Issues articles which includes some general AGS import issues.

The STCI group is not supported for import into OpenGround and will cause errors if included in an AGS 3.1 RTA data file. The STCI group must be deleted from the AGS data file before importing into OpenGround. Any entries in the DICT group for the STCI Group must also be deleted from the AGS data file.

Note: Inclusion of the STCI group in an AGS data file may result in a number of seemingly unrelated error messages during import. Please delete the STCI group before troubleshooting further as that may resolve other error messages.

Issues with Date/Time and Duration formats are a common cause of import errors. You can try adding “hhmm” to the AGS UNIT group, which will often resolve some common issues.

If that does not resolve it, you may need to update and clean the Date/Time values within the AGS data file, so they are in the proper format. Or, if the Date/Time data is not critical, you can consider modifying the XML mapping file to remove the import mapping for that heading.

Certain groups and headings from AGS 3.1 RTA 1.1 are not mapped for import into OpenGround. This is often because the groups/headings have been deprecated or re-structured in more recent data formats and are not compatible with the standard Australia configuration pack data model. Known instances of this are listed below:

Groups not imported:

CLSS (Data from SAMP and child lab data groups is imported, but import of CLSS data is not currently supported.)
?STCI (See Item 1 above.)
?TRIR

Headings not imported:

The XXXX_PRBY, XXXX_PRDT, XXXX_CKBY, XXXX_CKDT headings in lab and in situ testing groups.
Other headings:

Group	Heading
CNMT	?CNMT_ULIM
CNMT	?CNMT_TTBY
CORE	?CORE_RATE
DETL	?DETL_LEG
DISC	?DISC_RGHC
DPRB	DPRB_DEL
DPRI	?DPRI_INC
GRAG	?GRAG_LSPT
GRAG	?GRAG_TYHY
HOLE	HOLE_BACD
HOLE	?HOLE_PHOT
HOLE	?HOLE_DBCB
ICCT	?ICCT_PREP
IINF	?IINF_SECS
IINF	?GEOL_STAT
IPRM	IPRM_STG
IPRM	IPRM_TYPE
IPRM	IPRM_SWAL
IPRM	?IPRM_IPRS
IPRS	?IPRM_STG
IPRS	?IPRS_PRES
IPRS	?IPRS_VOL
IPRS	?IPRS_DUR
IPRS	?IPRS_IPRS
LHIF	?LHIF_STAT
LLIN	?LLIN_HIST
LLPL	?LLPL_HIST
LMOC	?LMOC_FLCO
LPDN	?LPDN_PDF
LPDN	?LPDN_PDC
LPDN	?LPDN_PDS
LPDN	?LPDN_WA
PMTD	?PMTD_TPC1
PMTD	?PMTD_TPC2
PMTD	?PMTD_TPC3
PTIM	?PTIM_SFTM
RCKS	?RCKS_CONF
ROCK	FILE_FSET
RPLT	?RPLT_P
RPLT	?RPLT_PLSS
STCG	?STCG_MILE
STCT	?STCT_SLP
STCT	?STCT_DPPR
STCT	?STCT_CRN
STCT	?STCT_SCN1
STCT	?STCT_SCD1
STCT	?STCT_SCN2
STCT	?STCT_SCD2
STCT	?STCT_DECD
STDG	?STDG_RCMP
TRIG	?TRIG_TEXC
TRIG	?TRIG_MOD
TRIG	?TRIG_19Ø
TRIG	?TRIG_375
TRIG	?TRIG_PNC
TRIG	?TRIG_PS1
TRIG	?TRIG_PS3
TRIX	?TRIX_MODR
TRIX	?TRIX_LMR
TRIX	?TRIX_LDR
TRIX	?TRIX_TCMP
WETH	?WETH_CONF

Note: Not all AGS headings are imported 1:1 into OpenGround headings. For example, in some cases, multiple AGS headings may be concatenated together into a single OpenGround heading. In other cases, data from a single AGS group may be split into multiple OpenGround groups, or data from multiple OpenGround groups may be merged into a single OpenGround group.

The Type (Soil or Rock) for Field Geological Description layers is determined by whether data is included in the GORA/B or GOSA/B groups. If there are layers in the AGS data file that are only populated in the GEOL group and don’t have data populated for that layer in the GOR/GOS groups, then the Type will not be populated for that layer. If this causes problems for your project, you can use the Bulk Update tool to populate the Type after performing the initial data import. (For example, filter the Legend Code headings down to soil or rock materials, and then Bulk Updating to ‘Y’ (Rock) or ‘N’ (Soil) as appropriate.
In AGS 3.1 RTA 1.1 and in AGS 4.1 (UK), the Geology Code headings are included in the GEOL group (GEOL_GEOL & GEOL_GEO2). In AGS 4.1 AU, GEOL_GEOL & GEOL_GEO2 have been deprecated and replaced by separate GEO1 & GEO2 groups. Accordingly, the standard Australia configuration pack contains both headings for the Geology Codes in the Field Geological Descriptions group (corresponding to GEOL_GEOL & GEOL_GEO2), as well as separate ‘Geology Codes 1’ & ‘Geology Codes 2’ groups that correspond to the GEO1 & GEO2 groups. Geology Codes will be imported into both the Field Geologic Descriptions group, as well as the separate Geology Code groups. Depending on your workflows and requirements, you may want to modify the import mapping file to import into just one location.
The GORA/B and GOSA/B groups each contain the “XXXX_ODR” and “XXXX_STN” headings to describe odour and staining. In more recent Australian AGS data formats, a single heading is included in the GEOL group to describe odour and staining for the entire layer. The standard OpenGround data structure follows the more recent convention and uses a single field per layer in the Field Geological Descriptions Accordingly, if odour/staining data is included within multiple GOR/GOS groups for a single layer, there will be a clash and data from only one of the groups will be imported into OpenGround. The import mapping is set up so data from GORA/GOSA will overwrite data from GORB/GOSB. There may be other occurrences where similar clashes can occur.
HOLE_LGDT is imported into OpenGround’s Depth Related Exploratory Hole Information group. In some cases, HOLE_LGDT may fail to import.
In AGS 4.1, the IPRG and IPRT groups for In Situ Permeability data were deprecated and replaced by the FGHG, FGHI, FGHS & FGHT groups for Field Geohydraulic Testing. The OpenGround data model contains legacy In Situ Permeabiity groups for backwards compatibility to import IPRG and IPRT data, as well as new groups for Field Geohydraulic Testing. AGS 3.1 RTA 1.1 includes the IPRM & IPRS groups for In Situ Permeablity. Data from the IPRM & IPRS groups is mapped to import into OpenGround’s Field Geohydraulic Testing groups where possible.
The CDIA group is imported into the Casing Diameter by Depth group in OpenGround. Casing Diameter by Depth has the key fields Location ID, Depth Base, and Diameter. In OpenGround, Diameter must be a numeric value. In AGS 3.1 RTA, Diameter (CDIA_HOLE) can be text or numeric. Numeric CDIA_HOLE values will be imported into the Diameter heading in OpenGround. Text values (like ‘HW’ or ‘PW’) will be imported into the non-key Casing Code Accordingly, if you have 2 CDIA records with the same CDIA_CDEP (Depth Base) value and a text CDIA_HOLE value, there will be no Diameter key to uniquely distinguish the 2 Casing records, and you will get a duplicate key error during import. To help limit this, the import mapping for CDIA includes logic to assign a numeric Diameter value for common casing types. If you still encounter duplicate key issues, you may need to modify the data in the AGS data file to get it to import.

AGS 3.1 RTA 1.1 ABBR codes have only been populated to OpenGround Picklists for certain headings that are commonly used for reporting and other typical workflows, such as HOLE_TYPE or GEOL_LEG. Picklist Sets have been configured to filter AGS 3.1 RTA values vs. AGS 4.1 AU values for these Picklists. Where codes are used in the AGS data file that are not in the Picklists, the data will be added to the project-level picklist during import. You may choose to add additional values to the configuration pack Picklists if required for your workflows.
If you have a Picklist Set applied for your project and you try to import values into a Picklist field that are not allocated in that Picklist Set, you will get errors in the Preparation step similar to below.

The options are to do one of the following:

a. Create a new project that does not use a Picklist Set (you can’t remove a Picklist Set after the project has been created).

b. Add the values to the Picklist Set.

c. Modify the values in the AGS file to their corresponding values in your Picklist Set.

Export from the standard Australia configuration pack to AGS 3.1 RTA 1.1 is not currently supported. This mapping file only supports the import of AGS 3.1 RTA 1.1 data into OpenGround.

AGS 3.1 RTA 1.1 Import

Jesse Greenwald — Fri, 05 May 2023 18:45:42 GMT

Revision 2 posted to OpenGround Wiki by Jesse Greenwald on 5/5/2023 6:45:42 PM

Known issues and additional information:

The STCI group is not supported for import into OpenGround and will cause errors if included in an AGS 3.1 RTA data file. The STCI group must be deleted from the AGS data file before importing into OpenGround. Any entries in the DICT group for the STCI Group must also be deleted from the AGS data file.

Issues with Date/Time and Duration formats are a common cause of import errors. You can try adding “hhmm” to the AGS UNIT group, which will often resolve some common issues.

Certain groups and headings from AGS 3.1 RTA 1.1 are not mapped for import into OpenGround. This is often because the groups/headings have been deprecated or re-structured in more recent data formats and are not compatible with the standard Australia configuration pack data model. Known instances of this are listed below:

Groups not imported:

CLSS (Data from SAMP and child lab data groups is imported, but import of CLSS data is not currently supported.)
?STCI (See Item 1 above.)
?TRIR

Headings not imported:

The XXXX_PRBY, XXXX_PRDT, XXXX_CKBY, XXXX_CKDT headings in lab and in situ testing groups.
Other headings:

Group	Heading
CNMT	?CNMT_ULIM
CNMT	?CNMT_TTBY
CORE	?CORE_RATE
DETL	?DETL_LEG
DISC	?DISC_RGHC
DPRB	DPRB_DEL
DPRI	?DPRI_INC
GRAG	?GRAG_LSPT
GRAG	?GRAG_TYHY
HOLE	HOLE_BACD
HOLE	?HOLE_PHOT
HOLE	?HOLE_DBCB
ICCT	?ICCT_PREP
IINF	?IINF_SECS
IINF	?GEOL_STAT
IPRM	IPRM_STG
IPRM	IPRM_TYPE
IPRM	IPRM_SWAL
IPRM	?IPRM_IPRS
IPRS	?IPRM_STG
IPRS	?IPRS_PRES
IPRS	?IPRS_VOL
IPRS	?IPRS_DUR
IPRS	?IPRS_IPRS
LHIF	?LHIF_STAT
LLIN	?LLIN_HIST
LLPL	?LLPL_HIST
LMOC	?LMOC_FLCO
LPDN	?LPDN_PDF
LPDN	?LPDN_PDC
LPDN	?LPDN_PDS
LPDN	?LPDN_WA
PMTD	?PMTD_TPC1
PMTD	?PMTD_TPC2
PMTD	?PMTD_TPC3
PTIM	?PTIM_SFTM
RCKS	?RCKS_CONF
ROCK	FILE_FSET
RPLT	?RPLT_P
RPLT	?RPLT_PLSS
STCG	?STCG_MILE
STCT	?STCT_SLP
STCT	?STCT_DPPR
STCT	?STCT_CRN
STCT	?STCT_SCN1
STCT	?STCT_SCD1
STCT	?STCT_SCN2
STCT	?STCT_SCD2
STCT	?STCT_DECD
STDG	?STDG_RCMP
TRIG	?TRIG_TEXC
TRIG	?TRIG_MOD
TRIG	?TRIG_19Ø
TRIG	?TRIG_375
TRIG	?TRIG_PNC
TRIG	?TRIG_PS1
TRIG	?TRIG_PS3
TRIX	?TRIX_MODR
TRIX	?TRIX_LMR
TRIX	?TRIX_LDR
TRIX	?TRIX_TCMP
WETH	?WETH_CONF

The Type (Soil or Rock) for Field Geological Description layers is determined by whether data is included in the GORA/B or GOSA/B groups. If there are layers in the AGS data file that are only populated in the GEOL group and don’t have data populated for that layer in the GOR/GOS groups, then the Type will not be populated for that layer. If this causes problems for your project, you can use the Bulk Update tool to populate the Type after performing the initial data import. (For example, filter the Legend Code headings down to soil or rock materials, and then Bulk Updating to ‘Y’ (Rock) or ‘N’ (Soil) as appropriate.
In AGS 3.1 RTA 1.1 and in AGS 4.1 (UK), the Geology Code headings are included in the GEOL group (GEOL_GEOL & GEOL_GEO2). In AGS 4.1 AU, GEOL_GEOL & GEOL_GEO2 have been deprecated and replaced by separate GEO1 & GEO2 groups. Accordingly, the standard Australia configuration pack contains both headings for the Geology Codes in the Field Geological Descriptions group (corresponding to GEOL_GEOL & GEOL_GEO2), as well as separate ‘Geology Codes 1’ & ‘Geology Codes 2’ groups that correspond to the GEO1 & GEO2 groups. Geology Codes will be imported into both the Field Geologic Descriptions group, as well as the separate Geology Code groups. Depending on your workflows and requirements, you may want to modify the import mapping file to import into just one location.
The GORA/B and GOSA/B groups each contain the “XXXX_ODR” and “XXXX_STN” headings to describe odour and staining. In more recent Australian AGS data formats, a single heading is included in the GEOL group to describe odour and staining for the entire layer. The standard OpenGround data structure follows the more recent convention and uses a single field per layer in the Field Geological Descriptions Accordingly, if odour/staining data is included within multiple GOR/GOS groups for a single layer, there will be a clash and data from only one of the groups will be imported into OpenGround. The import mapping is set up so data from GORA/GOSA will overwrite data from GORB/GOSB. There may be other occurrences where similar clashes can occur.
HOLE_LGDT is imported into OpenGround’s Depth Related Exploratory Hole Information group. In some cases, HOLE_LGDT may fail to import.
In AGS 4.1, the IPRG and IPRT groups for In Situ Permeability data were deprecated and replaced by the FGHG, FGHI, FGHS & FGHT groups for Field Geohydraulic Testing. The OpenGround data model contains legacy In Situ Permeabiity groups for backwards compatibility to import IPRG and IPRT data, as well as new groups for Field Geohydraulic Testing. AGS 3.1 RTA 1.1 includes the IPRM & IPRS groups for In Situ Permeablity. Data from the IPRM & IPRS groups is mapped to import into OpenGround’s Field Geohydraulic Testing groups where possible.
The CDIA group is imported into the Casing Diameter by Depth group in OpenGround. Casing Diameter by Depth has the key fields Location ID, Depth Base, and Diameter. In OpenGround, Diameter must be a numeric value. In AGS 3.1 RTA, Diameter (CDIA_HOLE) can be text or numeric. Numeric CDIA_HOLE values will be imported into the Diameter heading in OpenGround. Text values (like ‘HW’ or ‘PW’) will be imported into the non-key Casing Code Accordingly, if you have 2 CDIA records with the same CDIA_CDEP (Depth Base) value and a text CDIA_HOLE value, there will be no Diameter key to uniquely distinguish the 2 Casing records, and you will get a duplicate key error during import. To help limit this, the import mapping for CDIA includes logic to assign a numeric Diameter value for common casing types. If you still encounter duplicate key issues, you may need to modify the data in the AGS data file to get it to import.

AGS 3.1 RTA 1.1 ABBR codes have only been populated to OpenGround Picklists for certain headings that are commonly used for reporting and other typical workflows, such as HOLE_TYPE or GEOL_LEG. Picklist Sets have been configured to filter AGS 3.1 RTA values vs. AGS 4.1 AU values for these Picklists. Where codes are used in the AGS data file that are not in the Picklists, the data will be added to the project-level picklist during import. You may choose to add additional values to the configuration pack Picklists if required for your workflows.
If you have a Picklist Set applied for your project and you try to import values into a Picklist field that are not allocated in that Picklist Set, you will get errors in the Preparation step similar to below.

The options are to do one of the following:

a. Create a new project that does not use a Picklist Set (you can’t remove a Picklist Set after the project has been created).

b. Add the values to the Picklist Set.

c. Modify the values in the AGS file to their corresponding values in your Picklist Set.

Export from the standard Australia configuration pack to AGS 3.1 RTA 1.1 is not currently supported. This mapping file only supports the import of AGS 3.1 RTA 1.1 data into OpenGround.

AGS 3.1 RTA 1.1 Import

Jesse Greenwald — Fri, 05 May 2023 18:34:14 GMT

Revision 1 posted to OpenGround Wiki by Jesse Greenwald on 5/5/2023 6:34:14 PM

Known issues and additional information:

The STCI group is not supported for import into OpenGround and will cause errors if included in an AGS 3.1 RTA data file. The STCI group must be deleted from the AGS data file before importing into OpenGround. Any entries in the DICT group for the STCI Group must also be deleted from the AGS data file.

Issues with Date/Time and Duration formats are a common cause of import errors. You can try adding “hhmm” to the AGS UNIT group, which will often resolve some common issues.

Certain groups and headings from AGS 3.1 RTA 1.1 are not mapped for import into OpenGround. This is often because the groups/headings have been deprecated or re-structured in more recent data formats and are not compatible with the standard Australia configuration pack data model. Known instances of this are listed below:

Groups not imported:

CLSS (Data from SAMP and child lab data groups is imported, but import of CLSS data is not currently supported.)
?STCI (See Item 1 above.)
?TRIR

Headings not imported:

The XXXX_PRBY, XXXX_PRDT, XXXX_CKBY, XXXX_CKDT headings in lab and in situ testing groups.
Other headings:

Group	Heading
CNMT	?CNMT_ULIM
CNMT	?CNMT_TTBY
CORE	?CORE_RATE
DETL	?DETL_LEG
DISC	?DISC_RGHC
DPRB	DPRB_DEL
DPRI	?DPRI_INC
GRAG	?GRAG_LSPT
GRAG	?GRAG_TYHY
HOLE	HOLE_BACD
HOLE	?HOLE_PHOT
HOLE	?HOLE_DBCB
ICCT	?ICCT_PREP
IINF	?IINF_SECS
IINF	?GEOL_STAT
IPRM	IPRM_STG
IPRM	IPRM_TYPE
IPRM	IPRM_SWAL
IPRM	?IPRM_IPRS
IPRS	?IPRM_STG
IPRS	?IPRS_PRES
IPRS	?IPRS_VOL
IPRS	?IPRS_DUR
IPRS	?IPRS_IPRS
LHIF	?LHIF_STAT
LLIN	?LLIN_HIST
LLPL	?LLPL_HIST
LMOC	?LMOC_FLCO
LPDN	?LPDN_PDF
LPDN	?LPDN_PDC
LPDN	?LPDN_PDS
LPDN	?LPDN_WA
PMTD	?PMTD_TPC1
PMTD	?PMTD_TPC2
PMTD	?PMTD_TPC3
PTIM	?PTIM_SFTM
RCKS	?RCKS_CONF
ROCK	FILE_FSET
RPLT	?RPLT_P
RPLT	?RPLT_PLSS
STCG	?STCG_MILE
STCT	?STCT_SLP
STCT	?STCT_DPPR
STCT	?STCT_CRN
STCT	?STCT_SCN1
STCT	?STCT_SCD1
STCT	?STCT_SCN2
STCT	?STCT_SCD2
STCT	?STCT_DECD
STDG	?STDG_RCMP
TRIG	?TRIG_TEXC
TRIG	?TRIG_MOD
TRIG	?TRIG_19Ø
TRIG	?TRIG_375
TRIG	?TRIG_PNC
TRIG	?TRIG_PS1
TRIG	?TRIG_PS3
TRIX	?TRIX_MODR
TRIX	?TRIX_LMR
TRIX	?TRIX_LDR
TRIX	?TRIX_TCMP
WETH	?WETH_CONF

The Type (Soil or Rock) for Field Geological Description layers is determined by whether data is included in the GORA/B or GOSA/B groups. If there are layers in the AGS data file that are only populated in the GEOL group and don’t have data populated for that layer in the GOR/GOS groups, then the Type will not be populated for that layer. If this causes problems for your project, you can use the Bulk Update tool to populate the Type after performing the initial data import. (For example, filter the Legend Code headings down to soil or rock materials, and then Bulk Updating to ‘Y’ (Rock) or ‘N’ (Soil) as appropriate.
In AGS 3.1 RTA 1.1 and in AGS 4.1 (UK), the Geology Code headings are included in the GEOL group (GEOL_GEOL & GEOL_GEO2). In AGS 4.1 AU, GEOL_GEOL & GEOL_GEO2 have been deprecated and replaced by separate GEO1 & GEO2 groups. Accordingly, the standard Australia configuration pack contains both headings for the Geology Codes in the Field Geological Descriptions group (corresponding to GEOL_GEOL & GEOL_GEO2), as well as separate ‘Geology Codes 1’ & ‘Geology Codes 2’ groups that correspond to the GEO1 & GEO2 groups. Geology Codes will be imported into both the Field Geologic Descriptions group, as well as the separate Geology Code groups. Depending on your workflows and requirements, you may want to modify the import mapping file to import into just one location.
The GORA/B and GOSA/B groups each contain the “XXXX_ODR” and “XXXX_STN” headings to describe odour and staining. In more recent Australian AGS data formats, a single heading is included in the GEOL group to describe odour and staining for the entire layer. The standard OpenGround data structure follows the more recent convention and uses a single field per layer in the Field Geological Descriptions Accordingly, if odour/staining data is included within multiple GOR/GOS groups for a single layer, there will be a clash and data from only one of the groups will be imported into OpenGround. The import mapping is set up so data from GORA/GOSA will overwrite data from GORB/GOSB. There may be other occurrences where similar clashes can occur.
HOLE_LGDT is imported into OpenGround’s Depth Related Exploratory Hole Information In some cases, HOLE_LGDT may fail to import.
In AGS 4.1, the IPRG and IPRT groups for In Situ Permeability data were deprecated and replaced by the FGHG, FGHI, FGHS & FGHT groups for Field Geohydraulic Testing. The OpenGround data model contains legacy In Situ Permeabiity groups for backwards compatibility to import IPRG and IPRT data, as well as new groups for Field Geohydraulic Testing. AGS 3.1 RTA 1.1 includes the IPRM & IPRS groups for In Situ Permeablity. Data from the IPRM & IPRS groups is mapped to import into OpenGround’s Field Geohydraulic Testing groups where possible.
AGS 3.1 RTA 1.1 ABBR codes have only been populated to OpenGround Picklists for certain headings that are commonly used for reporting and other typical workflows, such as HOLE_TYPE or GEOL_LEG. Picklist Sets have been configured to filter AGS 3.1 RTA values vs. AGS 4.1 AU values for these Picklists. Where codes are used in the AGS data file that are not in the Picklists, the data will be added to the project-level picklist during import. You may choose to add additional values to the configuration pack Picklists if required for your workflows.
The CDIA group is imported into the Casing Diameter by Depth group in OpenGround. Casing Diameter by Depth has the key fields Location ID, Depth Base, and Diameter. In OpenGround, Diameter must be a numeric value. In AGS 3.1 RTA, Diameter (CDIA_HOLE) can be text or numeric. Numeric CDIA_HOLE values will be imported into the Diameter heading in OpenGround. Text values (like ‘HW’ or ‘PW’) will be imported into the non-key Casing Code Accordingly, if you have 2 CDIA records with the same CDIA_CDEP (Depth Base) value and a text CDIA_HOLE value, there will be no Diameter key to uniquely distinguish the 2 Casing records, and you will get a duplicate key error during import. To help limit this, the import mapping for CDIA includes logic to assign a numeric Diameter value for common casing types. If you still encounter duplicate key issues, you may need to modify the data in the AGS data file to get it to import.

If you have a Picklist Set applied for your project and you try to import values into a Picklist field that are not allocated in that Picklist Set, you will get errors in the Preparation step similar to below.

The options are to do one of the following:

a. Create a new project that does not use a Picklist Set (you can’t remove a Picklist Set after the project has been created).

b. Add the values to the Picklist Set.

c. Modify the values in the AGS file to their corresponding values in your Picklist Set.

Export from the standard Australia configuration pack to AGS 3.1 RTA 1.1 is not currently supported. This mapping file only supports the import of AGS 3.1 RTA 1.1 data into OpenGround.