[Big-devel] Dithering of geocode

[Jim C. <jr...@an...>]

Greg has just been checking our AVH implementation to ensure that we are 
dithering our public records appropriately.

You will notice on the CHAH AVH site we removed all the links to the 
portals until we  were happy that they we not delivering inappropriate data 
to the public.  Tim asked us to put them back because they are needed for 
promotional demonstration purposes.

He assured me the NSW one is ok so it is, now linked; I will be relinking 
CANB shortly, MEL looks ok unless I hear otherwise, I will relink that one 
too.  Ben - are you happy with PERTH?

Anyway, Greg and I have been talking about where the dithering takes 
place.  At the moment, each institution undertakes to dither the geocode on 
the provider side, strip out or dumb down the locality, etc. in response to 
a request, and when you look at the data there is not much in the way on 
consistency in how this is done.

For the geocode at least, is this something that could be done at the 
portal rather than (or as well as) at the provider side?  That is, could we 
ensure that each AVH  node ensures that the geocode is dumbed down to the 
nearest 5 minutes (or whatever), regardless of what precision it comes in 
at?   This would ensure a minimum tolerance, but individual institution 
could still deliver coarser information if they so wished according to 
their local policy.

jim

ps - does anyone have a current and official copy of the HISPID fields for 
public data consumption agreed by CHAH following the AD CHAH 
meeting?   This is a foundation document and sort of our equivalent to our 
version of the Darwin Core - it should be on the source forge site and as 
part of the distribution documentation somewhere...


~ Jim Croft ~ jr...@an... ~ 02-62465500 ~ www.anbg.gov.au/jrc/ ~