-
Quality Criteria
- Scalibility
- Accuracy
-
Security
- People shouldn't be able to access the model files
-
Product Elements
-
ConX Measuring Tool
-
Images go from PDF to PNG
- data from the image goes to ConX storage file then to the Database
-
Image goes into the Cloudfront
-
It was stated Pdfs become PNG only, not Jpeg
- Ben found that he can covert a pdf to Jpeg
-
4000 thousand images have been converted to detect a model for a plan and elevation. To also tell the differences.
- What kind of imaages were uploaded?
- What dates were used?
- What was the Quality of the images?
- Were the files only in English
- Once the images are received by Bison AX
- So once BisonAx detects the plans and elevations and they create the polygon images from the images.
- Detecting the scale of the plans and elevations they have found by using a recurrent convolutional neural network
- It is noted there are errors with photocopied PDFs
- When measuring the scale, how much of difference is measuring a room from the inside vs from outside the walls?
-
API
-
1) Receives a .png file from Cloud Front (We require to check with ConX)
- Is the .png file that of a photocopied plan?
- Is the .png file corrupted?
- 2) Can the API detect if the sent .png is a Top down or Elevation plan?
- 3) Can the API Detect text in the .png
- 4) Can the API find the scale fron the detected text
- 5) Can the API convert the scale to match the page size received from the ConX DB?
- 6) Can the API create the boundry box around the uploaded .png file
-
7) Does the API give an Output?
- Will it be L * W in pixels?
- Is it in the unit mentioned in the plan? ex: meters
- Is it a calculated output?
-
Security
- Concern: Unauthorised users should not have accessto the algorithm
- BisonAX uses java web as it caters to authorisation and authentication
- Conx uses bearer token for authorisation (to be confirmed)
- Floating Topic
- Floating Topic