Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Earlier
  3. Thanks for the additional details. I'll note that you can associate a photo with a group of RTI image sets - which doesn't totally get what you are asking for, but is simpler than associating with each image set. Also, the ability to "duplicate" image sets and/or groups of image sets will also automatically associate the photo. I agree that these ideas are "workarounds" for what you are asking for, but thought I would throw them out there in the hope that you might find the suggestions useful. Carla
  4. Thanks Carla, yes understand can create a grouping for the dome, and apologies if I didn't make question clear. The point was that the dome structure is (relatively) invariant, so rather than have to associate pictures of the dome or rig with every image set taken with the dome, the 'normalised' solution would be to associate the pictures with the equipment. Similar might apply to, say, a photogrammetry turntable arrangement which was used repeatedly. Dave
  5. Thanks Erich, Have just tried that and, exactly as you say, ticking '[ ] Show associated?' does allow an operator to be added with another role. I would observe/suggest: 1) Not sure if it might be better either completely without the need to tick that box, or reverse the default / pre-tick the box. It certainly isn't obvious (until you know how!) 2) As you say, once that box is ticked, not only can you associate multiple roles, but you can add several instances of the same actor/operator with exactly the same role. Would strongly suggest that is not a valid result, so basic validation when associating an operator with an image set would be to present only those roles which they don't have already - so adding a completely new operator would in effect offer all roles; adding an operator for a second or subsequent time would offer a reduced set of roles (NOT IN ...) Dave
  6. First of all, thanks for your comments, Dave. As Carla has already replied to some of them, I'd like to supply information regarding your last topic: As with most association forms, it is actually possible to associate the same operator more than once with a specific image set, thus expressing more than one role. You simply have to check "Show associated?" in the upper part of the form, in order to include operators already assigned in the list of eligible persons (left pane), giving the possibility to associate the same person again with another (or even the same) role. I hope that solves your issue.
  7. Well that seems to have fixed the problem. Another point - when specifying a GPS location for a location to be accurate you also need to specify the coordinate system and projection as well as the GPS Co-ordinates.
  8. Hey guys! Thanks for figuring this out. I'm on the road doing training so just saw this. We definitely should make the default be to install the database. This probably needs its own topic where we can show the details and folks can find it easily. When I'm back on a computer (rather than my phone) I'll get that set up. Note that you may may need to start Postgres after rebooting your computer- or you will see the same message.
  9. Dave - thanks for the feedback. We are planning to internationalize the software to make supporting different localizations easier. I agree that dates can be tricky - and maybe we should just make the month and date formats clear as a start. Thanks for bringing up the dome scenario. Most folks are doing the highlight method of RTI - and this is a little bit skewed that way. Remember that you can enter as much or as little data as you want - so you can easily skip the string length - or use it to record the radius (i.e. the light standoff on your dome). You can make your own equipment category for a dome. Put in whatever you want about it, and associate an image or two of the dome with any groups of image sets - or image sets you wish. Good point about operator roles. Initially we were thinking about collecting the initial event of capturing the image sets, and so you can make these whatever level of specificity you want. I use "image capture" for a person playing multiple roles in the image capture. Good point about making it possible to associate the same person as the image processor. Thanks for the feedback! Carla
  10. cdschroer

    DLN:Inspector version 1.0 Beta

    Thanks for the feedback Dave. Here are a couple of notes: 1. You can run inspector without the database from DLNCC - and that might be the easiest way to use it when you are just getting started. This is also great for checking your own legacy data, that isn't in the DLNCC tool. If you want to do this you can turn off using the DLN in the "options" pane. You can turn it back on any time you like. 2. If you want to use it with the sample data, you will need to change the path for the sample data to wherever you installed it on your hard drive. I should have included that in the README for the sample data - sorry about that. If you use Inspector with DLNCC - it assumes it can find the files and folders in the stored path for the project. So, update the path at the project level, and keep the sample files under that and it should work. Thanks for taking the time to try out the tools! I think you will find the Inspector reports really useful, once you get over these early hiccups. Carla
  11. DLN:CC Beta – software version 1.0.3 (build 26 Apr 2018 15:55:31) / DB version 2.2.3 First few observations / comments: Needs Regionalisation, in particular dates – looking at examples logged today (4 June 2018) it looks like 6 April 2018 (6-4-2018). If the system can’t/won’t reference the users’ locale, or maybe even as a ‘better’ fix, suggest that the date format, when displayed at least, is dd-mmm-yyyy so it shows 7-Feb-2018 etc which is then un-ambiguous world-wide. Registering an RTI image set has various string (Egyptian, not computer!)-related prompts. Might I suggest there’s a tick-box/radio-button or similar to indicate string or dome? Talking of domes, I can see how one would create an entry for a dome in the equipment register. Domes are rarely off-the-shelf and thinking of how one could/would document a dome, I wonder if the ability to associate photographs with project setups could usefully be extended to allow one or more photos of a piece of equipment (e.g. a dome type rig) to be associated with that equipment entry to save having to re-associate them with every group or set of images acquired using the same rig. In documenting an Image Set, it allows Operators to be associated, and to specify their role. However, it only allows one role per operator. In real life there may well be multiple roles for an actor/operator (e.g. image acquisition, computer processing). Could ‘fudge’ this by creating hybrid roles (e.g. 'photographer / computer operator'), or having schizophrenic clones of the same operator (‘Dave Martin – photographer’, ‘Dave Martin – computer operator’) but that is de-normalised and doesn’t reflect reality; so multiple roles are needed. Dave
  12. Trying to use DLN:Inspector with a DLN database (the sample database which installs with DLN:CC). The 'Project' at the top of the DLN:Inspector GUI does allow you to select a project; but the drop-down 'Group' to select image groups drop-down/combo is always empty so cannot get any further. Same if run DLN:Inspector RTI or PG. The DLN database has both the LACMA tests (RTI and PG) and some of my own initial tests in as well. None of them are accessible from DLN:Inspector (also, unlike DLN:CC, there's no 'About' which allows one to report more detailed version/build info, only the 'Version 1.0 Beta' in the title bar of the application)
  13. UPDATE: Have found a short-term work-around. I guess that there is a password embedded in the DLN applications, and if DLN:CC starts it must have the correct password. I noticed that on the DLN:CC Admin menu there was a 'Run script' option, so I first of all tried running the 'createpg.sql' script from DLN:CC - the script started OK, but then failed because the three sub-scripts that created the sequences, tables and then inserted the ref data only had relative paths when called from within 'createpg.sql'. So, I was going to modify a copy of 'createpg.sql' to embed the paths, but instead from within DLN:CC which was logged in to the database, I just ran the 'createsequence.sql', then 'createtable.sql' and finally 'insertlookupdata.sql' - all of which ran OK to completion. I can now start DLN:Inspector and connect to the DLN database. Dave
  14. Hi Carla, Have tried to install DLN:Inspector. Once I found out how to get DLN:CC to start (separate thread in DLN:CC section) I tried to start DLN:Inspector again and it came up with the first message shown below that the database had not been update for DLN:Inspector and to see the documentation for instructions. Checked online and in the installed program groups and could not spot the documentation. In the end I started DLN:Inspector 'without the DLN' and then, by clicking [Help] it opened the PDF. I then followed the instructions (which I guess are OK for beta testing but possibly not ideal for end-users long term) but, when the update is run, it fails with the message shown in the second screenshot. Dave
  15. UPDATE: - I had a look at/for the (not) installed database, then repeated the installation, and I've got it working now. I think problem when application was trying to connect to the database was not so much 'no password' as in fact 'no database'! The installer's default option under 'DLNCC Database' is 'Upgrade existing database'. If there is no database to install, it silently skips that stage. For first install, manually changing the option to 'New database, replacing the existing' seems to rectify the situation. This also removes the complaint when DLN:Inspector starts) Iain - suggest you try re-installing and tick the 'New database' option and see if that helps. I think / would suggest: the installer script needs to be 'cleverer' so if no database installed it will install skeleton one, or at least prompt the user; or at least the database option text in the installer screen above needs extra (like the PostgresSQL) so it maybe says 'New database, replacing the existing (check if first installation)' or at least some pre-install info/advice for the user . Dave
  16. Carla - similar (I think) question to IainS. When starting DLN:CC, it attempts to connect to the database - it pops up a database login (first pic), username defaults to 'postgres' with an option of two databases to connect to ('cpt_db' and 'cpt_db_v2.1'). Default password is blank, but there must be a password set as can't get beyond this point. Edit: I guess because DLN:CC hasn't got beyond this stage, DLN:Inspector complains at startup as well (second pic) Dave
  17. I have downloaded the Capture Context tool - it is asking me for log in details I don't have - have I missed something?? Iain
  18. I'd second the need for ground control points particularly if you are tying the photogrametric map into other maps (such as site plans or local topographic maps) with any form of precision. Cheers Iain
  19. We at CHI are thrilled to announce the release of the first two tools (Version 1 Beta) in a new software suite, the Digital Lab Notebook (DLN). DLN is a metadata toolkit designed to simplify the collection of standards-based metadata, essential to scientific imaging. The goal is widespread democratization of tools that worldwide cultural caretakers can deploy to digitally capture, build, archive, and reuse digital representations. We hope you will download and try out these new tools! DLN:CaptureContext With a user-friendly interface, this tool expedites and simplifies user input of metadata -- such as locations, institutions, imaging subjects, image rights -- with a template process. DLN:Inspector This tool automatically ensures that each image set meets the requirements for high-quality computational photography imaging, checking for image-processing errors, such as sharpening, that should not be applied to photogrammetry or RTI image data. Instructional Videos for DLN See our new Vimeo channel -- Simplifying Scientific Imaging -- where we have posted an instructional video series about the DLN, what it does, how to use the software tools, and more.
  20. Welcome to the forum for the DLN:Inspector tool - one of the first two tools in the Digital Lab Notebook (DLN), a software pipeline made up of open source software and associated good practices. In this forum, we encourage you to share your questions, issues, or comments about using DLN:Inspector. The open source DLN:Inspector tool can be used to validate image sets created for Photogrammetry or Reflectance Transformation Imaging (RTI) You can download both the DLN tools from this page: http://culturalheritageimaging.org/What_We_Offer/Downloads/DLN/index.html There are Instructional videos describing how to work with the tools on this Vimeo channel: https://vimeo.com/channels/digitallabnotebook
  21. Welcome to the forum for the DLN:CaptureContext (DLNCC) tool! DLNCC is one of the first two tools in the Digital Lab Notebook (DLN), a software pipeline made up of open source software and associated good practices. In this forum, we encourage you to share your questions, issues, or comments about using DLNCC. DLNCC is all about collecting rich metadata for your photogrammetry and Reflectance Transformation Imaging (RTI) projects. You can easily reuse data about equipment, people, locations, subjects and more. The data can be exported as Linked Open Data mapped to the CIDOC Conceptual Reference Model (CRM) for archiving and reuse. And, you don't need to know anything about these metadata standards to produce these results. You can download the Capture Context tool, along with a user guide from this page http://culturalheritageimaging.org/What_We_Offer/Downloads/DLN/dln-cc/index.html There are Instructional videos describing how to work with the tools on this Vimeo channel: https://vimeo.com/channels/digitallabnotebook Please give us your feedback!
  22. endeavour

    camera footprint

    hi Tom. now i have read the website. and now i understand how it works and why i had this differences. so far i hav'nt tried the formula but sure i'll have better results. thank you again so much. sunny greetings from zurich switzerland
  23. endeavour

    camera footprint

    thank you Tom great site! i'll check it out and will give feedback.
  24. macsurveyr

    camera footprint

    Martin, There is a more exact formula that can be used to calculate the footprint at closer distances such as you are doing but it is still an approximation. You can explore this website for more information. Depth of Field (DoF), Angle of View, and Equivalent Lens Calculator Make sure to click on the See Notes link under the 2 methods for calculating the field of view. Once there, be sure to follow the other link Calculation the Angle of View: When Theory Meets Practice. Additionally, lens distortion can account for a few percent less (usually) field of view. Tom
  25. endeavour

    camera footprint

    thank you Tom i'm talking of course not about the viewfinder but about the covered area in an image which i measured now again along with other prime lenses and a mirorless lumix GF1. see the results attached chart. with the canon lenses the difference between calculation and real world is irregular while with lumix zoom lens more regular but not really regular either. the difference is allways in the 20% range which is quiet a bit. still looking for an explanation. or a formula . thanks everybody Martin
  26. macsurveyr

    camera footprint

    Hmmm, Not sure I can explain it since the calculated footprint can be confirmed. That leaves what you are seeing to be the mystery. I believe spec wise, the Canon viewfinder is supposed to cover ~96% of the actual footprint so again, not sure I can explain it based on the numbers. Tom
  27. endeavour

    camera footprint

    hi everybody i have a question: i tried to calculate the footprint (area covered) of a camera setting with my canon 5dsr having 8688x5792 pixels on a 36x24mm sensor which is a SPS of 0.00414365mm. now with a 35mm lens and 500mm distance i calculate a covered area of 514x342mm. ((calculation according to the "US Bureau of Land Management Publication: Tech Note 248 on Photogrammetry")) BUT if i look thru the camera viewfinder the covered area at 500mm distance the covered area is only approx 410x273mm to achive an area as the calculated 514x342mm i must set the lens on 610mm any ideas whats wrong here? it's still an about 20% difference from calculation to "reality" thanks everybody for every sugestion best greetings from zurich switzerland martin
  1. Load more activity
×