Skip to main content
  • EN

Currently, searching for a location in a workspace app’s geometry parameter window appends the search bar contents to Nominatim’s URL.

 

Example 1:

 

What gets appended does not allow users or workspace app authors to include additional parameters limiting users’ search results in the Nominatim URL. Adding parameters that are compatible with the q parameter such as countrycodes, limit, and layer to the Nominatim URL breaks the resulting GET request.

 

Example 2:

 

FME Flow should check if the Nominatim URL already includes parameters designed to limit users’ search results before deciding what to append so the final result is always a valid GET request such as: https://nominatim.openstreetmap.org/search.php?countrycodes=ca&limit=1&q=vancouver&format=jsonv2

 

The current workaround is to add the additional parameters in the search bar. Example: “vancouver&countrycodes=ca&limit=1” This is cumbersome for users.

 

Posted from:

 

Please also add the option to limit the geometry to a certain area. You can set the initial bounds but that still doesn't stop the user from creating a geometry on the other side of the world.

Great addition.

 

On the topic of the Nominatim API, restricting search results to a specific area is possible using the viewbox and bounded parameters.

I haven't really used the mapping part in FME before, but have used Nominatim.

Can you define a selfhosted Nominatim instance to use?

​@hkingsbury  Yes, it is possible to use a Nominatim API hosted elsewhere. Please see this article for reference.

Community Stats

31,073
Posts
117,799
Replies
38,834
Members

Latest FME

Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.