# Extent changing in ArcGIS Pro when shapefile added to map which only had basemap?

Using ArcGIS 10.3 for Desktop:

In ArcMap:

• Open a Blank Map
• Add Basemap of Imagery (but any basemap will do)
• Zoom to Australia (but any area will do)
• Add the countries shapefile from Natural Earth (but any shapefile that covers an area much larger than where the basemap has been zoomed to will do)
• Notice how the extent does not change which to me is the expected behaviour

In ArcGIS Pro:

• Create a project using Map.aptx
• Change the Basemap to Imagery (but any basemap will do)
• Zoom to Australia (but any area will do)
• Add the countries shapefile from Natural Earth (but any shapefile that covers an area much larger than where the basemap has been zoomed to will do)
• Notice how the extent changes to become the extent of the shapefile that was just added

I think the software behaviour observed in the last dot point is a bug, and am wondering if anybody has already reported this and has a bug (NIM) number that can be used to track its resolution?

When I submitted this to local Esri support they responded:

AcrGIS Pro is designed to interact with data differently than ArcMAp. The zooming to a input layers extent, is a modification within ArcGIS Pro which is designed to make it easier for users to interect with their data. This is not considered a bug and does not have a NIM number.

I still think it is a bug and will be interested to see if this software behaviour is changed to match that of ArcMap in a later release.

## Manage data

In ArcGIS Pro , you typically work in a project that is saved on your computer. However, you don't always need to save a project. Sometimes your tasks involve data preparation and management, and you don't need to make maps or solve analysis problems. In these situations, you can start ArcGIS Pro without creating a project. You can then process your data and close the application without saving a project.

• Estimated time: 60 minutes (including optional section)
• Software requirements:
• ArcGIS Pro
• ArcGIS Online portal connection

## ArcGIS Maps for Adobe Creative Cloud 2.2.2 patch (macOS) is now available

by XingdongZhang

ArcGIS Maps for Adobe Creative Cloud 2.2.2 patch (macOS) is now available. Download it from here. This patch addresses the issue of AIX files not opening for mac users with the latest Illustrator updates version 25.1 and above.

For a detailed description of the issue, please see the GeoNet post.

Please continue the conversations on our forums or contact Esri Technical Support if you encounter any issues. You can also post ideas on the ArcGIS Ideas site. ArcGIS Ideas is a good way for you to get involved in making our application better.

## Issue with snapping and performance speed

We have been encountering problems lately while editing (using 10 sp 2). The speed of ArcMap while editing slows to a crawl, and snapping will not work (unless classic snapping is enabled).

I was wondering if anyone else has encountered this issue?

Do you have a basemap layer (created either by Add Data > Add Basemap Layer or New Basemap Layer in the table of contents) in your map? We have found that sometimes large features in basemaps can cause snapping performance issues. If so, try turning off the basemap and seeing if snapping improves.

by RichardFairhurs t

We have been encountering problems lately while editing (using 10 sp 2). The speed of ArcMap while editing slows to a crawl, and snapping will not work (unless classic snapping is enabled).

I was wondering if anyone else has encountered this issue?

I also had this issue while editing. Make sure all of the data in your map is in the same projection. ArcMap will warn you which layers have a different projection than the data frame when you start editing. After I did this my editing jumped to near instant speed and snapping worked like a charm.'

I am experiencing similar performance issues with snapping in ArcGIS 10 SP4.

I've been searching for information on how the snapping environment works as it appears to require caching of all potential snapping geometry into memory when starting an edit session, but this thread is the only information I've found talking about performance issues.

My observations are similar. The fewer layers in the map document, the better editing/snapping experience. The smaller the files, the better the snapping experience. Switching to the classic snapping environment provides no boost in performance. I didn't test snapping using files in different projections/coordinate systems, but I think the comment regarding indexing is right on.

The biggest breakthrough came when I loaded only two layers in ArcMap and tested snapping to a 150Mb parcel shapefile and ArcMap fell on it's face and was excruciatingly slow with no snapping ability. Snapping on the same parcel file loaded into file geodatabase. very fast with no problems. Snapping performance on the same parcels loaded into SDE is somewhere in between. I can open a map document with several SDE layers (including parcels), start an edit session, and although ArcMap performance does not slow down noticeably, the interactive snapping does not appear regardless of which features over which I hover! I then walk away from my computer for 15 minutes, come back, and the interactive snapping magically starts working beautifully.

Please do not point us to help documentation on how to use snapping or another blog on how to effectively use the simple, flexible, and great new snapping environment. Someone please provide better detail on what ArcMap does to enable snapping when an edit session is started please so we can find work-arounds to these snapping performance issues.

Thanks for everyone who took part (567 responses in total). Check the GitHub for charts and full results:

65% United States, 34% Other

Largest other: Canada 10.6%, United Kingdom 4.6%, Australia 2.1%, Germany 1.8%, Netherlands 1.6%, Ireland 1.6%

Largest states: California 13%, Texas 8%, Virginia 5%, Colorado 5%, Pennsylvania 4%, Washington 4%

Age: 54% are between 25 and 34

52% of Masters/PhD students recommend getting one, just 5% say outright no

So, Should I get a Masters?, generally yes, but it depends on your circumstances.

50% are Mid level, I guess it is a pretty broad category

Pretty broad mix of work lengths:

How long have you been working? Not employed. 8.907563 Under 1 year 13.949580 1-2 years 11.764706 2-5 years 23.025210 5-10 years 22.352941 11-25 years 18.151261 26 or more years 1.848739

53% have GIS officially in their job title

Analyst is the most common job tile

1.4% do not use desktop GIS software at all

