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.

Sign up for GitHub

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

Jump to bottom

geospatialdata and upsert/geom endpoints are not behaving similarly #42

Open
ar-siddiqui opened this issue Nov 5, 2022 · 1 comment
Open

geospatialdata and upsert/geom endpoints are not behaving similarly #42

ar-siddiqui opened this issue Nov 5, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@ar-siddiqui
Copy link

With the recent simplification of endpoints in #13 different endpoints behave differently for example, gesopatialdata only consider a model geospatial if it has .projection file while upsert/geom would take into account other kinds of projections files as well.

Thus if you don't have .projection file in a model but other kinds of projection files gesopatialdata would fail but upsert/geom would not.
@ar-siddiqui ar-siddiqui added the bug Something isn't working label Nov 5, 2022
@ar-siddiqui
Copy link
Author

Millbrook Trib to MC.zip

Sample model to test.

Code link: https://github.com/Dewberry/mcat-ras/blob/main/tools/model.go#L261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ar-siddiqui