feat(crs): accept EPSG:xxxx shorthand in the crs query parameter - #2431
Open
C1-BA-B1-F3 wants to merge 5 commits into
Open
C1-BA-B1-F3 wants to merge 5 commits into
C1-BA-B1-F3 wants to merge 5 commits into
Conversation
PostgreSQL and MongoDB managers ignored the limit and offset parameters, returning all jobs regardless of the query string. Apply offset before limit in both backends, matching the existing TinyDB behaviour. Fixes geopython#2426
…ints The tilematrixsets and tilematrixset HTML handlers passed api.tpl_config as the template configuration, but that dict carries the full server config (including 'server') and lacks the 'path' key that render_j2_template expects. The lookup therefore always fell back to the default templates, ignoring any custom theme. Pass api.config['server']['templates'] instead, matching every other render_j2_template call site. Fixes geopython#2422
…DBAPI A provider configured with a bare connection string (e.g. "postgresql://user@host/db") resolved to SQLAlchemy's default DBAPI for that backend — psycopg (v3) for PostgreSQL. Deployments that only install psycopg2 then fail with 'ModuleNotFoundError: No module named psycopg' even though the provider pins 'postgresql+psycopg2'. When the caller's URL has no '+driver' suffix and the provider's driver_name does, rewrite the URL's drivername to the pinned one. Fixes geopython#2424
…bsent The MapScript provider only read options.projection, ignoring the documented storage_crs configuration. Deployments that set storage_crs (like every other provider) silently got EPSG:4326, producing empty images for data in any other projection. Use storage_crs when options.projection is not set; the legacy options.projection override still wins when present so existing workarounds keep working. Fixes geopython#2400
The crs parameter only accepted the full URI form (http://www.opengis.net/def/crs/EPSG/0/28992); the common shorthand EPSG:28992 was rejected with 'CRS not supported for this collection'. Normalize an EPSG:xxxx query parameter to the canonical URL before matching against the supported-CRS list, so both forms work. Fixes geopython#2375
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
crsquery parameter only accepted the full URI form:The common shorthand
?crs=EPSG:28992was rejected withCRS 'EPSG:28992' not supported for this collection, even though it denotes the same CRS.Fix
Add
normalize_crs_uriwhich converts anEPSG:xxxxshorthand to the canonical URL before matching against the supported-CRS list. Non-EPSG inputs (URNs, URLs, custom identifiers) pass through unchanged.Test plan
Fixes #2375