GeoPrism Registry Documentation
  • Versions
    • Version 1.0.0
      • 1. Introduction
      • 2. Authors
      • 3. Deployment and setup
        • 3.1. License
        • 3.2. Creating a new installation
          • 3.2.1 System Architecture
          • 3.2.2. Hardware requirements
          • 3.2.3. SSL
          • 3.2.4. Installation, configuration and update
        • 3.3. Organization management
          • 3.3.1. Create an organization
          • 3.3.2. Invite a user to serve as the Registry Administrator for an organization
        • 3.4. Localization
          • 3.4.1. Install a new locale
          • 3.4.2. Export the default localization spreadsheet
          • 3.4.3. Add or edit a locale in the exported localization spreadsheet
          • 3.4.4. Import a new locale from the localization spreadsheet
          • 3.4.5. Switch locale
          • 3.4.6. Uninstall a locale
        • 3.5. System email management
        • 3.6. Branding (Logo)
        • 3.7. FHIR custom implementation
          • 3.7.1. Maven project setup
          • 3.7.2. Create a custom implementation for exporting data to FHIR
          • 3.7.3. Create a custom implementation for importing data from FHIR to GeoPrism Registry
          • 3.7.4. Register the implementations with the Java Services architecture
          • 3.7.5. Deploy implementation to server
        • 3.8. Configuration-based type setup
          • 3.8.1. Import type definitions
          • 3.8.2. Configuration-based type setup
          • 3.8.3. Hierarchy type definitions
          • 3.8.4. Directed acyclic graph type definitions
          • 3.8.5. Undirect graph type definitions
        • 3.9. DHIS2 OAuth integration
          • 3.9.1. Configuring DHIS2
        • 3.10. Database Migrations
      • 4. External system integration
        • 4.1. Available APIs
        • 4.2. Register and synchronize an external system
          • 4.2.1. DHIS2
          • 4.2.2. Reveal
          • 4.2.3. FHIR
      • 5. GeoPrism Registry key components
        • 5.1. Content
          • 5.1.1. Geographic features and geographic objects
          • 5.1.2. Geographic object types and groups
          • 5.1.3. Data elements and classification tables
          • 5.1.4. Hierarchies
          • 5.1.5. Lists
          • 5.1.6. Geospatial data
          • 5.1.7. Data quality
        • 5.2. Content-related capacities of GeoPrism Registry
          • 5.2.1. Changes over time
          • 5.2.2. Unique identifier
          • 5.2.3. Master vs. non-master
          • 5.2.4. Accessibility
          • 5.2.5. Documentation (metadata)
          • 5.2.6. Languages and character encoding
        • 5.3. User roles and rights
          • 5.3.1. Roles
          • 5.3.2. Rights by role
        • 5.4. User interface
          • 5.4.1. Home page
          • 5.4.2. Modules
          • 5.4.3. Settings
      • 6. GeoPrism Registry tutorial
        • 6.1. GeoPrism Registry sandbox
          • 6.1.1. Purpose
          • 6.1.2. Organizations and roles
          • 6.1.3. Content
          • 6.1.4. Access
        • 6.2. Logging in
          • 6.2.1. Local GeoPrism Registry credentials
          • 6.2.2. DHIS2 credentials
        • 6.3. User management
          • 6.3.1. Adding users
          • 6.3.2. Inviting users
          • 6.3.3. Resetting a forgotten password (local GeoPrism Registry credentials)
          • 6.3.4. Changing a password
          • 6.3.5. Enabling OAuth integration
        • 6.4. Content setup
          • 6.4.1. Groups
            • 6.4.1.1. Adding a group
            • 6.4.1.2. Adding a Geo-Object Type to a group
            • 6.4.1.3. Managing the attributes for a Geo-Object Type in a group
            • 6.4.1.4. Editing the metadata of a group
            • 6.4.1.5. Delete a group
          • 6.4.2. Geo-Object Types (outside a group)
            • 6.4.2.1. Adding a Geo-Object Type
            • 6.4.2.2. Managing the attributes of a Geo-Object Type
            • 6.4.2.3. Editing the metadata of a Geo-Object Type
            • 6.4.2.4. Deleting a Geo-Object Type
          • 6.4.3. Hierarchies
            • 6.4.3.1. Adding a hierarchy
            • 6.4.3.2. Managing the content of the hierarchy
            • 6.4.3.3. Editing the metadata of a hierarchy
            • 6.4.3.4. Deleting a hierarchy
        • 6.5. Content management
          • 6.5.1. Lists and spatial data
            • 6.5.1.1. Importing data
            • 6.5.1.2. Creating a set
            • 6.5.1.3. Managing versions of a set
            • 6.5.1.4. Exploring lists and spatial data
            • 6.5.1.5. Editing lists and spatial data
            • 6.5.1.6. Curating lists and spatial data
            • 6.5.1.7. Exporting lists and spatial data
          • 6.5.2. Change requests
            • 6.5.2.1. Submitting a change request
            • 6.5.2.2. Reviewing a change request
          • 6.5.3. Historical events
            • 6.5.3.1. Creating a historical event
            • 6.5.3.2. Exploring historical events
            • 6.5.3.3. Editing a historical event
            • 6.5.3.4. Exporting historical events
    • Version 1.4.x
      • 1. Introduction
      • 2. Authors
      • 3. Deployment and setup
        • 3.1. License
        • 3.2. Creating a new installation
          • 3.2.1 System Architecture
          • 3.2.2. Hardware requirements
          • 3.2.3. SSL
          • 3.2.4. Installation, configuration and update
        • 3.3. Organization management
          • 3.3.1. Create an organization
          • 3.3.2. Invite a user to serve as the Registry Administrator for an organization
        • 3.4. Localization
          • 3.4.1. Install a new locale
          • 3.4.2. Export the default localization spreadsheet
          • 3.4.3. Add or edit a locale in the exported localization spreadsheet
          • 3.4.4. Import a new locale from the localization spreadsheet
          • 3.4.5. Switch locale
          • 3.4.6. Uninstall a locale
        • 3.5. System email management
        • 3.6. Branding (Logo)
        • 3.7. FHIR custom implementation
          • 3.7.1. Maven project setup
          • 3.7.2. Create a custom implementation for exporting data to FHIR
          • 3.7.3. Create a custom implementation for importing data from FHIR to GeoPrism Registry
          • 3.7.4. Register the implementations with the Java Services architecture
          • 3.7.5. Deploy implementation to server
        • 3.8. Configuration-based type setup
          • 3.8.1. Import type definitions
          • 3.8.2. Configuration-based type setup
          • 3.8.3. Hierarchy type definitions
          • 3.8.4. Directed acyclic graph type definitions
          • 3.8.5. Undirect graph type definitions
        • 3.9. DHIS2 OAuth integration
          • 3.9.1. Configuring DHIS2
        • 3.10. Database Migrations
      • 4. External system integration
        • 4.1. Available APIs
        • 4.2. Register and synchronize an external system
          • 4.2.1. DHIS2
          • 4.2.2. Reveal
          • 4.2.3. FHIR
      • 5. GeoPrism Registry key components
        • 5.1. Content
          • 5.1.1. Geographic features and geographic objects
          • 5.1.2. Geographic object types and groups
          • 5.1.3. Data elements and classification tables
          • 5.1.4. Hierarchies
          • 5.1.5. Lists
          • 5.1.6. Geospatial data
          • 5.1.7. Data quality
        • 5.2. Content-related capacities of GeoPrism Registry
          • 5.2.1. Changes over time
          • 5.2.2. Unique identifier
          • 5.2.3. Master vs. non-master
          • 5.2.4. Accessibility
          • 5.2.5. Documentation (metadata)
          • 5.2.6. Languages and character encoding
        • 5.3. User roles and rights
          • 5.3.1. Roles
          • 5.3.2. Rights by role
        • 5.4. User interface
          • 5.4.1. Home page
          • 5.4.2. Modules
          • 5.4.3. Settings
      • 6. GeoPrism Registry tutorial
        • 6.1. GeoPrism Registry sandbox
          • 6.1.1. Purpose
          • 6.1.2. Organizations and roles
          • 6.1.3. Content
          • 6.1.4. Access
        • 6.2. Logging in
          • 6.2.1. Local GeoPrism Registry credentials
          • 6.2.2. DHIS2 credentials
        • 6.3. User management
          • 6.3.1. Adding users
          • 6.3.2. Inviting users
          • 6.3.3. Resetting a forgotten password (local GeoPrism Registry credentials)
          • 6.3.4. Changing a password
          • 6.3.5. Enabling OAuth integration
        • 6.4. Content setup
          • 6.4.1. Groups
            • 6.4.1.1. Adding a group
            • 6.4.1.2. Adding a Geo-Object Type to a group
            • 6.4.1.3. Managing the attributes for a Geo-Object Type in a group
            • 6.4.1.4. Editing the metadata of a group
            • 6.4.1.5. Delete a group
          • 6.4.2. Geo-Object Types (outside a group)
            • 6.4.2.1. Adding a Geo-Object Type
            • 6.4.2.2. Managing the attributes of a Geo-Object Type
            • 6.4.2.3. Editing the metadata of a Geo-Object Type
            • 6.4.2.4. Deleting a Geo-Object Type
          • 6.4.3. Hierarchies
            • 6.4.3.1. Adding a hierarchy
            • 6.4.3.2. Managing the content of the hierarchy
            • 6.4.3.3. Editing the metadata of a hierarchy
            • 6.4.3.4. Deleting a hierarchy
        • 6.5. Content management
          • 6.5.1. Lists and spatial data
            • 6.5.1.1. Importing data
            • 6.5.1.2. Creating a set
            • 6.5.1.3. Managing versions of a set
            • 6.5.1.4. Exploring lists and spatial data
            • 6.5.1.5. Editing lists and spatial data
            • 6.5.1.6. Curating lists and spatial data
            • 6.5.1.7. Exporting lists and spatial data
          • 6.5.2. Change requests
            • 6.5.2.1. Submitting a change request
            • 6.5.2.2. Reviewing a change request
          • 6.5.3. Historical events
            • 6.5.3.1. Creating a historical event
            • 6.5.3.2. Exploring historical events
            • 6.5.3.3. Editing a historical event
            • 6.5.3.4. Exporting historical events
    • ສະບັບ 1.4.x (ພາສາລາວ)
      • 1. ບົດນຳ
      • 2. ຜູ້ຂຽນ
      • 3. ການນໍາໃຊ້ ແລະ ການຕັ້ງຄ່າ
        • 3.1. ໃບອະນຸຍາດ
        • 3.2. ການສ້າງການຕິດຕັ້ງໃໝ່
          • 3.2.1. ລະບົບສະຖາປັດຕະຍະກໍາ
          • 3.2.2. ຂໍ້ກຳນົດດ້ານຮາດແວ
          • 3.2.3. SSL
          • 3.2.4. ການຕິດຕັ້ງ, ການກຳນົດຄ່າ ແລະ ການປັບປຸງ
        • 3.3. ການຈັດການອົງກອນ
          • 3.3.1. ການສ້າງອົງກອນ
          • 3.3.2. ເຊີນຜູ້ໃຊ້ໃຫ້ເຮັດໜ້າທີ່ເປັນຜູ້ບໍລິຫານການລົງທະບຽນ (Registry Administrator) ສຳລັບອົງກອນ
        • 3.4. ການກຳນົດທ້ອງຖິ່ນ
          • 3.4.1. ຕິດຕັ້ງພາສາທ້ອງຖິ່ນໃໝ່
          • 3.4.2. ການສົ່ງອອກຕາຕະລາງພາສາທ້ອງຖິ່ນເລີ່ມຕົ້ນ
          • 3.4.3. ການເພີ່ມ ຫຼື ການແກ້ໄຂພາສາໃນຕາຕະລາງພາສາທ້ອງຖິ່ນທີ່ສົ່ງອອກ
          • 3.4.4. ການນໍາເຂົ້າພາສາໃໝ່ຈາກຕາຕະລາງພາສາທ້ອງຖິ່ນ
          • 3.4.5. ການສະຫຼັບພາສາ
          • 3.4.6. ຖອນການຕິດຕັ້ງພາສາ
        • 3.5. ການຈັດການອີເມວຂອງລະບົບ
        • 3.6. ຍີ່ຫໍ້ (ໂລໂກ້)
        • 3.7. ການຕິດຕັ້ງ FHIR ແບບກຳນົດເອງ
          • 3.7.1. ການຕິດຕັ້ງໂຄງການ Maven
          • 3.7.2. ສ້າງການຕິດຕັ້ງແບບກຳນົດເອງສຳລັບການສົ່ງອອກຂໍ້ມູນໄປຍັງ FHIR
          • 3.7.3. ສ້າງການຕິດຕັ້ງແບບກໍານົດເອງສໍາລັບການນໍາເຂົ້າຂໍ້ມູນຈາກ FHIR ໄປຫາ GeoPrism Registry
          • 3.7.4. ການລົງທະບຽນການຕິດຕັ້ງສ້າງສະຖາປັດຕະຍະກໍາລະບົບ Java Services
          • 3.7.5. ການນຳໃຊ້ຕິດຕັ້ງເທິງລະບົບ
        • 3.8. ການຕັ້ງຄ່າ ຄ່າກຳນົດ (configuration-based type setup)
          • 3.8.1. ຄຳນິຍາມຂອງປະເພດການນຳເຂົ້າ
          • 3.8.2. ການກຳນົດຄ່າປະເພດໂດຍອີງໃສ່ການຕັ້ງຄ່າ (configuration-based type setup)
          • 3.8.3. ຄຳນິຍາມຂອງປະເພດ hierarchy
          • 3.8.4. ຄຳນິຍາມຂອງປະເພດກຣາຟ acyclic ທີ່ມີໂຕຊີ້ບອກ (directed acyclic graph)
          • 3.8.5. ຄຳນິຍາມຂອງປະເພດກຣາຟທີ່ບໍ່ມີທິດທາງ (undirected graph)
        • 3.9. ການເຊື່ອມກັນຂອງ DHIS2 OAuth (DHIS2 OAuth integration)
          • 3.9.1. ການກຳນົດຄ່າ DHIS2
        • 3.10. ການໂອນຍ້າຍຖານຂໍ້ມູນ (database migrations)
      • 4. ການເຊື່ອມໂຍງລະບົບພາຍນອກ
        • 4.1. APIs ທີ່ມີຢູ່
        • 4.2. ການລົງທະບຽນ ແລະ ການເຊື່ອມຕໍ່ລະບົບພາຍນອກ
          • 4.2.1. DHIS2
          • 4.2.2. Reveal
          • 4.2.3. FHIR
      • 5. ອົງປະກອບທີ່ສໍາຄັນ GeoPrism Registry
        • 5.1. ເນື້ອໃນ
          • 5.1.1. ລັກສະນະທາງພູມິສາດ ແລະ ວັດຖຸທາງພູມິສາດ
          • 5.1.2. ປະເພດວັດຖຸ ແລະ ກຸ່ມພູມິສາດ
          • 5.1.3. ອົງປະກອບຂໍ້ມູນ ແລະ ຕາຕະລາງການຈັດປະເພດ
          • 5.1.4. ລໍາດັບຊັ້ນ ຫຼື ໂຄງຮ່າງການຈັດຕັ້ງ
          • 5.1.5. ບັນຊີລາຍການ
          • 5.1.6. ຂໍ້ມູນທາງພູມິສາດ
          • 5.1.7. ຄຸນນະພາບຂໍ້ມູນ
        • 5.2. ຄວາມສາມາດທີ່ກ່ຽວຂ້ອງກັບເນື້ອຫາຂອງ GeoPrism Registry
          • 5.2.1. ການປ່ຽນແປງຕາມເວລາ
          • 5.2.2. ຕົວລະບຸຕົວຕົນທີ່ເປັນເອກະລັກ
          • 5.2.3. ຕົ້ນສະບັບ ແລະ ບໍ່ແມ່ນຕົ້ນສະບັບ
          • 5.2.4. ການເຂົ້າເຖິງ
          • 5.2.5. ເອກະສານປະກອບ (metadata)
          • 5.2.6. ພາສາ ແລະ ການເຂົ້າລະຫັດຕົວອັກສອນ
        • 5.3. ບົດບາດ ແລະ ສິດຂອງຜູ້ໃຊ້
          • 5.3.1. ບົດບາດ
          • 5.3.2. ສິດທິຕາມພາລະບົດບາດ
        • 5.4. ການໂຕ້ຕອບຜູ້ໃຊ້
          • 5.4.1. ໜ້າຫຼັກ
          • 5.4.2. ໂມດູນ
          • 5.4.3. ການຕັ້ງຄ່າ
      • 6. ການສອນ GeoPrism Registry
        • 6.1. GeoPrism Registry sandbox
          • 6.1.1. ຈຸດປະສົງ
          • 6.1.2. ອົງກອນ ແລະ ພາລະບົດບາດ
          • 6.1.3. ເນື້ອໃນ
          • 6.1.4. ການເຂົ້າເຖິງ
        • 6.2. ການເຂົ້າສູ່ລະບົບ
          • 6.2.1. ຂໍ້ມູນຮັບຮອງ local GeoPrism Registry
          • 6.2.2. ຂໍ້ມູນຮັບຮອງ DHIS2
        • 6.3. ການຈັດການຜູ້ໃຊ້
          • 6.3.1. ການເພີ່ມຜູ້ໃຊ້
          • 6.3.2. ການເຊີນຜູ້ໃຊ້
          • 6.3.3. ການຕັ້ງຄ່າລະຫັດຜ່ານໃໝ່ຈາກການລືມລະຫັດ (ຂໍ້ມູນຮັບຮອງ local GeoPrism Registry)
          • 6.3.4. ການປ່ຽນລະຫັດຜ່ານ
          • 6.3.5. ເປີດໃຊ້ການເຊື່ອມໂຍງ OAuth
        • 6.4. ການຕັ້ງຄ່າເນື້ອຫາ
          • 6.4.1. ກຸ່ມ
            • 6.4.1.1. ການເພີ່ມກຸ່ມ
            • 6.4.1.2. ການເພີ່ມ Geo-Object Type ໃສ່ກຸ່ມ
            • 6.4.1.3. ການຈັດການຄຸນລັກສະນະສໍາລັບ Geo-Object Type ໃນກຸ່ມ
            • 6.4.1.4. ການແກ້ໄຂ metadata ຂອງກຸ່ມ
            • 6.4.1.5. ການລຶບກຸ່ມ
          • 6.4.2. Geo-Object Type (ນອກກຸ່ມ)
            • 6.4.2.1. ການເພີ່ມ Geo-Object Type
            • 6.4.2.2. ການຈັດການຄຸນລັກສະນະຂອງ Geo-Object Type
            • 6.4.2.3. ການແກ້ໄຂ metadata ຂອງ Geo-Object Type
            • 6.4.2.4. ການລຶບ Geo-Object Type
          • 6.4.3. Hierarchies
            • 6.4.3.1. ການເພີ່ມລຳດັບຊັ້ນ
            • 6.4.3.2. ການຈັດການເນື້ອໃນຂອງລໍາດັບຊັ້ນ
            • 6.4.3.3. ການແກ້ໄຂ metadata ຂອງລໍາດັບຊັ້ນ
            • 6.4.3.4. ການລຶບລຳດັບຊັ້ນ
        • 6.5. ການຈັດການເນື້ອຫາ
          • 6.5.1. ລາຍການ ແລະ ຂໍ້ມູນພື້ນທີ່
            • 6.5.1.1. ການນຳເຂົ້າຂໍ້ມູນ
            • 6.5.1.2. ການສ້າງຊຸດ
            • 6.5.1.3. ການຈັດການລຸ້ນຂອງຊຸດ
            • 6.5.1.4. ການຄົ້ນຫາລາຍການ ແລະ ຂໍ້ມູນພື້ນທີ່
            • 6.5.1.5. ແກ້ໄຂລາຍການ ແລະ ຂໍ້ມູນພື້ນທີ່
            • 6.5.1.6. ຈັດການລາຍການ ແລະ ຂໍ້ມູນພື້ນທີ່
            • 6.5.1.7. ການສົ່ງອອກລາຍການ ແລະ ຂໍ້ມູນພື້ນທີ່
          • 6.5.2. ການປ່ຽນແປງຄຳຮ້ອງຂໍ
            • 6.5.2.1. ການສົ່ງຄໍາຮ້ອງຂໍການປ່ຽນແປງ
            • 6.5.2.2. ການກວດສອບຄຳຮ້ອງຂໍການປ່ຽນແປງ
          • 6.5.3. ເຫດການທີ່ເກີດຂຶ້ນມາກ່ອນ (Historical events)
            • 6.5.3.1. ການສ້າງ historical event
            • 6.5.3.2. ການສຳຫຼວດ historical events
            • 6.5.3.3. ການແກ້ໄຂ historical events
            • 6.5.3.4. ການສົ່ງອອກ historical events
  • Fundamentals
    • Glossary of terms
  • API Documentation
  • Install from Docker Hub