VS Code is the most popular IDE with 17.5% of people using it (up from 2 users total in 2019), overtaking PyCharm which has 13.5%.

In general: 88% use ArcGIS, 48% use QGIS, and 46% use Google Earth, 18% use AutoCAD

Outside of the big 2, GRASS has 9% usage, Global Mapper 6.5%, ENVI 6%, ERDAS 5%, and MapInfo 2%, and Idrisi 1%

As their primary GIS: 78% use ArcGIS, 16% use QGIS

This varies regionally: United States: ArcGIS 87.9% / QGIS 5.6% Canada: ArcGIS 80.0% / QGIS 11.7% United Kingdom: ArcGIS 38.5% / QGIS 53.8% Australia: ArcGIS 83.3% / QGIS 0% Germany: ArcGIS 30% / QGIS 70.0% Ireland: ArcGIS 66.7% / QGIS 22.2% Netherlands: ArcGIS 55.6% / QGIS 33.3% Europe as a whole: ArcGIS 45.6% / QGIS 49.4%

So if you are in the US/Australia, learn ArcGIS. If you are in Europe also learn QGIS.

Of ArcGIS users, 20% use Pro Exclusively (up from 6% in 2019), 19% do not use Pro at all (down from 31% in 2019). Clear change in trend: ArcGIS Pro Usage

71% do not use design software to finish maps. 8% use "Other" software to finish maps. Beating out Illustrator 7.6%, Illustrator & PhotoShop 3.9%, GIMP 3%, InkScape 2.8%, and PhotoShop 2.6%

60% work with primarily Vector data, 33% is 50/50, 6% Raster

43% of jobs do not require programming, 52% require Python (although 62% of people use Python), 30% require SQL, 19% require JavaScript, 6% C#, 4% .NET, 4% R, 2% Java, Arcade & C++ 0.4%

Database of choice: File Geodatabase (ESRI) 37%, PostgreSQL 21%, SQL Server 15%. However in the "Other GIS software" question, 28% use SQL Server. So people might use it and not like it. for 2023 ask 2 questions: What is your proffered database, how do you store your data in work. MySQL and Oracle are at 3.35%.

12% just use ShapeFiles (down from 13% is 2019 and 15.% in 2017), 3.5% use SQLite

Of those 6%, 11% got a raise as a result of getting it, and 31% had it paid for by their employer

66.7% use 2 monitors, 18.7% and around 12% use 1/just a laptop/tablet.

55% of job do not (or did not before COVID) require field work (include might be a better way to phrase it instead of require).

Only around 8% of jobs require field work at least once a week.

Sentiments: Management, Developer, Retirement

Sentiments: Learn to Code/Program, GIS is a tool, be open to learning (passion, innovation)

Not a huge impact on GIS as a profession in general. With 66% saying it did not make much difference to their GIS profession. 22% say a positive impact, just 12% had saw a negative impact.

71% are working from home at the time of the survey. 12% are back in the office, and 10% did not work from home at all. 6% were already home based.

50% expect to continue to work from home to some extent, 30% completely, and 18% will be going back/are back in the office.

So in general people are really happy with their choice of GIS, and the future looks optimistic.

The most important question on the survey:

Should we ban memes?

So combining that with the most common word from the word clouds, we get:

haha GIS go brrrr, which will be the official meme policy of r/GIS going forward.

This year we asked salary as an actual number. Which allows us to look at some of the data in terms of salary.

The Median salary for r/GIS (excluding answers below 5k) is: $60654 Gender in the responses does not seem to be a factor in pay. Being in the United States is a factor. With salaries around$10k higher in the US.

Programming vs Non-Programming.

If your job requires programming, the median salary after 1 years of work is around \$10k higher.

## SUPERFUND_IDEM_IN.SHP: Sites in Indiana on the IDEM Superfund Program List (Indiana Department of Environmental Management, Point Shapefile)

The following is excerpted from the metadata provided by IDEM, OLQ for the source shapefile IDEM_SUPERFUND.SHP:

"The Office of Land Quality Superfund program works with the U.S. Environmental Protection Agency (U.S. EPA) to clean up sites contaminated with hazardous waste that may require complex investigations, significant cleanup actions, and long-term attention. The program involves a multi-phase process that begins with an assessment to determine if contamination is present that may impact a community. Sites that are determined to be a problem are put on the National Priorities List (NPL). They continue through the Superfund process to determine what contamination exists, how far it may have spread, and what risk that contamination may pose. Then sites are cleaned up to reduce or eliminate risk to human health and the environment so they can be made available for beneficial reuse to the greatest extent possible. Some sites have been delisted from the NPL but are still subject to review and maintenance." Purpose: This data set was developed to provide accurate coordinate information for managed facilities and customers of the Indiana Department of Environmental Management.

The following is excerpted from the metadata provided by IDEM, OLQ for the source shapefile IDEM_SUPERFUND.SHP:

