Skip to content
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

Anonymous incore client #451

Open
longshuicy opened this issue Nov 27, 2023 · 2 comments
Open

Anonymous incore client #451

longshuicy opened this issue Nov 27, 2023 · 2 comments
Assignees
Labels
3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem

Comments

@longshuicy
Copy link
Member

longshuicy commented Nov 27, 2023

  1. Allow empty or anonymous incore client
  2. Remove any interaction with remote services
  3. Double check if all analyses and utility functions still run
  4. Check its impact on pyincore-viz
@longshuicy longshuicy added the 3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem label Nov 27, 2023
@longshuicy
Copy link
Member Author

longshuicy commented Nov 28, 2023

We still have at least a few place that talks to the remote service to get the demand units and demand types. Anywhere that uses def get_allowed_demands(self, hazard_type, timeout=(30, 600), **kwargs)

Analysis being affected by are:
pipelinedamage.py
buildingdamage.py
nonstructbuildingdamage.py

This is resolved

@longshuicy
Copy link
Member Author

longshuicy commented Nov 28, 2023

Some of the pyincore-viz method assumes wms layer on geoserver. Need to find out what they are and what's the implication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem
Projects
None yet
Development

No branches or pull requests

1 participant