Powered by GitBook
On this page
  • Importing a spreadsheet (list)
  • Importing a shapefile
Edit on GitHub
Export as PDF
  1. Versions
  2. Version 1.0.0
  3. 6. GeoPrism Registry tutorial
  4. 6.5. Content management
  5. 6.5.1. Lists and spatial data

6.5.1.1. Importing data

Previous6.5.1. Lists and spatial dataNext6.5.1.2. Creating a set

Last updated 2 years ago

Registry Administrators and Registry Maintainers can import the lists and spatial data of the Geo-Object Types under the curation mandate of their organization

To import Geo-Object data into GeoPrism Registry, we have to take into account the Geo-Object Types, attributes, and hierarchies that have been defined. The data to be imported needs to be formatted so the fields/columns can be mapped onto the attributes of the relevant Geo-Object Type, and where available, hierarchy information can be matched with the correct hierarchy.

Importing a spreadsheet (list)

Lists are imported in GeoPrism Registry under the form of a spreadsheet.

To be able to smoothly import a list to GeoPrism Registry, the following basic requirements must be followed:

  • The spreadsheet must be in XLSX format

  • The spreadsheet must contain the values for all the attributes that have been defined in the data dictionary as well as the parents for the hierarchies the Geo-Object Type is a part of

  • A header must exist on the first row that contains the unique label for each attribute

  • Each column must be set to the appropriate data type

  • The data should be in the first worksheet of the XLSX file; all other worksheets will be ignored by the system

  • There should be no formulas in the spreadsheet as these are not supported

  • Geographic coordinates included in the spreadsheet must be unprojected () and stored in separated columns (latitude and longitude)

