New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved support for INSPIRE #860

Closed
tfr42 opened this Issue Oct 23, 2017 · 9 comments

Comments

Projects
None yet
3 participants
@tfr42
Copy link
Member

tfr42 commented Oct 23, 2017

we have an important request for your next TMC-Meeting: As you know deegree3 is used by many governmental organizations for the implementation of web services according to INSPIRE. The next milestone (aka deadline…) on the INSPIRE roadmap will be the 23/11/2017 and every responsible organization has to provide its interoperable spatial data sets (Annex I) until this date.

In this context many improvements and bugfixes were promoted by LDBV Bayern / LGB Brandenburg in cooperation with known service providers. Unfortunately many organizations are still working with deegree 3.4 RC3 or other versions (it’s a small mess at the moment) and they encounter huge problems which are already solved in the developments we ordered.

For this reason, we strongly recommend to take the following tickets into account and we hope that you’ll integrate these improvements in the new release (or at least into a release candidate):

We think it would be more effective and easier for INSPIRE users if these developements were available in one merged version. The community would benefit and it would increase the distribution of deegree.

refs:

@tfr42 tfr42 added the enhancement label Oct 23, 2017

@tfr42 tfr42 added this to the 3.4 milestone Oct 23, 2017

@tfr42

This comment has been minimized.

Copy link
Member Author

tfr42 commented Nov 6, 2017

Issue PR GA version VERIFIED BY USER workspace/test data
#573 #837 3.4-RC5 - -
#742 #817 3.4-RC6 - -
#713 #752, #796 3.4-RC4 - -
#745 #887 3.4-RC7 - -
#747 #787 3.4-RC5 YES -
#781 #834 3.4-RC5 YES -
#782 #836 3.4-RC5 YES -
#749 #820 3.4-RC5 #864 -
#827 #838 3.4-RC4 YES -
#711 #840 3.4-RC5 - -

@marcus-mohr please comment for which issues you can provide feedback

@mrcsmhr

This comment has been minimized.

Copy link

mrcsmhr commented Nov 16, 2017

I've tested PR #820 - please see: #864

@JuergenWeichand

This comment has been minimized.

Copy link

JuergenWeichand commented Nov 21, 2017

[LDBV] #781 (#834) is successfully fixed in 3.4-RC5.

@mrcsmhr

This comment has been minimized.

Copy link

mrcsmhr commented Dec 6, 2017

I can confirm that #747 (#787) now works as expected in 3.4-RC5

@mrcsmhr

This comment has been minimized.

Copy link

mrcsmhr commented Dec 6, 2017

#782 (#836) is also "fixed". But the <soapwms:ExtendedCapabilities> element ist not disabled by default.

@mrcsmhr

This comment has been minimized.

Copy link

mrcsmhr commented Dec 6, 2017

#827 (#838) is fixed!

@mrcsmhr

This comment has been minimized.

Copy link

mrcsmhr commented Dec 6, 2017

#573 (#837) doesn't seem to be fixed. Now there is another bug which affects the gml output of a getfeature request and there are also problems with filtering at layerstyling.

@tfr42 tfr42 removed this from the 3.4 milestone Apr 7, 2018

@tfr42

This comment has been minimized.

Copy link
Member Author

tfr42 commented Apr 8, 2018

@marcus-mohr Have you tried to apply the provided information as in #573 (comment) and following comments to verify the expected behavior?

@tfr42

This comment has been minimized.

Copy link
Member Author

tfr42 commented Jun 18, 2018

deegree webservices version 3.4.0 is GA. Please create a new issue in case you encounter an error or problem.

@tfr42 tfr42 closed this Jun 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment