Proceed to GeoCommunity Home Page


SpatialNewsGIS Data DepotGeoImaging ChannelGIS and MappingSoftwareGIS JobsGeoBids-RFPsGeoCommunity MarketplaceGIS Event Listings
HomeLoginAccountsAboutContactAdvertiseSearchFAQsForumsCartFree Newsletter

Sponsored by:


TOPICS
Today's News

Submit News

Feature Articles

Product Reviews

Education

News Affiliates

Discussions

Newsletters

Email Lists

Polls

Editor's Corner


SpatialNews Daily Newswire!
Subscribe now!

Latest Industry Headlines
SiteVision GIS Partnership With City of Roanoke VA Goes Live
Garmin® Introduces Delta™ Upland Remote Trainer with Beeper
Caliper Offers Updated Chile Data for Use with Maptitude 2013
Southampton’s Go! Rhinos Trail Mapped by Ordnance Survey
New Approach to Measuring Coral Growth Offers Valuable Tool for Reef Managers
Topo ly - Tailor-Fit for Companies' Online Mapping Needs

Latest GeoBids-RFPs
Nautical Charts*Poland
Software & Telemetry GPS
Spatial Data Management-DC
Geospatial and Mapping-DC
Next-Gen 911-MO

Recent Job Opportunities
Planner/GIS Specialist
Team Leader- Grape Supply Systems
Geospatial Developer

Recent Discussions
Raster images
cartographic symbology
Telephone Exchange areas in Europe
Problem showcasing Vector map on Windows CE device
Base map

GeoCommunity Mailing List
 
Mailing List Archives

Subject: Re: [gislist] Protocol for citing sources of data? - an example
Date:  01/16/2007 01:45:00 PM
From:  Marcus Brast



I like the idea of the Easter Egg in addition to the more open citing of
the info, prevents someone from just copying the info and deleting the
blatant cite.

Marcus W. Brast
IT Manager/Senior GIS Analyst
Berg-Oliver Associates, Inc.
14701 St. Mary's Lane, Suite 400
Houston, TX 77079
Work: 281-589-0898 ext. 30
Mobile: 832-335-5094
Fax: 281-589-0007
mbrast@bergoliver.com


------------------------------------------------------------------------
--
---------------------------
The information transmitted is intended only for the person
or entity to which it is addressed and may contain confidential
and/or privileged material. If you are not the intended recipient
of this message you are hereby notified that any use, review,
retransmission, dissemination, distribution, reproduction or any
action taken in reliance upon this message is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer. Any views expressed in this message
are those of the individual sender and may not necessarily reflect
the views of the company.
-----------------------------
------------------------------------------------------------------------
--


-----Original Message-----
From: gislist-bounces@lists.geocomm.com
[mailto:gislist-bounces@lists.geocomm.com] On Behalf Of DickBoyd@aol.com
Sent: Tuesday, January 16, 2007 12:13 PM
To: J.CHAMBERLIN@CGIAR.ORG: kmwolfe@adelphia.net:
jeremy_olynik@hotmail.com: pibinko@gmail.com: gislist@lists.geocomm.com
Subject: Re: [gislist] Protocol for citing sources of data? - an example


In a message dated 1/16/2007 3:25:44 A.M. Pacific Standard Time,
J.CHAMBERLIN@CGIAR.ORG writes:

I think you have an obligation to cite whenever possible. There are
many
ways to indicate the value-addition that you have provided, without
neglecting to give credit to your inputs. If a map or table that I
produce for publication draws in any substantial way from someone
else's
primary dataset, I might cite something like this within the text:

Source: Author's calculation, based on CIESIN/IFPRI/WB/CIAT (2006).



Another means of quoting the source are the little personal Easter Eggs

added to the map. Cartographers often add a fictitious road, or give a
personal
name to some feature, or introduce an error or use an open symbol, such
as a
star to indicate some feature which normally calls for a solid star. Or
the
legend is toggled. Normally the legend is not visible. A series of
commands, hot
keys or the like is required to view this hidden data.

If someone does copy their work, the original identification established
by
these tags is still there.

Metadata is good. Possibly the user of the data has a metadata link in
one
of the tags.

Being able to identify the source of data simplifies quality control.
Those
intermediate users of copied data feel no motivation to correct errors.
So if
someone else tells them of an error, the most likely response is
nothing. Or
if there is a response it is along the lines of "he's no my job". Or to

correct the error only in that application and allow the error to
continue with
other uses of the prime data. The thinking is possibly what they don't
know
won't hurt them.

_DickBoyd@aol.com_ (mailto:DickBoyd@aol.com)
_______________________________________________
gislist mailing list
gislist@lists.geocomm.com
http://lists.geocomm.com/mailman/listinfo/gislist

_________________________________
This list is brought to you by
The GeoCommunity
http://www.geocomm.com/
_______________________________________________
gislist mailing list
gislist@lists.geocomm.com
http://lists.geocomm.com/mailman/listinfo/gislist

_________________________________
This list is brought to you by
The GeoCommunity
http://www.geocomm.com/

Sponsored by:

For information
regarding
advertising rates
Click Here!

Copyright© 1995-2012 MindSites Group / Privacy Policy

GeoCommunity™, Wireless Developer Network™, GIS Data Depot®, and Spatial News™
including all logos and other service marks
are registered trademarks and trade communities of
MindSites Group