JohannaOtt

Results 87 issues of JohannaOtt

Version 4.1.0.SNAPSHOT Build 734217868 Revision 7fd6e6b3c63a30c87cd03f0e513ed8247cb7c871 Abstract case: - join two featuretypes A and B on their properties a and b - focus should be on featuretype A - an...

bug
prio-3-could
confirmed

A reader for MySQL databases should be added in order to support one more format. If possible in the scope of this issue, a writer should be added, too. Otherwise,...

io
feature
funding-welcome
planned

Currently, when using a structural Retype mapping, there is no option to change single elements. Sometimes, there are use cases, where you want to keep the biggest part of the...

Version 4.2.0.SNAPSHOT Build 202203231441 Revision 1a25d6c351035ec4c3e162fdf7db4dcc1ee4d07c When importing an xml schema (for example INSPIRE presets), a lot of info messages ("Particle that allows any element is not supported" and "White...

confirmed

When editing mappable source or target types, it would be convenient to be able to chose multiple types without having to activate the checkmark for all of them individually. A...

enhancement
ui
ux
planned

Version 4.1.0.SNAPSHOT Build 763247191 Revision df620a7f13f58d8b80d5f5b3f488e3c3a3229e35 When transforming several objects to XPlan and exporting them with the Xplan writer using the functionality to create separate output files for every plan...

bug
io
prio-3-could

Version 4.2.0.SNAPSHOT Build 202203231441 Revision 1a25d6c351035ec4c3e162fdf7db4dcc1ee4d07c When importing a schema (for example [this one](https://wetransform.box.com/shared/static/aepzhy68v1s9hs8f1yocssdhxxdm36wm.xsd)) that is importing a type used in a choice from two different XSDs, the choice is...

enhancement
planned

According to [this issue](https://github.com/BRGM/gml_application_schema_toolbox/issues/83#issuecomment-498143290) QGIS has some namespace prefixes reserved for internal use. For users creating data with hale studio and planning to load their data with QGIS, it would...

enhancement
io
prio-3-could
planned

Description done with an example case to make the schema construct easier to understand: Work with omso:ProfileObservation The element result.ReferenceableGridCoverage.rangeSet.ValueArray.valueComponents can contain multiple occurrences of the choice used in it....

bug
planned

When the source element for a classification function is a complex element which has a value, the classification fails with the following error message: `org.springframework.core.convert.ConverterNotFoundException: No converter found capable of...

bug
cst
done