If the spreadsheet has multiple tabs only the first tab will be used for the import

Importing a spreadsheet happens as follows:

  1. Go to the Import module either by clicking the module icon on the homepage or by clicking the hamburger menu () in the upper right corner and selecting Import.\

  2. If an external system has been registered in GeoPrism Registry (see ), a window will open providing the option for the import to take place from an external system or from your computer. Choose the option that applies.\

  3. Ensure the Import Spreadsheet tab is selected.\

  4. Fill out the following fields for the list you would like to import:\

    Field
    Description
    Required

    Hierarchy

    The hierarchy the Geo-Object Type for which you are importing a list belongs to. The dropdown list of hierarchies will depend on the hierarchies created for the organization you are a part of. If the Geo-Object type is part of several hierarchies then the data elements in the XLSX file containing this information will have to be imported separately for each hierarchy

    Required

    Geo-Object Type

    The Geo-Object Type for which you are importing content into GeoPrism Registry. The dropdown will contain the list of Geo-Object Types over which the user has the curation mandate and which are part of the hierarchy that has been selected

    Required

    Import Strategy

    The import strategy for the list being imported:

    • New and update: This will import the Geo-Objects and associated attributes in the spreadsheetthat are not yet in GeoPrism Registry as well as overwrite the attributes of the Geo-Objects from the list that are already in GeoPrism Registry.

    • New only: This will import only the Geo-Objects from the spreadsheet that are not yet in GeoPrism Registry. If the file contains Geo-Objects that were already in GeoPrism Registry (same unique identifier and/or label depending on the selected matching method) then the import will fail to avoid creating duplicates.

    • Update only: This will overwrite the attributes of the Geo-Objects from the spreadsheet that are already in GeoPrism Registry. If the imported file contains Geo-Objects that are not already in GeoPrism Registry then these will not be imported.

    Required

    Start Date

    The start of the date of validity of the Geo-Objects in the spreadsheet. All the Geo-Objects in the spreadsheet, whether new or for update, should have the same start date of validity.

    Required

    End Date

    The end of the date of validity of the Geo-Objects in the list. All the Geo-Objects in the spreadsheet, whether new or for update, should have the same end date of validity. If the Geo-Objects in the spreadsheet are still valid on the date it is being imported in GeoPrism Registry, click the Set as most current button.

    Required

    Import blank cell

    Selecting this option ensures that if there are empty cells in the list being imported, they are imported as empty attribute values (overwrite). This option gives more control to ensure that updates will either only update cells with values or to overwrite existing values with null values.

  5. Click the Choose file button and in the window that opens, browse to the location of the spreadsheet you would like to import. Select the file and click Open.\

  6. Click the Submit button in the Spreadsheet import window.

  7. The Attribute Matching window opens containing the attributes for the Geo-Object Type. The number of attributes that appears depends on the number of attributes created for the Geo-Object Type for which the spreadsheet is being imported. In the dropdown option for each field, choose the attribute from the list being imported that matches the created attribute of the Geo-Object Type. Click the Next button. Note: When the spreadsheet is formatted correctly and completely as mentioned at the start of this section, you should be able to match all of its attributes to the Geo-Object Type for which it is being imported. Otherwise, some of the attributes will be left blank.

  8. The Hierarchy Matching window opens listing the Geo-Object Types considered as parents in to the Geo-Object Type for which the spreadsheet is being imported. The number of parent Geo-Object Types that will be listed depends on the position of the imported Geo-Object Type data in the hierarchy. Fill out the following fields for each parent Geo-Object Type:\

    Field
    Description
    Required

    Source file parent column

    The attribute from the spreadsheet being imported that corresponds to the parent Geo-Object Type (unique identifier or name)

    Match Strategy

    The strategy by which the selected attribute will be matched:

    • Using the code, label, and synonyms

    • Using the code only (fastest)

    Note: Hierarchy matching is optional.

  9. Click Submit.

  10. The import will start processing. Click the Go to jobs button to view the progress.\

  11. This will direct you to the Scheduled Jobs module. If there is no problem with the imported spreadsheet, the page will look as below. You will see the imported spreadsheet as one of the completed jobs when you click on the View completed jobs button.\

  12. If there is any problem with the spreadsheet being imported, you will see this in the In progress section, with the part of the process with the problem highlighted in red. Click on the Resolve Problems button to see the details of the problem.\

  13. The Job Details page will provide the problem type, message, and row number details of the issue and give you options on how to solve each problem when you click the Resolve button. Note: Depending on the problem type, GeoPrism Registry may ask you to fix the problem in the spreadsheet itself and then re-import it.

  14. Depending on the problem type, there may also be cases when you may ignore the errors and proceed with the import. When this is the case, click the Ignore All Errors button.\

  15. A warning message will appear asking if you want to mark the import as completed. Click the Complete Import button. This will complete the import process.\

  16. You will see the imported spreadsheet when you click on the View completed jobs button.\

