V1.6.1-Beta - 2020-05-27

Features

  1. PAVAPI-936 - Support for Multiple Coordinate Reference Systems. You can now control the CRS used by response spatial data. Depending on your use-case you might need data represented in WGS 84 (a global datum) or GDA-2020 Australia’s new datum. With this new feature, you can control the spatial representation through a new header removing the need for complex transformation on your client end. This feature is essential as the government and other entities that use spatial data start the move to Australia’s new Datum GDA-2020, for more detail on what GDA-2020 is or why you should care about the spatial accuracy of your data. Check out this link here
  2. PAVAPI-392 - Add support for GDA 2020 & GDA 94 & WGS 84 & AGD-66

An excellent video by Small Island Studio on why GDA 2020 is so important to all of us.

Further resources on Datums and spatial accuracy

Improvements

  1. PAVAPI-881 - Serve Get Address from new faster scalable infrastructure (10% faster get address calls)
  2. PAVAPI-863 - Improved daily data load process, reduced execution time

Bug Fix

  1. PAVAPI-586 - Further De-Duplicate addresses between G-NAF and G-NAF Live
  2. PAVAPI-819 - Multiple values for addressType is not allowed
  3. PAVAPI-940 - Remove special characters

V1.5.14 – 2020-02-13

Bug Fix

  1. PAVAPI-642 – Bug: incorrect handling of: ‘unit 9 s’ (partial input sometimes returns no suggestions)
  2. PAVAPI-763 – Bug: searches with period between state abbreviations (e.g. N.S.W.)
  3. PAVAPI-766 – Bug: extremely large street number input causes status 501 (e.g 208201911122 Smith st)

Improvements

  1. PAVAPI-720 - Improvement: More matching of alternative spellings of postal addresses (e.g. Post Office Box)
  2. PAVAPI-701 - Improvement: Reduction of suggestions with no match at all. In our testing this has resulted in 3.5% more queries are responding with suggestions now. Below are some examples of queries that now return results.
    1. Examples 4 CIRCULAR QUAY WEST, THE ROCKS NSW 2000
    2. Example: 14 city centre mall

Known Issues

  1. PAVAPI-661 – Bug: 985 addresses have no formatted address due to missing postcode (e.g. add4806828d5a30)
  2. PAVAPI-753 – Bug: use of addressType=mailing and dataset=gnaf or gnaflive returns PO Boxes when it should not
  3. PAVAPI-222 - Bug: Strata Plan Addresses has a blank character in their lotIdentifier field

V1.5.13 - 2020-02-06

Features

  1. a

Bug Fix

Improvements

Known Issues


V1.5.10 - 2019-12-02

Bug Fix

  1. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive
  2. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal

Improvements

  1. Significant backend infrastructure improvements to increase scalability and performance
  2. PAVAPI-584 - Improvement: performance of locality name search
  3. PAVAPI-626 - Suggestion Response Time Improvements, six of the eight performance improvements applied.
  4. Improved infrastructure alerting and monitoring.

Known Issues

  1. PAVAPI-626 - Suggestion Response Time Improvements, this is an epic that holds eight stories around improvements to suggestion response time
  2. PAVAPI-600 Street suffix support in parsed suggestion engine
  3. PAVAPI-584 - Improvement: performance of locality name search
  4. PAVAPI-222 - Bug: Strata Plan Addresses has a blank character in their lotIdentifier field
  5. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive

Bug Fix

  1. PAVAPI-633 - Bug: PostCode mistakes, return 0 results.

Known Issues

  1. PAVAPI-626 - Suggestion Response Time Improvements, this is an epic that holds 8 stories around improvements to suggestion response time
  2. PAVAPI-600 Street suffix support in parsed suggestion engine
  3. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal
  4. PAVAPI-584 - Improvement: performance of locality name search
  5. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive
  6. PAVAPI-222 - Bug: Strata Plan Addresses has blank character in their lotIdentifier field
  7. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive

V1.5.8-beta - 2019-11-08

Bug Fix

  1. PAVAPI-468 Improved suggestions when no Unit Type is entered in query

Improvements

  1. PAVAPI-618 Partial implementation of improved ranged numbered address ranking

Known Issues

  1. PAVAPI-626 - Suggestion Response Time Improvements, this is an epic that holds 8 stories around improvements to suggestion response time
  2. PAVAPI-600 Street suffix support in parsed suggestion engine
  3. PAVAPI-633 - Bug: PostCode errors return 0 results
  4. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal
  5. PAVAPI-584 - Improvement: performance of locality name search
  6. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive
  7. PAVAPI-222 - Bug: Strata Plan Addresses has blank character in their lotIdentifier field
  8. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive

V1.5.7-beta - 2019-11-05

