- Full Description
Pro Oracle Spatial for Oracle Database 11g shows how to take advantage of Oracle Databases builtin feature set for working with locationbased data. A great deal of the information used in business today is associated with location in some way, and analysis of that data is becoming ever more important in today's mobile and highly connected world. In Pro Oracle Spatial for Oracle Database 11g, authors Ravi Kothuri and Albert Godfrind address:
- The special nature of spatial data and its role in professional and consumer applications
- Issues in spatial data management such as modeling, storing, accessing, and analyzing spatial data
- The Oracle Spatial solution and the integration of spatial data into enterprise databases
- How spatial information is used to understand business and support decisions, to manage customer relations, and to better serve private and corporate users
When you read Pro Oracle Spatial for Oracle Database 11g, youre learning from the very best. Ravi Kothuri is a key member of Oracles Spatial development team. Albert Godfrind consults widely with Oracle clients on the implementation of Oracle Spatial, develops training courses, and presents frequently at conferences. Together they have crafted a technically sound and authoritative fountain of information on working with spatial data in the Oracle database.
What youll learn
- About new Oracle Spatial features in Oracle Database 11g, including support for the European Petroleum Standards Group (EPSG) data model, the ability to publish to Google Earth, integration with Google Maps, and much more
- The use of Oracles built-in SDO_GEOMETRY data type for storing locationbased data
- How to geocode your data, beginning with postal addresses and ending with SDO_GEOMETRY objects that enable future analysis as well as forming the foundation of working with spatial data within Oracle
- How to create and display maps to help you visualize and analyze your geocoded data
- About network modeling, which is useful in computing routes, travel distances, and proximity based upon travel time
- How to optimize analysis of your spatial data by creating spatial indexes and custom operators
Who this book is for
Pro Oracle Spatial for Oracle Database 11g is aimed at software developers who wish to develop applications using Oracles extensive and strong support for working with spatial, or geocoded, data.
- Source Code/Downloads
On page map_large.dmp:After I import this data to 11gR2 and run validate geometry numerous errors are found in the US_PARKS layer. In addition none of the attempts i have made to fix the data (like running rectify_geometry) have worked properly. Do you have a suggested workaround for this problem?
On page 98:
Listing 4-30: There is a missing comma after the 0 in in the ordinates array.
Listing 4-31: There is an extra comma after the 1 used in the interpretation for the SDO_ELEM_INFO_ARRAY. In addition, the SDO_ORDINATES_ARRAY is wrong since it should be SDO_ORDINATE_ARRAY.
On page 99 and 100:
Listing 4-32: The comment next to the SDO_GTYPE is wrong, it describes a 3D line when it should be describing a surface or 3D polygon.
Also, note that the element type is set to 3 in the SDO_ELEM_INFO_ARRAY when it should be 1003.
Additionally, the SDO_ORDINATES_ARRAY is wrong since it should be SDO_ORDINATE_ARRAY
On page 101:
Listing 4-33: There a couple of errors in this code, first, the comment for the interpretation in the SDO_ELEM_INFO_ARRAY says "connected by straight lines" when it should say "interpretation for a rectangle"; besides that, there is an extra comma after the interpretation number that needs to be removed.
Secondly, SDO_ORDINATES_ARRAY should be SDO_ORDINATE_ARRAY.
On page 104:
Listing 4-36: inside the SDO_ORDINATE_ARRAY, the ordinates for the inner rectangle are specified in the wrong order, when working with composite surfaces, for the inner polygon you have to specify the order as <max,min> instead of <min, max>, so instead of:
3, 1, 2, 3.5, 1.5, 2
the order should be
3.5, 1.5, 2, 3, 1, 2
Also note that SDO_ORDINATE_ARRAY, is named SDO_ORDINATES_ARRAY which is wrong.
On page 105:
Listing 4-37: I have a problem with the ORDINATES, when validating the geometry I receive the following error message:
ORA-54518: shared edge of composite surface not oriented correctly
Cause: A shared edge (one shared by two polygons) in a composite surface was not correctly oriented. Each shared edge must be oriented in one direction with respect to its first polygon and then in the reverse direction with respect to its second polygon.
Action: Reverse one of the directions of the shared edge with respect to its polygons.
I was trying to fix the SQL code by myself but I couldn't find a way to get rid of the previous error message during geometry validation. Could you point what is the problem with this code?
By the way, a couple of additional problems:
-SDO_ORDINATES_ARRAY should be SDO_ORINDATE_ARRAY.
-One of the corners for the left side face is specified as 2.0.2, when it should be 2,0,2,
On page 388:In the listing 10-31, the object netConstraint is not used.