"This project is the first phase in the creation of a base locational data set to establish Geographic Information Systems as an integral part of data management for the Superfund program. Envrionmental Project Managers were trained in techniques and proper use of Global Positioning Systems. Trained staff then went into the field and collected GPS information at managed sites. This information was then brought back to the office, processed, and QA/QC'd before being deposited in a central archive." Supplemental_Information: This data set generally contains the location of access points to managed sites, along with a unique identifier for each location. Time_Period_of_Content: Time_Period_Information: Single_Date/Time: Calendar_Date: 20181019 Currentness_Reference: Publication date Status: Progress: In work Maintenance_and_Update_Frequency: Quarterly Spatial_Domain: Bounding_Coordinates: West_Bounding_Coordinate: -87.523572 East_Bounding_Coordinate: -85.053059 North_Bounding_Coordinate: 41.723690 South_Bounding_Coordinate: 38.677804 Keywords: Theme: Theme_Keyword_Thesaurus: Geography Network Keyword Thesaurus Theme_Keyword: environment Theme_Keyword: structure Theme: Theme_Keyword_Thesaurus: IGS Metadata Thesaurus Theme_Keyword: Indiana Geological and Water Survey (IGWS) Theme_Keyword: Indiana Department of Environmental Management (IDEM) Theme_Keyword: U.S. Environmental Protection Agency (U.S. EPA) Theme_Keyword: Office of Land Quality (OLQ) Theme_Keyword: Superfund Program Theme_Keyword: Superfund Theme_Keyword: Superfund National Priorities List (NPL) Theme_Keyword: Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA) Theme_Keyword: Resource Conservation and Recovery Act (RCRA) Theme_Keyword: global positioning system (GPS) Theme_Keyword: access point Theme_Keyword: managed site Theme_Keyword: regulated facility Theme_Keyword: contamination Theme_Keyword: water quality Theme_Keyword: hazard Theme_Keyword: hazardous waste Theme_Keyword: pollution Theme_Keyword: polluted site Theme_Keyword: manufacturing facility Theme_Keyword: processing plant Theme_Keyword: landfill Theme_Keyword: mining site Place: Place_Keyword_Thesaurus: IGS Metadata Thesaurus Place_Keyword: Indiana Place_Keyword: Adams County Place_Keyword: Bartholomew County Place_Keyword: Boone County Place_Keyword: Elkhart County Place_Keyword: Grant County Place_Keyword: Hancock County Place_Keyword: Howard County Place_Keyword: Jackson County Place_Keyword: Jefferson County Place_Keyword: Knox County Place_Keyword: Kosciusko County Place_Keyword: La Porte County Place_Keyword: Lake County Place_Keyword: Marion County Place_Keyword: Miami County Place_Keyword: Monroe County Place_Keyword: Montgomery County Place_Keyword: Owen County Place_Keyword: St Joseph County Place_Keyword: Tippecanoe County Place_Keyword: Vigo County Place_Keyword: Whitley County Access_Constraints: This file is available to anyone, but access may be contingent on written request, specific terms relevant to the agency or person making the request, and (or) current freedom of information statutes in the state of Indiana. Use_Constraints: DATA DISCLAIMER - This data set is provided by Indiana University, Indiana Geological and Water Survey, and contains data believed to be accurate however, a degree of error is inherent in all data. This product is distributed "AS-IS" without warranties of any kind, either expressed or implied, including but not limited to warranties of suitability of a particular purpose or use. No attempt has been made in either the designed format or production of these data to define the limits or jurisdiction of any federal, state, or local government. These data are intended for use only at the published scale or smaller and are for reference purposes only. They are not to be construed as a legal document or survey instrument. A detailed on-the-ground survey and historical analysis of a single site may differ from these data.

CREDIT - It is requested that the Superfund Program, Office of Land Quality, Indiana Department of Environmental Management be cited in any products generated from this data. The following source citation should be included: [SUPERFUND_IDEM_IN.SHP: Sites in Indiana on the IDEM Superfund Program List (Indiana Department of Environmental Management, Point Shapefile), digital compilation by IGWS, 20181019].

LIMITATION OF WARRANTIES AND LIABILITY - This product is provided "AS IS", without any other warranties or conditions, expressed or implied, including, but not limited to, warranties for product quality, or suitability to a particular purpose or use. The risk or liability resulting from the use of this product is assumed by the user. Indiana University, Indiana Geological and Water Survey shares no liability with product users indirect, incidental, special, or consequential damages whatsoever, including, but not limited to, loss of revenue or profit, lost or damaged data or other commercial or economic loss. Indiana University, Indiana Geological Survey is not responsible for claims by a third party. The maximum aggregate liability to the original purchaser shall not exceed the amount paid by you for the product.

Point_of_Contact: Contact_Information: Contact_Organization_Primary: Contact_Organization: Indiana Geological and Water Survey Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-855-7636 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 - 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Data_Set_Credit: Federal Cleanup, Superfund, & NRDA section, Office of Land Quality, IDEM

Native_Data_Set_Environment: Esri ArcGIS version 10.6 shapefile format, approximately 192 Kb, Microsoft Windows 7 Enterpris, Esri ArcCatalog 10.6

Data_Quality_Information: Attribute_Accuracy: Attribute_Accuracy_Report: This data set was provided by IDEM personnel and is assumed to be accurate.

The following is excerpted from the metadata provided by IDEM, OLQ for the source shapefile IDEM_SUPERFUND.SHP:

"All attributes created during the process were verified by displaying the lines in the database and verifying consistency. However, no formal tests were performed. Omissions or null values in certain fields is due to the fact that edits were made in the data dictionary (adding or deleting attribute information) as the project progressed, information was unknown or mistakenly left out, or the field with the ommission was not relative to the method used to collect the data. Therefore accuracy cannot be guaranteed or verified."

Logical_Consistency_Report: This data set was provided by IDEM personnel and is assumed to be accurate.

Completeness_Report: The following is excerpted from the metadata provided by IDEM, OLQ for the source shapefile IDEM_SUPERFUND.SHP:

