Is there a way to load spatial data (column of type geometry) directly from a Microsoft SQL Server into SPSS Modeler via a database node as type geospatial? So far I only had success with shapefiles (i.e. flat files) or csv (allows parsing of square brackets as geospatial type) as input.
For some reason SPSS Modeler does not recognize the geometry type from the database. Workaround to load as WKT representation does only seem to work for Point geometries (i.e. to create geospatial data type/ list out of parsed x/y coordinate), also due to character field length limitation for wkt-representations of polygons.
Related
Hi am having trouble understanding data conversion in ssis. when should one convert data types,should I always convert or I only convert when ssis has data type compatibility issues?
Am struggling to understand if i should convert when i import from excel to sql server or from sql server to excel or from text file file to sql server or from sql server to text file etc?
Please help me understanding data conversion in ssis.
The need to convert data from one data type to another will largely be dictated by the business need for it. For example, the ID fields are usually Integers and need not be converted, but a phone number on the other hand may have "(" or hyphens that need to be removed before they are loaded onto your destination database.
SSIS offer's ways to convert data that will ultimately fit the pattern/datatype that you need it to be in. A comprehensive list of the supported data types is here
I'm trying to move data from Oracle to SQL Server. We have a large number of NUMBER fields in the original Oracle 11g schema. In SSIS, we are using an OLE destination control. Most of the NUMBER fields are mapping to float fields.
We are using the attunity connectors. I understand that there are mapping xml files in SSIS that will map numeric data types to SSIS data types; however, I need something that will take a sample of the data and infer the correct numeric, sql server destination data type.
Is there a solution for this problem? There are a lot of fields, we are worried about manually mapping them.
Thanks!
I'm writing an app to query spatial data from SQL Server and add the results to an Elasticsearch index.
Is there an effective method to convert SQL Server Geometry data (point, line, or polygon) to corresponding Elasticsearch Geo Shapes?
Is that possible to parse and import an arbitrary XML file to SQL Server tables using C#?
The XML file can be highly hierarchical.
I have 1 Gb XML-file, I do not know anything about it.
How can I determine what tables it contains, create them at SQL Server and bulk load the data to SQL Server?
Is that possible?
No.
XML and SQL are very, very different things. It is possible to take SQL data an save it into XML, and such SQL-like XML can be converted back to an SQL database, but arbitrary XML that did not originate in an SQL-like system is not likely to be easily convertible to an SQL database schema in any meaningful way.
You could work out an SQL schema that represents generic XML in a key-value type design but it would not be an SQL schema in the traditional meaning of the word.
I want to know how the geospatial data (e.g shapefile) stored in Orcle DB? In which format shapefile stored in Oracle DB ?
Is the shapefile is stored at any physical location let say c:\folder and then in Oracle DB we use some reference to this c:\folder path. is it like that ?
plz explain.
secondly, how we can retrieve shapefile from Oracle DB ?
regards
A good place to start is the Oracle Spatial User's Guide and Reference (at http://docs.oracle.com/cd/B19306_01/appdev.102/b14255/toc.htm for 10g Release 2).
The "built-in" functionality for spatial data involves storing the spatial data in the database itself using rows and columns like other kinds of data. For example, you might have a CITIES table with "regular" columns like CITY_NAME and a "spatial" column (maybe named LOCATION) that contains the spatial representation of each city (maybe a point or polygon). Oracle provides a special data type named SDO_GEOMETRY for storing spatial data in this way, along with functionality for indexing, searching, transforming, etc. Oracle also provides utilities for converting shapefiles into this format.
There are two "levels" of spatial functionality -- the "basic" level (Oracle Locator) which is part of every edition (XE, Standard, Enterprise, etc.), and the "extended" level (Oracle Spatial) which is an additional cost option for the Enterprise Edition only.