Proc GINSIDE Optimization

Reply
New Contributor
Posts: 3

Proc GINSIDE Optimization

Does anyone know of any tips to optimize proc GINSIDE? It just seems like it is using a fair amount of I/O time. I didn't see an documentation on this in particular, but is there any particular index that you could put on either the input table or the map table that would speed up the process? I am mapping points into 2000 block groups, and it seems to be faster if I split up the map datasets into states. I could go further and do counties but that would be a lot of tables. Does anyone else have any similar tests or know of any techniques with this proc?

Thanks--

Super Contributor
Posts: 398

Re: Proc GINSIDE Optimization

I'm running into the same issue if anyone has any ideas.  I know this is an old post but I have over 600 million rows of census block data.

Super User
Posts: 10,483

Re: Proc GINSIDE Optimization

Is your data 600 million records or the block level map boundary data file?

Super Contributor
Posts: 398

Re: Proc GINSIDE Optimization

Hi ballardw,

It's the block level map boundary data file.  My address file has a little more then 13,000.

Thank you

Ask a Question
Discussion stats
  • 3 replies
  • 294 views
  • 0 likes
  • 3 in conversation