Posted by
Cory Horner on
Mar 23, 2007; 7:43pm
URL: http://civicaccess.416.s1.nabble.com/civic-engagement-using-portal-pages-tp947p964.html
Tracey P. Lauriault wrote:
> Hey Cory,
>
> I like the conversation on the list to!
>
> See my comments below, just trying to make sure i am comprehend what you
> are saying
>
> . Cory Horner wrote:
>
>> There are 3 pieces to the whole puzzle:
>> 1. address to latitude-longitude
>>
>>
> is this the address of the hotspot? If so do you have a list of hotspots
> from isf mtl to start w/address soz you can get the lat long
>
I was talking more generally -- a hotspot, or someone's house. You are
correct though -- the ISF hotspots would figure out their lat-long
coords only once, and after that would only perform 2 and 3.
>> 2. latitude-longitude to riding(s)
>>
>>
> So you have a boundary file (polygon files) of the ridings and the
> hotspot lat long point files will overlay onto the riding polygon file
> soz you can see what is what and then you would add the riding as an
> attribute to the hotspots tables? What about the postal code files that
> are associated to the riding files?
>
We don't really have access to those -- and a postal code to riding
lookup isn't very accurate, as some people have indicated. It would be
better to go from an address directly to a riding, and then only get one
result. Alternatively, we could list all ridings within a x kilometer
radius of the address.
>> 3. riding to feed
>>
>>
> so i guess hotspot address to riding to feed and then to the portal page
>
That's it... for clarity let's draw a picture:
ISF portal page ----(lat-long coords)----> script
<------content----------
> What geomatics software are you using to do all this in?
Likely a PostgreSQL open-source database with PostGIS spatial
extensions. Shapefiles can be imported easily.
Cheers,
Cory.