Importing a shapefile

Spatial data is imported into GeoPrism Registry through shapefiles.

To be able to smoothly import shapefiles into GeoPrism Registry, these basic requirements must be followed:

  • As a shapefile consists of multiple files that collectively make up a shapefile, these files must be compressed into a zipped (.zip) file before importing.

  • The shapefile must include data only for a single Geo-Object Type.

Shapefiles are imported as follows:

  1. Click on the Import Shapefile tab.

  2. Fill out the following fields for the shapefile you would like to import:\

    Field
    Description
    Required

    Hierarchy

    The hierarchy the Geo-Object Type for which you are importing a shapefile belongs to. The dropdown list of hierarchies will depend on the hierarchies created for the organization you are a part of.

    Required

    Geo-Object Type

    The Geo-Object Type of the shapefile you would like to import. The dropdown list of Geo-Object Types will depend on the hierarchy selected in the Hierarchy field.

    Required

    Import Strategy

    The import strategy for the shapefile being imported:

    • New and update: This will import the Geo-Objects in the shapefile that are not yet in GeoPrism Registry as well as overwrite the attributes of Geo-Objects from the shapefile that are already in GeoPrism Registry.

    • New only: This will import only the Geo-Objects from the shapefile that are not yet in GeoPrism Registry. If the imported file contains Geo-Objects that are already in GeoPrism Registry (same unique identifier and/or label depending on what is selected during matching) then the import will fail to avoid creating duplicates.

    • Update only: This will overwrite the attributes of the Geo-Objects from the list that are already in GeoPrism Registry. If the imported file contains Geo-Objects that are not yet in GeoPrism Registry, these will not be imported.

    Required

    Start Date

    The start of the date of validity of the Geo-Objects in the shapefile. All the Geo-Objects in the shapefile being imported, whether new or for update, should have the same start date of validity.

    Required

    End Date

    The end of the date of validity of the Geo-Objects in the shapefile. All the Geo-Objects in the shapefile being imported, whether new or for update, should have the same end date of validity. If the shapefile is still valid on the date it is being imported in GeoPrism Registry, click the Set as most current button.

    Required

    Import blank cells

    Selecting this option ensures that if there are empty cells in the list being imported, they are imported as empty attribute values (overwrite). This option gives more control to ensure that updates will either only update cells with values or to overwrite existing values with null values.

  3. Click the Choose file button and in the window that opens, browse to the location of the compressed shapefile (.zip file) you would like to import. Select the file and click Open.\

  4. Click the Submit button in the Shapefile import window.

  5. The Attribute Matching window opens containing the attributes for the Geo-Object Type. The number of attributes that appears depends on the number of attributes created for the Geo-Object Type for which the shapefile is being imported. In the dropdown option for each field, choose the attribute from the shapefile being imported that matches the created attribute of the Geo-Object Type. Click the Next button. Note: When the shapefile is formatted correctly and completely, you should be able to match all of its attributes to the Geo-Object Type for which it is being imported. Otherwise, some of the attributes will be left blank.

  6. The Hierarchy Matching window opens listing the Geo-Object Types above (parent) the Geo-Object Type for which the shapefile is being imported. The number of Geo-Object Types listed depends on the position in the hierarchy of the Geo-Object Type for which the shapefile is being imported. Fill out the following fields for each parent Geo-Object Type:\

    Field
    Description

    Source file parent column

    The attribute from the shapefile being imported that corresponds to the parent Geo-Object Type (unique identifier or name)

    Match Strategy

    The strategy on how the selected attribute will be matched:

    • Using the code, label, and synonyms

    • Using the code only (fastest)

    Note: The hierarchy matching is optional. This could be completed if you have added the hierarchy information to the shapefile you are importing.

  7. Click Submit.

  8. The import will start processing. Click the Go to jobs button to view the progress.\

  9. This will direct you to the Scheduled Jobs module. If there is no problem with the imported shapefile, the page will look as follows. You will see the imported shapefile listed as one of the completed jobs when you click on the View completed jobs button.\

  10. If there is any problem with the shapefile being imported, you will see this in the In progress section with the part of the process with the problem highlighted in red. Click on the Resolve Problems button to see the details of the problem.\

  11. The Job Details page will provide the problem type, message, and row number details of the issue and give you options on how to solve each problem when you click the Resolve button. Note: Depending on the problem type, GeoPrism Registry may ask you to fix the problem in the shapefile itself and then re-import it.

  12. Depending on the problem type, there may also be cases when you can ignore the errors and proceed with the import. When this is the case, click the Ignore All Errors button.\

  13. A warning message will appear asking if you want to mark the import as completed. Click the Complete import button. This will complete the import process.\

  14. You will see the imported shapefile when you click on the View completed jobs button.\


The spatial data must be in format.

The shapefile must be unprojected (). Otherwise, GeoPrism Registry will give an error message and the import will not take place.

Go to the Import module either by clicking the module icon on the homepage or by clicking the hamburger menu () in the upper right corner and selecting Import.\

If an external system has been registered in GeoPrism Registry (see ) a window will open providing the option for the import to take place from an external system or from your computer. Choose the option that applies.\

shapefile
World Geodetic System 1984; EPSG:4326
section 4
World Geodetic System 1984; EPSG:4326
section 4