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

Add geopackage handling in incore services #205

Closed
7 of 8 tasks
ywkim312 opened this issue Aug 25, 2023 · 0 comments · Fixed by #224
Closed
7 of 8 tasks

Add geopackage handling in incore services #205

ywkim312 opened this issue Aug 25, 2023 · 0 comments · Fixed by #224
Assignees
Labels
5storypoints Between 16-24hrs, may involve chainings, new pipelines, very complex models

Comments

@ywkim312
Copy link
Member

ywkim312 commented Aug 25, 2023

Currently, geopackage handling only happens in geoserver upload part. Make incore-services to be able to handle the geopackage handling by adding the data's format like 'geopackage' then upload it into data service. This should be done after the geoserver connection upgrade PR get merged.

There are things that needs to be implemented

  • service should be able to catch if it is geopackage
  • the new format "geopackage" should be used
  • check routine in geopackage if the guid exists
  • check if geopackage has one database
  • geopackage should be able to join with table
  • geoserver should be able to handle geoserver upload
  • when uploading geoserver, it has to have dataset id as a name instead of database name
  • need to handle sqlite for quering the dbname and rename it in geopackage
@ywkim312 ywkim312 self-assigned this Aug 25, 2023
@ywkim312 ywkim312 added the 2storypoint Between 2-6 hours of work, requiring email and/or a brief meeting label Aug 25, 2023
@ywkim312 ywkim312 added 3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem and removed 2storypoint Between 2-6 hours of work, requiring email and/or a brief meeting labels Sep 20, 2023
@ywkim312 ywkim312 linked a pull request Oct 4, 2023 that will close this issue
@ywkim312 ywkim312 added 5storypoints Between 16-24hrs, may involve chainings, new pipelines, very complex models and removed 3storypoints Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem labels Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5storypoints Between 16-24hrs, may involve chainings, new pipelines, very complex models
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant