Those are questions from a Geographic Information Systems class, from Lab book G

Question

Those are questions from a Geographic Information Systems class, from Lab book GIS Tutorial 3 (3.1 and 3.2 )- Populating Geodatabase

1-Name two options for transferring data from an existing shapefile to a geodatabase. Explain the advantages and disadvantages of each option?

2-Given What you already know about feature subtypes, why is it important to have the ability to import features directly into a subtype in the existing geodatabase?

3- What is a load procedure, and why is it important for you to develop and follow one? What knowledge is required to successfully develop and execute the load procedure?

4- Using the Simple Data Loader, What option must you specify before objects are load into a subtype?

5- What is the best way to quickly determine whether the import procedure was correctly performed?

Explanation / Answer

1. Feature class to feature class and turn table to feature class are the two options for transferring data from exisitng shapefile to a geodatabase.

Advantages of feature class to feature calss option :

Disadvantages :

Advantages of Turn table to feature class option:

The turn feature class to be created is placed in the same workspace as the reference line feature class.

The coordinates in the output turn feature class will have elevation (Z) values if the reference line feature class supports Z values.

Load Phase: The load phase loads the data into the end target, which may be a simple delimited flat file. Depending on the requirements, this process varies widely. Some data warehouses may overwrite information with cumulative information; updating extracted data is frequently done on a daily, weekly, or monthly basis. Other data warehouses may add new data in a historical form at regular intervals. To understand this, consider a data warehouse that is required to maintain sales records of the last year.. However, the entry of data for any one year window is made in a historical manner. The timing and scope to replace or append are strategic design choices dependent on the time available and the business needs. More complex systems can maintain a history and audit trail of all changes to the data loaded in the data warehouse. As the load phase interacts with a database, the constraints defined in the database schema as well as in triggers activated upon data load apply , which also contribute to the overall data quality performance.

Determining whether the import procedure was correctly performed:

Importing a single sheet or range of data is straightforward. Import the entire sheet or range into a single table and then normalize. If the Excel file contains more than one sheet, you must decide whether all that data belongs to separate tables or to one inclusive table. The general rules of thumb follow:

Suppose, If we have a file that contains 14 sheets: a list of customers, a list of products, and 12 monthly lists of orders. The customers, the products, and the orders are all related. Customer and products records consists of two different purposes and structures, the data is inconsistent, even though it's related. Consequently, you'd import the customer and product sheets into separate tables. The 12 monthly sheets are consistent with one another, so you'd probably import them into a single table.

Related Questions

Navigate

• Browse (All)
• Browse T
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.