I attended a couple of pre-conference knowledge immersion seminars – one titled “Strategies for Enterprisewide Web Services” and one titled “Mobile Technology for the Enterprise”. As a whole, I was really happy with the event. Last week I attended GITA’s 2008 Geospatial Infrastructure Solutions Conference in Seattle, WA. Perfect geometry, perfect topology between features, with no slivers or gaps… a thing of beauty. The result in my case is census blocks seemlessly split based on a seperate layer of line work. If you didnt take my advice from step one and ignored the “Display Properties Dialog for New Features” button, then it might force you to click OK for every newly split feature. Depending on the complexity of the features that it is analyzing and the sheer number of records, it may take a little time to complete. Double-click somewhere – anywhere – on the map window and let Geomedia do its thing. Turn on locatability for the streets layer, and select the features that you want to use as a basis for splitting census blocks.ĥ. Be sure to do this without unselecting those features.Ĥ. Turn OFF locatability on the census blocks layer (the layer to be split). Notice that a new toolbar appears with four buttons on it… split by point, split by line, split by polygon, and split by selected features. Select the census blocks and initiate the split tool in Geomedia. Also, and this is important, make sure that the “Display Properties Dialog for New Features” button is unpressed.Ģ. Load the feature class that you want to split (in my case, census blocks), and the features that you want to split by (in my case, streets). How to do it in Geomedia? The solution is easy, but not at all obvious (at least to me). Although I had the option to do this work with custom code in Oracle Spatial, I wanted to use Geomedia in order to avoid the Oracle customization time sink. One of the basic challenges in this project was to find an efficient way to split hundreds of thousands of polygons (census blocks) using a separate, and rather large layer of line geometry – in this case, statewide commercial street data. Click here for a more complete case study on my company’s website. Select all objects for maintenance.A little more than a year ago, I did a project for a left leaning political organization that had an interest in developing an automated means to create (and recreate) a national layer of election precincts to support activities like political canvasing. Load data into the new analytic workspace as described in " Loading Data Into Cubes". The Correct Duplicate Names From Analytic Workspace Template Import dialog box appears if any objects, such as a cube, dimensions, or the analytic workspace, duplicate object names that already exist in the schema.Įnter new names to resolve any conflicts, then click OK.īefore loading the data, you may want to browse the dimensional objects and make any changes to the object names, cube partitioning, or aggregation strategy. Open the upgrade template that you created previously. On the Connect to Database dialog box, log in with the new user name and select OLAP 11g/12c for the Cube Type.Įxpand the tree, right-click Analytic Workspaces under the new schema, and select Create Analytic Workspace From Template. Right-click the connection again and select Connect Database. Right-click the connection in the tree and select Disconnect Database. You cannot edit the names now, but you can change them later. The Create 12c Upgrade Template for 12 c Analytic Workspace dialog box appears if any subobjects, such as a level and a hierarchy, have the same name.ĭuplicate object names are changed automatically for the upgrade. Right-click the analytic workspace and select Create 12c Upgrade Template for 11g Analytic Workspace. See " Opening a Database Connection".Įxpand the navigation tree until the name of the analytic workspace appears. On the Connect to Database dialog box, select OLAP 11g/12c for the Cube Type. If necessary, create a new database connection to the database instance with the analytic workspace. Open Analytic Workspace Manager for Oracle Database 12 c Release 1. To upgrade an OLAP 11 g analytic workspace:
0 Comments
Leave a Reply. |