issues
search
geosolutions-it
/
inspire-issues
This repository works as an aggregator for GeoServer known issues with respect to INSPIRE compliance and support.
https://waffle.io/geosolutions-it/inspire-issues
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Where to retrieve the INSPIRE SpatialDataSetIdentifier elements
#33
nmco
opened
5 years ago
0
Investigate and fix HALE app-schema plugin build issue
#32
fernandor777
opened
5 years ago
9
AppSchema: Argument "targetCRS" should not be null - 2.15.0
#31
morcom
closed
5 years ago
1
GeoServer doesn't enforce the selected SRS style if the axis EAST \ NORTH or uknown
#30
nmco
opened
5 years ago
6
WFS GetPropertyValue requests fail with App-Schema defined feature types
#29
nmco
opened
5 years ago
0
Multiple xlinks not possible at base feature level
#28
nmco
opened
5 years ago
0
WFS Schema Location incorrect in DescribeFeatureType
#27
nmco
closed
5 years ago
1
On a GetFeature WFS 2.0 request on a virtual service is not possible anymore to get the response in browser, the only response is the default one that is the file to be saved as "application".
#26
nmco
opened
5 years ago
1
On a WFS 2.0.0 served with Geoserver and AppSchema, the GetProperyValue for geometry returns a java.lang.ClassCastException message, while for all other properties it works.
#25
nmco
opened
5 years ago
0
Extended capabilities in geoserver are incomplete and EC tests are not passed
#24
nmco
opened
5 years ago
0
Geoserver Global Settings dont apply to GML 3.2 GetFeature data
#23
nmco
opened
5 years ago
0
Currently Geoserver's virtual services cant be used for ensuring a unique endpoint per dataset (but only per featureType)
#22
nmco
opened
5 years ago
0
GetFeature requests to virtual services are returning null namespace prefixes, therefore virtual services cant be used as endpoints to fullfill REQ. 51
#21
nmco
closed
5 years ago
1
GetSpatialDataSet StoredQuerry is providing null namespace prefixes while retriewing a dataset with multiple featureTypes.
#20
nmco
closed
5 years ago
1
GetProperyValue for an element of a featureType embeded in another featureType is returning null namespace prefixes in the GML
#19
nmco
closed
5 years ago
1
SLD editing fails sometimes when updating a ComplexFeature layer style
#18
nmco
opened
5 years ago
0
SLD rules based on complex feature attributes fails
#17
nmco
opened
5 years ago
1
FeatureTypes/layers always published in all service types
#16
nmco
opened
5 years ago
1
It is not possible to provide access via WFS to more than one dataset based on multiple INSPIRE data themes (XSD files)
#15
nmco
opened
5 years ago
1
Querying multiple type names in Stored queries fails
#14
nmco
opened
5 years ago
1
It is not possible to use more than one endpoint per Geoserver instance
#13
nmco
opened
5 years ago
1
It is not posible to retrieve and test the dataset provided via WFS in the EC Geoportal if a data provider has to provide more than one dataset via Geoserver
#12
nmco
opened
5 years ago
1
It is not possible to create two or more endpoints for an XSD schema
#11
nmco
opened
5 years ago
2
Requests for multiple complex features crashes Geoserver
#10
nmco
opened
5 years ago
1
WFS-T doesn't work with complex features
#9
nmco
opened
5 years ago
1
WMS doesn't work on some geometry types * gml:MultiSurface
#8
nmco
opened
5 years ago
1
Stored Queries
#7
nmco
opened
5 years ago
3
NULL namespace prefixes used in AppSchema WFS GetFeature responses
#6
simboss
closed
5 years ago
2
App-Schema requires the same prefix used in the same mappings for filtering
#5
nmco
opened
5 years ago
0
It should not be mandatory to use always use the full resource name when querying a complex feature type
#4
nmco
opened
5 years ago
2
Allow the usage of ':' in a layer name
#3
nmco
opened
5 years ago
1
Layer name needs to be equal to the feature type name which needs to be equal to the XML element name
#2
nmco
opened
5 years ago
2
Unique Endpoint per Dataset
#1
nmco
opened
5 years ago
3