-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
New Release v1.48.2 - #patch #1142
Commits on Nov 26, 2024
-
PB-1221 : partially out of bound KML was ignored entirely
The KML extent detection was not performing as expected with KML that had only one dimension out of LV95 bounds. To counteract that, I've reverted the logic in the extent calculation, transforming LV95 bounds into WGS84 to do the matching instead of transforming a potentially big WGS84 extent to LV95 (lead to big math error...)
Configuration menu - View commit details
-
Copy full SHA for 42ea977 - Browse repository at this point
Copy the full SHA 42ea977View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9a9c1f6 - Browse repository at this point
Copy the full SHA 9a9c1f6View commit details -
PB-1211 : do not add ; if layer with feature selection is alone
When opening the app with a layerId=featureId URL param, the ; was still added to the layers URL param after processing the feature pre-selection. This means the layers URL param was malformed and an error showed up.
Configuration menu - View commit details
-
Copy full SHA for 4e091ae - Browse repository at this point
Copy the full SHA 4e091aeView commit details -
Merge pull request #1140 from geoadmin/bug-PB-1211-more-link-issue
PB-1211 : do not add ; if layer with feature selection is alone
Configuration menu - View commit details
-
Copy full SHA for f501424 - Browse repository at this point
Copy the full SHA f501424View commit details -
PB-1222 : fix mishandling of feature ID that are "number-like"
some feature IDs ends with something like "1314.070" and the layer parsing code was transforming them into number, removing the trailing zero from the ID. This broke many "Link to object" link generated by the backend. Also fixing an issue with the time slider warning not being wrapped in an array, and generating a crash when its value was not set to something valid
Configuration menu - View commit details
-
Copy full SHA for d0fae6a - Browse repository at this point
Copy the full SHA d0fae6aView commit details -
Merge pull request #1141 from geoadmin/fix-PB-1222-broken-link-to-object
PB-1222 : fix mishandling of feature ID that are "number-like"
Configuration menu - View commit details
-
Copy full SHA for 6180886 - Browse repository at this point
Copy the full SHA 6180886View commit details -
Configuration menu - View commit details
-
Copy full SHA for a654fc0 - Browse repository at this point
Copy the full SHA a654fc0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 64cf53f - Browse repository at this point
Copy the full SHA 64cf53fView commit details -
Merge pull request #1137 from geoadmin/fix-pb-1128-permalink-problem
PB-1128: fix permalink custom attributes
Configuration menu - View commit details
-
Copy full SHA for 0e9fc33 - Browse repository at this point
Copy the full SHA 0e9fc33View commit details