Version 1.3 adds the parameters below:

- concavity parameter, specifying this parameter you can have less or more points on the resulting polygon, from a convex polygon to a detailed concave polygon.

- bicycleOnPredestrian parameter, specifying this parameter bicycles can go on pedestrian areas.

- buffering parameter, specifying how to buffer the resulting polygon.

- restrctedAreas parameter, specifying if want to include restricted access areas.

- pedestrianAnbBikeOnTrunk parameter, specifying if want to include trunk ways for pedestrian and bicycle.

- fastestRouting parameter, specifying, for isodistances/motor vehicle, if want to use fastest routing instead all routing.

For javascript API the signature of getIsoline method has been changed.

To get the iso4app Engine simply include the script:

    <!-- Iso4App library  -->
    <script src="http://www.iso4app.net/api/js?v=1.3&lkey=YOUR_API_KEY"></script>

and declare the engine variable:

    <script;>
       var engine = new iso4app.Engine();
    </script>

In order to use iso4app API you have to specify an API Key (YOUR_API_KEY).
After the registration in the iso4app web site we send you a key with a limited number of credits; you can use it for development purposes.

iso4app.Engine class

iso4app.Isoline class

Isoline object returned from the engine getIsoline method.

Input Point: the point you specify (lat,lng) when you invoke the method getIsoline()

Start Point: when you give iso4app an Input Point it looks for the nearest point having an isoline associated to it. If the "as the crow flies" distance between "input point" and "start point" exceeds the maxApprox values, iso4app returns an error.

iso4app.Distance class

Constants used to indicate distance values.

If you need to use other values, for example 2857 meters you can use directly the string "2857m".

iso4app.Time class

Constants used to indicate time values.

If you need to use other values, for example 1354 seconds you can use directly the string "1354s".

iso4app.Mobility class

Constants used to indicate travel type values.

iso4app.Speed class

Constants used to indicate speed type values.

iso4app.Concavity class

Constants used to indicate the concavity of the resulting polygon.

Higher value you set, more polygon points you get.

iso4app.Buffering class

Constants used to indicate how to buffer the resulting polygon.

Higher value you set, more buffer size you get. The value in meters are indicative only and may vary depending on the resulting polygon.

A request to the Iso4app API includes the basic elements shown in the following table.

In addition you have to specify the parameters below.

Below a sample call for an Isodistance.

http://www.iso4app.net/rest/1.3/isoline.geojson?licKey=87B7FB96-83DA-4FBD-A312-7822B96BB143
&type=isodistance
&value=10000
&lat=43.334098
&lng=-1.7920697
&approx=1000
&mobility=motor_vehicle
&speedType=normal
&reduceQueue=false
&avoidTolls=true
&restrictedAreas=false
&fastestRouting=true
&concavity=6
&buffering=3
&reqId=A57X

XML Response

See isoline.xsd schema.

The API returns a top-level "isoline" element as the answer to a isoline resource.
Within the root tag you'll find:

See isoline.xml sample.

JSON Response

In the json format the returned object corresponds to the isoline object.
The information are the same presented in the xml format.
In json format the polygons collection contains a variable number of polygon object; every polygon object has its exterior and interior property (see note [*]).
Every ring is represented as an array element.

See isoline.json sample.

GEOJSON Response

The geojson isoline is expressed as a FeatureCollection.
There are three features: input point, start point and isoline.
The geometry object of the first two properties is a Point while the geometry for the isoline representation is a Multipolygon geometry object (see note [*]).
The properties are the same properties discussed in the XML RESPONSE section.

See isoline.geojson sample.

[*] Iso4app will provide more than one polygon and the interior ring only in the future, when public transport isochrones will be available.

HTTP Status Codes

Iso4app rest API supports the standard HTTP status codes.

Poi clustering gives you a way to group your POI on clusters based on their distance or time from a starting point.

Poi clustering limitation: free Api-key is limited to 20 poi. Paid Api-key is limited to 200 poi.

A request to the Iso4app API includes the basic elements shown in the following table.

In addition you have to specify the parameters below.

Below a sample call for a Poi Clustering.

http://www.iso4app.net/rest/1.3/poiClustering.json?licKey={YOUR_API_KEY}
&type=isochrone
&values=120,300,480
&poiList=1 42.4410680 19.2471670,2 42.4384160 19.2473170,3 42.4389610 19.2656800,4 42.4402750 19.2649500,5 42.434247 19.279333
&lat=42.4386290
&lng=19.2516300
&approx=1000
&mobility=motor_vehicle
&speedType=normal
&reduceQueue=false
&avoidTolls=true
&speedLimit=30
&concavity=6
&buffering=3
&reqId=A57X

XML Response

See poicluster.xsd schema.

The API returns a top-level "poiCluster" element as the answer to a poiClustering resource.

See poicluster.xml sample.

JSON Response

In the json format the returned object corresponds to the poiClustering object.
The information are the same presented in the xml format.

See poicluster.json sample.

GEOJSON Response

The geojson is expressed as a FeatureCollection.
There are five features: input point, start point, one or more cluster and one or more poi.

See poicluster.geojson sample.

To get the iso4app Engine simply include the script:

    <!-- Iso4App library  -->
    <script src="http://www.iso4app.net/api/js?v=1.2&lkey=YOUR_API_KEY"></script>

and declare the engine variable:

    <script;>
       var engine = new iso4app.Engine();
    </script>

