I have contours generated in ArcGIS and now it is in a file geodatabase. We need to share it with another application in our company that is using Oracle. Can Oracle without SDE store contours?

And another question that they had, if it can store them can it be a single field or has to be each contour line a separate field/record?

closed as too broad by PolyGeo Oct 15 '17 at 9:57

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Yes, of course Oracle can store contours. What you really want to know is if ArcGIS can store a vector layer in Oracle without enabling an Enterprise geodatabase. It is GIS SE policy to only ask one question per Question. Please add relevant details (exact software releases, what your research indicated is possible, and what you have tried) and remove or restructure the second question. – Vince Sep 15 '17 at 10:18

Oracle most certainly can store them (it can store practically anything you can throw in).

How you store them, well, depends on your app logic/goal:
At one end, you can store a single line per record (e.g. a closed polyline).
At the other end, theoretically, you can store all of them in one record, in one field (one single multiline) - not practical at all.
You can also store one multiline per altitude value (one row, one multiline, for 10m, another one for 20m etc).
Oracle also supports multiple geometry columns in the same table (even of different types of geometry), but it wouldn't be easy to find an application that could display that (in most, you would have to create one 'layer' per geometry column of the table).

In between those options, you must find the implementation that works best for your business logic - the combinations can cover pretty much any case.
At the end, it all depends on the total number of nodes (resolution+dataset), on how you plan to use this table (what kind of queries/processes you'll run) and on your hardware (CPU, RAM, Oracle version).
It is a very common requirement and an optimal implementation can easily be made (I work with millions of geometries in Oracle, every day, with hardly any GUI at all).

Without any info about your dataset I can hardly be anything more than theoretical, but, closing, one of the most common and versatile scenarios would be to store each contour as a single record, with the altitude value as an attribute (e.g. ID, ALT_VALUE, GEOMETRY).

Not the answer you're looking for? Browse other questions tagged or ask your own question.