-
Notifications
You must be signed in to change notification settings - Fork 0
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
Skeleton #9
Closed
Closed
Skeleton #9
Changes from 23 commits
Commits
Show all changes
69 commits
Select commit
Hold shift + click to select a range
dd2f342
skeleton fixed
MichelDaab 271836c
before pruning lines
MichelDaab 75cc05a
works but too slow
MichelDaab 59bd099
save before creation of the Branch class
MichelDaab 4265cf0
Intermediary commit
MichelDaab 1feaf72
acceptable result
MichelDaab e7a11c0
gap closed from mask
MichelDaab 822403b
closing gaps by proximity to mask
MichelDaab 25fe0c1
whole skeleton process works, no test yet
MichelDaab d64bb34
Clean version to create skeleton,
MichelDaab e69c9a5
forget to remove a line
MichelDaab bfc4969
Change to add DB credentials as GITHUB secrets
MichelDaab 316a8c7
add dot_env for local variables (like passwords)
MichelDaab c7e24ca
unittesting for git action
MichelDaab f29eb49
change gitignore
MichelDaab 26f16e5
fix typo for credentials in ci.yaml
MichelDaab 9a77787
Some corrections following PR comments
MichelDaab d16339c
Refacto README, Dockerfile and test
mdupaysign 275b5d1
Fix readme layout
leavauchier 8208f0d
Update lidro/create_mask_hydro/rasters/create_mask_raster.py
mdupaysign 8ec7df3
Update lidro/create_mask_hydro/rasters/create_mask_raster.py
mdupaysign 6172944
Update create_mask_raster.py
mdupaysign 126798a
Update lidro/create_mask_hydro/rasters/create_mask_raster.py
mdupaysign f2f67cf
update main_merge_mask.py
mdupaysign 690461a
refacto with Lea
mdupaysign 8e09393
manual correction for rebase
MichelDaab 6c9ad27
move main_skeleton into lidro
MichelDaab 7a523c0
merge skeleton lines at the end
MichelDaab e578b35
fix final merge lines
MichelDaab 162992e
adding some tests
MichelDaab 973e3be
remove launch.json
MichelDaab 400e84d
better path (...maybe ???)
MichelDaab e9bc6a0
specify the WATER_MIN_SIZE parameter
MichelDaab f6f8aa1
more explanation for WATER_MIN_SIZE parameter
MichelDaab 6a50fd5
To create skeleton lines, we only care
MichelDaab 6cc70f6
fix to tests to match the changes of
MichelDaab 4154e7d
small fix in case there is no bridge
MichelDaab 8cf1c15
fix a rare case
MichelDaab fc9925f
change request to database to be sligthly faster
MichelDaab 74e5627
add a test for the db query, only played
MichelDaab 90dd93b
Merge branch 'dev' into skeleton
MichelDaab a2b2ca8
adding an example for create skeleton lines
MichelDaab 5677001
removed a forgotten comment
MichelDaab 5d7230f
changes according to Palvina's code review
MichelDaab 5331b8a
removing files coming from God knows where
MichelDaab 7c09772
removing .env
MichelDaab 7c69a40
adding "null" to some config values to be consistent
MichelDaab 2fe5a40
add null to config str to be consistent
MichelDaab ca9c0b9
a strange case of problem with git merge,
MichelDaab edc195b
moved the "make valid" at the beginning,
MichelDaab 80f3c41
removed an unnecessary copy
MichelDaab 76487b7
removed a typo and a log file that has no
MichelDaab eaeb81b
Set the UPPERCASE of configs to lowercase
MichelDaab 8e9bda8
changes to code from dev that have been
MichelDaab 77d99a0
Update of the readme.md for the location of
MichelDaab 7e2c66d
get the right submodule data
MichelDaab d9b9f7d
removing "ci" directory, that has no business
MichelDaab 58c64fc
changing test name to be more explicit
MichelDaab 04521c3
correction of a modification on
MichelDaab 34684de
add a test to branch
MichelDaab ac91fa1
revert some changes that a misuse of git created
MichelDaab 89e7085
fix a typo
MichelDaab 86e4050
fix a previous unwanted change
MichelDaab ef1aa3e
fix another unwanted change
MichelDaab f94c7ee
changes so all submodules can be run with
MichelDaab d977f10
moving input/ouptut files from skeleton.filepth to
MichelDaab a0870d0
Add the possibility to disable db connection
MichelDaab 109f43f
Add another test to branch
MichelDaab 1130aef
add small comment about db_using_db
MichelDaab File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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
This file was deleted.
Oops, something went wrong.
MichelDaab marked this conversation as resolved.
Show resolved
Hide resolved
|
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
Submodule data
updated
from c9398e to 19f969
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
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
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
leavauchier marked this conversation as resolved.
Show resolved
Hide resolved
|
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Effectivement sur Github les codes ne doivent pas être rendu publique ! Il va falloir en discuter, l'idée serait peut-être de fournir un shapefile ou geojson des données vectorielles que tu as besoin afin que quelqu'un en externe puisse également lancer le code. a discuter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
J'interroge la présence de pont sur des endroits où je soupçonne qu'on peut prolonger l'eau. Ce n'est pas possible de préparer les données à l'avance, à moins de vouloir faire à chaque fois un shapefile avec tous les ponts du bloc traité
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Est-ce que c'est envisageable (dans une autre MR) de rendre ça plus indépendant de la base de donnée, pour que les externes puissent utiliser la BDTOPO ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MichelDaab
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Si la base de données a la même structure, c'est déjà possible de changer d'adresse de base de données dans le fichier config.
Si la base de données a une structure différente, cela veut dire que la requête est différente. Au mieux on peut peut-être rendre la requête configurable, mais cela demanderait des acrobaties étrange car il faudrait mettre dans la config des strings qui peuvent être parsées pour y injecter les valeurs utilse pour l'interrogation de la nouvelle base.
Cela me semble être un casse-tête qui ne se justifie pas car on ne va pas avoir une nouvelle base avec une nouvelle structure tous les quatre matins, c'est sans doute plus facile d'écrire les requêtes en amont pour chaque base qu'on envisage, et de rajouter un switch dans la config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Et mettre la requête dans un fichier sql à part (en rendant le chemin vers le fichier paramétrable) pour que quelqu'un qui veut changer la requête puisse le faire facilement ? A quel point c'est faisable / facile ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
La difficulté principale c'est qu'il faut injecter dans la requête les coordonnées d'une ligne pour savoir si cette ligne croise un pont existant. Donc il faut en quelque sorte trouver un moyen pour rendre la requête dynamique, sans savoir par avance quelle tête elle aura.
Par exemple, voilà une partie d'une des deux requête sql qui existent :
"AND ST_Intersects(ST_Force2D(geometrie), ST_GeomFromText('[AJOUTER LIGNE ICI]'))"
On peut envisager de faire une substitution d'une chaine particulière décidée à l'avnace, par exemple [LINE ICI].
Et il faut le faire deux fois, une fois pour les ponts linéaires, une fois pour les ponts surfaciques. Donc en plus on se rajoute l'éventualité d'un nombre quelconque de requête, peut-être juste une, peut-être trois...
Et à côté de cela il faut pouvoir expliquer à l'utilisateur ce mécanisme interne pour qu'il puisse modifier sa requête en fonction des modalités de notre "dynamiqueur" pour qu'elle puisse être lu, puisque c'est lui qui au final écrira sa requête.
Dans l'exemple au-dessus, il faut que l'utilisateur ait bien compris où mettre [LINE ICI], que c'est à l'intérieur d'une parenthèse de la fonction "ST_GeomFromText" qu'il aura ajouté, et ainsi de suite.
Pour moi cela m'a tout l'air d'être une usine à gaz, et que si on veut d'autres BD il sera plus simple d'écrire nous-même une requête idoine pour chaque
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Effectivement... ça a pas l'air si facile finalement (j'avais pas pensé à la partie interactive). Tant pis
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mdupaysign C'est bon pour toi pour la question initiale ? Normalement les codes ne sont plus là