06-23-2016 05:05 AM
I want to use existing GeoMedia Access-Warehouses as Input for a spatial model, but I only find operators that can handle with Shape, SQL- or Oracle. Can't I connect directly to a .mdb-Warehouse?
Solved! Go to Solution.
06-29-2016 09:20 AM
Spatial Model Editor 2016 currenly supports feature data stored as:
Access stored (GDO) Features are not supported as a source of input to the Features Input object.
06-30-2016 07:37 AM
I found the operator "vector attribute input (Legacy).
in this there is Filename -> Geomedia File proxy (gwp) where it is possible connect a dataserves of GM ( access, shp, ecc. )
is it the right way ?
Of course I have not been able to make it work .....
07-01-2016 01:56 AM
thank you for your idea!
With the mentioned operator I'm able to connect an acces-database
ERDAS IMAGINE Help -> Connect to GeoMedia Database Workflow
There is a detailed step-by-step instruction how to connect including the creation of so called "GeoMedia File Proxy"!
You can connect to each mdb that you want, choose your feature classes and afterwards work with them in the spatial modeler!
Have a try!
PS: This is the link of my local Help-Site:
Or just search for "GeoMedia database workflow"
07-19-2016 08:02 AM
I have seen this entry, but in the Spatial Modeler, it is not possible to create a GeoMedia File Proxy. I have already made it in the past, but directly in ERDAS Imagine.
Can you confirm to me that the only way is to install ERDAS Imagine to be able to connect the Spatial Modeler to Access database, and if yes, is this GeoMedia File Proxy possible with the Essential version of Imagine (which is accessible with a GeoMedia licence)?
07-20-2016 09:19 AM
The Spatial Model Editor delivered with GeoMedia 2016 supports the following data sources:
These are all supported data sources for models imported to Smart M.App. The Imagine GeoMedia Warehouse Proxy (.gwp) file for serving record sets from a 32 bit data server into Imagine is not supported (at least at this time) however parts of IMAGINE besides Spatial Modeler do still take GWP. Understanably this is a point of confussion that needs to be better documented in the Help as requested by Doc Defect 1-M2V815.
GWP for use in Imagine is used for GDO-based access, which Spatial Modeler can’t do because of its 64-bit requirement for Smart M.App (IMAGINE itself is 64-bit). Enhancement CR 1-M2VQ8V request support for serving standard GeoMedia warehouse GDO data sources into Spatial Model Editor.
07-27-2016 12:00 PM
Starting with the 2016 release, the internal implementations of spatial modeler operators must all be 64-bit-ready and thread-safe. The GDO and GeoMedia object model previously used in certain operators satisfy neither requirement. The generation of Microsoft Access / DAO / Jet that is used for the Access data server is also not satisfactory in that regard. The 2016 implementation of the feature operators therefore uses different technology internally now, and you have seen above the list of supported data source types. More will come.
All of the above pertains to running models through Spatial Model Editor, its command-line executable, etc. The rules will be different when we introduce the Run Spatial Model command in GeoMedia. This capability, which was not quite ready in time to make the GeoMedia 2016 cutoff, will allow you to input any GeoMedia "recordset" (i.e. feature class, query, categorized item, etc.) into a parameterized spatial model, and then see the results within GeoMedia. This will be an exciting addition! - Hal
06-08-2018 06:05 AM
has anyone else been trying to do this more recently? My interest stems from trying to use Section 23: Combine Vector Class to a Classified Landcover Image of the IMAGINE Training Tutorials, which begins by setting the vector file type to .gwp...........which does not appear to be an option in IMAGINE18.
I can not find the Connect to GeoMedia Database workflow that is referred to in the Solution .........anywhere in the IMAGINE Help files...(there are workflows for converting gwp to .shp....).
I will likely work around this by obtaining a vector file of streets another way, but thought I'd alert someone to this contradiction btw. the training materials and the current version of the software....