GISP Proposal for Exam Requirement

Last week the GISCI had a press release announcing:

GISCI Invites Comment on Proposed Examination Requirement

From the GISCI website:

“After much consideration and deliberation, the GIS Certification Institute (GISCI) invites you to review a proposal to update requirements for GIS Professional (GISP) certification.  Key among the proposed updates is the addition of a required examination.”

This press release is inviting people to comment on the proposal to update the GISP requirements to include a required examination.

Now, anyone that is already a GISP, or has considered becoming a GISP, or has followed the GISP saga, is probably well aware of the numerous debates on the many social networking sites with respect to ‘what’ being a GISP really means.  I have contributed to many of those discussions, and don’t intend to re-start or re-hash the details here.  All I’m going to say is, if you have an opinion on this topic, don’t sit back, go make your voice heard and get involved.

The proposal can be read here, and today the site went live, so go make your voice heard!

Until next time,
Take care

Warren M

Comments

Post a Comment

Popular posts from this blog

ArcGIS: Packaging error - General function failure

Image
Whoa... 2 posts within 2 months...  I'm on a roll baby...   :-) In today's episode I want to document what I've discovered with the following lovely error when attempting to create a Map Package: I've had this very insightful (hint:sarcasm) message box pop-up a number of times when trying to create a Map Package.  After much copying/pasting, renaming, re-connecting data sources I finally figured out what the problem was in this particular instance. This particular map had some DWG files connected to the map, and some of these DWG names contained a special character "#", and also contained extra 'dots' in the name to delimit a date.  For example: Name#-2013.04.09.dwg In my testing and trials, removing the '#' symbol did not resolve the issue, and it wasn't until I removed the extra 'dots' in the name that I was finally able to successfully generate the package.  Further testing revealed that the '#' symbol
Read more

More ArcGIS Woes with 'Special' Characters...

Image
It's no secret that I've griped and complained about many of ArcGIS's quirks that seem stuck or rooted in the 80's ...  One would think I wouldn't be surprised anymore when I come across such silly issues... But I am. The latest 'undocumented feature' I've discovered is that the Field Calculator will fail if there is forward slash ( '\' ) in the Layer name. ArcGIS 11 can't come soon enough.
Read more

ArcGIS Collector: Update Error Code 1006

Image
Alright, this is the second time this happened to me, and I neglected to document it the first time, so I had to search again to find the answer, so I will document it here, and now. Here goes... If you happen to come across ArcGIS Collector throwing an error when updating a feature, and the error states something along the lines of: Invalid untrusted Html content detected in field: Have no fear, there is a simple fix.  Well, that is, it's a simple fix if this is 'local' map, not accessible to the general public.  That's only because ESRI doesn't actually 'recommend' this fix. So what is 'this fix' I speak of? A little more background... If you have any fields that contain HTML content, there is a chance that Collector could see that as malicious content, and it will block it.  You can see a list of allowable HTML tags in Collector a this link . In my instance, I am running some database triggers to populate and update a URL field, where
Read more