You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the website supports only one mined property type while Texada supports several. Since Issue70 will likely change the format around substantially, it would be best to tackle this issue after issue70
[Issue created by carolemieux: 2015-08-27]
[Last updated on bitbucket: 2016-01-06]
[Comment created by bestchai: 2016-01-06]
Here is an example of a json output form Texada for mining multiple property types. It seems straight-forward to parse this on the client-side to support mining of multiple prop types.
Currently, the website supports only one mined property type while Texada supports several. Since Issue70 will likely change the format around substantially, it would be best to tackle this issue after issue70
[Issue created by carolemieux: 2015-08-27]
[Last updated on bitbucket: 2016-01-06]
[Comment created by bestchai: 2016-01-06]
Here is an example of a json output form Texada for mining multiple property types. It seems straight-forward to parse this on the client-side to support mining of multiple prop types.
The text was updated successfully, but these errors were encountered: