MAPBOX_ACCESS_TOKEN=<your_token>to https://github.com/GeoNode/geonode/blob/master/.env run
docker-compose down && docker-compose up -dand it should show up
/admin/layers/uploadsession/there you can see the storage of your originally uploaded files of a layer. Then continue here: https://github.com/GeoNode/geonode/blob/9f1474a784682e919e70963ae1fd1da0919ff576/geonode/proxy/views.py#L263 this should be the view that might handle the download. maybe you can debug it in a shell ... ?
docker-compose down && docker-compose up -dto populate your vars and to be sure also cleared your browser cache? I'm asking as from what I see in settings.py it should work like this: if this is set: https://github.com/GeoNode/geonode/blob/master/geonode/settings.py#L1395 (which you can set by an env var) this well get true: https://github.com/GeoNode/geonode/blob/master/geonode/settings.py#L1492-L1503 and add mapbox to your map
I'm not sure if I'm in the right place, but looking for some pointers.
New to the GIS world, I've been reading up for the last several weeks, but it's time to ask the experts =]
I've got a client that works with GIS and their current process involves receiving shape files from a vendor [they call it gold], then their analysts use this data in ArcGis SDE.
One challenge they have is how to share corrections or modifications with other groups in the enterprise.
The current policy is to send a screen shot/file to the vendor, then the vendor updates it and sends it back for re-integration.
I thought maybe this would work better if there was a version control system like git, then I stumbled on to GeoTools which looked like a good library to start.
Then I found GeoGig, which seem to do just that!
Further study led me to GeoShape, which looks abandoned on GitHub - but I found GeoNode and was excited to see lot's of activity!
I'm putting together an architecture plan for the client that essentially takes the shape file commits it to GeoGig and send data downstream to their ArcGis DB.
Then the analysts can clone, branch, modify, and share.
Does GeoNode make this easier? Or would it fit into this process somewhere?
@jdbranham for sure it is, and it would be very useful for a lot of people. The only reason why this is not yet a GeoNode feature is because it requires a lot of work, impacting the core architecture of GeoNode in many ways.
That's great! I'll open an issue for enhancement/discussion if that's the best course.