Bug Fix

  1. PAVAPI-627 - query with lower case charactors is very slow.
  2. PAVAPI-607 - messages missing when no results are returned
  3. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive

Improvements

  1. PAVAPI-578 - Performance improvement on suggestions that start with a street name - Example St Kilda Rd or Victoria St
  2. PAVAPI-595 and PAVAPI-611 - Improved handelling of ranged street number queries - Example 47-52 HENRY COX DR or 121-133 CAPITOL or 23-25 SUTHERLAND CR
  3. PAVAPI-599 - Timeout or slow performance when street name has only 1 char - Example unit 5/2 s
  4. PAVAPI-578 - Improvement: queries starting with a street name only are slower than we’d like - Example smith st takes 7 seconds to return suggestions

Known Issues

  1. PAVAPI-626 - Suggestion Response Time Improvements, this is an epic that holds 8 stories around improvements to suggestion response time

  2. PAVAPI-600 Street suffix support in parsed suggestion engine

  3. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal

  4. PAVAPI-584 - Improvement: performance of locality name search

  5. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive

  6. PAVAPI-222 - Bug: Strata Plan Addresses has blank character in their lotIdentifier field

  7. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive


V1.5.6-beta - 2019-10-11

Bug Fix

  1. PAVAPI-587 – Unit numbered queries with less than 3 characters in street name return very poor suggestions. –Example unit 6 113 c returns no unit 6 113 suggestions.
  2. PAVAPI-585 – Duplicate suggestions (exactly the same suggestions) - Example query 180 oxford street c returns the same suggest as the top 3 suggestions.
    1. PAVAPI-606 - PO BOX query on GNAF returns status 503 error

Known issues

  1. PAVAPI-595 - Ranged number handling
  2. PAVAPI-599 - Timeout or slow performance when street name has only 1 char - Example unit 5/2 s
  3. PAVAPI-600 Street suffix support in parsed suggestion engine
  4. PAVAPI-468 Improved suggestions when no Unit Type is entered in query
  5. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal
  6. PAVAPI-584 - Improvement: performance of locality name search
  7. PAVAPI-578 - Improvement: queries starting with a street name only are slower than we’d like - Example smith st takes 7 seconds to return suggestions
  8. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive
  9. PAVAPI-222 - Bug: Strata Plan Addresses has blank character in their lotIdentifier field
  10. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive

V1.5.5-beta - 2019-10-04

Bug Fix

  1. PAVAPI-582 - Slow performing query when query has just unitNumber and streetNumber only – Example query unit 6 113

Improvement

  1. PAVAPI-591 - The parsed engine is the default engine in beta no more /parsed
  2. PAVAPI-596 - Short queries timeout or are just slow - example 162 F or 10 R or 162 Fox

Known issues

  1. PAVAPI-587 – Unit numbered queries with less than 3 characters in street name return very poor suggestions. –Example unit 6 113 c returns no unit 6 113 suggestions.
  2. PAVAPI-585 – Duplicate suggestions (exactly the same suggestions) - Example query 180 oxford street c returns the same suggest as the top 3 suggestions.
  3. PAVAPI-595 - Ranged number handling
  4. PAVAPI-606 - PO BOX query on GNAF returns status 503 error
  5. PAVAPI-578 - Improvement: queries starting with a street name only are slower than we’d like - Example smith st takes 7 seconds to return suggestions
  6. PAVAPI-584 - Improvement: performance of locality name search
  7. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive
  8. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive
  9. PAVAPI-222 - Bug: Strata Plan Addresses has blank character in their lotIdentifier field (PAV)
  10. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal
  11. Street suffix parsing

NOTE: The next release will have the parsed engine being the default behaviour of the Beta API.



V1.5.4-beta - 2019-09-26

New Features:

  1. PAVAPI-347 - Neighbouring locality matching
  2. PAVAPI-347 - Alias locality matching
  3. PAVAPI-490 - Street name miss spellings / phonetic matching
  4. PAVAPI-490 - Locality name miss spellings / phonetic matching
  5. PAVAPI-560 - Ranking of results based on customer feedback
  6. PAVAPI-454 – primary addresses are prioritised in suggestion response
  7. PAVAPI-503 - Suggestions with or without building name entered
  8. All addresses are serched as default behaviour – with the option to configurable dataset or addressType parameters

Bug Fix

  1. PAVAPI-583 – Site name incorrectly mapped from parser to query Example query The village Unit 15 now returns THE VILLAGE UNIT 15 118 ELIZABETH ST, ASHFIELD NSW 2131
  2. PAVAPI-226 - Bug: No matching suggestions for street numbers with a letter suffix Example query 27 araban now returns 27A Arabana St Aranda ACT
  3. PAVAPI-260 - Bug: Some addresses have a postcode of 9999 Example query 1435 Cotter R now returns the correct locality and postcode 1435 COTTER RD, STROMLO ACT 2611
  4. PAVAPI-508 - When searching combined dataset some addresses are not found if sitename is not included Example query 8 djaadjawan close now returns results in parsed endpoint

