Hi Willem, yes please file the issue there, I will fix it in the source
now. thanks, -jeff
On 2025-04-15 7:30 a.m., Willem Jenniskens via MapServer-dev wrote:
Thanks, I am not really familiar with open source development. But I
think this should be fixed in the source on github, right?
Should I create an 'issue' on https://github.com/MapServer/MapServer/
issues <https://github.com/MapServer/MapServer/issues> or something else?
------------------------------------------------------------------------
*Van:* MapServer-dev <[email protected]> namens
Gérald Fenoy via MapServer-dev <[email protected]>
*Verzonden:* dinsdag 15 april 2025 10:57
*Aan:* Sebastiaan Couwenberg <[email protected]>
*CC:* [email protected] <[email protected]>
*Onderwerp:* Re: [MapServer-dev] ogcapi.cpp 404 on https://
raw.githubusercontent.com/opengeospatial/ogcapi-processes/master/core/
openapi/schemas/exception.yaml
Hi,
You can also use the official schemas directory below:
https://schemas.opengis.net/ogcapi/common/part1/1.0/openapi/schemas/
exception.yaml <https://schemas.opengis.net/ogcapi/common/part1/1.0/
openapi/schemas/exception.yaml>
Best regards
Gérald Fenoy
Le 15 avr. 2025 à 10:35, Sebastiaan Couwenberg via MapServer-dev
<[email protected]> a écrit :
On 4/15/25 9:06 AM, Willem Jenniskens via MapServer-dev wrote:
In mapogcapi.cpp this url is present:
https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/
master/core/openapi/schemas/exception.yaml <https://
raw.githubusercontent.com/opengeospatial/ogcapi-processes/master/core/
openapi/schemas/exception.yaml>
It gives 404. I think it should be:
https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/
master/openapi/schemas/common-core/exception.yaml <https://
raw.githubusercontent.com/opengeospatial/ogcapi-processes/master/
openapi/schemas/common-core/exception.yaml>
or
https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/refs/
heads/master/openapi/schemas/common-core/exception.yaml <https://
raw.githubusercontent.com/opengeospatial/ogcapi-processes/refs/heads/
master/openapi/schemas/common-core/exception.yaml>
Do you agree? What is the best way to do this?
Using one of the tags should be a more stable ref than master, e.g.:
https://raw.githubusercontent.com/opengeospatial/ogcapi-processes/refs/
tags/1.0-draft.6/core/openapi/schemas/exception.yaml <https://
raw.githubusercontent.com/opengeospatial/ogcapi-processes/refs/tags/1.0-
draft.6/core/openapi/schemas/exception.yaml>
A specific commit should also be stable:
https://raw.githubusercontent.com/opengeospatial/ogcapi-
processes/6f4945ed158fa064bb75a0f11d24c8f683f2fb6b/core/openapi/schemas/
exception.yaml <https://raw.githubusercontent.com/opengeospatial/ogcapi-
processes/6f4945ed158fa064bb75a0f11d24c8f683f2fb6b/core/openapi/schemas/
exception.yaml>
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
_______________________________________________
MapServer-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev <https://
lists.osgeo.org/mailman/listinfo/mapserver-dev>
_______________________________________________
MapServer-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev <https://
lists.osgeo.org/mailman/listinfo/mapserver-dev>
_______________________________________________
MapServer-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
--
Jeff McKenna
GatewayGeo: Developers of MS4W, & offering MapServer Consulting/Dev
co-founder of FOSS4G
http://gatewaygeo.com/
_______________________________________________
MapServer-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