"Data were collected by the Federal Cleanup, Superfund, NRDA section within the Office of Land Quality, the Indiana Department of Environmental Management. This dataset is incomplete and a work in progress, as sites are GPS'd as they are inspected. This dataset contains information that represents what had been recorded, processed, and archived by IDEM personnel at a time previous to publication. However the data set may be incomplete and/or inaccurate due to the ever-changing status of managed facilities and sites, and due to the data collection and processing efforts of IDEM staff. It is an ever-changing work in progress. The Superfund section was also responsible for collecting attribute information for each location. The data has been QA/QC'd for consistency but no formal tests were performed on accuracy. Therefore accuracy cannot be guaranteed or verified. Omissions or null values in certain fields is due to the fact that edits were made in the data dictionary (adding or deleting attribute information) as the project progressed, information was unknown or mistakenly left out, or the field with the ommission was not relative to the method used to collect the data."

Positional_Accuracy: Horizontal_Positional_Accuracy: Horizontal_Positional_Accuracy_Report: The following is excerpted from the metadata provided by IDEM, OLQ for the source shapefile IDEM_SUPERFUND.SHP:

"The data were collected with a GPS GIS-mapping system. The accuracy of the coordinates should be from 1-5 meters, depending upon the type of GPS instrument used, the collection environment (ie., multipath, SNR, and PDOP), and the number of positions logged for each location. However, this accuracy cannot be guaranteed or verified. Each GPS unit should have been configured within the specifications of the manufacturer. However, if necessary, the field personnel would configure the unit outside of specifications if environmental conditions warranted. Accuracy was checked by logging both Maximum PDOP and the standard deviations of the positional average of each location collected. If maximum PDOP value was > 6, the value for the "In_specs" field was input as "NO". If the standard deviation was > 8, the corrected GPS file was analyzed for signs of multipath and/or outliers, and edited accordingly. It was then re-exported to the archive. If the data set was uneditable it was still left in the archive. The "In-specs" field was changed to "No" and the location could have an accuracy > 5 meters.

"If the environmental conditions of the collection session fell within the acceptable ranges for data collection as defined by the technical specifications of the instrument used and specific instrument configuration, then the accuracy of the collected coordinates should be within those values as given by the manufacturer. The GeoExplorer Unit has an accuracy range of 2 to 5 meters (post-processed), the GeoExplorer 3 and 3c a range of 1 to 5 meters (post-processed), and the Pro XR has a range of .50 cm - 1m differential accuracy to real-time differential correction.

"If the environmental conditions and/or technical configurations were not met, then the values could exceed those given by the manufacturer."

Vertical_Positional_Accuracy: Vertical_Positional_Accuracy_Report: The following is excerpted from the metadata provided by IDEM, OLQ for the source shapefile IDEM_SUPERFUND.SHP:

"The vertical accuracy for GPS data collection can be two to three times less accurate than horizontal accuracy. The vertical accuracy for these locations could have up to 15 meters of error. However, this accuracy cannot be guaranteed or verified. Height above Ellipsoid values have been recorded, but it is strongly suggested that the values not be used for any analysis.

Process_Step: Process_Description: IGS personnel received an ESRI shapefile named SUPERFUND from IDEM personnel on August 16, 2002. SUPERFUND was loaded into ESRI ArcView 3.3 and the following columns were deleted from the associated attribute table: LONGITUDE, LATITUDE, HAE, NORTHING, EASTING, METHOD, IN_SPECS, REG_PROG, C_INITIALS, GENERATOR, MAX_PDOP, CORR_TYPE, RCVR_TYPE, GPS_TIME, DATAFILE, UNFILT_POS and STD_DEV. The shapefile was also visually checked to insure that all data points provided actually fell within the accepted IGS state boundary. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN. It should also be noted that portions of the associated metadata provided by IDEM for SUPERFUND was extracted and included in this metadata file. Source_Used_Citation_Abbreviation: SUPERFUND.SHP Process_Date: 20021219 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated shapefile (and metadata), in the form of an ESRI shapefile, named SUPERFUND from IDEM personnel (Shane Moore) on January 14, 2003. The shapefile was visually checked to insure that all data points provided actually fell within the accepted IGS state boundary. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN to follow internal naming conventions. Source_Used_Citation_Abbreviation: SUPERFUND.SHP Process_Date: 20030114 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated shapefile (and metadata), in the form of an ESRI shapefile, named SUPERFUND from IDEM personnel (Shane Moore) on June 3, 2004. The shapefile was visually checked to insure that all data points provided actually fell within the accepted IGS state boundary. The shapefile was then edited by removing the following fields from the associated attribute table: HORIZONTAL, NORTHING, EASTING, STANDARD_D, LOCATION_A, POSTAL_COD, and COUNTY_NAM. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN to follow internal naming conventions. Source_Used_Citation_Abbreviation: SUPERFUND.SHP Process_Date: 20040603 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated shapefile (and metadata), in the form of an ESRI shapefile, named SUPERFUND from IDEM personnel (Shane Moore) on January 4, 2005. The shapefile was visually checked to insure that all data points provided actually fell within the accepted IGS state boundary. The shapefile was then edited by removing the following fields from the associated attribute table: HORIZONTAL, NORTHING, EASTING, STANDARD_D, LOCATION_A, POSTAL_COD, and COUNTY_NAM. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN to follow internal naming conventions. Source_Used_Citation_Abbreviation: SUPERFUND.SHP Process_Date: 20050104 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated ESRI geodatabase (and metadata) named "OLQ_GPS_DATA_IGS.MDB" from IDEM personnel (Shane Moore) on April 25, 2005. OLQ_GPS_DATA_IGS.MDB was loaded into ESRI ArcMap 9.0 and the subset of data containing Superfund site locations was exported to an ESRI shapefile format. The shapefile was visually checked to insure that all data points provided actually fell within the accepted IGS state boundary. The shapefile was then edited by removing the following fields from the associated attribute table: HORIZONTAL, NORTHING, EASTING, STANDARD_D, LOCATION_A, POSTAL_COD and COUNTY_NAM. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN.SHP to follow internal naming conventions. Source_Used_Citation_Abbreviation: OLQ_GPS_DATA_IGS.MDB Process_Date: 20050425 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated ESRI geodatabase (and metadata) named "OLQ IndianaMap Export-06012009.gdb" from IDEM personnel (Shane Moore) on June 4, 2009. "OLQ IndianaMap Export-06012009.gdb" was loaded into ESRI ArcMap 9.3.1 and the subset of data containing Superfund site locations were examined and exported as an ESRI shapefile. The shapefile was then edited by removing the following fields from the associated attribute table: HORIZONTAL, NORTHING, EASTING, STANDARD_D, LOCATION_A, POSTAL_COD and COUNTY_NAM. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN.SHP to follow internal naming conventions. Source_Used_Citation_Abbreviation: OLQ IndianaMap Export-06012009.gdb Process_Date: 20090604 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated ESRI geodatabase (and metadata) named "OLQ IndianaMap Export-04162010.gdb" from IDEM personnel (Shane Moore) on April 16, 2010. "OLQ IndianaMap Export-04162010.gdb" was loaded into ESRI ArcMap 9.3.1 and the subset of data containing Superfund site locations were examined and exported as an ESRI shapefile.

