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
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
The text was updated successfully, but these errors were encountered:
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
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
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
The text was updated successfully, but these errors were encountered: