SV: [Mapserver-inspire] MapServer and INSPIRE

Thomas Ellett Thomas.Ellett at
Mon Apr 18 03:17:39 EDT 2011

Hi All, I'd agree with Daniel's thinking on this, especially in light of the fact that the May 9th deadline has now been taken off the INSPIRE Roadmap, so I presume the new date to aim for is November 9th when view and discovery services must be operational. Therefore to aim for a 6.2 summer release with a complete solution seems to be a good option.

Tom Ellett von Brasch
Senior Engineer
Norwegian Mapping Authority
Telephone + 47 45 80 64 02
Mobile + 47 45 80 64 02
E-mail:Thomas.Ellett at 
DISCLAIMER: This e-mail message and any attachments are confidential and may be privileged or otherwise protected by legal rules, and for use by the addressee only. If the message is received by anyone other than the addressee, please delete it and any attachments from your computer without copying it or disclosing its contents to anyone. Whilst all reasonable care has been taken to avoid the transmission of viruses, no responsibility is accepted in this regard and the recipient should scan and carry out such other checks as it considers appropriate.

-----Opprinnelig melding-----
Fra: mapserver-inspire-bounces at [mailto:mapserver-inspire-bounces at] På vegne av Daniel Morissette
Sendt: 18. april 2011 04:59
Til: mapserver-inspire at
Emne: 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

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
Provider of Professional MapServer Support since 2000
Mapserver-inspire mailing list
Mapserver-inspire at

More information about the Mapserver-inspire mailing list