Modify ↓
#4922 closed enhancement (duplicate)
possibility to mark objects/layer to exclude from upload
| Reported by: | skyper | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | exclude upload | Cc: |
Description (last modified by )
It would be nice if you could mark/tag elements somehow, that they are stored on your local saved .osm but not uploaded at all.
For example I do not want to share my favorite chanterelle spots but I want to have it in my local osm
This would be also interesting for virtuell areas like TMC-Areas.
Thanks for your work.
skyper
Attachments (0)
Change History (6)
follow-up: 2 comment:1 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
comment:2 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | needinfo → new |
Replying to anonymous:
Why don't you handle them in different files (i.e. different data sets)?
This will work for my secrets but is not practical for share data which should not be uploaded.
comment:4 by , 14 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | possibility to mark objects to exclude from upload → possibility to mark objects/layer to exclude from upload |
Ok, the individual objects are not that important but to mark a layer as private and exclude it from upload should work.
comment:5 by , 13 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Why don't you handle them in different files (i.e. different data sets)?