Hi Martin, >http://www.geoapi.org/ server has just been fixed - sorry for the >disturbance.
Thanks! And see https://github.com/opengeospatial/geoapi/issues/33 (: >http://nexus.senbox.net/ seems to be down for now. Let see later if >still the case. In the meantime, you can remove the following line in >the root pom.xml file of GeoAPI (near the end of the file): Just did that, and it worked. Thanks! Without looking at the Python module with more calm, isn't it common to use Jython for creating a bridge from Python to access Java objects? Any reason for using JPY instead? (hadn't heard about it). At work (research company) most scientists are using R and Python. So perhaps if it's simple enough, there could be something similar with rJava? >By the way, if there is any Python developer reading this, feedback >would be welcome since I'm not myself a Python developer. Initial Python >API documentation is available there: >http://www.geoapi.org/snapshot/python/index.html At work I use a bit of Python. The documentation looks good! Whenever I have to use an API, I usually look for requirements & installation, and then forexamples. One API I used recently is construct, to parse some binary data https://construct.readthedocs.io/en/latest/ There are sections for requirements and installation. The part about pip is probably the most important for me, as I expect to be able to create a virtual env in Anaconda or virtualenv to play with the API first. And most sections contain a short example, similar to what you would see in a Jupyter notebook. When I click on "Spatial representation", I see the description of the types, but not how to use it. If there are some issues for this API, I'd be happy to spend some spare time reading the docs, and trying to suggest a few paragraphs for installation, requirements, and some examples. That way I will learn about it as well. Cheers Bruno ________________________________ From: Martin Desruisseaux <[email protected]> To: Bruno Kinoshita <[email protected]> Cc: [email protected] Sent: Monday, 7 May 2018 8:02 PM Subject: Re: Little help building Apache SIS Hello Bruno (and thanks Hao for the detailed build instructions!) Le 07/05/2018 à 00:41, Bruno Kinoshita a écrit : > At work we use Java GIS libraries and metadata, although some of it is > running on some old versions. We are now updating these libraries, and I am > interested in learning more about Apache SIS & GeoAPI, to see if parts of > our code base could be replaced by both/either. Cool! Do not hesitate to let us know about any issue. > I tried to build Apache SIS, but it fails saying that it can't find the > parent of some of its modules. GeoAPI yesterday failed too, saying that the > JPY project could not be found. I looked at their Maven repository (senbox) > and it was returning error 500 too. http://www.geoapi.org/ server has just been fixed - sorry for the disturbance. http://nexus.senbox.net/ seems to be down for now. Let see later if still the case. In the meantime, you can remove the following line in the root pom.xml file of GeoAPI (near the end of the file): <module>geoapi-java-python</module> The GeoAPI Java-Python bridge is a new GeoAPI module under development which allow to use any GeoAPI implementation (not necessarily Apache SIS) in Java from the Python language, or conversely a GeoAPI implementation in Python from the Java language. When completed, it will allow to use parts of Apache SIS from Python. This module is being created because of the popularity of Python language among scientists, and because it is an OGC requirement to demonstrate that GeoAPI can work with other languages than Java. I will post more about this module when completed. But since Apache SIS does not yet use it, you can safely exclude it from the build. By the way, if there is any Python developer reading this, feedback would be welcome since I'm not myself a Python developer. Initial Python API documentation is available there: http://www.geoapi.org/snapshot/python/index.html > I couldn't find an YAML file for Travis-CI, so looked at builds.apache.org > to see if I could understand how Apache SIS was being built, but found > nothing different from what I was doing. > > The docs I followed : http://sis.apache.org/source.html Did you tried to build the trunk or a branch? When building the trunk, there is no need to try to build GeoAPI first because the trunk is nailed down on the GeoAPI 3.0.1 standard release from OGC. Only the branches use GeoAPI snapshots. The instruction for Eclipse IDE may be out-dated since I'm not aware of an Eclipse user having tried them recently. I will check if there is other instructions needed to be updated. Regards, Martin