No changes in this dataset were apparent from the last update date on June 4, 2009 so only the metadata was edited to reflect this information. No changes to the SUPERFUND_IDEM_IN.SHP were made. Source_Used_Citation_Abbreviation: OLQ IndianaMap Export-04162010.gdb Process_Date: 20100416 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated ESRI geodatabase (and metadata) named "IndianaMapUpdate_June2013.gdb" from IDEM personnel (Shane Moore) on June 25, 2013. "IndianaMapUpdate_June2013.gdb" was loaded into ESRI ArcMap 10.1 and the subset of data containing Superfund site locations were examined and exported as an ESRI shapefile. The shapefile was then edited by removing the following fields from the associated attribute table: AGENCY_INT, SUB_PROGRA, LONGITUDE, LATITUDE, METHOD_DES, COLLECTOR_, COLLECTOR1, ACCURACY, ACCURACY_U, GPS_RECEIV, SOURCE_MAP, EASTING, and NORTHING. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN.SHP to follow internal naming conventions. Source_Used_Citation_Abbreviation: IndianaMapUpdate_June2013.gdb Process_Date: 20130625 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGS personnel received an updated Esri geodatabase (and metadata) named "IndianaMapUpdate_February2015.gdb" from IDEM personnel (Shane Moore) on February 25, 2015. "IndianaMapUpdate_February2015.gdb" was loaded into Esri ArcMap 10.3 and the subset of data containing Superfund site locations were examined and exported as an Esri shapefile. The shapefile was then edited by removing the following fields from the associated attribute table: AGENCY_INT, SUB_PROGRA, LONGITUDE, LATITUDE, METHOD_DES, COLLECTOR_, COLLECTOR1, ACCURACY, ACCURACY_U, GPS_RECEIV, SOURCE_MAP, EASTING, and NORTHING. IGS personnel then saved the edited shapefile as SUPERFUND_IDEM_IN.SHP to follow internal naming conventions. Source_Used_Citation_Abbreviation: IndianaMapUpdate_February2015.gdb Process_Date: 20150225 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: IGWS personnel received an Esri point shapefile named "IDEM_SUPERFUND.SHP" from IDEM personnel (Miranda Hancock) on October 19, 2018. IDEM_SUPERFUND.SHP was re-projected using ESRI ArcCatalog 10.6.0.8321 from geographic coordinates (World WGS 1984) to projected coordinates (UTM Zone 16 NAD83), and then renamed "SUPERFUND_IDEM_IN.SHP" to conform to internal naming conventions of the IGWS.

SUPERFUND_IDEM_IN.SHP was then loaded into Esri ArcMap, along with to the most recent version of the previously published data (20150225) for superfund sites. The layers were visually compared to record any significant changes to the structure of the attribute table, fields, or values, as well as to the changes in the total number of records provided (20150225 contained 83 locations, 20181019 contains 83 locations). The shapefile was then edited by removing the following fields from the associated attribute table: AGENCY_INT, SUB_PROGRA, METHOD_DES, COLLECTOR_, COLLECTOR1, ACCURACY, ACCURACY_U, GPS_RECEIV, and SOURCE_MAP. Source_Used_Citation_Abbreviation: IDEM_SUPERFUND.SHP Process_Date: 20181019 Source_Produced_Citation_Abbreviation: SUPERFUND_IDEM_IN.SHP Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological and Water Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Process_Step: Process_Description: This metadata file was pre-parsed and parsed using CNS (Chew and Spit, v. 2.6.1) and MP (Metadata Parser, v. 2.7.1) software written by Peter N. Schweitzer (U.S. Geological Survey). The errors generated by MP were all addressed and corrected, except that no values were assigned to "Abscissa_Resolution" and "Ordinate_Resolution." Process_Date: 20181227 Process_Contact: Contact_Information: Contact_Person_Primary: Contact_Organization: Indiana Geological and Water Survey Contact_Person: Chris Dintaman Contact_Position: Geologist, GIS Specialist Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-856-5654 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays

Spatial_Data_Organization_Information: Indirect_Spatial_Reference: Indiana Direct_Spatial_Reference_Method: Point Point_and_Vector_Object_Information: SDTS_Terms_Description: SDTS_Point_and_Vector_Object_Type: Point Point_and_Vector_Object_Count: 83