Improvement

  1. PAVAPI-537 - Suggestions in the Parsed Engine have been greatly improved in performance

Known issues

  1. PAVAPI-585 – Duplicate suggestions (exactly the same suggestions) Example query 180 oxford street c returns the same suggest as the top 3 suggestions, this is due to alias and neighbouring locality matching. IN PROGRESS
  2. PAVAPI-582 – Slow performing query when query has just unitNumber and streetNumber only Example query unit 6 113 IN PROGRESS
  3. Ranged number handling more details coming
  4. Street suffix parsing more details coming
  5. PAVAPI-587 – Unit numbered queries with less than 3 characters in street name return very poor suggestions. Example unit 6 113 c returns no unit 6 113 suggestions. NEXT
  6. PAVAPI-578 - Improvement: queries starting with a street name only are slower than we’d like Example smith st takes 7 seconds to return suggestions BACKLOG
  7. PAVAPI-584 - Improvement: performance of locality name search BACKLOG
  8. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive BACKLOG
  9. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive BACKLOG
  10. PAVAPI-222 - Bug: Strata Plan Addresses has blank character in their lotIdentifier field (PAV) BACKLOG
  11. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal BACKLOG

V1.5.2-beta - 2019-08-06

Bug Fix

  1. PAVAPI-495 - Bug: Preventing matching of PO BOX and other mailing address types in Parsed Engine

Improvement

  1. PAVAPI-500 - Parsed Engine now supports Dataset parameter
  2. PAVAPI-502 - Parsed Engine now supports addressType parameter
  3. PAVAPI-504 - Parsed Engine now supports stateTerritory parameter
  4. PAVAPI-480 - Parsed Engine Street number and ranged number fuzzy matching
  5. PAVAPI-506 - Added profiling to parsed engine for analysis on query performance
  6. PAVAPI-417 - Testing Framework for parsed engine

Known issues

  1. Suggestions in the Parsed Engine are slow and need to be optimised.
  2. PAVAPI-511 - Bug: GetSuggestion stateTerritory validation error returns 404 not status 400 for gnafLive
  3. PAVAPI-186 - Bug: Missing Predictions for Other Territories in gnafLive
  4. PAVAPI-222 - Bug: Strata Plan Addresses has blank character in their lotIdentifier field (PAV)
  5. PAVAPI-486 - Bug: Aliases addresses returned from suggest as if principal
  6. PAVAPI-226 - Bug: No matching suggestions for street numbers with a letter suffix
  7. PAVAPI-260 - Bug: Some addresses have a postcode of 9999
  8. PAVAPI-529 - Bug: missing postal

V1.5.1-beta - 2019-07-15

Bug Fix

  1. PAVAPI-447 - Confidence -1 addresses on GNAF returned as suggestions
  2. PAVAPI-472 - Mail Address duplicate addresses
  3. PAVAPI-473 - Combined Dataset not supporting street first suggestions
  4. PAVAPI-474 - No suggestions from unit type in query with building name first
  5. PAVAPI-476 - levelType is abbreviated in full address string
  6. PAVAPI-484 - Addresses not correctly idenfied as the same address in multiple datasets
  7. PAVAPI-485 - “CARE PO” and “CMA” addresses not found in combined but in Mail Address
  8. PAVAPI-492 - street_type and street_description values are reversed in GNAF addresses
  9. PAVAPI-512 - levelType abbreviated matching regression in Mail Address

Improvement

  1. PAVAPI-501 - Parsed Engine now supports maxNumberOfResults
  2. PAVAPI-494 - More standardization of address string format between GNAF,Mail Address and GNAF Live
  3. PAVAPI-483 - Parsed Engine supports predictions on all address elements

Known issues

  1. PAVAPI-495 - Bug: Preventing matching of PO BOX and other mailing address types in Parsed Engine
  2. PAVAPI-226 - Bug: No matching suggestions for street numbers with a letter suffix
  3. PAVAPI-260 - Bug: Some addresses have a postcode of 9999

V1.5.0-beta - 2019-06-07

Features

  1. PAVAPI-378 - Single predictions on all addresses (combined address dataset)
  2. PAVAPI-392 - Filter predictions by physical or mailing address (addressType)
  3. PAVAPI-394 - Prototype parsed Suggest Engine (Machine Learning address suggestions)
  4. PAVAPI-400 - New dataset attribute returned to describe which dataset an address is found in
  5. PAVAPI-479 - Parsed Engine Street first predictions

Bug Fix

  1. PAVAPI-460 - Lot number in formatted_address string when the street has a street number

V1.4.1 - 2019-04-18

Bug Fix

  1. PAVAPI-402 - missing unit + level numbered addresses in Mail Address

Improvement

  1. PAVAPI-451 - Suggestions when no unitType is entered in the query
  2. PAVAPI-442 - Suggestions when the query starts with a street name first

V1.4.0 - 2019-04-11

Features

  1. PAVAPI-331 - Fuzzy Logic on GNAF/PAF addresses
  2. PAVAPI-332 - Increased maxResults
  3. PAVAPI-346 - GNAF - Alias localities
  4. PAVAPI-348 - GNAF/Mail Address - Street name/type abbreviation
  5. PAVAPI-349 - GNAF/Mail Address - Plural and non-plural handling
  6. PAVAPI-351 - Mail Address - PO Box alternative Spellings
  7. PAVAPI-384 - GNAF/Mail Address - range number formatting
  8. PAVAPI-401 - GNAF/Mail Address - unit number formatting
  9. PAVAPI-404 - GNAF - Consistency in stateTerritory to be abbreviated
  10. PAVAPI-410 - GNAF/Mail Address - levelType fuzzy matching
  11. PAVAPI-434 - GNAF/Mail Address - Get predictions when you don’t enter a building or site name

Bug Fix

  1. PAVAPI-458 - Both dataset and contributor are in the wrong location in response

Improvement

  1. PAVAPI-450 - Support for both API-Key and Authorization header

V1.3.5-beta - 2019-04-04

Bug Fix

Improvement

Known issues

V1.3.4-beta - 2019-03-22

Bug Fix

Improvement

Known issues

V1.3.3-beta - 2019-03-06

Bug Fix

  1. PAVAPI-258 - QLD data load process failure
  2. PAVAPI-352 - NSW daily process stalled
  3. PAVAPI-374 - Suggestions not returned once locality is entered
  4. PAVAPI-375 - Mail Address

V1.3.2-beta - 2019-02-25

Bug Fix

  1. PAVAPI-366 - Get Address (GNAF) response bugs (type,empty string,N/A)
  2. PAVAPI-367 - Get Address missing dataset and contributor key/value
  3. PAVAPI-368 - Get Address missing postal_delivery_number and postal_delivery_type
  4. PAVAPI-369 - Get Address (Mail Address) response bugs (type,empty string,N/A)
  5. PAVAPI-382 - Missing suggestions when substituting street type abbreviations

V1.3.0-beta - 2019-01-31

Features

  1. PAVAPI-266 - New data source, GNAF.
  2. PAVAPI-267 - New data source, Mail Address
  3. Dataset parameter to select dataset

Bug Fix

  1. PAVAPI-172 - Missing SA addresses
  2. PAVAPI-326 - VIC addresses update stalled
  3. PAVAPI-192 - logging bug for custom attribute
  4. PAVAPI-329 - GNAF addresses missing

Improvement

  1. PAVAPI-275 - Performance Testing Framework
  2. PAVAPI-283 - New API doc

V1.2.1-beta - 2018-11-29

Bug Fix

  1. PAVAPI-214 - Addresses in A’Beckett St not found (apostrophe bug)

Improvement

  1. Implement CICD
  2. Seperate codebase into API and database

V1.2.0-beta - 2018-11-16

Features

  1. Sensative data filtering

V1.1.2 - 2018-09-20

Bug Fix

  1. PAVAPI-216 - Suburb values not updated for The Hills LGA
  2. PAVAPI-171 - Daily reporting not logging
  3. PAVAPI-189 - NEW QLD addresses missing street type if longer than 5 char
  4. PAVAPI-193 - Get Address calls returning null flagged as successful
  5. PAVAPI-194 - NSW Daily address supply stalled
  6. PAVAPI-229 - Demo app slow and unresponsive

V1.1.0 - 2018-01-14

Features

  1. PAVAPI-93 - State/Territory suggestions filtering from a comma-sepperated list

Bug Fix

  1. PAVAPI-146 - Duplicate addresses
  2. PAVAPI-147 - Environment switching failure

V1.0.1 - 2017-12-22

Bug Fix

  1. PAVAPI-123 - Fix demo page
  2. PAVAPI-105 - Missing suggest calls
  3. PAVAPI-136 - Manually update NT data
  4. PAVAPI-72 - Fix http error status code logs

V1.0.0 - 2017-10-12

Features

  1. Get Endpoint that takes a partial adderess string and returns autocomplete suggestions
  2. Get Endpoint that returns address details given a unique temporary identifier
  3. Daily (where possible) updated addresses
  4. Control the number of possible suggestions returned with a parameter
  5. Only Jurisdictional address data is used