Urbex DB – Easy location managment
A few years back I began with urbex photography. Back then I was lucky to find a location and was happy with the few photo’s I could take. After a while getting locations was not a problem anymore. But managing all those locations was more challenging. It was a almost impossible so I lost control of my 3000 pins. My Google maps was one big mess of all kinds of colored pins. It contained duplicated pins but with other names etc, etc.
My engineering brain was busy how to get a grip on my locations. I needed a system where I could store my locations. That gave an overview of my locations. A system that will warn me when I add a duplicate item with an other name. This system should be capable of searching and filtering. It will import locations from all kinds of files like KML and KMZ. That could export a selection of locations so I could load them in my cars navigation.
But why should I want to do this all by my self, I knew other urbexers with the same problem and as we had a chat we were often looking for the same locations and we ware tiered of all the rumors about entrances and states. So this system needs to be multi user so all users can add locations, could rate it, add notes for others, make wishlists so planning a trip and find a partner is easy. Pin point a location plan a route and list all locations near this route. Day’s went by and my head was full of idea’s to much to write down.
I was thinking about a kind of urbex location society and the worst part: It only existed in my head...
Lucky for me, I’m an software engineer, I could build it. Again my mind went crazy and I never could start it because of the mess in my own head. Via my current employer I followed a lot of training courses like software architecture, lean, agile, UML and design patterns. I was told how to think, design, build and test in a structured way piece by piece. Now is the time to bring it all together.
The Urbex DB will be a multi-user web based dashboard to manage POI’s. Per POI users can gather and share information. It will provide tools like a map overview, search, filter, duplicate detection. It should be able to calculate routes. It will import/export geo information. It can be used for a guide for exchange and trip planning. Answer questions what location is most wanted by the users. Users have a central page to get informed about trips, new locations and notifications.
- Urbex DB will be a plugin for WordPress.
- Urbex DB data will be stored encrypted.
Able to handle muti users a kind of hierarchic was needed. I identified five different user roles. This also helped me to setup more specified use case.
- Administrator: Should be able change anything within the system.
- Moderator: Should be able to activate/deactivate/delete users and approve new/delete locations.
- Active User: Should be able to use the system, add new locations.
- Inactive User: Should be able to log in the system and can peek at the locations without the geographical information.
- Foo: Should not be able to enter the system and will not see anything at all, information should be useless.
The use cases are the expectations with a user role point of view.