Spatial_Reference_Information: Horizontal_Coordinate_System_Definition: Planar: Grid_Coordinate_System: Grid_Coordinate_System_Name: Universal Transverse Mercator Universal_Transverse_Mercator: UTM_Zone_Number: 16 Transverse_Mercator: Scale_Factor_at_Central_Meridian: 0.999600 Longitude_of_Central_Meridian: -87.000000 Latitude_of_Projection_Origin: 0.000000 False_Easting: 500000.000000 False_Northing: 0.000000 Planar_Coordinate_Information: Planar_Coordinate_Encoding_Method: Row and column Coordinate_Representation: Abscissa_Resolution: Ordinate_Resolution: Planar_Distance_Units: Meters Geodetic_Model: Horizontal_Datum_Name: North American Datum of 1983 Ellipsoid_Name: GRS 80 Semi-major_Axis: 6378137.0000000 Denominator_of_Flattening_Ratio: 298.26

Entity_and_Attribute_Information: Detailed_Description: Entity_Type: Entity_Type_Label: SUPERFUND_IDEM_IN.DBF Entity_Type_Definition: Shapefile Attribute Table Entity_Type_Definition_Source: None Attribute: Attribute_Label: FID Attribute_Definition: Internal feature number Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Sequential unique whole numbers that are automatically generated Attribute: Attribute_Label: Shape Attribute_Definition: Feature geometry Attribute_Definition_Source: ESRI Attribute_Domain_Values: Unrepresentable_Domain: Coordinates defining the features Attribute: Attribute_Label: REGULATORY Attribute_Definition: Unique code to idenify the entity Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Unrepresentable_Domain: Character field Attribute: Attribute_Label: AGENCY_I_1 Attribute_Definition: Source Name Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Unrepresentable_Domain: Character field Attribute: Attribute_Label: PROGRAM Attribute_Definition: IDEMs managing program name (SF = Superfund sites) Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Unrepresentable_Domain: Character field Attribute: Attribute_Label: REFERENCE_ Attribute_Definition: Describes what is being located at the site Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: Access Point Enumerated_Domain_Value_Definition: A gate, front door, or entrance that provides access to a managed site from a road or highway Enumerated_Domain_Value_Definition_Source: IDEM MAD Codes Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: Building Enumerated_Domain_Value_Definition: A building within an areal boundary Enumerated_Domain_Value_Definition_Source: IDEM MAD Codes Attribute_Domain_Values: Enumerated_Domain: Enumerated_Domain_Value: Center Enumerated_Domain_Value_Definition: A point of approximate center within an areal boundary Enumerated_Domain_Value_Definition_Source: IDEM MAD Codes Attribute: Attribute_Label: PHYSICAL_A Attribute_Definition: The address of site Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Unrepresentable_Domain: Character field Attribute: Attribute_Label: MUNICIPALI Attribute_Definition: City or town name where the site is located Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Unrepresentable_Domain: Character field Attribute: Attribute_Label: ZIP_CODE Attribute_Definition: The zip code of site Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Unrepresentable_Domain: Character field Attribute: Attribute_Label: DATA_COLLE Attribute_Definition: The date that GPS data were collected by IDEM personnel Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 6/22/2000 Range_Domain_Maximum: 2/9/2011 Attribute_Units_of_Measure: Calendar date Attribute: Attribute_Label: LONGITUDE Attribute_Definition: Longitude coordinate value for access point location (WGS 1984) Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: -87.567494 Range_Domain_Maximum: -84.828431 Attribute_Units_of_Measure: Decimal degrees Attribute: Attribute_Label: LATITUDE Attribute_Definition: Latitude coordinate value for access point location (WGS 1984) Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 37.980966 Range_Domain_Maximum: 41.723628 Attribute_Units_of_Measure: Decimal degrees Attribute: Attribute_Label: EASTING Attribute_Definition: Longitude coordinate value for access point location (UTM Zone 16, NAD83) Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 450162.482211 Range_Domain_Maximum: 688373.630082 Attribute_Units_of_Measure: Meters Attribute: Attribute_Label: Northing Attribute_Definition: Latitude coordinate value for access point location (UTM Zone 16, NAD83) Attribute_Definition_Source: Office of Land Quality, Indiana Department of Environmental Management Attribute_Domain_Values: Range_Domain: Range_Domain_Minimum: 4203855.0349 Range_Domain_Maximum: 4619098.60993 Attribute_Units_of_Measure: Meters

Distribution_Information: Distributor: Contact_Information: Contact_Organization_Primary: Contact_Organization: Indiana Geological and Water Survey Contact_Person: Publication Sales Contact_Position: Clerk Contact_Address: Address_Type: Mailing and physical address Address: 611 North Walnut Grove Avenue City: Bloomington State_or_Province: Indiana Postal_Code: 47405-2208 Country: USA Contact_Voice_Telephone: 812-855-7636 Contact_Facsimile_Telephone: 812-855-2862 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: 0800 to 1700 Eastern Standard Time Contact_Instructions: Monday through Friday, except holidays Resource_Description: Downloadable data

Distribution_Liability: DATA DISCLAIMER - This data set is provided by Indiana University, Indiana Geological and Water Survey, and contains data believed to be accurate however, a degree of error is inherent in all data. This product is distributed "AS-IS" without warranties of any kind, either expressed or implied, including but not limited to warranties of suitability of a particular purpose or use. No attempt has been made in either the designed format or production of these data to define the limits or jurisdiction of any federal, state, or local government. These data are intended for use only at the published scale or smaller and are for reference purposes only. They are not to be construed as a legal document or survey instrument. A detailed on-the-ground survey and historical analysis of a single site may differ from these data.

CREDIT - It is requested that the Superfund Program, Office of Land Quality, Indiana Department of Environmental Management be cited in any products generated from this data. The following source citation should be included: [SUPERFUND_IDEM_IN.SHP: Sites in Indiana on the IDEM Superfund Program List (Indiana Department of Environmental Management, Point Shapefile), digital compilation by IGWS, 20181019].

LIMITATION OF WARRANTIES AND LIABILITY - This product is provided "AS IS", without any other warranties or conditions, expressed or implied, including, but not limited to, warranties for product quality, or suitability to a particular purpose or use. The risk or liability resulting from the use of this product is assumed by the user. Indiana University, Indiana Geological and Water Survey shares no liability with product users indirect, incidental, special, or consequential damages whatsoever, including, but not limited to, loss of revenue or profit, lost or damaged data or other commercial or economic loss. Indiana University, Indiana Geological Survey is not responsible for claims by a third party. The maximum aggregate liability to the original purchaser shall not exceed the amount paid by you for the product.

Distribution_Information: Distributor: Contact_Information: Contact_Organization_Primary: Contact_Organization: Indiana Department of Environmental Management Contact_Person: Miranda Hancock Contact_Position: GIS Coordinator (Information Services) Contact_Address: Address_Type: Mailing and physical address Address: 100 North Senate Avenue City: Indianapolis State_or_Province: Indiana Postal_Code: 46206-6015 Country: USA Contact_Voice_Telephone: 317-232-8742 Contact_Facsimile_Telephone: 317-233-3403 Contact_Electronic_Mail_Address: [email protected] Hours_of_Service: M-F, 8:00am-5:00pm, Eastern Standard Time Contact_Instructions: For inquiries, please e-mail

Resource_Description: Superfund Sites Shapefile Distribution_Liability: The following is excerpted from the metadata provided by IDEM, OLQ for the source shapefile IDEM_SUPERFUND.SHP:

THE INDIANA DEPARTMENT OF ENVIRONMENTAL MANAGEMENT (IDEM), ITS EMPLOYEES, SUCCESSORS OR ASSIGNS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE COMPLETENESS, SUITABILITY, RELIABILITY, AVAILABILITY AND ACCURACY OF DATA, SOFTWARE, INFORMATION OR SERVICES PROVIDED.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, ANY INFORMATION RETRIEVED FROM OR DELIVERED TO AN INDIVIDUAL OR ENTITY THROUGH THE AUSPICES OF IDEM ARE PROVIDED "AS IS" AND INCLUDES ALL FAULTS WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND. THE RECIPIENT, OF THE DATA, SOFTWARE, INFORMATION OR SERVICES, ACKNOWLEDGES AND AGREES THAT IT HAS RECEIVED ADEQUATE NOTICE THAT USE OF THE DATA, SOFTWARE, INFORMATION OR SERVICES IS AT RECIPIENTS OWN RISK.

IDEM AND OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THE AFOREMENTIONED MATERIAL, INCLUDING WARRANTIES OF MERCHANTABILITY, TITLE, NONINFRINGEMENT, FITNESS FOR A PARTICULAR PURPOSE, LACK OF VIRUSES, ACCURACY OR COMPLETENESS OF RESPONSES, RESULTS, LACK OF NEGLIGENCE OR LACK OF WORKMANLIKE EFFORT, QUIET ENJOYMENT, QUIET POSSESSION, AND CORRESPONDENCE TO DESCRIPTION. FURTHER THE ABOVE LIST OF DISCLAIMED WARRANTIES IS NOT EXHAUSTIVE AS ANY AND ALL WARRANTIES AND CONDITIONS ARE DISCLAIMED. THE ENTIRE RISK ARISING OUT OF THE USE OF OR PERFORMANCE OF THE DATA, SOFTWARE, INFORMATION OR SERVICES IS BORNE BY THE RECIPIENT.

EXCLUSION OF INCIDENTAL, CONSEQUENTIAL AND CERTAIN OTHER DAMAGES.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL IDEM OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR: LOSS OF PROFITS, LOSS OF CONFIDENTIAL OR OTHER INFORMATION, BUSINESS INTERRUPTION, PERSONAL INJURY, LOSS OF PRIVACY, FAILURE TO MEET ANY DUTY (INCLUDING GOOD FAITH AND REASONABLE CARE), NEGLIGENCE, AND ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER, ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OR INABILITY TO USE, THE DATA, SOFTWARE, INFORMATION OR SERVICES, EVEN IF THE RECIPIENT IS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. RECIPIENT'S SOLE REMEDY IS TO DISCONTINUE THE USE OF THE DATA, SOFTWARE, INFORMATION OR SERVICES."

## Layer does not match imagery by 400 meters..

