[Auto-affectation] Prise en compte de format wkt spécifique #3589
Conversation
This file contains 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
|
hmeneuvrier
approved these changes
Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket
#3588
Description
Certaines zones au format WKT ne sont pas prises en compte correctement.
Exemple :
MULTIPOLYGON (((X1 Y1, X2 Y2),(X3 Y3, X4 Y4)))Il y a un tableau à un seul élément imbriqué (alors qu'on cherche à récupérer directement cet élément comme une liste.
Cela provoque une erreur d'analyse.
Et comme l'enregistrement en bdd (
flush) de la géolocalisation est fait après, certaines géolocalisation sont mal initialisées dans ce cas.Changements apportés
flushavant de faire l'auto-affectation (pour au moins enregistrer la géolocalisation)Tests