AW: AW: AW: [Mapserver-inspire] MapServer and INSPIRE
Martin Kofahl
M.Kofahl at gmx.net
Thu Jan 5 15:39:00 EST 2012
Hi Stephan,
I did add a patch regarding MetadataUrl etc. to #4129: http://trac.osgeo.org/mapserver/attachment/ticket/4129/metadataurl_dataurl_authorityurl_identifier.patch
Thus, wms_metadataurl_href is used twice, for the inspire extended capabilities and the root layer. Following other inspire metadata keys, I suggest renaming the inspire wms_metadataurl_href to wms_inspire_metadataurl_href:
--- tmp 2012-01-05 21:35:43.000000000 +0100
+++ mapows.c 2012-01-05 21:36:26.000000000 +0100
@@ -1101,11 +1101,11 @@
if (strcasecmp("url",inspire_capabilities) == 0)
{
- if ( msOWSLookupMetadata(&(map->web.metadata), namespaces, "metadataurl_href") != NULL )
+ if ( msOWSLookupMetadata(&(map->web.metadata), namespaces, "inspire_metadataurl_href") != NULL )
{
msIO_fprintf(stream, " <inspire_common:MetadataUrl xsi:type=\"inspire_common:resourceLocatorType\">\n");
- msOWSPrintEncodeMetadata(stream, &(map->web.metadata), namespaces, "metadataurl_href", OWS_WARN, " <inspire_common:URL>%s</inspire_common:URL>\n", "");
- msOWSPrintEncodeMetadata(stream, &(map->web.metadata), namespaces, "metadataurl_format", OWS_WARN, " <inspire_common:MediaType>%s</inspire_common:MediaType>\n", "");
+ msOWSPrintEncodeMetadata(stream, &(map->web.metadata), namespaces, "inspire_metadataurl_href", OWS_WARN, " <inspire_common:URL>%s</inspire_common:URL>\n", "");
+ msOWSPrintEncodeMetadata(stream, &(map->web.metadata), namespaces, "inspire_metadataurl_format", OWS_WARN, " <inspire_common:MediaType>%s</inspire_common:MediaType>\n", "");
msIO_fprintf(stream, " </inspire_common:MetadataUrl>\n");
}
else
@@ -1113,7 +1113,7 @@
status = action_if_not_found;
if (OWS_WARN == action_if_not_found)
{
- msIO_fprintf(stream, "<!-- WARNING: Mandatory metadata '%s%s' was missing in this context. -->\n", (namespaces?"..._":""), "metadataurl_href");
+ msIO_fprintf(stream, "<!-- WARNING: Mandatory metadata '%s%s' was missing in this context. -->\n", (namespaces?"..._":""), "inspire_metadataurl_href");
}
}
}
Kind regards,
Martin
-------- Original-Nachricht --------
> Datum: Thu, 05 Jan 2012 15:34:33 +0100
> Von: "Stephan Meißl" <stephan at meissl.name>
> An: Martin Kofahl <M.Kofahl at gmx.net>
> CC: E.Nash at dvz-mv.de, mapserver-inspire at lists.osgeo.org
> Betreff: Re: AW: AW: AW: [Mapserver-inspire] MapServer and INSPIRE
> Hi Martin,
>
> see comments below.
>
>
>
>
> On Thu, 2012-01-05 at 14:49 +0100, Martin Kofahl wrote:
> > Hi Stephan,
> >
> > handling of wms_layer_group looks ok. I did test GetMap and
> GetFeatureInfo. Now it's much easier to configure full featured groups. However, I did
> not alter the inspirevs_test service, because it looks as inspire view
> service may not have named groups. I did post a question on the inspire forum.
> See
> http://inspire-forum.jrc.ec.europa.eu/mod/groups/topicposts.php?topic=79913&group_guid=5205#34121.
> >
> great, it will be good to now the official answer for your post.
>
> > One thing I miss regarding wms_layer_group is the possibility to
> configures an unnamed group, thus for structuring the capabilities only.
> >
> All names that appear in wms_layer_group but don't have a layer with the
> same name are treated as unnamed groups.
>
> > Regarding open ToDos, here are my favorites:
> >
> > - I see GetLegendGraphic requests still not working:
> http://www.geodaten-mv.de/dienste/inspirevs_test?language=ger&version=1.3.0&service=WMS&request=GetLegendGraphic&sld_version=1.1.0&layer=TN.RailTransportNetwork.RailwayArea&format=image/png&STYLE=inspire_common:DEFAULT
> >
> Strange, GetLegendGraphic requests are working nicely in the test
> mapfile I generated from your one.
>
> > - The testsuite I use expects Content-Type application/vnd.ogc.gml
> instead of text/xml for GML-GetFeatureInfo responses. This has to be verified.
> >
> I agree.
>
> > - AuthorityURL and Identifier may be quired at rootlayer, too
> >
> You mean at service level and root layer?
>
> > - Map -> Web -> wms_metadataurl should be renamed to
> wms_inspiremetadaurl and Map -> Web -> wms_metadataurl should be available for the root layer.
> >
> Do you need the metadataurl only for the root layer?
>
> > - Handling of keywords should be revised. Instead of wms_inspire_keyword
> we should talk about wms_keywordvocabulary "ISO" and so parse
> wms_keywordlist and wms_keywordlist_ISO.
> >
> I agree, keywork handling needs some attention. If you have a good
> proposal I'd be happy to integrate it :)
>
> > - Style Title should be multilingual, too.
> >
> OK, that shouldn't be too difficult.
> >
> >
> > I can start with the AuthorityURL and MetadataUrl topics. Someone who
> can investigate into the GetLegendGraphic problem?
>
> Great, many thanks! As said GetLegendGraphic requests are working for
> me, so need to reproduce your problem first. Any ideas?
>
> cu
> Stephan
>
> >
> > Best regards,
> > Martin
> >
> > -------- Original-Nachricht --------
> > > Datum: Tue, 03 Jan 2012 15:02:16 +0100
> > > Von: "Stephan Meißl" <stephan at meissl.name>
> > > An: "Nash, Edward" <E.Nash at dvz-mv.de>
> > > CC: "mapserver-inspire at lists.osgeo.org"
> <mapserver-inspire at lists.osgeo.org>
> > > Betreff: Re: AW: AW: AW: [Mapserver-inspire] MapServer and INSPIRE
> >
> > > Hi Edward,
> > >
> > > finally I found some time to look into the test data and mapfile -
> this
> > > is really great, thanks a lot!
> > >
> > > I've added the test data and your mapfile adjusted to the current
> > > sandbox [1].
> > >
> > > Note that I've been working in the sandbox and implemented support for
> > > named group layers via "wms_layer_group" (see separate mail to the
> > > list). Could you maybe have a look at this implementation and see
> which
> > > of your ToDos still persist? I'd appreciate if we could share some
> tasks
> > > based on this ToDos. Thanks for your offer!
> > >
> > > cu
> > > Stephan
> > >
> > > [1] http://trac.osgeo.org/mapserver/changeset/12942
> > >
> > >
> > > On Fri, 2011-12-09 at 21:26 +0100, Nash, Edward wrote:
> > > > Hi Stephan & INSPIRE-listers,
> > > >
> > > > my colleagues have been busy and have produced some test data which
> > > conform to the INSPIRE data specs for transport networks, slightly
> denormalised
> > > to get a sane table/file structure, and an accompanying (heavily
> > > commented) Mapfile for use with the current INSPIRE sandbox version.
> Furthermore we
> > > have put up a public demo view service based on this which we will
> endeavor
> > > to keep updated as the sandbox version is changed.
> > > >
> > > > The ZIP archive of the data (Shapefiles, we thought these would be
> best
> > > for including in msautotest) is attached to ticket #3608, where the
> demo
> > > service and the Mapfile are also linked (see
> > > http://trac.osgeo.org/mapserver/ticket/3608#comment:17 from mko).
> > > >
> > > > For the impatient, here are the direct links:
> > > > Demo view service: http://www.geodaten-mv.de/dienste/inspirevs_test
> > > > Mapfile for demo:
> http://www.geodaten-mv.de/dienste/inspirevs_test.map
> > > > Demo dataset:
> > >
> http://trac.osgeo.org/mapserver/raw-attachment/ticket/3608/inspirevs_tn.zip
> > > >
> > > > The demo VS has been tested using two publicly available test
> suites;
> > > the results are documented in the header comments in the Mapfile,
> along with
> > > some TODOs. The most important of these to our mind are:
> > > > - the root layer and grouped layers should automatically be of type
> > > UNION, in order to better supply the required metadata.
> > > > - UNION layers should support multiple geometries in order to reduce
> the
> > > various GROUP/wms_layer_group configurations.
> > > > - MetadataURL and inspire_common:MetadataURL should be two different
> > > things, set separately (affects root layer / service metadata).
> > > > - Similarly, keyword_iso doesn't replace keywordlist.
> > > > - LegendURL and Identifier/AuthorityUrl for the root layer don't
> work.
> > > >
> > > > There are also issues with the inheritance of attributes through the
> > > layer hierarchy, but these can probably be ignored as they are
> "features
> > > rather than bugs".
> > > >
> > > > Let me know if this small set of test data is sufficient for the
> needs
> > > msautotest, or any other feedback on our results.
> > > > Regarding the further work required, much of it is in any case
> fairly
> > > straightforward and we currently have capacity to work some of these
> things
> > > ourselves - but naturally don't want to duplicate effort if you or
> someone
> > > else is already working on the same tasks. Maybe we can split the
> tasks up
> > > into packages (e.g. metadata, layer structure, etc.) and we'll take on
> a
> > > package to keep things moving along?
> > > >
> > > > Regards,
> > > >
> > > > Edward
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Stephan Meißl [mailto:stephan at meissl.name]
> > > > Gesendet: Dienstag, 8. November 2011 15:26
> > > > An: Nash, Edward
> > > > Cc: mapserver-inspire at lists.osgeo.org
> > > > Betreff: Re: AW: AW: [Mapserver-inspire] MapServer and INSPIRE
> > > >
> > > > Edward,
> > > >
> > > > thanks again for your answer and offer. If you could provide some
> test
> > > > data in the INSPIRE structure that would be great. We would include
> this
> > > > data in msautotest for some INSPIRE tests where you could verify the
> > > > results in turn.
> > > >
> > > > Thanks,
> > > > Stephan
> > > >
> > > >
> > > > On Wed, 2011-11-02 at 11:57 +0100, Nash, Edward wrote:
> > > > > Hi Stephan,
> > > > >
> > > > > now it's my turn to be tardy - apologies.
> > > > >
> > > > > Unfortunately neither we nor our customers have any real world
> data
> > > which we can offer - however we could generate some data in the
> INSPIRE
> > > structures (e.g. transport networks) if this would be a viable
> alternative.
> > > > >
> > > > > We would be happy to look at checking the keys or the layers: we
> are
> > > familiar with the codebase and the specifications, and we don't expect
> any
> > > major surprises there. As previously written we could donate some time
> for
> > > this.
> > > > >
> > > > > Let me know if you want to take up any of these offers: I will get
> > > back to you sooner this time.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Edward
> > > > >
> > > > > -----Ursprüngliche Nachricht-----
> > > > > Von: Stephan Meißl [mailto:stephan at meissl.name]
> > > > > Gesendet: Dienstag, 11. Oktober 2011 17:07
> > > > > An: Nash, Edward
> > > > > Cc: mapserver-inspire at lists.osgeo.org
> > > > > Betreff: Re: AW: [Mapserver-inspire] MapServer and INSPIRE
> > > > >
> > > > > Edward,
> > > > >
> > > > > sorry for my quite late response, I promise to be more responsive
> now
> > > > > that this deadline I was working on is over.
> > > > >
> > > > > The main points are to check the usage of metadata keys (syntax
> for
> > > > > keys, reporting of missing keys, etc.) and the arbitrary grouping
> of
> > > > > layers to any depth.
> > > > >
> > > > > One point where we definitely would need some help is in testing
> and
> > > > > test data. During the summer of code project we asked for some
> real
> > > > > world demo datasets for the msautotest test suite but so far we
> don't
> > > > > have any. Could you maybe help out here?
> > > > >
> > > > > Thanks,
> > > > > Stephan
> > > > >
> > > > >
> > > > > On Thu, 2011-09-29 at 10:57 +0200, Nash, Edward wrote:
> > > > > > Hi Stephan,
> > > > > >
> > > > > > have you got some documentation of exactly what the adjustments
> are
> > > which have been identified?
> > > > > >
> > > > > > We can't help with funding, but we could put some developer time
> > > into this to get it moving forward - others may be in a similar
> position. We'd
> > > rather put our time into something which is going in the "right"
> direction
> > > though, rather than just producing patches which are good enough to do
> a
> > > job for us but otherwise disappear into trac never to make it to
> trunk.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Edward
> > > > > >
> > > > > > -----Ursprüngliche Nachricht-----
> > > > > > Von: mapserver-inspire-bounces at lists.osgeo.org
> > > [mailto:mapserver-inspire-bounces at lists.osgeo.org] Im Auftrag von
> Stephan Meißl
> > > > > > Gesendet: Dienstag, 27. September 2011 14:49
> > > > > > An: Martin Kofahl
> > > > > > Cc: mapserver-inspire at lists.osgeo.org
> > > > > > Betreff: Re: [Mapserver-inspire] MapServer and INSPIRE
> > > > > >
> > > > > > All,
> > > > > >
> > > > > > Stefan did a great job in the summer-of-code project. However,
> the
> > > code
> > > > > > needs some polishing here and there e.g. at the code sprint in
> > > Denver we
> > > > > > discussed some adjustments that are needed.
> > > > > >
> > > > > > The major remaining part for full INSPIRE compatibility, as far
> as I
> > > > > > understand, is the support for arbitrary grouping of layers to
> any
> > > > > > depth. I need to take a closer look at ticket #1632 to seriously
> > > > > > calculate the remaining work.
> > > > > >
> > > > > > Anyway, we'd definitely be willing to look into this but some
> > > funding
> > > > > > would be very much appreciated :).
> > > > > >
> > > > > > cu
> > > > > > Stephan
> > > > > >
> > > > > >
> > > > > > On Tue, 2011-09-27 at 13:59 +0200, Martin Kofahl wrote:
> > > > > > > Thomas,
> > > > > > > can you give an outline about remaining work? I see union
> layers
> > > finished, concept for multilingualism existing, ...
> > > > > > >
> > > > > > > Kind regards,
> > > > > > > Martin
> > > > > > >
> > > > > > > -------- Original-Nachricht --------
> > > > > > > > Datum: Mon, 26 Sep 2011 17:38:33 +0200
> > > > > > > > Von: thomas bonfort <thomas.bonfort at gmail.com>
> > > > > > > > An: "Passmore, James H." <jpass at bgs.ac.uk>
> > > > > > > > CC: "mapserver-inspire at lists.osgeo.org"
> > > <mapserver-inspire at lists.osgeo.org>
> > > > > > > > Betreff: Re: [Mapserver-inspire] MapServer and INSPIRE
> > > > > > >
> > > > > > > > James,
> > > > > > > > trunk will be entering release-mode at the beginning of
> 2012, so
> > > the
> > > > > > > > actual release would probably be around end of february.
> > > > > > > > Speaking of inspire specifically, at the code sprint in
> Denver
> > > we came
> > > > > > > > to the conclusion that we are in a rather desperate need of
> > > funding to
> > > > > > > > finish off the work that was started during the
> summer-of-code
> > > program
> > > > > > > > so that the inspire features can be cleanly integrated for
> the
> > > next
> > > > > > > > release. If you or any other organization following this
> list is
> > > in a
> > > > > > > > position to help with funding, please do speak up on this
> list
> > > so we
> > > > > > > > can get this rolling. I would also imagine that an earlier
> > > release
> > > > > > > > containing only the inspire improvements could be a
> possibility.
> > > > > > > >
> > > > > > > > best regards,
> > > > > > > > thomas
> > > > > > > >
> > > > > > > > On Mon, Sep 26, 2011 at 17:27, Passmore, James H.
> > > <jpass at bgs.ac.uk> wrote:
> > > > > > > > > I'm not sure if I ever believe the MapServer roadmap (or
> maybe
> > > I just
> > > > > > > > don't understand what it's telling me). Can anyone provide
> a
> > > heads up as
> > > > > > > > when MapServer 6.2 might be released? And importantly will
> it
> > > be the first
> > > > > > > > WMS server software to support INSPIRE multi-lingual
> services?
> > > > > > > > >
> > > > > > > > > thanks
> > > > > > > > >
> > > > > > > > > James
> > > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: mapserver-inspire-bounces at lists.osgeo.org
> > > > > > > > [mailto:mapserver-inspire-bounces at lists.osgeo.org] On Behalf
> Of
> > > Daniel Morissette
> > > > > > > > > Sent: Monday, April 18, 2011 3:59 AM
> > > > > > > > > To: mapserver-inspire at lists.osgeo.org
> > > > > > > > > Subject: Re: [Mapserver-inspire] MapServer and INSPIRE
> > > > > > > > >
> > > > > > > > > On 11-04-16 03:08 PM, Martin Kofahl wrote:
> > > > > > > > >> Thanks to James, I could easily extend the
> GetCapabilities
> > > output for
> > > > > > > > scenario 1 and focused on multi-language support for now. We
> > > could take
> > > > > > > > advantage of MapServer variable substitution from url.
> > > > > > > > >>
> > > > > > > > >> Please take a look at
> > > > > > > > http://trac.osgeo.org/mapserver/ticket/3608#comment:11
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > > I see that you raised priority on the ticket, possibly in
> the
> > > hope that
> > > > > > > > > we can fit this in 6.0? This caught the attention of the
> > > release
> > > > > > > > > manager. ;-)
> > > > > > > > >
> > > > > > > > > Unfortunately I think it's too late to put this in 6.0 and
> > > this should
> > > > > > > > > be pushed to 6.2. Note that there are talks of doing a 6.2
> in
> > > the summer
> > > > > > > > > (definitely before FOSS4G) so the delay would not be too
> long.
> > > In the
> > > > > > > > > meantime users who require this level of INSPIRE support
> could
> > > apply the
> > > > > > > > > patch locally, but there are a few reasons why I think we
> > > should wait
> > > > > > > > > until 6.2 for the official release of this code:
> > > > > > > > >
> > > > > > > > > 1- We are way past the 6.0 feature freeze and this is
> clearly
> > > a new
> > > > > > > > > feature and not a bug fix
> > > > > > > > >
> > > > > > > > > 2- Unless I'm mistaken, this patch addresses only a subset
> of
> > > the
> > > > > > > > > INSPIRE requirements and may not be compatible with a more
> > > complete
> > > > > > > > > solution that would come in 6.2 to more widely address
> INSPIRE
> > > > > > > > > requirements (what this mapserver-inspire group needs to
> work
> > > on)...
> > > > > > > > > what I mean is that once something like this is released,
> it
> > > will be
> > > > > > > > > nearly impossible to take it out, so I'd rather wait until
> we
> > > have a
> > > > > > > > > solid solution instead of putting something in that we may
> > > have to take
> > > > > > > > > back out later.
> > > > > > > > >
> > > > > > > > > What do others think?
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Daniel Morissette
> > > > > > > > > http://www.mapgears.com/
> > > > > > > > > Provider of Professional MapServer Support since 2000
> > > > > > > > > _______________________________________________
> > > > > > > > > Mapserver-inspire mailing list
> > > > > > > > > Mapserver-inspire at lists.osgeo.org
> > > > > > > > > http://lists.osgeo.org/mailman/listinfo/mapserver-inspire
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > This message (and any attachments) is for the recipient
> only.
> > > NERC
> > > > > > > > > is subject to the Freedom of Information Act 2000 and the
> > > contents
> > > > > > > > > of this email and any reply you make may be disclosed by
> NERC
> > > unless
> > > > > > > > > it is exempt from release under the Act. Any material
> supplied
> > > to
> > > > > > > > > NERC may be stored in an electronic records management
> system.
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > Mapserver-inspire mailing list
> > > > > > > > > Mapserver-inspire at lists.osgeo.org
> > > > > > > > > http://lists.osgeo.org/mailman/listinfo/mapserver-inspire
> > > > > > > > >
> > > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Mapserver-inspire mailing list
> > > > > > > > Mapserver-inspire at lists.osgeo.org
> > > > > > > > http://lists.osgeo.org/mailman/listinfo/mapserver-inspire
> > > > > > > _______________________________________________
> > > > > > > Mapserver-inspire mailing list
> > > > > > > Mapserver-inspire at lists.osgeo.org
> > > > > > > http://lists.osgeo.org/mailman/listinfo/mapserver-inspire
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Mapserver-inspire mailing list
> > > > > > Mapserver-inspire at lists.osgeo.org
> > > > > > http://lists.osgeo.org/mailman/listinfo/mapserver-inspire
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Mapserver-inspire mailing list
> > > Mapserver-inspire at lists.osgeo.org
> > > http://lists.osgeo.org/mailman/listinfo/mapserver-inspire
>
>
More information about the Mapserver-inspire
mailing list