I have been looking for answers, from coordinate systems issues to projection issues but have not found a solution to this sticky one yet. As you can see below, my river SHP does not match the river on the satellite imagery. only by. 400 meters. Coordinate systems and projections are the same (I projected the river shapefile (was WGS84UTMzone47N) to the projection of the imagery. Would anyone have a clue what the problem is?

by NeilAyres

This sort of shift is caused by an incorrect datum (change in the underlying ellipsoidal model).

I took your mainrivers shapefile, I see it is of the Mekong river in Cambodia.

Yes, it's coordinate system is defined as UTM 47N and based on the WGS84 datum. However, if you assume that WGS84 is not the original datum for this data (depends on the source of these river polys, old carto sheets perhaps).

I looked up at ASPRS Clifford Mugnier Grids & Datums page and also at EPSG.org. There are several suggestions as to the original classical datums used by the French authorities in colonial days. One of which is India1960. (Don't know why they would have used this).

So, I copied the shapefile, gave it a new name, and then redefined the coord sys, changing the GCS to India 1960.

So the blue is the original, the green te new one, and I have applied one of the available transforms between India1960 & WGS84.

The base map in National Geographic (good enough in this case).

You can see that the green one is much closer to the basemap image. The difference here between old and new is

The fit is not exact (I wouldn't expect it to be), because we do not know on which datum this data was originally based.

## Define projection changes position of raster layer

I use define projection on a raster layer that has the spatial reference system User_defined equidistant_Cylindrical and the datum user_defined, and change it into either equidistant_culindrical (Sphere) or equidistant cylindrical (world).

I try to do it into both because I am not sure which of them is the correct one. My thought was then to convert into WGS_1984 afterwards and see which fits best.

However, when I do the define projection, the whole raster drastically changes position. How can this be? Isn't define projection just used to define the projection system, not actually changing the position or drawing. This is at least how it has normally worked for me.

The reason why I am doing this is because I want the data in WGS_1984. Any help on how I could do this is also needed.

I would very much appreciate any help. Thank you very much!

by DanPatterson_Re tired

Define Projection is only used when a file has an unknown projection or. as in your case. when it has been define incorrectly and has to be reverted back to the original projection

I didn't think define projection would move anything either but the project tool would if you had a projection assigned. Did you accidentally use the wrong one, maybe?

As can be seen , it changes a lot but the two defined rasters are quite similar (not the same but quite similar)

Dan, I am not sure what you mean by defined incorrecty. I mean I cant know whether it is defined incorrectly just because it is user defined?

Wes, As can be seen from the drawing both of them changes the position a lot.

Xander, the difference in my case is only about 10 km difference.

by DanPatterson_Re tired

Your first sentence. you applied a projection to a data set to see which one was best or worked best. Get the projection information from the source if it is known. If it is a matter that only one of the two is correct, you will quickly find out. as long as you have ruled out the possibility that neither are correct.

Thank you for this. The thing is that both seems to be from. When I convert both the defined rasters to WGS 1984 with "project raster" , the almost dont change - they are still as heavily distorted. Aboth 10 km different as mentioned above, but both many 1000 km off other WGS 1984 rasters.

by DanPatterson_Re tired

Is there a chance that you are doing these operations in the same data frame as other data? I would suggest you create two new data frames and place each file into its own data frame with no other data. Then . for each file, in its own data frame. you right-click on the layer, go to properties and determine the extent values. These will not change regardless of what you have done to the file in terms of defining a projection. Do the extents look reasonable? A file with a geographic coordinate system ( like a GCS WGS84) will only have values in the range -180 to 180 EW and -90 to 90 NS. If they are big numbers then you have projected data and the range in values will give you what type of projection it was or should be in. Ideally, both files should have the same extent if indeed they covered the same extent. If they have the same extent and they are defined differently, then one or both have been improperly defined when using the Define Projection Tool.

Now on to projection. When you use the Project Tool, always put the result into its own dataframe since a file that is projected will project-on-the-fly to try and match the projection of the dataframe. and as you have noted, when the file was defined wrong, then projected, it flies off to somewhere you don't want it to be.

The whole process of adding data to a data frame since ArcMape is to try to "be helpful". In the "old days" you would get the warning that things didn't match and sure enough, the files would fly off into their corners spatially separated because the projection files were wrong, undefined or mismatch. In order to fix this in the "helpful" environment, you need to examine their properties. understand their possible extent values for a given coordinate system/projection and then act accordingly.

So in summary, I have no clue what the real coordinate systems of the input files were, but IF they were defined by some other source and they were redefined correctly. set them back and ensure that they are correct. Once they are in a know, verified coordinate system. you can proceed to Projecting the data to a different coordinate system. Then. and only then. do I introduce other data into the dataframe. If all the files play nice. then they should overlap or abut perfectly.

## Ways to speed up drawing of layers in ArcMap?

I'm working with a layer of highways for the state of NC, but every time I change something, from altering symbol colors to panning to a different part of the state, it redraws. Which would be fine except for the fact that when it redraws, it takes forever. Okay maybe not forever, but it takes at least 2 minutes, sometimes 10, to redraw it. every time. I've been playing with different symbology for this and other layers to see what looks best (what I should include, exclude, etc.) but I've spent roughly an hour on this and have only made a few very minor changes. It's just annoying and I currently feel like the last part of my day has been wasted waiting on ArcGIS. Any recommendations to speed it up? I have to go through this full process another 60 times and Iɽ prefer not to spend 3 hours per map just waiting for it to draw stupid highways. (And no, I can't just take the highways layer out. I've already asked.) Iɽ much appreciate any advice.

TLDR Highways layer takes too long to draw and has to be redrawn a lot. Need help to speed it up.

## Why is the "Add Basemap" button not available? Trying to add a basemap of the United States.

Just a tip for all you basemap users. It's actually faster to setup an arcgis online gis server connection in arccatalog and add the basemap through that than it is adding it from the add data dropdown menu.

On a sidenote I've noticed a lot of government agencies provide server connections to their data - it's been a nice alternative to hoarding shapefiles.

Any sources for how to do this?

I believe this can also happen when you don’t have a coordinate system set?

I think internet is unavailable.

Ok. I’m connected that time maybe it’s a matter of weak connection.

You could also try closing program, opening a new window and adding the base map before adding the other layers. This has worked for me in the past, tho I’m not sure why.