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

Migrate or Remove Nancy API & Associated SOE #412

Closed
steveoh opened this issue Nov 17, 2020 · 2 comments
Closed

Migrate or Remove Nancy API & Associated SOE #412

steveoh opened this issue Nov 17, 2020 · 2 comments

Comments

@steveoh
Copy link
Member

steveoh commented Nov 17, 2020

The API provides:

  • simplified queries on the client-side
  • location- and temporal-based authorization

We could update the client-side code to make separate queries to the individual feature services for each query layer.

I hope that authentication will be gone at some point.

We need to decide if we want to migrate the API to a GCP function or if we can get rid of it altogether.

https://github.com/NancyFx/Nancy is no longer maintained and should be migrated to the latest microsoft .net 5 web api framework and hosted as a GCP function.

@stdavis stdavis changed the title migrate unmaintained nancy api to .net 5 Migrate or Deprecate Nancy API & Associated SOE Apr 27, 2022
@stdavis stdavis changed the title Migrate or Deprecate Nancy API & Associated SOE Migrate or Remove Nancy API & Associated SOE Apr 27, 2022
@stdavis stdavis added this to the v2 milestone Mar 15, 2023
@stdavis
Copy link
Member

stdavis commented Mar 21, 2023

The plan for v2 is to deprecate the API/SOE in favor of client-side queries directly to feature services.

@stdavis stdavis self-assigned this May 18, 2023
@stdavis
Copy link
Member

stdavis commented Jul 19, 2023

I feel good about the current solution for the new app. FeatureLayer queries plus the create replica AGOL endpoint for downloads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants