gem / directobservationtoolsforwindows Goto Github PK

Adding/Viewing Sketch and Photo with Space in Filename Causes Problems

Tools AddPoint and Query Point are disabled if the GEM project is opened by double clicking. It would appear that a different code path is invoked when a project is double clicked.

Need Mechanism to Link a list of All Photos, rather than photos at each point. Auto linking would be really nice.

E.g. Double quotes, single quote. Especially in comments and filename fields.

• Missing projection information when opened in ArcGIS (E).

“Roof cover material” drop down “Tile (clay. Concrete)” should it be / instead of . I couldn’t find it in the taxonomy.

System.Data.DBConcurrencyException: Concurrency violation: the UpdateCommand affected 0 of the expected 1 records

Hi Julian,

There is a small problem with the way dates are being populated in the SQLite database. The Android tool and Windows tool appear to do it in different ways. This is particularly a problem with the field PROJ_DATE in the table GEM_PROJECT. Currently as things stand it is not possible to open an Android version of the database using the Windows Tool. If the PROJ_DATE field is modified outside the IDC Tool then everything works as expected.

SQLite does not have a specific Date type and stores dates as strings behind the scenes. I think this is the root of the problem.

Here are a few tests I did using SQL to populate the database with different datetime formats.

UPDATE GEM_PROJECT SET PROJ_DATE='2013-03-03'; This one causes the Windows tool to fail (not interpreted as a true date) UPDATE GEM_PROJECT SET PROJ_DATE='2013-03-03 01:25:23'; This is ok and works fine (probably not the best way as we are dealing with Date data types) UPDATE GEM_PROJECT SET PROJ_DATE=datetime('2013-03-03'); This is ok and works fine UPDATE GEM_PROJECT SET PROJ_DATE= datetime('2013-03-03 01:25:23'); This is ok and works fine

So it looks like we need to be careful if we populate Date fields using a string, probably best to convert to a true date using a datetime function.

Can you please let us know how you are populating the PROJ_DATE field, are you using a string or are you using a datetime function to convert? Also how easy would it be for you to change this behaviour in your App?

Cheers
Keith

Masonary reinforcement, drop down list “bamboo-.cane- or rope-reinforced” delete the full stop

Entered No. storeys below ground. Without choosing Between/exactly/approximately I was able to insert a number. Should this be possible if we don’t know if the number if exact or approximate?

Year of construction, I tested 19888 as the exact year. Are we tracking any inputs for errors?

• Transverse recorded for LLRS, when longitudinal LLRS input (E).
• Retrofit information column shown in database but not available to record on Android tool (E).

Cancel Changes results in two dialogs asking the same question if Yes is clicked.
Ok if No is clicked

X, Y - Long, Lat - Not constrained

slope degrees is also not tracked e.g. I could enter 99999 (all these points on tracking entries could be made clear in the user manual i.e. we don’t do any Q/A during field capture)

Standard MapWindow Identify Tool brings up Data Collection Form. Is this by design? It is a bit confusing to have both the Data Collection form and the Identify dialog together!

Please update with the latest logo

Plan area (confirm if in m or what units)

Add Version Number into database settings table

In the dropdown list ‘masonary mortar type’ there is “Cement mortar” and “Cement:lime mortar” check spaces and why one has a colon.

At present there is no easy way of transferring data collected on the Android tool to the Windows tool. There should be an “import data from Android tool” option. The present system of opening a new project and changing filenames and file extensions is not an effective solution for two tools designed to work together .

Application fails to open existing projects on certain PC's Application randonly crashes. Re trying will eventualy open the project. For some reason double clicking on the project file has a better odds of opening the project than opening the project from within the application. It is suspected that the PROJ4 projection library is involved. The issue has all the hallmarks of a memory leak.

Clicking and applying the Query Point tool does not work immediately after clicking Update Changes on collection Form. Clicking and applying the Query Point tool a second time works.

The data collected by the two users, on different buildings in the study areas was merged.
Data merge was successful and when exported to csv and shp, merged database contained the correct number of records.
However, I could not seem to display (in MapWinGIS) all of the points in the merged database, only the points in the original database.

Error when exporting – for one record (record 31), the columns are offset, see Table 2 (E):

Replicate by doing the following:

1. Click the Query Point tool
2. Apply the tool to an observation
3. Close the Form
4. Click the Query Point tool
5. Apply the tool to an observation
6. Nothing happens
7. Click the Query Point tool
8. Apply the tool to an observation
9. It works this time

I cannot seem to export the photographs so that they display in Google Earth, I have made the following checks (E):
• Checked that the photographs are linked.
• Ticked the box that says imbed the photographs in a kmz.
• Saved the file in different folders (including in the folder with the images).

GPS USB unit is not working when project projection is set to Pseudo Mercator. The tool is able to connect to the GPS unit, but can't get a fix or any NMEA sentences in. When trying to disconnect the GPS, the tool crashes with no errors or warnings.

Year of construction, I tested 19888 as the exact year. This is not constrained.

Masonary” should be spelt “masonry”. It is masonry in the taxonomy.

There is a problem when the help tab is clicked before anything else. This is due to the fact that no context is set until a value in a control is selected or a label clicked. The Help context should be set to general help at the start.

Number fo dwellings” to “of”

Query point also lets the user edit the point – should this be stated in the tool button e.g. Query/edit point