Widget - using data with no WFS endpoint

Available for  Pozi Pro and Pozi Enterprise subscribers.


This article describes using a Pozi Widget when the data behind the Widget is not stored on data.gov.au, or is not available as a WFS endpoint on data.gov.au.  For details using a Pozi Widget when the data is available on data.gov.au with a WFS endpoint, please refer to the article "Widget - using WFS endpoint on data.gov.au".

The Pozi Widget is a html component that can be embedded into your organisation's website via an  iframe element, to add geospatial data search capability.

When the widget starts you can enter a physical address and when the address is selected the system retrieves the configured geospatial dataset.

For example, by typing in a home address, it could retrieve your next rubbish collection date.

Quick start example

Scenario 1: Display data under search box

This example will return the next rubbish pickup date for any address in Cardinia Shire.


Tip: Open URL and try "3 Albert St"

Scenario 2: Open map in new tab at address

This example will open a new tab with the Pozi map at the new address.


Tip: Open URL and try "3 Albert St"

(Important note: The default setting in Internet Explorer and Firefox is to restrict popups. This may result is the user being presented with a browser dialog asking them to first enable browser popups. To avoid this issue the URL can be edited to remove the "&newtab=true" text.  However, this will result in the results of the address search appearing in the same tab. See further discussion regarding using newtab=true in the Optional Parameters section below)

URL Parameters

Required Parameters

Base URL


Note: Requires # on the end

widget=true is required to identify the URL request as being a widget.


This is the Card Layer Name as it appears in Pozi, after selecting a property.  

So for example, in Pozi we have clicked on a property in Cardinia which has displayed the data card in the image below, and we can see the see the specific name of the Waste and Recycling Collection data card.

Note however that the URL must include %20 to replace the spaces in the name, so it will actually look like this in the URL:  card=Waste%20and%20Recycling%20Collection


These are the Field names (one or more) as they appear in Pozi, after selecting a property.

To use the example above, in Pozi we have clicked on a property in Cardinia which has displayed the data card in the image below, and after selecting the Waste and Recycling Collection data card, we can see the field names we are interested in, for example, Next Rubbish Bin Collection (note that it is not case sensitive).

As with the card name above, the URL must include %20 to replace the spaces in the name, so it will actually look like this in the URL:  fieldnames=Next%20Rubbish%20Bin%20Collection

Multiple field names are separated by commas:  fieldnames=Next%20Rubbish%20Bin%20Collection,Next%20Green%20Waste%20Bin%20Collection

Optional Parameters


This parameter hides the fieldnames and only displays the field data.


For example:



If this parameter is added, the current page will be redirected to the Pozi map zoomed to the address.



If this parameter is added, the Pozi map will be loaded in a new tab zoomed to the address. Note this option can have issues with browser security such as the built in popup blockers, in particular in IE and Firefox. Whilst the user can change the settings in their browser to allow popups, depending on the expected customer, it may be more appropriate to avoid using the Newtab parameter and live with the downside of having the Pozi map load in the same tab as the address search was performed.



By default the font size of the widget text is set to 18. However, you can specify a different font size by using the optional font size parameter, for example:



The projection will normally be presumed to be WGS84 (EPSG=4326). It is possible to specify a different projection by explicitly declaring it in the URL (truncated here for clarity):


Note that this sort of parameter is referred to as a Hash Parameter, and is added to the URL using a forward slash (/) rather than the usual ampersand (&).

The most common projections (other than WGS84) can be reviewed here:


Using iframes

Example of using iFrame.  Note that multiple field names are separated by commas:

<iframe style="border:none; height: 300px; width: 100%; overflow: hidden;" src="https://centralgoldfields.pozi.com/widget.html#card=Waste Collection&fieldnames=Next Rubbish Pickup,Next Recycling Pickup,Next Green Waste Pickup,Next Hard Waste Pickup&fontsize=28" />

See other  iframe parameters:


Managing Scrollbars

When using a small iframe, you may encounter scrollbars. You can control the appearance of scrollbars using the CSS   overflow setting.

<style>     iframe {         overflow:hidden;     } </style> (...) <iframe scrolling="no" src="http://www.google.com" width="400px" height="300"></iframe>

For more information about overflow, see  https://developer.mozilla.org/en-US/docs/Web/CSS/overflow

Developer Notes

Example URL for testing in development environment: