Thanks for that, Chris.
The problem with various query parameters is that:
1)
I would want the equivalent of &search to work internally and externally. No problem internally as I have a LLPG point layer for staff users. But this would only work externally if I had an address point dataset (LLPG) in the public facing version, which for PSMA reasons I can't do.
2)
Most postcodes cover multiple addresses. So if I run a query calling on, say, SE15 4AW I would get back a query of 25 points. The beauty of &search in Stratus Connect (and I appreciate it may have been a customisation via RIA) is that all you’d need to add is &search=SE15 4AW and it would effectively place SE15 4AW into the search box, run a search on SE15 4AW and then return the first SE15 4AW it finds with a with a map marker.
Here’s a Stratus Connect example: http://maps.southwark.gov.uk/connect/southwark.jsp?tooltip=yes&search=SE15 4AW
It would be great to have this kind if functionality in SSA.