In order to use iso4app API you have to specify an API Key (YOUR_API_KEY).
After the registration in the iso4app web site we send you a key with a limited number of credits; you can use it for development purposes.

iso4app.Engine class

If you prefer you can use the iso4app toolbar in your GUI.
Using iso4app toolbar is simple, you have to create a DIV element and obtain a reference to this element in the browser's DOM. When you create the iso4app Engine you'll pass the DIV reference to the constructor.
In this case when you'll invoke the method getIsoline() you have to provide only latitude and longitude of your point; iso4app will read the other parameters directly from the toolbar.

iso4app.Isoline class

Isoline object returned from the engine getIsoline method.

Input Point: the point you specify (lat,lng) when you invoke the method getIsoline()

Start Point: when you give iso4app an Input Point it looks for the nearest point having an isoline associated to it. If the "as the crow flies" distance between "input point" and "start point" exceeds the maxApprox values, iso4app returns an error.

iso4app.Distance class

Constants used to indicate distance values.

If you need to use other values, for example 2857 meters you can use directly the string "2857m".

iso4app.Time class

Constants used to indicate time values.

If you need to use other values, for example 1354 seconds you can use directly the string "1354s".

iso4app.Mobility class

Constants used to indicate travel type values.

iso4app.Speed class

Constants used to indicate speed type values.

A request to the Iso4app API includes the basic elements shown in the following table.

In addition you have to specify the parameters below.

Below a sample call for an Isodistance.

http://www.iso4app.net/rest/1.2/isoline.geojson?licKey=87B7FB96-83DA-4FBD-A312-7822B96BB143
&type=isodistance
&value=10000
&lat=43.334098
&lng=-1.7920697
&approx=1000
&mobility=motor_vehicle
&speedType=normal
&reduceQueue=false
&avoidTolls=true
&speedLimit=30
&reqId=A57X

XML Response

See isoline.xsd schema.

The API returns a top-level "isoline" element as the answer to a isoline resource.
Within the root tag you'll find:

See isoline.xml sample.

JSON Response

In the json format the returned object corresponds to the isoline object.
The information are the same presented in the xml format.
In json format the polygons collection contains a variable number of polygon object; every polygon object has its exterior and interior property (see note [*]).
Every ring is represented as an array element.

See isoline.json sample.

GEOJSON Response

The geojson isoline is expressed as a FeatureCollection.
There are three features: input point, start point and isoline.
The geometry object of the first two properties is a Point while the geometry for the isoline representation is a Multipolygon geometry object (see note [*]).
The properties are the same properties discussed in the XML RESPONSE section.

See isoline.geojson sample.

[*] Iso4app will provide more than one polygon and the interior ring only in the future, when public transport isochrones will be available.

HTTP Status Codes

Iso4app rest API supports the standard HTTP status codes.

The Iso4App API is currenlty available in the geographical zones presented in the table below.
Please contact us at if you need another one.

(*) isolines are limited to the zone boundary.
This zone is not connected to other neighboring zones covered by Iso4App.

Freemium (no registration)
If you use the demo API Key 87B7FB96-83DA-4FBD-A312-7822B96BB143 you can ask for 10km isodistances and 10 minutes isochrones. This API Key is used in the demo page, and you can use it for development purposes.

Freemium (registration required)
After registration we give you a personal API Key by which you can ask for every type of isolines; you can use it in the demo page or for development purposes.
This API key is limited in credits and time.

Premium (registration required)
You can extend your API Key purchasing new credits.

Credits cost per isoline type:

Thematic map credit usage:
 - ISOCHRONE AND ISODISTANCES with OSM category: isoline credits are multiplied by 4.
 - ISODISTANCES with categories other than OSM: isoline credits + 10 credits + 4 credits every 500 meters.
 - ISOCHRONES MOTOR VEHICLE with categories other than OSM: isoline credits + 10 credits + 4 credits every minute.
 - ISOCHRONES BICYCLE with categories other than OSM: isoline credits + 10 credits + 3 credits every minute.
 - ISOCHRONES PEDESTRIAN with categories other than OSM: isoline credits + 10 credits + 2 credits every minute.

Other credit consumption:

• Uploading/Showing the polygon constraint: 1 credit
• Export isolines (GeoJson or KML or KMZ): 4 credits for each isoline.
• Google Places search: 1 credit for search and 1 credit for places selection.
• Street Network: isoline credits are multiplied by 4.
• Layer of POIs: Uploading: 5 credits + 1 credit each 25 POIs. Removing: 2 credits. Showing(**): 0 credits the first 100 POIs. Exceeded POIs: 1 credit each 200 POIs.
• Scenario: Saving: 4 credits for each isoline. Removing: 2 credits. Showing: 0 credit.

On our Online App, when the parameters panel is opened, the credits calculator will be shown. The calculator show the isoline cost. The use of other features (layer/scenario) will be accounted without being shown.

(*) The response time depends on the number of ways to analyze. You can have a response less then 1 second as well as greather than 1 minute

(**) for each map refresh (pan/zoom) credits will be charged. In order to avoid charging you have to use a high level of zoom (closer to the ground)

Available license:

Monthly Plan

- Basic plan start from 2000 credits at fixed cost.

- After 2000 credits you pay according to consumption.

- You can choose the monthly limit.

Please ask for quotation!

Pay as you go

- Start from 2000 credits.

- You can recharge it at any time.

- After the expiration your API-Key will be stopped, however the ramaining credits will be valid and usable after a recharge.

- Payment in advance.

Options and prices available after registration!