Welcome to LSDN !

About this site...

This site is introducing some developmental services considered to be useful to mush up. These services provided in this site have been developed or are being developed at LAIS ( Labo. of Agric. Info. Systems ) up to March 2006, and at DSS ( Decision Support System Research Subteam ) from April 2006 to now.

Most of these services are XML Web services and REST (REpresentational State Transfer) Web API services.

These services are provided as they are with no warranty. Client usage of these services are allowed under users' responsibility.

Development support information and service

Following information and service are available now.

Sharing service of data type definition for PFUManager^*

This service is designed to share information of data type definition for PFUManager, providing several methods as XML Web service for search, retrieval and registration of data type definition.

DataType specification has been extended with addition of definition items such as 'data-type', 'missing value', 'note' on Nov. 2010.

Here is accessing point to this service.

Here is WSDL^* of this service. Note that you may need to rewrite the host address of this service in stub routine generated by your development tool.

Here is online document (only in Japanese) on usage of this service.
　

Judging service for adaptability of vegetable cropping

## XML Web service ##

This service is a XML Web service used internally at "Judging site for adaptability of vegetable cropping".

Here is access point to this service.

Here is WSDL of this service.

Here is online document (only in Japanese) on usage of this service.
## REST Web API service ##

This service is a REST type Web API used internally at "Judging site for adaptability of vegetable cropping".

Here is a demonstration page using this API. In this page a conventional web form invokes this API through CGI.

Here is access point to this service. You will get summary of this Web API.

Here is online document (only in Japanese) on usage of this Web API service.
　

Predicting service of rice plant growth

This XML web service is used internally at "Predicting site of rice plant growth".

Here is access point to this service.

Here is WSDL of this service.

Here is online document (only in Japanese) on usage of this service.
　

Geocoding service (Latitude & Longitude <---> JCODE : address code defined in JAPAN)^*

This service converts address code in Japan to global position and global position to address code. JCODE defined in Japan is used as address code. Latitude and longitude in decimal degree are used as global position.
Here is access point to this service.
Here is WSDL^* of this service. Note that you may need to rewrite the host address of this service in stub routine generated by your development tool.

Here is online documentation (only in Japanese) on usage of this service.

This service accesses to another geocoding Web API service on "Finds.jp site". For details of this Web API, refer to Finds.jp / Web Service page.
　

Authoring service of ESRI world file for GIS applications (under implementation)

An authoring service of ESRI world file is planned.
　

Note : how to use some XML web services with '*' mark.
!!! You need to change the host address in stub routine calling these services. !!!

Some XML web service introduced above are running on other internal server machine via this "AGinfo.JP" site server. Therefore, host address of these service are generated to access to this internal server in the stub routines generated by your development tool based on the WSDL of these services. But from outside of "AGinfo.JP", any service client can not access to the internal server where these services are running.

To access the internal server, you need to change the host address in stub routines. Open your source file including stub routines to these services generated by your development tool. The host address of these services may be generated as "150.26.38.218". Change this host address to "www.aginfo.jp/LSDN" carefully and exactly. Other parts of URI to these services must not be changed. After this change, you can build your client application and you will get normal access to these services.