Skip to content
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

Administrative unit versus AdminUnit address component #1

Open
MichalMed opened this issue Aug 30, 2018 · 0 comments
Open

Administrative unit versus AdminUnit address component #1

MichalMed opened this issue Aug 30, 2018 · 0 comments

Comments

@MichalMed
Copy link

http://inspire-sandbox.jrc.ec.europa.eu/etf-webapp/v2/TestRuns/EID7b4422c4-9b05-4722-ad9a-0f73e6b7f507.html

While testing addresses, I get new errors on address components. It says that element situatedWithin and component must be AddressComponent or its subtype. I get it, but we're using direct link to theme Administrative Units for AdminUnitName component http://services.cuzk.cz/wfs/inspire-au-wfs.asp?service=WFS&VERSION=2.0.0&request=GetFeature&storedQuery_id=urn:ogc:def:query:OGC-WFS::GetFeatureById&Id=AU.1.1 and I think this is completely legal. Administrative Unit is definitely where the address is locatedWithin. For sure we can switch to components form addresses theme, but the infomration is not so rich a nd anyway, there should be some link to AU, if possible. Whats your o.pinion? (ad-ia.b.1, ad-ia.b.6)

Similar problem is with constraint ad-as.b.1. We refere to the country from the theme AU, but validator expects component.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant