in the feature Analyzer the measurement of the Date Chart is always measuring the main field definition.
In other Charts there is the possibility to set a different field for the x-axis.
I know the possibility of the stacking option. However, defining the x-axis would be easier to understand.
Would it be possible to extend the Date Chart by this function?
Take some taxi data set that includes the pickup point and time as well as the costs of the drive. At the moment, the date chart can only show the number of pick ups. However, I would like to set the sum of the costs per time.
In the Feature Analyzer of MAE 16.5 all date charts can only be used if there aren't any values of NULL.
If there are values of NULL, the format is taken as incorrect and the chart can't be defined.
However, we have got a lot of examples where it would be reasonable to show date charts containing NA's.
I suggest a similar checkbox as for other charts saying 'Hide Null or Empty Values'. FA_NULLValues.png
When configuring a WFS-T service the only thing needed to make a WFS to be transactional is a SQL Server, SQL Server Spatial or Oracle Read-Write Data Server.
However if we want a WFS non transactional with a connection made to a SQL Server Spatial Data Server it isn't possible because the Data Server os SQL Server Spatial is only Read-Write. It doesn't exists a SQL Server Spatial Read-Only Data Server.
There is a workaround to achieve this but it required that the user changes the capabilities xml document for each service and removes the transactional part, restart all the services, clean temporary files and also establish a SQL Server Spatial connection with a db user that has only read-only privileges.
It would be great if there was a way to configure the possibility of making a WFS to be transactional (always requires a Read-Write connection), or a WFS with a SQL Server Spatial Read-Write connection to be non transactional, in the administration console configuration of the service.
I would like to see WMTS support within ERDAS IMAGINE. WMS as well as WCS are supported via Open Web Service but not WMTS. Some services (e.g. coming from www.basemap.at) are only available as WMTS and not as WMS.
Thanks for getting this into the product.
for LineVectorLayers there is a possibility to define the style of the features. Thereby, also the selectionColor can be set. I assume the same for Polygons.
<LineVectorLayer Entity="Entity" Color="#483d70" SelectionColor="#ff4cfc" StrokeWidth="1">
For MarkerVectorLayers there is the possibility to define own icons. However, the style of the selection can't be defined (as far as I am right here?) and is always visualized through a violet circle (screenshot).
It would be great to be able to
i. change the style of the 'selection circle' similar to the lineVectorLayer
ii. to define another customized Icon for selected objects.
Thanks and regards,
while creating large Spatial Models it is often very helpfull to create Submodels to keep the whole model overseeable.
As fast as this can be done, as comlicated it is to resolve the submodel if it is needed later. It is possible with the "undo" function, but if you want to resolve the submodel to a later point, you have to copy and paste and reconnect all port-connections.
So my question: Is it possible to implement a Button like the "create Submodel" Button to resolve the submodel, so that you keep all Input-/Output-Port connections?
This would sometimes helo a lot to save time during the spatial modelling process..
As a GeoMedia user, I want to have a checkbox on the Legend Entry Properties dialog for turning the display of the Boundary on and off, just as I have for turning the Fill and Point display on and off, so that I don't have to enter the Style Properties dialog to turn off my area boundaries.
As a GeoMedia user interested in accessing tabular information from Microsoft Excel spreadsheets, I want GeoMedia to support XLSX files from more recent versions of Excel, so that I am not restricted to use of older-format Excel files.
An example of a recent problem with accessing older XLS files can be found here:
As a GeoMedia user, I want to be able to access the different file formats supported by GeoMedia via a drag-and-drop action without having to go through warehouse connection commands, so that data interaction and visualization are made simpler and faster.
As a Spatial Modeler user, I want to have a Union Features operator made available, so that I have functionality equivalent to the GeoMedia command Union.
There have been many requests to have a new web client delivered with ERDAS APOLLO that is more lightweight, built on newer technologies, and provides a more modern look. The idea here is to provide a client that is more intuitive and easier to use than the current solution.
Adding a note from another related idea (https://community.hexagongeospatial.com/t5/Product-Ideas/New-APOLLO-Web-Client/idi-p/16138):
As a user of the Apollo Portal client to search for and discover image files for analysis, I often have search results with several hundred datasets. The current detailed and thumbnail views are adequate for a small number of datasets, but is cumbersome when the number of datasets is large. The attribute columns in the gridded display should be configurable at an enterprise level. The ability to sort by any column in ascending or descending mode is required. The user should be able to “select” a dataset by selecting a row in the gridded display or by selecting a footprint in the map panel. There should be a mode that scrolls the gridded display to selected dataset’s row when it’s footprint is selected and windows the map panel on the dataset’s footprint when it’s row is selected. The Data Window/ Map Window functionality in GeoMedia is a good example of the functionality desired. When image footprints are displayed in the map window and a data window is opened with the footprint attributes and the Map Window properties are set to Fit and Zoom out, the map window will fit to the image footprint when selected in the data window, and the data window scrolls to the row of a footprint selected in the map view.
As a user of GeoMedia, I want the legend right-click command "Display Data Window" to work for top-level thematic legend entries as well as standard legend entries and thematic sub legend entries, so that I can easily access all features in my thematic display in a single data window.
Currently the command is dimmed when selecting the top level of the thematic legend entry.
As a Spatial Modeler user, I want to have a Generate Functional Attributes operator made available, so that I have functionality equivalent to the GeoMedia command Functional Attributes.
I would like to see an new operator that could take as input an Boundary (IMAGINE.Boundary) and output Features (IMAGINE.Features).
That would allow a boundary from (say) an raster image to be available as a feature that can be used for feature analysis. e.g. filter feature by the raster boundary.
example concept (Mock up of an 'Boundary to Features' operator and how it could be used):
(An alternative approach would be to introduce a new Functional Attribute Expression such as 'CREATEPOINT(X,Y,Z,CRS)'. Could then take the Boundary and extract MinX, MaxX, MinY, MaxY as input to Create Point expression. That could then feed into existing functional attribute CREATEPOLYGON expression which I suspect would give Boundary To Features equiv)
As a Spatial Modeler user, I want the Features Database Output operator to add support for GeoPackage databases, so that I can output spatial model results directly into my GeoPackage database.
As a Spatial Modeler user, I want to have a Summarize Related Features operator made available, so that I have functionality equivalent to the GeoMedia command Aggregation.
Most of our customers do some editing in GMSC and they also have more groups in the legend. When user expands some themes in legend and then enter the editing mode, all themes are collapsed again. This is very frustrating for these users, when there are more groups in legend and they need to expand them again after each editing. Persisting legend state after editing would give more comfort to the users.