Skip to main content
Solved

AGOL content into local shapefiles - use _name as folder names


pinkopo
Contributor
Forum|alt.badge.img+5

Hi guys

im trying to craete a workbench to backup my agol group content into local shapefiles.

ideally i want to use _name (feature service name) as folder names so web layers (using fme_feature_type as dynamic shapefile name) goes into each folders by their service name.

 

however, for some reason the fanout option couldnt work. Also tried to create attribtue with the output file path then use it as destination esri shapefile folder on the writter - this solution doesnt work neither.

 

wondering if anyone know a good practice for this?

 

Thanks!

Best answer by virtualcitymatt

pinkopo wrote:

Thanks Matt.

using feature writer it did successfully create the folders based on service name but somehow only schema went into these folders as shapefiles (named creator).. all other shapefiles are still get written on the higher level folder..

 

 image 

Definitely interesting here - it's hard to say what's going on here without looking at the attributes and where they're coming from.

 

One thing which you might want to make sure is that the schema and data features both have an attribute called _name as this is deciding where the data should be written to. You might need to change the attribute merge mode in the FeatureReader to have merge attributes instead of just using those from the restul. I see that the ArgGIS connection also produces a _name attribute? I assume it's the same?

 

 

View original
Did this help you find an answer to your question?

4 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+35

You might have more luck using the FeatureWriter instead of the Shapefile writer itself. Personally I find it a little easier to configure for these kinds of workflows.

 

something like this:

 

image 

If this doesn't work then you might need to explain more about specifically what isn't working here


pinkopo
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • July 7, 2023
virtualcitymatt wrote:

You might have more luck using the FeatureWriter instead of the Shapefile writer itself. Personally I find it a little easier to configure for these kinds of workflows.

 

something like this:

 

image 

If this doesn't work then you might need to explain more about specifically what isn't working here

Thanks Matt.

using feature writer it did successfully create the folders based on service name but somehow only schema went into these folders as shapefiles (named creator).. all other shapefiles are still get written on the higher level folder..

 

 image 


virtualcitymatt
Celebrity
Forum|alt.badge.img+35
pinkopo wrote:

Thanks Matt.

using feature writer it did successfully create the folders based on service name but somehow only schema went into these folders as shapefiles (named creator).. all other shapefiles are still get written on the higher level folder..

 

 image 

Definitely interesting here - it's hard to say what's going on here without looking at the attributes and where they're coming from.

 

One thing which you might want to make sure is that the schema and data features both have an attribute called _name as this is deciding where the data should be written to. You might need to change the attribute merge mode in the FeatureReader to have merge attributes instead of just using those from the restul. I see that the ArgGIS connection also produces a _name attribute? I assume it's the same?

 

 


pinkopo
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • July 11, 2023
pinkopo wrote:

Thanks Matt.

using feature writer it did successfully create the folders based on service name but somehow only schema went into these folders as shapefiles (named creator).. all other shapefiles are still get written on the higher level folder..

 

 image 

Thanks Matt by changing the attribute merge mode it worked`` wohoooo😁


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings