|
I came across an old DB entry of a building that's repurposed. It said "Drop everything - must see" and has all the data at the time it was abandoned. I know that you all have said in the past that you want to use it as sort of a time capsule of past abandonments, so I was thinking I should leave everything the way it is other than changing the status to "Repurposed" and writing that it is no longer abandoned. Thoughts?
Are we living a life that is safe from harm? Of course not, we never are. But that's not the right question. The question is, are we living a life that is worth the harm? |
|
I would change the status but not touch the "Drop everything must see." If you have a link or something showing the change, you can add that somewhere without deleting anyone else's text.
|
|
Posted by Steed I would change the status but not touch the "Drop everything must see." If you have a link or something showing the change, you can add that somewhere without deleting anyone else's text.
|
This is what I do, along with adding a small note to the description listing when it was repurposed (ex: repurposed as of 10/2018) and what it was repurposed as. On another DB etiquette side note, what's the proper form for drains with two outfalls a decent distance from one another? I know of two outfalls that are on opposite ends of the same storm drain main line. I've already added one of the outfalls, but should the other one be in the DB too?
[last edit 10/7/2018 9:16 PM by Aran - edited 1 times]
"Sorry, I didn't know I'm not supposed to be here," he said, knowing full well he wasn't supposed to be there. |
|
If the location is active, then I would mark it as active. The status isn't intended to be a time capsule.. it is pertinent information for other members.
"Great architecture has only two natural enemies: water and stupid men." - Richard Nickel |
|
Posted by Aran On another DB etiquette side note, what's the proper form for drains with two outfalls a decent distance from one another? I know of two outfalls that are on opposite ends of the same storm drain main line. I've already added one of the outfalls, but should the other one be in the DB too?
|
That's a tough question. I think the tunnel is one system and one entry is most appropriate. When you explore them, do you go from one to the other, or do you usually just stay in the vicinity of one or the other? There's one underground river I've added two locations for where there is an upstream segment and a downstream segment with an exit between them, and the tunnel shape, accessibility, and safety are very different in both. I've also had to think hard on adding subway lines to the LDB, as I can't just add every entry and exit point.
|
|
I have a little side question somewhat relevant to the topic at hand, I am a full member and I am wondering how I can update the validation of a location. I will explore something from the DB and see that it was validated a year or more ago and I would like to update that so it's validation is current. I will feel quite silly if it is a simple thing, I have looked many times in how to lol.
|
|
Posted by Masakari I have a little side question somewhat relevant to the topic at hand, I am a full member and I am wondering how I can update the validation of a location. I will explore something from the DB and see that it was validated a year or more ago and I would like to update that so it's validation is current. I will feel quite silly if it is a simple thing, I have looked many times in how to lol.
|
You have to run for Moderator. I hear there is a vacancy.
|
|
Posted by Masakari I have a little side question somewhat relevant to the topic at hand, I am a full member and I am wondering how I can update the validation of a location. I will explore something from the DB and see that it was validated a year or more ago and I would like to update that so it's validation is current. I will feel quite silly if it is a simple thing, I have looked many times in how to lol.
|
I usually add an album of my visit labeled "[season/month] [year]" to the DB entry. That way, anyone checking that particular entry can at least see that it was still standing. This is especially helpful for DB entries for locations that are still around but haven't been updated in 5+ years.
"Sorry, I didn't know I'm not supposed to be here," he said, knowing full well he wasn't supposed to be there. |
|
Posted by Aran
I usually add an album of my visit labeled "[season/month] [year]" to the DB entry. That way, anyone checking that particular entry can at least see that it was still standing. This is especially helpful for DB entries for locations that are still around but haven't been updated in 5+ years.
|
You don't have to put the date in the gallery name. There's the Gallery Date field, which should reflect the day the pictures were taken rather than the day of upload. That's enough to show the timing of the photos and gives you more room for a more descriptive gallery name. For instance you could put something like "Returned on Christmas 2017 and found a crater" 2017-12-25
|
|
Posted by Aran
I usually add an album of my visit labeled "[season/month] [year]" to the DB entry. That way, anyone checking that particular entry can at least see that it was still standing. This is especially helpful for DB entries for locations that are still around but haven't been updated in 5+ years.
|
That's an excellent idea! I will do that in the future thanks! Moderator eh? What are the requirements for that? Sounds prestigious!
|
|
Posted by 2Xplorations
You have to run for Moderator. I hear there is a vacancy.
|
Mike hasn't been LDB Mod for some time now.
In order to use your head, you have to go out of your mind. |
|
Posted by Radio2600
Mike hasn't been LDB Mod for some time now.
|
Really ? I was not referring to him.
|