You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if we need to create the calculated variables?
We shouldn't be creating project cards for them so I'm wondering what the reasoning was?
If the reason is because we are reading in a log-file with calculated properties, then we should just ignore those properties as that would probably be a lot quicker than doing a bunch of GIS joins and we are starting to have issues with performance.
@e-lo Because Lasso was used to write out project cards for base network correction, e.g. John found links with assign_group to be corrected in his QA/QC process.
Ok. - Since this seems to be taking a bunch of time I'm going to make this an optional flag.
e-lo
changed the title
? Do we need "calculated variables" to create project card?
Don't need "calculated variables" to be calculated every time we create project card.
Jun 10, 2020
- Project changes now broken out into a few methods.
- More error catching and general robustness in project creation/ log file processing methods.
- Doesn't do geo calculations by default but can do if flagged with a keyword (Fixes#81 )
- Added tests for csv and shp project changes read-in
TODO:
- Update test csv and shp files to be regular fields (not calculated)
- Add test for new util method
- Do some testing to make sure errors are obvious for all likely problematic inputs.
I'm wondering if we need to create the calculated variables?
We shouldn't be creating project cards for them so I'm wondering what the reasoning was?
If the reason is because we are reading in a log-file with calculated properties, then we should just ignore those properties as that would probably be a lot quicker than doing a bunch of GIS joins and we are starting to have issues with performance.
Lasso/lasso/project.py
Line 231 in 6bdfecc
The text was updated successfully, but these errors were encountered: