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

raster symlinking broken? #100

Open
springmeyer opened this issue May 17, 2013 · 6 comments
Open

raster symlinking broken? #100

springmeyer opened this issue May 17, 2013 · 6 comments

Comments

@springmeyer
Copy link
Member

had a report from @hrwgc that raster data was copied into the project/layers folder instead of being symlinked. Smells like a regression in millstone. Need to dig into this to see if I can replicate.

@hrwgc
Copy link

hrwgc commented May 17, 2013

I noticed this behavior on a dev build with raster colorizer. The layers were copied (8GB worth!).

Sent from my iPhone

On May 16, 2013, at 9:51 PM, Dane Springmeyer notifications@github.com wrote:

had a report from @hrwgc that raster data was copied into the project/layers folder instead of being symlinked. Smells like a regression in millstone. Need to dig into this to see if I can replicate.


Reply to this email directly or view it on GitHub.

@springmeyer
Copy link
Member Author

unable to replicate. If the file path to a .tif is relative then the path to the exact spot is made absolute. If the path is absolute, it is symlinked. I cannot see a case where the data is copied.

springmeyer pushed a commit that referenced this issue Aug 9, 2013
@hrwgc
Copy link

hrwgc commented Aug 27, 2013

@springmeyer I'm noticing this behavior again, I'm on TileMill Version 0.10.1 (v0.10.1-59-g338d40a). The source Tiffs are copied to the project/$project/layers/ directory rather than being sym-linked. If you want to try to replicate, here is the tilemill project and source layers.

@hrwgc hrwgc reopened this Aug 27, 2013
@springmeyer
Copy link
Member Author

Can you set up a fresh project that also hits this problem, document the steps you took, then share that exactly. A project that already has the data copied in is unlikely to be possible for me to replicate with.

@hrwgc
Copy link

hrwgc commented Sep 24, 2013

Ok - get ready for some odd behavior @springmeyer.

I was able to replicate this issue using TileMill Version 0.10.1 (v0.10.1-120-g182c947).

I had a suspicion the issue was related to Dropbox, as I noticed Dropbox was churning trying to sync while I was working with the tiffs in TileMill. Here's how I replicated the issue.

If Dropbox is running in background (i.e., syncing is not paused) when I create the new project and add the layer to the project, the geotiff is not symlinked to the layers directory, it is copied.

If Dropbox sync is paused when I add the layer to the project, the geotiff is symlinked, not copied.

In both instances during my test to replicate this issue, I only added the geotiff to a clean, new project. I didn't modify carto or any project settings. They use the default PNG24 image setting.

@springmeyer
Copy link
Member Author

bizarre, but thanks for the details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants