jdbranham
commented
3 years ago After much research, I've found there were some folks that put together an open source stack with GeoGig as the version management.
But that stack, "OpenGeo Suite" is no longer maintained. It is an interesting history...
The developers created an org called ROGUE JCTD, and created another mashup called "GeoSHAPE", that included GeoGig, GeoServer, GeoNode, OpenLayers, and MapLoom [a visualizer including a UI to resolve GeoGig conflicts.
This project became a commercial project called "Boundless Server", then they closed the source up, and from my understanding, were merged/bought by 'planet'.
So a UI for managing GeoGig edits/merges/conflicts will need to be developed from scratch - and maybe inspiration from MapLoom.
The current plan is to setup GeoServer with GigGig extension, and build a UI to replace GeoExplorer in GeoNode to interact with the rest APIs.
I'm new to the GIS world, so hopefully I understand how these components are fitting together.
If anyone has tips, or experience to share, I'd be very grateful.
Hi! I've got a client interested in change management of "gold" level data coming from vendors.
The internal analysts may need to modify the data, then send it back to the vendor to incorporate their corrections, then it's reimported from the vendor. This process takes at least 2 months end-to-end.
I'm working on a solution that introduces version control of the files imported from the vendor, but allows the analysts to create a new branch to share with others. We can call that "silver" level data.
The data can then be consumed by others before it's gone through the vendor again.
I stumbled onto GeoTools, then found this project [great work btw] and I think it's a good fit for this use-case.
The users may not be comfortable with the CLI operations, but a UI may be appealing.
Are there any UI projects in the works? Or is this something the community might like?