Não foi possível enviar o arquivo. Será algum problema com as permissões?
Diferenças
Aqui você vê as diferenças entre duas revisões dessa página.
| Ambos lados da revisão anterior Revisão anterior Próxima revisão | Revisão anterior | ||
|
software:art:faq [2007/05/18 19:28] leonardo |
software:art:faq [2008/11/13 13:27] (atual) pedro |
||
|---|---|---|---|
| Linha 1: | Linha 1: | ||
| - | ====== aRT: FAQ ====== | + | ====== FaQ: Frequent aRT Questions ====== |
| - | - **Q:** Which DBMS' does aRT supports? | + | - **Which DBMS' does aRT support?** |
| - | * **A:** Currently only MySQL and Postgres. | + | * Currently only MySQL and Postgres. |
| - | * In principle aRT can support any DBMS supported Terralib. All is needed is to extend aRT for other DBMS already supoported by Terralib. Contributions to extend the list of supported DBMS are welcome. | + | * In principle aRT can support any DBMS supported by TerraLib. All is needed is to extend aRT for other DBMS already supported. Contributions to extend the list of supported DBMS are welcome. |
| - | * we should have a road map to guide such expansions! | + | * We should have a roadmap to guide such expansions! |
| - | - **Q:** Can I run aRT without a DBMS? | + | - **Can I run aRT without a DBMS?** |
| - | * currently no. There are plans to implement this. | + | * Currently no. There are plans to implement this. |
| - | - **Q:** how does aRT get to know which DBMS do I have? | + | - ** How does aRT get to know which DBMS do I have?** |
| - | * aRT (on LINUX) has a ''configure'' tool which runs during the instalation and searches for the supported BDMS available in the system | + | * aRT (on Linux) has a ''configure'' tool which runs during the installation and searches for the supported DBMS available in the system |
| - | - **Q:** Why do I get ''ID'' from ''getPoints()'' and ''id'' ''from getData()'' on a layer? | + | - ** Why do I get ''ID'' from ''getPoints()'' and ''id'' from ''getData()'' on an attribute table of layer?** |
| - | * **A:** This is not a //bug//, but a //feature//. sp package uses ID to represent the identification of spatial objects. We just follow the pattern. Points do not need to have an identification so we introduced an ID in order to follow the spatial model for lines and polygons. Data from attribute tables are "as is". If you want to ferlessly put together attributes and geometries, then use themes. | + | * Indeed, this is not a bug, but a //feature//. sp package uses ID to represent the identification of spatial objects. We just follow the pattern. Points do not need to have an identification so we introduced an ID in order to follow the spatial model for lines and polygons. Data from attribute tables are "as is". If you want to fearlessly put together attributes and geometries, then use themes. |
| + | - **Is there any step-by-step manual to install aRT on Linux?** | ||
| + | * Yes. You can find it [[software:art:install|here]]. | ||
| + | - **Is there any step-by-step manual to install aRT on Windows?** | ||
| + | * Currently no but steps includes: (i) install the DBMS (currently MySQL), install the aRT windows package as indicated at the aRT web page. | ||
| + | - **ID vs id : lower vs upper case problem. When retrieving data with getPoints() we have ID for column names whereas id for getData().** | ||
| + | * Instead of merging the ids by yourself, aRT can do it by using aRTthemes, which joins geometry and attributes safely. This problem happens because sp uses ID for the identifiers, while TerraLib lets the user to choose the name. | ||
| + | - **Is there any aRT discussion list?** | ||
| + | * Yes, please write an e-mail to art_l at leg.ufpr.br | ||
| + | |||
