We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
mcf uses a plain number for crs at
pygeometa/sample.yml
Line 54 in 335e1b8
this probably assumes the epsg: prefix, but what happens if a crs uses a different prefix? like esri: crs:
wouldn't it be better to allow a prefix, and assume 'epsg:' if none is given (backwards compat)
this actually contradicts the schema, which indicates a full uri as default value
pygeometa/pygeometa/schemas/mcf/core.yaml
Line 250 in 4c20962
The text was updated successfully, but these errors were encountered:
No branches or pull requests
mcf uses a plain number for crs at
pygeometa/sample.yml
Line 54 in 335e1b8
this probably assumes the epsg: prefix, but what happens if a crs uses a different prefix? like esri: crs:
wouldn't it be better to allow a prefix, and assume 'epsg:' if none is given (backwards compat)
this actually contradicts the schema, which indicates a full uri as default value
pygeometa/pygeometa/schemas/mcf/core.yaml
Line 250 in 4c20962
The text was updated successfully, but these errors were encountered: