Bedrock geologic map of Monroe County (Indiana)

[ericjohannes]

Name:

Hasenmueller, W. A., Estell, C. M., Keith, B., and Thompson, T. A., 2009, Bedrock geologic map of Monroe County, Indiana: Indiana Geological Survey Miscellaneous Map 73, scale 1:48,000

Source URL:

https://iu.box.com/s/qy1ks2jlmxwsfo3kjjylqgknz4rwlj9o

Updated data: https://iu.box.com/s/053oa67y57xlr7txh34wwxzzsi060xap

Estimated scale:

large

Folder name:

Dataset names:

BedrockGeology_MonroeCo.shp

Updated: LeesvilleAnti.shp Faults_MonroeCo.shp

Number of bedrock polygons: 31

Lithology field:

Time field:

GeologicAg

Stratigraphy name field:

MapUnit

Description field:

UnitDescri

Comments field:

Comments:

Updated: LeesvilleAnti.shp - name of the anticline is "Leesville Anticline" Faults_MonroeCo.shp - fault name is in "Fault" field

Todo:

• [ ] Insert new source record
• [ ] Add data to database
• [ ] Process and add to homogenized tables
• [ ] Process and import lines
• [ ] Process and import points
• [ ] Match
• [ ] Roll tiles

[aazaff]

@ericjohannes, This looks pretty good.

1. Is there any line or point work that goes with this map?
2. The age given for some of these is Valmeyeran. That is not a recognized geologic age name. I googled it and it seems to be equivalent to the Visean, but can you please ask one of your geologists to confirm?

[aazaff]

@garymotz, @ericjohannes

Btw, here is a list of all recognized stratigraphic intervals.

Although Macrostrat can theoretically do the work of converting informal intervals to a recognized interval, it would be best if Indiana did this step.

[aazaff]

Btw, I was wrong... Valmeyeran is recognized... so no problem.

[ericjohannes]

Glad the age name wasn't a problem in the end. We're looking into lines and points

[ericjohannes]

We added lines for faults and an anticline. I added a link to the updated data and information about it in the issue

[aazaff]

Please take a look @cvavrus

[cvavrus]

@ericjohannes the unitdescri column appears to be cut short for some of the units, do you have another document that includes the full description?

[cvavrus]

@ericjohannes is this the correct map? https://igws.indiana.edu/bookstore/details.cfm?Pub_Num=MM73

[ericjohannes]

@cambro that is the correct map Here is a document with the full unit descriptions https://iu.box.com/s/ru993wm8o4fn90hbzt427i9k7k7hqvss

[cvavrus]

Assuming that was the right map:

Folder name: in_monroe

Suggested inserts:

INSERT INTO maps.large (orig_id,source_id,name,age,descrip,strat_name,t_interval,b_interval,geom) 
SELECT gid,1,mapunit,geologicag,descrip,strat_name,late_id,early_id,ST_MakeValid(geom) FROM sources.in_monroe where geom is not null;

INSERT INTO lines.large (orig_id,source_id,descrip,name,new_type,geom) 
SELECT gid,1,fault,name,new_type,ST_MakeValid(geom) FROM sources.in_monroe_lines where new_type is not null and geom is not null;

[aazaff]

@ericjohannes, just as an FYI for future reference: ESRI Shapefile format has hard-coded size limits - 10 characters for field names, 245 characters for cell values, and 2 GB for file size. The 245 character limit is the biggest problem from Macrostrat's perspective, so make sure that any maps you submit as Shapefiles are not losing text. You can always submit as a different (better) file format if you see that your data is being truncated.

@cvavrus, thanks for stepping up and doing additional research. In the case of these maps submitted by the Indiana survey - i.e, issues created by @ericjohannes or @garymotz - the goal is to have them do all the actual work. So if you see something wrong before you can queue it up for ingestion, just tell them what to do. The goal is to have them working in parallel with you, not to add to your existing workload. If you have specific questions, feel free to reach out to me via telegram. Shanan can give you my contact info.

[cvavrus]

@aazaff oops! My mistake, thank you for letting me know.

[aazaff]

@cvavrus No problem... we are just figuring all of this out as we go.

[ericjohannes]

@aazaff thanks, we'll try to use gdbs if that's better, and thanks @cvavrus for looking into the unit descriptions

[aazaff]

@cvavrus Can this one be assigned to @cambro now?

[cvavrus]

yes, it should be good to go